A Solana Program Change Can Be Compatible with One Consumer but Not Another
Testing Provider Changes Against Consumer-Declared Requirements
Posts / 85 records
Searchable archive. For the latest feed with pagination, start on the home page.
A chronological index of field notes on research, engineering, markets, and protocols.
Testing Provider Changes Against Consumer-Declared Requirements
Two compiled Solana implementations accepted the same call. Both transactions succeeded; only one preserved the caller’s fixed postcondition.
I Searched the Transaction for the Slippage Threshold. I Found the Quote Instead.
Can a Solana Transaction Prove the Router?
How I Turned AMM Logs Into a Causal Pipeline
Dynamic Fees in AMMs: When the Signal Matters
Building an Interactive P2P Attack Gym in Rust
Three Classic Blockchain Attacks, Rebuilt in a Rust Local Lab
Building a Stablecoin Audit Toolkit Around Evidence, Not Dashboards
Before SNARKs: Building a Mini ZK-Rollup Verifier in Rust
Metering Chain: QA That Follows Business Logic
Blockchain in 2026: Trust, State, and Why Rust Fits
Metering Chain Phase 4: Settlement and Economic Finality
Metering Chain Phase 3: Capability-Driven Delegation
Metering Chain Phase 2: Deterministic Authorization for Multi-Operator DePIN
Learning Consensus Algorithms: A Hands-On Comparison with Rust