Introducing ZIP-48 Support, Secure Message Signing, and Public Key Retrieval #147
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.
The snap now brings full ZIP-48 transparent multisig support with Asigna into MetaMask Snaps by exposing new RPC methods that can be invoked via
wallet_invokeSnap. Every method enforces well-formed ZIP-48 derivation paths (starting withm/…), derives keys throughsnap_getBip32Entropy, and displays a user-facing confirmation dialog before any sensitive action is performed.signTransparent– takes a list of transaction sighashes tied to a ZIP-48 derivation path, shows the recipient/amount/network to the user, and upon confirmation returns DER signatures withSIGHASH_ALL, ready to be assembled into the multisig transaction.signTransparentMessage– signs arbitrary text messages with the selected transparent key, applies ZIP-302 message framing, verifies the signature on-device, and optionally checks the derived address against a providedexpectedAddressto prevent account mix-ups.getTransparentPublicKey– safely derives and returns the compressed public key for any ZIP-48 path after the user approves a dialog showing the origin and requested derivation path.This makes the snap cover the full transparent ZIP-48 workflow—transaction signing, message signing, and key disclosure—with explicit user consent at each step.