02Sheet 02.03.049 · Entries

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).

FIG. · Where it sits · inside LedgerCloseMetaCAP-0046 · H-B7 · H-B13 · H-A7
auth tree 245 nodes deep, the maximum that applies
a valid ledger the WASM decoder rejects
depth limit exceeded
auth entries name an address the meta never touches

The shape

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). The kits[1] contract appears 244 times in the auth and never in the meta. @stellar/stellar-xdr-json 30.0.0 (WASM) cannot decode this ledger; native rs-stellar-xdr can.

Variants

VariantProtocolNetworkSourceSizesha256
p30-mainnet-generatedP30mainnet passphrasegenerated by stellar-core v30.0.029,780 B4dabb873a396…
p28-mainnet-generatedP28mainnet passphrasegenerated by stellar-core v30.0.029,772 Bb5e104842e4d…
p30-testnet-generatedP30testnet passphrasegenerated by stellar-core v30.0.029,780 Bcdc0876232a7…
p28-testnet-generatedP28testnet passphrasegenerated by stellar-core v30.0.029,772 B558f01d3a986…

What a correct reader returns

A correct reader findsValueBacked by
The call succeeds; the success hash covers its return value (u32 1) and no events, the same on every network.df071a249d03fc2f22313f75c734a254bbea03124cea77001704db0670b2fc02snapshotcorewalker
It changes no ledger entry.length 0snapshot

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 auth.tree-depth-245-max · compiled from catalog/auth.tree-depth-245-max.json · entry.json

On this page