I cannot find the release notes for the latest two releases of Citrea but their recent
blog post describes the Header Chain Circuit:
One of the key enablers of Light Client Proofs is the Header Chain Circuit. The Header Chain Circuit is a Rust codebase designed to run in Risc0, generating a recursive ZK proof of Bitcoin’s full header chain. Thanks to recursion, the prover can start from where the last proof ended, avoiding unnecessary time spent on proving the older blocks.
It crossed my mind that with the descibed changes we may be one step closer to
running a Citrea node on top of a pruned Bitcoin node. As of now, the official
documentation recommends to run the Bitcoin node with
-txindex=1 (which precludes pruning).Running Citrea's node with a pruned node (
prune=550 in bitcoin.conf) results in error:2025-01-12T15:22:05.312609Z INFO citrea_fullnode::runner: Starting to sync from L2 height 19201 2025-01-12T15:22:05.322085Z ERROR bitcoin_da::service: error=JSON-RPC error: RPC error response: RpcError { code: -1, message: "Block not available (pruned data)", data: None } 2025-01-12T15:22:05.925926Z ERROR bitcoin_da::service: error=JSON-RPC error: RPC error response: RpcError { code: -1, message: "Block not available (pruned data)", data: None }
Is the possibility of running a Citrea node with a pruned BTC node on the horizon
for Citrea users?