Modify CCTP crypto builtins to use Bytes #20798
Draft
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
2 tasks
carlpulley-da
commented
Feb 19, 2025
| version : UInt32 | ||
| burnToken : Bytes32 | ||
| mintRecipient : Bytes32 | ||
| amount : Int |
There was a problem hiding this comment.
Should we be considering using BigNumeric here instead (especially given this is targeting a UInt256)?
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.
Fixes https://github.com/DACH-NY/canton-network-utilities/issues/3165
CCTPMintToken.damlDaml-script test code currently fails with:
This is likely due to the ledger API not understanding
ByteStringencodings? This probably signals that there are some additional conversions needed here?