[gage]
Loading wallet…
Audited by
TERMS

Terms

These terms cover the interface at gage.cash, the public docs, the API, SDK and MCP server, reminders, support and the bug bounty. The deals themselves are governed by the contracts' code. This page says how each part works and what it does not do.

UPDATED 21 September 2026

What gage is

  1. 1gage is a set of contracts on Robinhood Chain (chain ID 4663) and an interface to them. The interface at gage.cash is one way to use the contracts. The contracts do not depend on it and keep working if the interface is unavailable.
  2. 2The deal contracts are immutable and have no admin path to user funds. Nobody, the gage team included, can move a user's collateral or USDG, delay a reclaim, accelerate a claim or reverse an outcome.
  3. 3The contracts around a deal (the collateral registry, fee routing and reward rates) have an owner. The owner is the deployment wallet listed on the status page, a single key that is not a Safe. Its powers are bounded in code and apply to new deals only; nothing the owner does changes a deal that is already funded.
  4. 4No liquidation means: nothing can touch your collateral before expiry; at expiry you choose. No price triggers anything in the deal path.
  5. 5gage.cash is published by the team behind it. USDG, Stock Tokens, GAGE, sGAGE and the pools they trade in are issued or operated by others, or by their own markets, not by the team.

Deals

  1. 6A listing is not a loan until it is funded. A deal has one bag of collateral, one cap in USDG and one date. The cap is fixed when the deal is funded and never grows.
  2. 7In the current version a deal can be funded in quarters by one or more lenders. The deal starts only when all quarters are funded. Until then the borrower receives nothing, no fee is charged, and a lender can withdraw a commitment. A listing that misses its funding deadline can be ended and its lenders refunded.
  3. 8Before expiry the borrower chooses: pay the full cap and reclaim, or walk away. When the term ends, repayment closes and the lenders may claim the collateral. Loans funded on the earlier engine keep the 48-hour grace window they were funded with, in which only the borrower can act. Walking away is a legitimate outcome, not a breach of these terms. Every outcome is final once its transaction executes.
  4. 9The right to reclaim can be sold whole to someone else through the interface. The buyer pays the seller an agreed price and, to take the collateral, must still pay the full original cap before a claim executes. A sale does not repay the loan, reduce the cap or restart the term.
  5. 10A cash-out route can repay the cap by selling the collateral in one transaction and credit you the remainder. It depends on supported routes and available liquidity. If the sale cannot meet the required minimum the whole transaction fails and the position stays open.
  6. 11Deals funded under an earlier version (the original deal contract and the companion LP deal contracts) keep the rules they were funded under. The docs say which rules apply to which contract.
  7. 12Which tokens, pools, terms, caps and sizes are allowed for new listings is set by the owner within the bounds in the contracts and can change at any time. A change never applies to a deal that is already funded.

Fees

  1. 13The current fees are a 1% origination fee on the gross amount funded, deducted when the deal starts; a 1% sale fee on reclaim rights and supported lender-position sales through gage, deducted from the seller's proceeds; and a 0.5% cash-out fee on the cash that remains after the full cap and financing costs. Paying the cap from your wallet carries no cash-out fee.
  2. 14Every fee is shown as an amount and a percentage for the term before you sign. Network gas is separate, set by the chain and paid by you.
  3. 15Fees are collected by the contracts and used to buy GAGE and place it in permanent GAGE-only floor bands in the GAGE/sGAGE pool. Purchases are batched, so a fee does not cause an immediate market buy. The floor adds liquidity at set prices; it does not guarantee a market price or unlimited exit liquidity.
  4. 16Fee levels can change for new deals within their compile-time bounds. A change never applies to a deal that is already funded.

Rewards and tokens

  1. 17sGAGE rewards for deals and for liquidity are paid from weekly budgets that the owner sets within bounds. When a week's budget is gone, deals funded later that week earn no sGAGE. The protocol can run with zero rewards, and a deal that started with none does not gain them later.
  2. 18Rewards unlock gradually over the deal term or, for liquidity, over seven days. No function, owner or otherwise, releases sGAGE ahead of the curve. In the current version, closing a deal early stops further rewards for both sides; what was earned stays earned.
  3. 19Any figure shown in USDG for sGAGE is an estimate at the current pool price. GAGE and sGAGE have no promised value. Nothing in the protocol guarantees a price, a market, a buyer or exit liquidity for either token.
  4. 20Reward rules, rates and the split between deals and liquidity can change for future weeks within their bounds. Rewards already granted to a deal or a position are not taken back.

