02Sheet 02.03.009 · Entries
A payment to a muxed address with ID 0
A muxed destination whose ID is 0: still an M address, distinct from the plain G account.
FIG. · Where it sits · inside LedgerCloseMetaCAP-0027 · CAP-0067 · H-A2
PaymentOp.destination muxed ID 0
The shape
A muxed destination whose ID is 0: still an M address, distinct from the plain G account. Readers that treat ID 0 as "no ID" collapse it into the base account.
Variants
| Variant | Protocol | Network | Source | Size | sha256 |
|---|---|---|---|---|---|
p30-mainnet-generated | P30 | mainnet passphrase | generated by stellar-core v30.0.0 | 3,660 B | 97127c4b5e2b… |
p30-testnet-generated | P30 | testnet passphrase | generated by stellar-core v30.0.0 | 3,660 B | 71736f78b456… |
What a correct reader returns
| A correct reader finds | Value | Backed by |
|---|---|---|
| The destination is bob muxed with ID 0, an M address. | MCDNGZ7NJFNBWBP7DXYQKJRBG2VAIR5DCCCLUDBZW5B3VGUFKDG5AAAAAAAAAAAAAAHBK | constructionsnapshotcorewalker |
| The transfer event names bob's base account and carries to_muxed_id 0. | some change where 2 fields match | snapshotcorewalker |
| Operation 0 succeeds. | success | snapshotcorewalker |
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 muxed.id-zero · compiled from catalog/muxed.id-zero.json · entry.json