fix(sdk-coin-eth): fix the verify confidential transfer for zama#9130
Merged
Conversation
TICKET: CHALO-696
Contributor
nvrakesh06
approved these changes
Jun 29, 2026
This file contains hidden or 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
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.
TICKET: CHALO-696
This pull request adds support for verifying direct confidential token transfers for hot/TSS EOA wallets, in addition to the existing multisig/smart-contract wallet path. The main changes include updating the confidential transfer verification logic to handle both transaction shapes, adding a new decoder for direct confidentialTransfer calldata, and extending the test suite to cover the new path.
Confidential transfer verification improvements:
Erc7984Token.verifyTransactionto support both sendMultiSig-wrapped (multisig/smart-contract wallet) and direct (hot/TSS EOA wallet) confidential transfer transactions. The code now detects the transaction shape by method ID and extracts the token contract address and transfer parameters accordingly. [1] [2] [3]decodeDirectConfidentialTransferCalldatainutils.tsto parse direct confidentialTransfer calldata and extract the recipient, encrypted handle, and input proof.erc7984Token.tsto include the new decoder and relevant method IDs.Testing enhancements: