02Sheet 02.03.011 · Entries

One payment with a muxed transaction source, operation source and destination

A payment where the transaction source, the operation source and the destination are all muxed accounts (M…), with IDs 1, 2^64-1 and 2^63.

FIG. · Where it sits · inside LedgerCloseMetaCAP-0027 · H-A1 · H-A2
Transaction.sourceAccount, Operation.sourceAccount and PaymentOp.destination as MuxedAccount
muxed IDs 1, 2^63 (above int64 max) and 2^64-1

The shape

A payment where the transaction source, the operation source and the destination are all muxed accounts (M…), with IDs 1, 2^64-1 and 2^63. Each M address is a base account plus a 64-bit ID: the ID must be kept, and balances belong to the base account. Readers that store the M string as the account, or drop the ID, misattribute or lose the payment.

Variants

VariantProtocolNetworkSourceSizesha256
p30-mainnet-generatedP30mainnet passphrasegenerated by stellar-core v30.0.02,456 Bfd9d0c246bf3…
p30-testnet-generatedP30testnet passphrasegenerated by stellar-core v30.0.02,456 Bc4d525c05899…

What a correct reader returns

A correct reader findsValueBacked by
The transaction source is alice muxed with ID 1.MBQXLZZTGUKRRRYDQNQOMKWL7DN3PGIBPNBIHDIO5KFPPPIFAHHQIAAAAAAAAAAAAGYJWconstructionsnapshotcorewalker
The operation source is alice muxed with ID 2^64-1.MBQXLZZTGUKRRRYDQNQOMKWL7DN3PGIBPNBIHDIO5KFPPPIFAHHQJ7777777777775YC2constructionsnapshotcorewalker
The destination is bob muxed with ID 2^63, above the int64 maximum.MCDNGZ7NJFNBWBP7DXYQKJRBG2VAIR5DCCCLUDBZW5B3VGUFKDG5BAAAAAAAAAAAACH6Qconstructionsnapshotcorewalker
Operation 0 succeeds.successsnapshotcorewalker

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 muxed.payment.every-position · compiled from catalog/muxed.payment.every-position.json · entry.json

On this page