02Sheet 02.03.013 · Entries
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.
FIG. · Where it sits · inside LedgerCloseMetaCAP-0027 · CAP-0046 · H-A9
muxed Operation.sourceAccount and MEMO_TEXT on RestoreFootprint
The shape
The operation source is M(alice, 2^64-1) and the memo text: valid for RestoreFootprint.
Variants
| Variant | Protocol | Network | Source | Size | sha256 |
|---|---|---|---|---|---|
p30-mainnet-generated | P30 | mainnet passphrase | generated by stellar-core v30.0.0 | 2,228 B | cc788bf7bf65… |
p28-mainnet-generated | P28 | mainnet passphrase | generated by stellar-core v30.0.0 | 2,220 B | 54241c192a17… |
p30-testnet-generated | P30 | testnet passphrase | generated by stellar-core v30.0.0 | 2,228 B | 4510d46002fa… |
p28-testnet-generated | P28 | testnet passphrase | generated by stellar-core v30.0.0 | 2,220 B | 13d16ae895ef… |
What a correct reader returns
| A correct reader finds | Value | Backed by |
|---|---|---|
| The operation source is alice muxed with ID 2^64-1. | MBQXLZZTGUKRRRYDQNQOMKWL7DN3PGIBPNBIHDIO5KFPPPIFAHHQJ7777777777775YC2 | constructionsnapshotcorewalker |
| The restore_footprint operation succeeds. | success | snapshotcorewalker |
Sightings
wallet-backend#753Check 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.soroban-restore-op-source-text-memo · compiled from catalog/muxed.soroban-restore-op-source-text-memo.json · entry.json
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.
EXTEND_FOOTPRINT_TTL from a muxed source with a text memo
Core refuses a memo or muxed source only on InvokeHostFunction (TransactionFrame::validateSorobanMemo); on TTL and restore operations both are valid.