02Sheet 02.03.031 · Entries

An XLM SAC transfer to a muxed address: the event splits it into to and to_muxed_id

The transfer argument is M(bob, 2^64-1). The event names bob's G address in topics and carries the ID as to_muxed_id (u64) in a data map instead of a bare i128.

FIG. · Where it sits · inside LedgerCloseMetaCAP-0067 · H-E2 · H-A11
transfer event data map with to_muxed_id u64
event splits M into to and to_muxed_id

The shape

The transfer argument is M(bob, 2^64-1). The event names bob's G address in topics and carries the ID as to_muxed_id (u64) in a data map instead of a bare i128.

Variants

VariantProtocolNetworkSourceSizesha256
p30-mainnet-generatedP30mainnet passphrasegenerated by stellar-core v30.0.03,456 B184a84c802d7…
p28-mainnet-generatedP28mainnet passphrasegenerated by stellar-core v30.0.03,448 B58eb92587cac…
p30-testnet-generatedP30testnet passphrasegenerated by stellar-core v30.0.03,456 B50b647df6ab3…
p28-testnet-generatedP28testnet passphrasegenerated by stellar-core v30.0.03,448 Bef6840100d7d…

What a correct reader returns

A correct reader findsValueBacked by
The event names bob's base account.some change where 1 fields matchsnapshotcorewalker
The data is a map with amount 1 and to_muxed_id 18446744073709551615.some change where 2 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 sac.xlm-transfer-muxed-destination · compiled from catalog/sac.xlm-transfer-muxed-destination.json · entry.json

On this page