02Sheet 02.03.119 · Entries
A transaction with the maximum 100 operations, each to a different muxed ID
operations<100> full: 100 payments to M(bob, 1) … M(bob, 100).
FIG. · Where it sits · inside LedgerCloseMetapre-cap · CAP-0027 · H-B12 · H-A1
Transaction.operations at its maximum of 100
100 muxed destination IDs of one account in one transaction
The shape
operations<100> full: 100 payments to M(bob, 1) … M(bob, 100). The classic transaction set holds exactly 100 operations, so this transaction fills its ledger alone.
Variants
| Variant | Protocol | Network | Source | Size | sha256 |
|---|---|---|---|---|---|
p30-mainnet-generated | P30 | mainnet passphrase | generated by stellar-core v30.0.0 | 94,776 B | 6d46db6d8fe5… |
p30-testnet-generated | P30 | testnet passphrase | generated by stellar-core v30.0.0 | 94,776 B | af7dee27fa40… |
What a correct reader returns
| A correct reader finds | Value | Backed by |
|---|---|---|
| The transaction has 100 operations. | length 100 | constructionsnapshot |
| The last pays bob muxed with ID 100. | MCDNGZ7NJFNBWBP7DXYQKJRBG2VAIR5DCCCLUDBZW5B3VGUFKDG5AAAAAAAAAAAAMQWDS | constructionsnapshotcorewalker |
| All 100 succeed; the ledger holds only this transaction. | length 1 | constructionsnapshot |
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 max-length.operations-100 · compiled from catalog/max-length.operations-100.json · entry.json
A transaction with the maximum 2 extra signers
Preconditions v2 extraSigners<2> full: two signed-payload keys, each needing its own signature; the transaction carries three.
A path payment through the maximum 5 intermediate assets
PATH_PAYMENT_STRICT_SEND from XLM through HOP1…HOP5 to HOP6: path<5> full, one offer crossed per hop, six claim atoms.