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

VariantProtocolNetworkSourceSizesha256
p30-mainnet-generatedP30mainnet passphrasegenerated by stellar-core v30.0.094,776 B6d46db6d8fe5…
p30-testnet-generatedP30testnet passphrasegenerated by stellar-core v30.0.094,776 Baf7dee27fa40…

What a correct reader returns

A correct reader findsValueBacked by
The transaction has 100 operations.length 100constructionsnapshot
The last pays bob muxed with ID 100.MCDNGZ7NJFNBWBP7DXYQKJRBG2VAIR5DCCCLUDBZW5B3VGUFKDG5AAAAAAAAAAAAMQWDSconstructionsnapshotcorewalker
All 100 succeed; the ledger holds only this transaction.length 1constructionsnapshot

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 max-length.operations-100 · compiled from catalog/max-length.operations-100.json · entry.json

On this page