You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, for shielding transfer from another chain to Namada, a user has to do a 2-step operation.
ibc-gen-shielded command to generate the MASP proofs on the target Namada
IBC transfer with the proofs in the memo field of ICS-20 packet data
Like regular IBC transfers, requesting IBC transfers without setting the MASP proofs is helpful to senders. (The difference is only specifying a payment address as a receiver.)
Send tokens with a payment address as a receiver from the source Namada like regular IBC transfers (ibc-transfer)
Hermes(IBC relayer) checks the transfer event
Hermes requests the MASP proof generation to the target Namada when the receiver address is a payment address
Hermes submits a transaction with MsgRecvPacket and the proof as transaction data
Like sending tokens: Namada's MsgTransfer has Option<IbcShieldedTransfer> (proof)
It means that we don't use the memo field anymore
Target Namada handles the message and the proof
The text was updated successfully, but these errors were encountered:
Currently, for shielding transfer from another chain to Namada, a user has to do a 2-step operation.
ibc-gen-shielded
command to generate the MASP proofs on the target NamadaLike regular IBC transfers, requesting IBC transfers without setting the MASP proofs is helpful to senders. (The difference is only specifying a payment address as a receiver.)
ibc-transfer
)MsgRecvPacket
and the proof as transaction dataMsgTransfer
hasOption<IbcShieldedTransfer>
(proof)The text was updated successfully, but these errors were encountered: