FIELD NOTES / 2026
Technical writing with the implementation left in.
Architecture, code, protocol decisions, failure modes, and the limits I found while building backend and cryptographic systems.
No launch summaries. No unexplained abstractions. Each note is grounded in a working repository and names what is unfinished.
Implementing sumcheck and GKR from first principles in Rust
A code-led path from multilinear evaluation tables to Fiat–Shamir sumcheck and layered-circuit reduction - with the shortcuts still present in the educational implementation.
Designing SIP-018 payment intents for metadata-reduced settlement
The authorization, replay, cancellation, asset-safety, and privacy decisions behind Privara - and the limits the protocol does not hide.
READ →Building a pay-per-request agent API with x402 on Algorand
How AgentHub turns an HTTP 402 challenge into mainnet USDC settlement - and what changes when failure can happen after a caller has paid.
READ →Designing Bondline: Group Commitments as On-Chain Incentives
How Circles, staked Bonds, Cosigns, threshold resolution, and a shared Pot turn personal deadlines into group-enforced commitments on Monad.
READ →Reusable ZK Credentials Without Exposing Identity Data
How StellarCred separates issuance, local proving, on-chain verification, and protocol reuse so applications can check claims without collecting the underlying credential data.
READ →Building Confidential Payments on Stellar
How Lucent combines Pedersen-committed balances, browser-generated UltraHonk proofs, Soroban verification, auditor ciphertexts, and payment-product UX on Stellar.
READ →Building Encrypted Applications on the EVM: Zama, Fhenix, and Three FHE Applications in Practice
A comparative engineering study of Zama fhEVM and Fhenix CoFHE through Shade, VeilDrop, and CipherMarket - three products with different privacy boundaries and decryption workflows.
READ →Turning OpenTelemetry signals into operational SLOs with SigNoz
A reproducible SLO pack that connects traces, RED metrics, correlated logs, error budgets, multi-window alerts, and live-fire verification.
READ →The Commitment Has to Come First: What My Rust KZG Prototype Taught Me About Binding
A code-led look at multilinear KZG openings, pairing checks, and the API mistake that can turn a valid proof into a meaningless one.