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.
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
| Variant | Protocol | Network | Source | Size | sha256 |
|---|---|---|---|---|---|
p30-mainnet-generated | P30 | mainnet passphrase | generated by stellar-core v30.0.0 | 5,836 B | 8a0b28f5e494… |
p30-testnet-generated | P30 | testnet passphrase | generated by stellar-core v30.0.0 | 5,836 B | 16c5b3f87521… |
What a correct reader returns
| A correct reader finds | Value | Backed by |
|---|---|---|
| This payment goes to bob muxed with ID 100. p30-mainnet-generated | MCDNGZ7NJFNBWBP7DXYQKJRBG2VAIR5DCCCLUDBZW5B3VGUFKDG5AAAAAAAAAAAAMQWDS | constructionsnapshotcorewalker |
| This payment goes to bob muxed with ID 100. p30-testnet-generated | MCDNGZ7NJFNBWBP7DXYQKJRBG2VAIR5DCCCLUDBZW5B3VGUFKDG5AAAAAAAAAAAAMQWDS | constructionsnapshotcorewalker |
| The same ledger holds the payment to bob muxed with ID 200. p30-mainnet-generated | some change where 1 fields match | constructionsnapshotcorewalker |
| The same ledger holds the payment to bob muxed with ID 200. p30-testnet-generated | some change where 1 fields match | constructionsnapshotcorewalker |
| Operation 0 succeeds. | success | snapshotcorewalker |
Sightings
wallet-backend#693Check 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.payment.two-ids-one-account-one-ledger · compiled from catalog/muxed.payment.two-ids-one-account-one-ledger.json · entry.json
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.
RESTORE_FOOTPRINT with a muxed operation source and a text memo
The operation source is M(alice, 2^64-1) and the memo text: valid for RestoreFootprint.