02Sheet 02.03.197 · Entries
A mainnet Soroban phase with three stages and two clusters in one stage
CAP-0063 parallel execution: the Soroban phase is stages of clusters of transactions.
FIG. · Where it sits · inside LedgerCloseMetaCAP-0063 · H-F5
ParallelTxsComponent with 3 stages, one holding 2 clusters
The shape
CAP-0063 parallel execution: the Soroban phase is stages of clusters of transactions. This mainnet ledger has 3 stages with 1, 2 and 1 clusters. Readers that assume one stage and one cluster drop transactions.
Variants
| Variant | Protocol | Network | Source | Size | sha256 |
|---|---|---|---|---|---|
p29-mainnet-mined-l65485185 | P29 | mainnet passphrase | mined from history | 2,495,988 B | fc6b3e490799… |
What a correct reader returns
| A correct reader finds | Value | Backed by |
|---|---|---|
| The Soroban phase has 3 stages. | length 3 | snapshot |
| The second stage has 2 clusters. | length 2 | snapshot |
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 parallel.three-stages-mainnet · compiled from catalog/parallel.three-stages-mainnet.json · entry.json
A protocol-30 header with a signed millisecond close time
CAP-0088: StellarValue ext signed_ms carries close_time_ms, signed by the node.
An offer match in a protocol-12 result decodes as ClaimOfferAtomV0: the seller is a raw ed25519 key
Before protocol 18 an offer claim was a ClaimOfferAtom whose seller was an AccountID.