The design is discovered, not invented.
I work with funded Web3 founders to find the right protocol architecture and carry it into a frozen specification. From there I build the contracts and public product, deploy the testnet, prepare the system for third-party audit, remediate the findings, and deploy to mainnet.
Built with you. For your vision.
From reserve architecture to a working omnichain testnet.
Global Gold began with a founder’s conviction: gold should be able to move through onchain markets as money again. I worked with Cole Chapman to translate that vision into protocol and token architecture. The protocol specification then moved through fifteen adversarial review rounds — R0 through R14 — and the vault specification passed five review gates of its own before production code began.
The system that followed combines a reserve-backed gold routing asset, liquidity steering, dynamic-fee markets, governance infrastructure, and omnichain transport. Its testnet deployment spans four chains connected through one LayerZero V2 mesh, with a custom frontend and an investor-facing demo surface.
The build is prepared for technical diligence and third-party audit handoff. It is testnet work — not a mainnet deployment.
One of the most important decisions was what not to keep. A CDP model was built and carried to the first testnet, then retired — the basket vault’s direct mint and redeem was the right architecture. Part of finding what should exist is retiring what should not.
The full case study covers the design, the build, the changes, and the work ready for review.
Seven steps. One continuous thread.
The seven steps settle decisions in sequence; each leaves the next an artifact to build on. The vision never changes hands. The mandate stays the same throughout: decentralization must survive the translation from a founder’s conviction into a system people can inspect, review, and operate.
Discovery
Discovery ends when the founder and I share an understanding of the technology under design.The architecture briefProtocol Architecture
Protocol architecture comes first — users, roles, value flows, system boundaries, integrations, and the core technology stack — before the formal token design begins.The system mapToken Architecture
With the protocol standing, the token is designed into it — tokenomics, incentives, emissions, vesting — and checked with economic simulations until protocol and token integrate into the complete Web3 architecture.Token architecture · incentive model · simulationsThe Translation Phase
Systems language becomes smart-contract language. Every contract, invariant, flow, architecture decision, and protection is resolved into a build-ready specification, reviewed adversarially, then frozen.The frozen specification · system + security architectureSmart Contract Development & Testnet Deployment
The specification becomes contracts, tests, security infrastructure, deployment tooling, and a working testnet — built and reviewed in waves, rehearsed, deployed, and tested end to end.Contracts · tests · review record · deployed testnet · runbookFront-End Development & Optional Gamification
A fully custom public product, with every user flow derived from the protocol architecture — connected to the testnet, tested end to end, and made observable through the Observatory.The finished product · testing scenarios · the ObservatoryPre-Mainnet Prep & Mainnet Deployment
I prepare the third-party audit handoff and oversee the pre-mainnet prep — remediation, final security and tokenomics passes — then deploy to mainnet.The audit-corrected system · security plan · mainnet deploymentThe system leaves a record.
The build does not end as code alone. It leaves founders and technical teams an operable, coherent system, plus a record a third-party auditor can pick up cold.
Frozen specification · findings ledger · invariant output
Deployment manifests · runbook · security controls
Finished frontend · tested user paths · Observatory
Audit correction · finalized security plan · mainnet deployment
One thread. Your vision stays yours.
I work with you through a weekly anchor call and report, with async calls and working sessions as the work requires. The architecture, decisions, risks, and next build targets remain visible throughout the engagement. You and I refine the vision together — you bring the conviction and the corrections; I bring the architecture and the execution. The vision stays yours the entire way. When the build is handed off, all of it is yours.
Decisions, open questions, risks, completed work, and next build targets — reviewed together each week, with working sessions between anchors when the work requires them.
Written from the actual work: timestamped, artifact-linked, tied to the current state of the spec or build.
The spec is the ruling document. If the vision deepens, the spec changes. If the spec changes, the build changes.
Issues are tracked, reviewed, remediated, accepted, or explicitly carried forward. Nothing important disappears into chat history.
The build stays legible to your CTO and security team at every step — it lives in artifacts, not in one person’s head.
I am Austin Seiberlich. Since founding Coincraft in 2022, I have shaped token economies and Web3 systems for 40+ companies — full protocol architecture, vesting design, simulations, incentive mechanics, and economic review.
Global Gold changed the scope. I crossed the line from architect to builder and carried the Global Gold protocol suite from idea to spec, contracts, adversarial review, four-chain testnet, and investor demo.
Prior work includes Heale, Kino, Pangea, Anyone Protocol, Altcoinist, Ready Games (later Play Network), Entangle, and ZeroLend.
I now build the systems I used to architect.
From the public record“Central to this paper is Austin Seiberlich of CoinCraft; a seasoned tokenomics expert. He brings his highly deductive and logical approach to the new mechanisms for the ANYONE token, often building a rationale from first principles.”
— The Foundation For Anyone · Anyone Protocol tokenomics
Tell me what you are building.
The first call starts with your system — and ends with how I would build it. If there is no fit, I will say so, and tell you what to do instead.
[email protected]