Transparency
Operated by AI, verified by chain
GBLIN is run as an experiment in machine-operated finance: the analysis, engineering and day-to-day operations are performed by AI systems, the balance sheet lives entirely on-chain, and the only human role is to sign. We do not ask anyone to trust this claim — every item below links to evidence that exists outside our control.
Honest scope: AI operation does not make the protocol risk-free, and GBLIN is volatile crypto exposure with a defensive policy — not a stablecoin and not financial advice. What AI operation changes is verifiability: policies are code, actions leave receipts.
Division of labor
AI operations
Reviews, code fixes, documentation, releases, risk analysis, strategy research, market monitoring, content drafting.
Autonomous contract
Target weights, Crash Shield activation and decay, fee accrual, the rebalancing auction — executed on-chain with no operator.
Human founder
Signs transactions (timelock schedule/execute, registrations), pushes releases, and can veto any scheduled change within the 48h window. Nothing else.
Claims and evidence
The risk policy is public code — and it has already acted on its own on mainnet.
On June 5, 2026 the Crash Shield of the previous index contract autonomously cut the WETH target weight from 45% to 9% after ETH crossed its drawdown threshold. No human intervened. The vault in service runs the same shield.
CrashShieldActivated tx on Basescan ↗Governance is a 48h public timelock.
The vault in service and its sequencer sentinel are owned by a 48-hour OpenZeppelin timelock, which also owns the previous index contract. Every parameter change is scheduled in public, bounded in code, and executable only after the delay.
GblinTimelockController on Basescan ↗The agent tooling is AI-built and published in public.
The open-source MCP server (20 tools, free by default) is maintained with AI-driven reviews and releases: each release is reviewed, corrected and published end-to-end by AI operations, with the human signing accounts only.
@gblin-protocol/mcp-server on npm ↗The protocol is listed in the official MCP Registry.
io.github.gblinproject/gblin-treasury-risk-regime — every version is published through the official mcp-publisher flow, with the hosted endpoint listed as a remote.
MCP Registry entry ↗All source code is public.
Contracts, webapp, MCP server, bots: every component that operates the protocol is open source and readable, including the history of AI-authored changes.
github.com/gblinproject ↗For a century, risk was an opinion you paid for. We are building it as an observable you verify: public policy code, signed risk attestations, and a treasury anyone can redeem in-kind at any time.