-
Notifications
You must be signed in to change notification settings - Fork 23
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: upload btc execution metadata to ipfs #339
Conversation
Signed-off-by: tcar <[email protected]>
Signed-off-by: tcar <[email protected]>
Go Test coverage is 66.7 %\ ✨ ✨ ✨ |
Signed-off-by: tcar <[email protected]>
Go Test coverage is 66.7 %\ ✨ ✨ ✨ |
Signed-off-by: tcar <[email protected]>
Go Test coverage is 66.7 %\ ✨ ✨ ✨ |
Signed-off-by: tcar <[email protected]>
Signed-off-by: tcar <[email protected]>
Go Test coverage is 65.7 %\ ✨ ✨ ✨ |
Signed-off-by: tcar <[email protected]>
Go Test coverage is 65.7 %\ ✨ ✨ ✨ |
…ar/execution_op_return Signed-off-by: tcar <[email protected]>
Go Test coverage is 65.7 %\ ✨ ✨ ✨ |
Signed-off-by: tcar <[email protected]>
Signed-off-by: tcar <[email protected]>
Go Test coverage is 66.6 %\ ✨ ✨ ✨ |
Signed-off-by: tcar <[email protected]>
Go Test coverage is 66.6 %\ ✨ ✨ ✨ |
Co-authored-by: Matija Petrunić <[email protected]>
Go Test coverage is 66.6 %\ ✨ ✨ ✨ |
…ar/execution_op_return
…ygma-relayer into tcar/execution_op_return
Go Test coverage is 66.6 %\ ✨ ✨ ✨ |
Signed-off-by: tcar <[email protected]>
Go Test coverage is 66.6 %\ ✨ ✨ ✨ |
Signed-off-by: tcar <[email protected]>
Go Test coverage is 66.6 %\ ✨ ✨ ✨ |
Signed-off-by: tcar <[email protected]>
Go Test coverage is 66.6 %\ ✨ ✨ ✨ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just some small changes and then it seems 👍
…ar/execution_op_return
Signed-off-by: tcar <[email protected]>
Go Test coverage is 66.7 %\ ✨ ✨ ✨ |
Signed-off-by: tcar <[email protected]>
Go Test coverage is 66.7 %\ ✨ ✨ ✨ |
Upload sourceDomainID and depositNonce to ipfs
Description
For each batch of btc executions upload metadata that is necessary for the indexer to index correctly evm -> btc transfers
The format of metadata that will be uploaded to ipfs is Array<{sourceDomain: number, depositNonce: number}>
After the metadata is uploaded insert OP_RETURN data into execution output with the format
syg_hash
Related Issue Or Context
Closes: #338
How Has This Been Tested? Testing details.
With e2e tests
this is execution raw transaction
0100000000010103d936b4889e953ecdd2402afc15558d2d7e8dee2177239a0350b1dc777ce5160000000000ffffffff0300e1f50500000000225120974fdb4e7e5e6b9d8768bcc8098d7204dff2228224434941a1aff258bdd30ccd0000000000000000346a327379675f516d544e5a376d334c6735526f46587244374a7a704d51505458734b614172734d4a346a5a4b6d364d624148574a78021024010000002251206a698882348433b57d549d6344f74500fcd13ad8d2200cdf89f8e39e5cafa7d501400897f399ac7c25036a8eec31583a1c533e3749ecec1cdaafcffcdd4392131c523e8beb71c0672444783377870a3dcd7a5ac908407bb0e8fb85d04726c0aa990d00000000
You can decode this and check the outputs hereThis was tested by using pinata
Types of changes
Checklist: