02Sheet 02.03.111 · Entries

MEMO_RETURN mapped to to_muxed_id bytes, the same as MEMO_HASH

CAP-0067 renders MEMO_RETURN in the transfer event as bytes, exactly as MEMO_HASH: from the event alone the two cannot be told apart.

FIG. · Where it sits · inside LedgerCloseMetaCAP-0067 · H-A6
MEMO_RETURN carried into the transfer event as to_muxed_id (bytes), indistinguishable from MEMO_HASH

The shape

CAP-0067 renders MEMO_RETURN in the transfer event as bytes, exactly as MEMO_HASH: from the event alone the two cannot be told apart.

Variants

VariantProtocolNetworkSourceSizesha256
p30-mainnet-generatedP30mainnet passphrasegenerated by stellar-core v30.0.03,712 B0a8bc9e95209…
p30-testnet-generatedP30testnet passphrasegenerated by stellar-core v30.0.03,712 B9a2f31668e08…

What a correct reader returns

A correct reader findsValueBacked by
The memo is MEMO_RETURN sha256("xdrproof:memo-return").732f7b35d98a49d5daa20443220652e762b59d7e3829733e8e66ce1eb874b99bconstructionsnapshotcorewalker
The transfer event carries the same 32 bytes as to_muxed_id bytes.some change where 1 fields matchconstructionsnapshotcorewalker

Check it yourself

make verify   # schema, hashes, the byte-for-byte round trip and every fact above
make oracle   # the facts' values, re-read by stellar-core and the schema walker

Entry id memo.return-as-bytes · compiled from catalog/memo.return-as-bytes.json · entry.json

On this page