The Architect's Brief
Writing
Weekly articles on Blockchain Architecture, AI × Web3, and Engineering Leadership.
Blockchain Architecture
Designing a Staking Contract That Won't Get Exploited
Most staking bugs are not exotic. They come from predictable mistakes in reward math, withdrawal flow, upgradeability, and trust boundaries.
Blockchain Architecture
The Data Sovereignty Constraint: Designing Blockchain Systems for Government
Government blockchain systems fail when architects treat public-chain patterns as universal. Data sovereignty changes the design from the first decision.
2 min readEngineering Leadership
Why I Stopped Writing Smart Contracts Before Auditing Them
Auditing changed how I write Solidity. Once you spend enough time reading production-bound contracts for failure modes, your default design instincts change.
2 min readOperations Cluster
L2 operations, wallet flows, and smart-contract risk
L2 Chains Are Not Hard to Deploy — The Hard Part Comes After
Deploying an OP Stack L2 takes a week. Running one in production takes ongoing engineering. The sequencer, bridge operations, oracle design, and L1 state posting are where the real work begins.
Building a Non-Custodial Wallet with Fireblocks: What Nobody Tells You
Fireblocks NCW solves part of the problem. The real complexity sits in recovery UX, session state, webhook timing, and transaction flows that fail halfway.
Why I Stopped Writing Smart Contracts Before Auditing Them
Auditing changed how I write Solidity. Once you spend enough time reading production-bound contracts for failure modes, your default design instincts change.
Designing a Staking Contract That Won't Get Exploited
Most staking bugs are not exotic. They come from predictable mistakes in reward math, withdrawal flow, upgradeability, and trust boundaries.
Sovereignty Cluster
Private-chain verification and regulated-system design
How We Built Cross-Chain Credential Verification Between a Private and Public Blockchain
Connecting Hyperledger Fabric to Polygon using a commit-reveal pattern and a lightweight oracle. Three transactions, 16 seconds, zero PII on a public chain.
The Data Sovereignty Constraint: Designing Blockchain Systems for Government
Government blockchain systems fail when architects treat public-chain patterns as universal. Data sovereignty changes the design from the first decision.
How ERC-4337 Changes Wallet Architecture Forever
Account Abstraction removes the EOA bottleneck. Here's what that means for wallet architecture, custody design, and the dApps built on top.
Archive
Engineering Leadership · 3 of 11 articles
Why I Stopped Writing Smart Contracts Before Auditing Them
Auditing changed how I write Solidity. Once you spend enough time reading production-bound contracts for failure modes, your default design instincts change.
Taking Over a Sprint Mid-Way: A Lead's Playbook
You've just been made Lead on a project mid-sprint. The previous lead is gone. Here's the first 48 hours.
What I Learned Leading a Blockchain Team from 10 to 50+ Engineers
The technical and organisational challenges of scaling a specialist blockchain team — hiring signals that actually matter, managing technical direction at scale, and what breaks when you grow too fast.