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

[Feature Request]: Allow user to set account sequence #3628

Open
a26nine opened this issue Aug 6, 2024 · 0 comments
Open

[Feature Request]: Allow user to set account sequence #3628

a26nine opened this issue Aug 6, 2024 · 0 comments
Labels
enhancement New feature or request external Issues created by non node team members

Comments

@a26nine
Copy link

a26nine commented Aug 6, 2024

Implementation ideas

Request to reopen #3164.

Rollup node is unable to post blobs anymore due to the incorrect account sequence error.

Semantic version: 0.14.1
Commit: 6549873516889aebcb787c4e9f2ae3b3258c386a
Build Date: 2024-07-24T10:43:02Z
System version: amd64/linux
Golang version: go1.22.5

Details

  • Running a rollup node with rollkit utilising local light node and local/public RPC
  • Due to some reason the blob submission fails with context deadline exceeded: DA layer submission failed error="failed to submit blocks: RPC client error: sendRequest failed: Post \"http://localhost:56658/\": context deadline exceeded" attempt=0 module=BlockManager
  • On the next try, the rollup node increments the sequence without verifying if the previous blob tx was submitted or not Account sequence increments even when the blob is not submitted successfully rollkit/rollkit#1787
  • If there are retries, the gap between actual and expected account sequence starts increasing (Sometimes the gap becomes as high as 30 sequences)

Also discussed in https://discord.com/channels/638338779505229824/1269171673467457618

Troubleshooting

  • Restarting rollup node daemon
  • Restarting light node
  • Restarting/Changing local/public RPC
  • Resyncing light node
  • Resyncing RPC

... doesn't fix it

Resolution

To resolve the issue, the account sequence has to be manually adjusted to cover the gap between actual and expected values. For that, we have to use celeastia-appd for posting blobs with manual account sequence as it's not possible with celestia-node. Also, to do it through celestia-appd, one has to either sync and run an RPC node or cycle over public RPC nodes and be lucky enough to land on one with a clean mempool.

In such a case, it'd be really helpful to have a feature thats allows the user to set the account sequence while posting blobs through a light node.

@a26nine a26nine added the enhancement New feature or request label Aug 6, 2024
@github-actions github-actions bot added the external Issues created by non node team members label Aug 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request external Issues created by non node team members
Projects
None yet
Development

No branches or pull requests

1 participant