Resilience Network.
A sovereign Layer-1 blockchain written in Go, pairing a full EVM execution layer with an Orchard zero-knowledge shielded pool — designed for consumers who shouldn’t need seed phrases and institutions who need auditable privacy.
Deterministic BFT finality · EVM + ZK shielded pool · FaceID passkey accounts.
Illustrative workflow · explore the engineering above
The problem
Blockchains force bad trade-offs. Consumers get seed phrases and gas tokens they don’t have — a funnel where most users never make a second transaction. Privacy is all-or-nothing: either a fully public ledger unacceptable for business, or mixer-style darkness that regulators ban. And lost keys mean lost funds. Each of these has been solved piecemeal with smart contracts; Resilience Network makes them protocol-level guarantees.
What I built
Built a Layer-1 in Go with 2-second slots and a BFT engine using ECVRF secret leader election, durable anti-equivocation locks, and single-pass finality in 1.4–1.8 seconds. The EVM layer keeps full bytecode parity — differentially fuzzed against Ethereum’s general state tests — with native precompiles for P-256 passkey signatures (FaceID/TouchID at roughly 6,900 gas), the .rsc name registry, and an ERC-4626-style liquid-staking vault. A Rust Orchard proving library (Halo 2, Pallas-Vesta) powers shielded transfers with viewing keys and single-payment proof receipts for auditable privacy. Transaction V2 adds session keys with spending limits, enshrined gas sponsorship, and guardian social recovery with a 7-day challenge window. The repo ships the full operator suite: node daemon, CLI, mTLS remote signer, block explorer, faucet, and a load-testing bench.
The engineering thinking
Privacy without compliance is a dead end, so disclosure is selective by design — viewing keys and payment proofs instead of either full transparency or darkness. Consumer onboarding has to live in the protocol, not in bundler contracts: passkeys and sponsored gas are enshrined. And correctness is treated as a release gate — protocol manifests pin feature activation heights, and 68 adversarial multi-node user stories simulate Byzantine nodes, partitions, disk exhaustion, and restart replays.
The outcome
The chain runs multi-validator test networks with deterministic commits: sub-2-second finality, an EVM at parity with Ethereum behavior, a functional shielded pool with selective disclosure, and compact-block light sync that cuts wallet bandwidth by roughly 84%. Pre-mainnet gates remain: an independent cryptographic audit of the proving library, an incentivized adversarial testnet, and the TypeScript/Web SDKs for passkey wallets.