02Sheet 02.03.012 · Entries

Payments to two different muxed IDs of one account in the same ledger

Two payments in one ledger reach M(bob, 100) and M(bob, 200): two muxed addresses, one base account.

FIG. · Where it sits · inside LedgerCloseMetaCAP-0027 · H-A1
two PaymentOp.destination muxed IDs over one base account in one ledger

The shape

Two payments in one ledger reach M(bob, 100) and M(bob, 200): two muxed addresses, one base account. Readers keyed by base account must keep both IDs; readers keyed by M address must not create two accounts. wallet-backend#693 mishandled two muxed IDs of one account in one ledger.

Variants

VariantProtocolNetworkSourceSizesha256
p30-mainnet-generatedP30mainnet passphrasegenerated by stellar-core v30.0.05,836 B8a0b28f5e494…
p30-testnet-generatedP30testnet passphrasegenerated by stellar-core v30.0.05,836 B16c5b3f87521…

What a correct reader returns

A correct reader findsValueBacked by
This payment goes to bob muxed with ID 100.
p30-mainnet-generated
MCDNGZ7NJFNBWBP7DXYQKJRBG2VAIR5DCCCLUDBZW5B3VGUFKDG5AAAAAAAAAAAAMQWDSconstructionsnapshotcorewalker
This payment goes to bob muxed with ID 100.
p30-testnet-generated
MCDNGZ7NJFNBWBP7DXYQKJRBG2VAIR5DCCCLUDBZW5B3VGUFKDG5AAAAAAAAAAAAMQWDSconstructionsnapshotcorewalker
The same ledger holds the payment to bob muxed with ID 200.
p30-mainnet-generated
some change where 1 fields matchconstructionsnapshotcorewalker
The same ledger holds the payment to bob muxed with ID 200.
p30-testnet-generated
some change where 1 fields matchconstructionsnapshotcorewalker
Operation 0 succeeds.successsnapshotcorewalker

Sightings

wallet-backend#693

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.two-ids-one-account-one-ledger · compiled from catalog/muxed.payment.two-ids-one-account-one-ledger.json · entry.json

On this page