02Sheet 02.03.050 · Entries
One level deeper, 246: included and trapped
The same shape with 246 nodes is accepted at submission and included, then fails trapped.
FIG. · Where it sits · inside LedgerCloseMetaCAP-0046 · H-B7 · H-C6
auth tree 246 deep: included, trapped
Soroban failure: trapped on auth depth
The shape
The same shape with 246 nodes is accepted at submission and included, then fails trapped.
Variants
| Variant | Protocol | Network | Source | Size | sha256 |
|---|---|---|---|---|---|
p30-mainnet-generated | P30 | mainnet passphrase | generated by stellar-core v30.0.0 | 29,840 B | 6cb00cc20430… |
p28-mainnet-generated | P28 | mainnet passphrase | generated by stellar-core v30.0.0 | 29,832 B | edeb62de5b1e… |
p30-testnet-generated | P30 | testnet passphrase | generated by stellar-core v30.0.0 | 29,840 B | df8fb8e3cca2… |
p28-testnet-generated | P28 | testnet passphrase | generated by stellar-core v30.0.0 | 29,832 B | d60ae77c80f2… |
p30-mainnet-generated-galexie | P30 | mainnet passphrase | generated by stellar-core v30.0.0 change order varies: 2 orderings in 2 runs | 31,408 B | 0a4f45df3ae2… |
What a correct reader returns
| A correct reader finds | Value | Backed by |
|---|---|---|
| The call fails: the host traps. | trapped | constructionsnapshotcorewalker |
| With diagnostic events (Galexie flags) the cause is shown: host_fn_failed with error context exceeded_limit. p30-mainnet-generated-galexie | some change where 1 fields match | snapshotcorewalker |
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 auth.tree-depth-246-trapped · compiled from catalog/auth.tree-depth-246-trapped.json · entry.json
The deepest authorization tree core applies: 245 invocations; the WASM decoder rejects it
One source-credential entry whose root invocation carries a chain of 244 never-called sub-invocations: 245 nodes, the deepest that applies at P30 (246 traps).
EXTEND_FOOTPRINT_TTL changes only a TTL entry
The data entry is untouched; only its TTL entry, named by sha256 of the data's LedgerKey, changes.