The Architect's Brief ✦
Writing
Articles on Blockchain Architecture, AI × Web3, and Engineering Leadership — what holds up in production, and what I'd do differently.
start anywhere — they stand alone
essays so far
pillars
minutes of reading
Fresh off the desk
Three Ways to Add Blockchain to Government Infrastructure
When a state service network wants tamper-evident credentials, the architecture question is not 'which chain?' It's 'where does the network live?' — and each answer costs an order of magnitude more than the last.
Blockchain Architecture · 3 min read
AI as Decision Support, Not Decision-Maker: Lessons From Building a Mentoring Platform
Matching mentors to learners looked like an AI problem. It turned out to be an architecture problem: keep a boring transactional core, put the AI beside it, and make every recommendation explain itself.
2 min read
Bitcoin's UTXO Model vs Account-Based Chains: Why It Matters for Wallet Design
Engineers who know Ethereum usually underestimate Bitcoin. It isn't a different API — it's a different mental model, and coin selection quietly decides both your users' fees and their privacy.
3 min read
Reading lists
L2 operations, wallet flows, and smart-contract risk
- L2 Chains Are Not Hard to Deploy — The Hard Part Comes AfterDeploying 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 YouFireblocks 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 ThemAuditing 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 ExploitedMost staking bugs are not exotic. They come from predictable mistakes in reward math, withdrawal flow, upgradeability, and trust boundaries.
Private-chain verification and regulated-system design
- How We Built Cross-Chain Credential Verification Between a Private and Public BlockchainConnecting 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 GovernmentGovernment 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 ForeverAccount Abstraction removes the EOA bottleneck. Here's what that means for wallet architecture, custody design, and the dApps built on top.
The whole archive
AI × Web3 · 4 of 16