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

16

essays so far

3

pillars

44

minutes of reading

Fresh off the desk

Latest ✦

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 × Web3

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

Blockchain

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 & smart-contract risk

L2 operations, wallet flows, and smart-contract risk

  1. 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.
  2. 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.
  3. 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.
  4. 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 chains & regulated systems

Private-chain verification and regulated-system design

  1. 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.
  2. 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.
  3. 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

Blockchain Architecture · 9 of 16

Blockchain ArchitectureSep 27, 2026 · 3 min

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 ArchitectureJul 9, 2026 · 3 min

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.

Blockchain ArchitectureApr 30, 2026 · 4 min

Hyperledger Fabric Is Not a Database: What Changes When You Think About It as a Network

Most Fabric projects that struggle make the same mistake: they treat the ledger like Postgres with signatures. The design gets easier once you model it as what it is — a network of organisations agreeing on shared rules.

Blockchain ArchitectureApr 3, 2026 · 2 min

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 ArchitectureApr 2, 2026 · 2 min

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.

Blockchain ArchitectureMar 27, 2026 · 2 min

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.

Blockchain ArchitectureMar 20, 2026 · 1 min

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.

Blockchain ArchitectureMar 20, 2026 · 4 min

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.

Blockchain ArchitectureFeb 18, 2026 · 6 min

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.