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

IBC Cell conflict of relayer and forcerelay-ckb-sdk generating tx at the same time #373

Closed
ashuralyk opened this issue Nov 7, 2023 · 2 comments · Fixed by #377
Closed
Assignees
Labels
enhancement New feature or request

Comments

@ashuralyk
Copy link
Contributor

ashuralyk commented Nov 7, 2023

Summary of Bug

since channel cell and packet cell only exist one instance in CKB, and also due to forcerelay and forcerelay-ckb-sdk work independently, so that cell compete happened while both of them generate transaction that consumes a same cell at the same time

I guess to regenerate transaction may solve this problem

@blckngm
Copy link
Contributor

blckngm commented Nov 7, 2023

The relayer needs to retry, generating a new tx using new cells. Maybe it's already handled by the framework (hermes)?

It's a nice to have for the cli. Users can always retry manually.

@Flouse Flouse added the enhancement New feature or request label Nov 7, 2023
@ashuralyk
Copy link
Contributor Author

The relayer needs to retry, generating a new tx using new cells. Maybe it's already handled by the framework (hermes)?

It's a nice to have for the cli. Users can always retry manually.

actually, I don't see any concerns about this issue in Hermes, and it doesn't retry sending transaction in the deployed instance

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants