> For the complete documentation index, see [llms.txt](https://docs.gage.cash/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gage.cash/protocol/status.md). # Audits and status Mainnet status, the security review, verified source, who owns which contract, and how to report a vulnerability. gage launched on **Robinhood Chain mainnet (4663) on 7 September 2026**. The live app is [gage.cash](https://gage.cash). The [contract directory](/protocol/addresses.md) lists the deployed addresses, each contract's purpose, pools, owner and seed position; the served [deployment manifest](https://gage.cash/api/deployment) is the machine-readable copy the app itself reads. ## Security review [Pashov Audit Group](https://www.pashov.com) reviewed the partner-lending contracts and the loan engine they lend through, from 28 September to 12 October 2026. The report and the code it reviewed are public in [DebenLabs/gage-audit](https://github.com/DebenLabs/gage-audit), with the commit hashes the report prints: the review ran at commit `0638b91a3bcdfc417ae09f4baf23299d5110f85e`, and the fixes were reviewed at `c4c6f7773449eb1f21a10faf6abe18ce852d326e`. The report lists 10 findings, 6 Low and 4 Informational, all marked fixed. * **In scope:** the Intent factory, vault, vault state, quote verifier, fill router, fee math, asset policy, lender market and reserve lens; the GradeRegistry; the V2 engine with its token collateral account, rewards and token registry; and the cash-out router and legacy adapter deployed with the engine. * **On mainnet:** the live partner-lending generations carry the first round of fixes. Two follow-ups reviewed on 16 October arrive with the next contract generation: a factory that creates no vault before its fill router is bound (L-02, L-05), and a recapitalization that pays a write-off's holders of record rather than the share price (I-01). Until then every live factory's fill router is bound, and no live vault is recapitalized. * **Outside the review:** among others DealVault and the extension vaults, the earlier engines, the Earn strategies and their factory, the token layer, the loop and rollover routers, and the private lane. ## Source verification All **17 launch contracts** have successful creation- and runtime-bytecode matches on Sourcify: 15 gage contracts plus the Pons-created GAGE token and bonding curve. The 15 gage contracts report `match` because their build omits CBOR metadata; the two Pons contracts report `exact_match`. The contracts deployed since launch have Sourcify records too: the extension vaults and their registries, the earlier engines [`0x0856…`](https://repo.sourcify.dev/4663/0x08561c817a5bf5230f91c001800449f047e4c07d) and [`0xfee7…`](https://repo.sourcify.dev/4663/0xfee799ade96229c2c128bc5ed9e55f8d9d01a7e9) and their adapter [`0x2166…`](https://repo.sourcify.dev/4663/0x2166a547bc27fef846c9858e3101b84d1a8d994e), each with a `match` record; the original engine `0x2265…` has none. So do the partner-lending contracts: the USDG generation's factory [`0x20a9…`](https://repo.sourcify.dev/4663/0x20a908d82885cf4e990a9f8f3f5a483687660822), core [`0x856e…`](https://repo.sourcify.dev/4663/0x856e4232469b957150cb29a8ce9b60059449e87e), registry, rewards, fill router, quote verifier, cash-out router and adapter; the loop, rollover and private borrow routers; the GLD and NVDA generations; every generation's rollover router; and the Privacy Pools Entrypoint and pools. The HIMS generation's contracts, other than its rollover router, have no Sourcify record yet. Any deployed address can be checked at `https://repo.sourcify.dev/4663/
`. In the directory every contract with a Sourcify record has a direct Sourcify link, and every contract a Blockscout activity link (`https://robinhoodchain.blockscout.com/address/
`). Native Blockscout checkmarks have not been confirmed for every address; use the Sourcify records as the source-verification evidence. **Source verification is not a security audit.** It lets readers compare source code with deployed bytecode. Repository tests and internal checks are not a substitute for an independent audit, and the security review above covers only the contracts it lists. ## Ownership and authority Two keys hold roles. The Safe **`0x30e8E13E62DFcd063AF763aB29501FeE74C4918e`** (1-of-2) owns the configuration contracts; the deployer **`0x86514e45293fcf111ED8A6bDA7c8bca4A64Dd9E5`**, an EOA, runs operations. The vault contracts have no owner. * **No owner, no upgrade path:** DealVault, the LP extension vaults, the native engines (the Intent cores among them), LPRewards, the Earn strategies and the partner vaults. Their settlement and withdrawal rules are in their deployed code. * **The Safe** owns the legacy CollateralRegistry, FeeSink, Emissions, FeeFloor, DealFeeRouter, the two extension registries, the registries and cash-out routers of the native engines, the Intent factories, the loop and rollover routers, the second-design HybridFactory, the EarnFactory and the GradeRegistry, and it is the admin of the Intent core's adapter. The transfers were accepted at block 62,622,930 on 14 September 2026; the Earn factory and grade registry were the Safe's from their first block. What each owner can change, and within which bound, is on [Parameters and bounds](/protocol/parameters.md): allowlists, limits, terms, fees and pauses on the registries; swap routes on the cash-out routers; the fee route and purchase thresholds; the epoch shares; strategy creation and the protocol fee recipient. * **The Safe** also owns the private lane's `PrivateBorrowRouter` and holds the owner role of gage's Privacy Pools Entrypoint (0xbow v1.3.0, deployed unchanged). The pools have no owner. The router and gage's deployment of the pools shipped unaudited at launch and join gage's next audit. * **The deployer** owns DealRewards and posts the epoch reward rates. It is also the deployer of the launch contracts, the admin of the two earlier legacy adapters (which engine each serves, for new loans only), the keeper, the curator and fee recipient of the two Earn strategies, and the seed recipient. It cannot withdraw a depositor's balance from a strategy or move any user's collateral or USDG. * **The seed position**, NFT 2126377, is held by CompoundingSeedTimelock until **7 September 2027, 19:25:26 UTC**, with its fees compounding into the same position. After that, anyone may trigger release to the fixed recipient, the deployer. Fee-funded floor bands have different custody and exit rules; see [The sGAGE floor](/pool/the-floor.md). These are the settings today. Read `owner()` and the configuration views on the contracts for current values. ## Reporting a vulnerability The [Bug bounty](/protocol/bug-bounty.md) covers contract scope, rewards, Immunefi severity standards and rules of engagement. Report privately through the form at [gage.cash/bugbounty/report](https://gage.cash/bugbounty/report), or as an agent through the support API with an x402 deposit, see [Submit a finding](/ai-agents/api.md#submit-a-finding). Do not post vulnerability details publicly. ## Licence Consult the SPDX headers of the matched sources. External Pons and Uniswap dependencies retain their own licences. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.gage.cash/protocol/status.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.