Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feat: Introduce eth_getTransactionBySenderAndNonce and additional protection mechanisms for cross chain transfers & reorgs #175

Open
sambacha opened this issue Aug 21, 2023 · 3 comments
Assignees
Labels
bug Something isn't working Cross-Chain / LayerZero Liveness / Finality / and other related issues specific to cross chain msging

Comments

@sambacha
Copy link
Contributor

New RPC Methods and Protection Mechanisms for Lz Transfers

We need to ensure that the DEST and SOURCE chain do not have differing views of a users state due to chain reorgs or liveness failures, etc.

  • add a min. time lock regardless of chain
  • support rpc method to assist in state verification for front end
  • more radical solutions (not for RC v1.0)

### eth_getTransactionBySenderAndNonce

Consider this use case.

We journal everything we do. If the system dies we recover the state from that journal and move on. You need to re sync your local state with the chain first. That may mean a tx having been replaced. You can get the new tx, you can only try to fetch the old one and you receive a null.

With  `eth_getTransactionBySenderAndNonce` you just check which tx is using your nonce, if any.

@sambacha sambacha added bug Something isn't working Cross-Chain / LayerZero Liveness / Finality / and other related issues specific to cross chain msging labels Aug 21, 2023
@sambacha
Copy link
Contributor Author

@ControlCplusControlV
Copy link
Contributor

L0 removed and reverted in

@sambacha
Copy link
Contributor Author

The proposed EIP spec is here: https://github.com/manifoldfinance/eip-proposal-rpc/blob/master/eth_getTransactionBySenderAndNonce.md

Just need to submit it now that the EIP repo has been split

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Cross-Chain / LayerZero Liveness / Finality / and other related issues specific to cross chain msging
Projects
None yet
Development

No branches or pull requests

2 participants