02Sheet 02.03.109 · Entries
MEMO_HASH mapped to to_muxed_id bytes
CAP-0067 renders MEMO_HASH in the transfer event as bytes, indistinguishable from MEMO_RETURN.
FIG. · Where it sits · inside LedgerCloseMetaCAP-0067 · H-A6
MEMO_HASH carried into the transfer event as to_muxed_id
bytes
The shape
CAP-0067 renders MEMO_HASH in the transfer event as bytes, indistinguishable from MEMO_RETURN.
Variants
| Variant | Protocol | Network | Source | Size | sha256 |
|---|---|---|---|---|---|
p30-mainnet-generated | P30 | mainnet passphrase | generated by stellar-core v30.0.0 | 3,712 B | a3fe348342b7… |
p30-testnet-generated | P30 | testnet passphrase | generated by stellar-core v30.0.0 | 3,712 B | fd139c0147ff… |
What a correct reader returns
| A correct reader finds | Value | Backed by |
|---|---|---|
| The memo is MEMO_HASH sha256("xdrproof:memo-hash"). | a01ecbb5d9870ec923a9f9750a7a87faae4913aedcb97154305f01f1a5180796 | constructionsnapshotcorewalker |
| The transfer event carries the same 32 bytes as to_muxed_id, as bytes: the memo type is gone. | some change where 2 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.hash-as-bytes · compiled from catalog/memo.hash-as-bytes.json · entry.json