Token listings are not endorsements

  1. 21Listing, displaying or supporting a token or liquidity pool on gage does not constitute an endorsement of that asset, its issuer, its team or its project. This includes allowing it as collateral or showing a rating, valuation or suggested terms. None of these is a recommendation to buy, hold, sell, borrow against or lend against the asset, or a guarantee of its safety, legitimacy, value, liquidity or future performance. You are responsible for assessing the asset and its risks before using it.

Prices and information

  1. 22The interface shows values from a valuation service that reads pools on the chain, and says where each value came from. The contracts never read a price. Every value on screen is a reference estimate, not a quote, and can differ from what a sale would return.
  2. 23Suggested caps, recommended ranges, returns and annualised figures are arithmetic on those estimates. They are shown so you can decide. They are not a recommendation to list, fund, hold or sell anything.
  3. 24Nothing on gage.cash, in the docs, in the API or from the team is financial advice.

Your responsibilities

  1. 25You control your wallet and your keys. gage never holds them, cannot recover them and cannot reverse a transaction you signed.
  2. 26You are responsible for reading each transaction before signing it. The interface shows the amount, rate, minimum and approvals; the transaction you sign is what executes.
  3. 27You are responsible for your deadlines. Reminders are a convenience and can fail. If you miss the deadline, the lender keeps your collateral.
  4. 28You must not use the interface, the API or an agent to attack the contracts, to interfere with other users or their transactions, or to test exploits against live funds. Security research follows the bug bounty's rules of engagement.
  5. 29If an agent or someone else acts through your wallet, what it signs is yours.

The interface, the API and agents

  1. 30gage.cash, the docs, the API, the SDK and the MCP server can be wrong, slow or down, and can be changed, rate-limited or withdrawn at any time. The contracts continue regardless.
  2. 31Transactions prepared by the API are unsigned and simulated. Data from the API is a reference, not an executable quote and not a judgement that a deal or an asset is suitable. The wallet that signs is responsible for what it submits.
  3. 32Robinhood Chain and its sequencer, Uniswap, the issuers of USDG and Stock Tokens, wallets, RPC providers and hosting are run by others. gage does not control them and is not responsible for their outages, changes or actions, including an issuer pausing a token.

Support, reminders and the bug bounty

  1. 33The interface has no accounts. It keeps a few flags in your browser, such as that you read the first-visit notes, the links to your own support tickets and the wallet you last connected, and records page views and a few product events (a door clicked, a wallet connected, money sent in or taken back out, an error code shown) through Vercel Analytics and a self-hosted Umami, with ticket links and loan numbers stripped and never a wallet address or an amount. Everything you do on the chain is public by nature.
  2. 34Contact support sends your message, the page you came from, and an email address and wallet if you give them, to the support service. Tickets are relayed to a private team channel on Discord and, if you gave an email, answered there through our email provider as well. Team members read tickets. We keep them so a conversation can be continued; send a ticket asking for deletion and we delete yours.
  3. 35Reminders store your wallet, the channel address you chose (a Telegram chat, an email or a push subscription), your preferences and the signature that authorised them. The Telegram portfolio bot lets anyone watch a public address without proving ownership. You can unsubscribe at any time; a message already sent cannot be recalled. Bot analytics keep only the chat, a command category and a time, for 35 days.
  4. 36A bug bounty report asks for a refundable deposit of 15 USDC on Base, paid from your wallet. The deposit is returned for every valid report, whatever its severity, and stays with gage for duplicates, claims that cannot be reproduced and spam. One report per wallet per day. The team decides validity and severity using the Immunefi classification; Immunefi does not host or guarantee the programme. Rewards follow the bug bounty policy. Report contents are stored on the support service and read by the team.

Changes and contact

  1. 37This page changes as the product does. The date at the top moves when it does. Nothing here changes a deal that is already funded.
  2. 38Questions go through Contact support on this site, or to @gagedotcash on X and Telegram.

Read this together with the Risk disclosure.