Pillar · reference · v3.0 · updated August 2026 · 9,400 words
Enterprise blockchain
A working reference for architects deciding whether a distributed ledger belongs in a system, and what it costs to run one inside an enterprise. Written from delivery experience, including the parts that went badly.
Written and reviewed by practitioners who have delivered these systems. Ungated, citable, and versioned — the changelog records what changed and why.
- Hubs
- 8
- Articles & tutorials
- 61
- Glossary terms
- 64
- Capability page
- Blockchain architecture & advisory
8 hubs
- 01
When a ledger is the wrong tool
The authoritative-record question, and the engagements that should end at it.
7 articles - 02
Chain selection
Finality assumptions, operating cost, tooling maturity, and the shortlist that follows.
9 articles - 03
Custody & key management
Signing boundaries, approval policy, key ceremonies and holder attrition.
8 articles - 04
Contracts and upgrade governance
Who can change the code, under what approval, and what an auditor makes of it.
8 articles - 05
Integration architecture
Adapters, idempotency, the signing boundary and the systems of record.
9 articles - 06
Reconciliation and the daily close
Tolerances, break procedures, and the record that is authoritative while a break is open.
7 articles - 07
Failure modes
Silent drift, key-holder attrition, upgrade capture, bridge exposure.
7 articles - 08
Cost and timeline
What a production deployment costs to run, and where the estimate goes wrong.
6 articles
Published in this pillar
- Technical14 min
Threshold signing fails at the rate your staff resign
A 3-of-5 signing policy looks conservative on the day it is designed. It is a headcount bet, and most institutions lose it within eighteen months — quietly, because nothing breaks until the day a signature is needed.
- Technical11 min
Chain selection under a finality constraint
How an accounting system’s finality assumption decides the shortlist before throughput does.
- Technical13 min
Custody design for tokenized reserves
When an instrument is redeemable against a physical reserve, the custody boundary and the reconciliation model are one design.
- Tutorial18 min
Building a reconciliation job against an EVM chain
A working example: idempotency keys, reorg handling, and a documented break procedure.
- Technical10 min
Upgradeable contracts as a governance question
Who can change the code, under what approval, and what that means to an auditor.
- Tutorial12 min
Key ceremonies that can be repeated
A ceremony performed once, by the people who designed it, proves very little. Designing one an operations team can run without you is the deliverable.
- Announcement6 min
The practice, and this site
What changed in the architecture of mlgblockchain.com, and why the old service pages now point here.
Changelog
- v3.0Failure modes promoted to their own hub after two post-mortems.
- v2.0Reconciliation separated from integration architecture.
- v1.0First publication.
For machine readers
TechArticle and DefinedTermSet markup, a stable citation block, and /llms.txt. Nothing here is gated or paywalled.
Other pillars
The term contract: The build — 250 terms here · The capital — gda.group · The coordination — flashygroup.com. One term, one home.