feat: get ckb txhash from job returnvalue #93
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
ahonn
changed the title
ahonn
force-pushed
the
feat/get-txhash-from-job
branch
from
fab26bb to
f556c22
Compare
Flouse
approved these changes
Apr 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
/rgbpp/v1/transaction/:btc_txidcurrently only searches for the transaction through the lock script. When the lock is BTCTimeLock, it may not be found. see: #45Therefore, obtaining the CKB txhash from the job to improve the speed and solve the problem of BTCTimeLock search. But the problem is that in different application instances, the job may not exist