Design an indexer: async tokio runtime, typed RPC client with serde, a channel between fetcher and writer tasks, Arc-shared config, typed errors with thiserror, retries with backoff, and property tests over reorg handling. This exercises ownership, concurrency, error design and the crate ecosystem at once.
← Rust theorytheory 0/50 · 0%
Blockchain · hard
50. Capstone: A Rust Chain Service
Putting the track together.
Check your understanding
1. Which runtime pattern suits an I/O-bound indexer?
2. Shared immutable config across tasks is best held in…