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
| Variant | Protocol | Network | Source | Size | sha256 |
|---|---|---|---|---|---|
p30-mainnet-generated | P30 | mainnet passphrase | generated by stellar-core v30.0.0 | 3,712 B | 0a8bc9e95209… |
p30-testnet-generated | P30 | testnet passphrase | generated by stellar-core v30.0.0 | 3,712 B | 9a2f31668e08… |
What a correct reader returns
| A correct reader finds | Value | Backed by |
|---|---|---|
| The memo is MEMO_RETURN sha256("xdrproof:memo-return"). | 732f7b35d98a49d5daa20443220652e762b59d7e3829733e8e66ce1eb874b99b | constructionsnapshotcorewalker |
| The transfer event carries the same 32 bytes as to_muxed_id bytes. | some change where 1 fields match | constructionsnapshotcorewalker |
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 walkerEntry id memo.return-as-bytes · compiled from catalog/memo.return-as-bytes.json · entry.json
MEMO_ID at u64 max, mapped to to_muxed_id
MEMO_ID 2^64-1 (above int64): JSON as a string, and CAP-0067 copies it into the transfer event as to_muxed_id (u64).
A 28-byte text memo that is not valid UTF-8, mapped into the transfer event
MEMO_TEXT holds 28 raw bytes that are not UTF-8 (the maximum length).