node Files

https://github.com/user-attachments/assets/b9f6f596-7726-4594-81f9-d149c76ee263

## Major 📜

### 🧾 Execution claims (fork at epoch 881, height 88,100,000)

• Validators now attest an execution claim: entry_height || entry_hash || root_contractstate || root_receipts (104 bytes), replacing entry_hash || mutations_hash
• A consensus (≥67% aggregate signature) now certifies the block's full state root and receipts root — any contract state or receipt can be proven from it
• Consensuses are stored and compared by claim hash; a node whose state root disagrees with the network halts as out of sync
• The header MMR (root_chain) commits claim hashes from the fork on: one recent certificate proves every earlier block's claim with an MMR proof
• root_validator is dropped from block headers after the fork — the validator set is provable from contract state
• ⚠️ Upgrade before height 88,100,000; nodes on older versions cannot follow the chain past the fork

### ⚡ Faster rooting

• Consensus signatures are verified on arrival, in parallel, against the epoch roster; rooting only re-checks quorum and masks
• A slash mid-epoch does not force re-verification (the roster is fixed for the epoch)

### 🚀 RPC performance

• /api/chain/stats cached for 1s; /api/chain/kpi cached; blocks-with-txs cached for rooted heights
• Tx lookups read each block once instead of once per tx; block height lookups are memoized
• 10x Faster Base58 encoding/decoding due to AI found degree optimization for native BigInt languages (erlang)
• Ping/tip broadcasts are single-flight, so HTTP floods can no longer stall the node
• Per-route HTTP cost tracking (HTTP.Stats)

## Breaking API changes ⚠️

• POST /api/contract/get_prefix is paged: returns %{rows, cursor} (up to 1000 rows / 1 MB); pass ?cursor=<cursor> for the next page; cursor is nil on the last page
• /api/proof/validators is removed
• Consensus output (/api/chain/...) shows the claim fields and claim_hash; after the fork consensus.mut_hash holds the claim hash
• MMR inclusion proofs: from the fork on, a proof carries the block's claim and the leaf is sha256(claim); below the fork the leaf stays the entry hash
• Attestation and consensus network messages change format at the fork

## Fixes & hardening 🔧

• Sync: a fork sibling that arrives after its height was applied is stored, so consensus can still pick it; catchup always asks for entries and lists the ones already held
• Slash retries reuse the stored slash entry instead of signing a conflicting one (fixes a slash-lock deadlock)
• Peer tips: an inflated announced height can no longer suppress later honest tips
• Inbox: attestations are filed by the height in their signed claim