02Sheet 02.03.110 · Entries

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).

FIG. · Where it sits · inside LedgerCloseMetaCAP-0067 · H-A6 · H-B10
MEMO_ID carried into the transfer event as to_muxed_id
u64
u64 above int64 max in JSON

The shape

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).

Variants

VariantProtocolNetworkSourceSizesha256
p30-mainnet-generatedP30mainnet passphrasegenerated by stellar-core v30.0.03,660 B2298b28fc3ef…
p30-testnet-generatedP30testnet passphrasegenerated by stellar-core v30.0.03,660 B303b879167a4…

What a correct reader returns

A correct reader findsValueBacked by
The memo ID is 18446744073709551615.18446744073709551615constructionsnapshotcorewalker
The transfer event carries it as to_muxed_id u64.some change where 1 fields matchsnapshotcorewalker

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.id-u64-max · compiled from catalog/memo.id-u64-max.json · entry.json

On this page