Tell me what you are building.
I work with founders, funds, and protocol teams building serious decentralized infrastructure — systems where the economy, contracts, liquidity, governance, frontend, and audit path all have to make sense together.
Built with you. For your vision.
Flagship: Global Gold — four-chain testnet, audit handoff prepared · Since 2022 · 40+ companies
Six things make the first conversation useful.
Do not include private keys, credentials, or confidential implementation details. Share enough for a useful first read.
- Project stageIdea, partial build, funded and ready, audit prep, or rescue situation
- Chain targetsL1, L2, omnichain, appchain, or undecided
- TimelineRaise, demo, audit, testnet, launch, internal milestone, or rescue deadline
- Raise statusBootstrapped, pre-raise, raising, funded, treasury-funded — or prefer to discuss privately
- Existing codebaseNo code, partial repo, working prototype, testnet deployment, audit findings, or production system
- Open questionThe main question still unresolved — economic architecture, mechanism design, cross-chain state, technical scope, security boundary
If someone introduced you, mention them.
Three steps.
I read the note myself. If there is no fit, I will say so.
The first call is a fit check: what you are building, what is real, what is broken, and where architectural ownership would help.
If there is fit, I send a brief written scope sketch recommending where the work should start, what I think the project needs next, what I would not do yet, and where the risk lives.
The work starts at the place where a wrong architecture decision would cost you the most.
The first conversation determines which starting point fits.
Clarity
“The idea is strong, but the economic machine is not coherent yet.” I review the concept and its economics from first principles. You walk away with an architecture direction: mechanism map, risk surface, recommended build path — and “do not build this yet” warnings where needed.Spec freeze
“We are about to spend serious money building — and the design still has holes.” The economic design becomes a frozen, build-ready specification covering contract boundaries, permissions, invariants, and failure modes. Builders, CTOs, investors, and security auditors can pick it up cold.Full protocol build · the flagship commission
“We need the protocol to exist — not just be described.” The frozen specification becomes contracts, tests, security infrastructure, a deployed testnet, and a finished public product. I prepare the third-party audit handoff, remediate the security firm’s findings, finalize the security plan, and deploy to mainnet. The full method ends with deployment. Global Gold records this path through step 6; its step 7 remains ahead.Rescue
“We already built it — and we no longer trust it.” The rescue starts by stopping the drift. I diagnose from the architecture down, simplify the system, and rebuild the part that matters. The deliverables: diagnosis, rewrite plan, rebuilt spec, audit handoff.Who this is for — and who it is not.
- Funded protocol founders
- RWA and asset-backed systems
- DeFi protocols
- Omnichain liquidity or governance systems
- Teams preparing for serious audit
- Funds with portfolio companies needing architecture-level help
- Teams with broken or confused builds
- Founders who need a built, deployed system
- Founders who want economic architecture and implementation held by the same mind
- Simple landing pages
- Generic NFT drops
- Shallow token launches
- Pure Web2 apps
- “Just write these contracts” staff augmentation
- Builds chosen on price alone
- Projects scoped without architecture
- Founders who want to skip spec and “just start coding”
The first note can be simple.
Share the project stage, chain targets, timeline, raise status, existing codebase, and the main question still unresolved. If some of that is undecided, say so. That is enough for me to understand where the conversation should begin.
If someone introduced you, mention them.