_gammadocs
Security

Security

How _gamma stays non-custodial — on-chain vaults, hardware-backed key management, multisig-gated policies, reviewed contracts, and continuous risk control.

Non-custodial design

_gamma never takes custody of your assets. When you deposit, your capital moves into an on-chain vault program and you receive share tokens — standard SPL tokens held in your own wallet. Those shares are your claim on the vault's Net Asset Value. The Gamma Economic Agent (G.E.A.) that runs a vault is an optimizer, not a custodian: it decides how pooled assets are allocated across vetted protocols, but it cannot pay them out to itself or to any wallet it chooses.

The vault is a Solana program with rules baked into its instructions. Only the holder of the share tokens can redeem them, and withdrawals settle to the redeeming wallet. The agent's signing authority is scoped to allocating into and out of approved protocols — not to sweeping funds out of the vault. Deposits and withdrawals are blocked when the published NAV is stale, so you can never enter or exit at a mispriced value. There are no lock-up periods, and your right to claim is enforced by the program, so even in the unwinding window your funds are never in limbo (see Deposits & withdrawals). What you trust is narrow and auditable: the vault program that holds funds and enforces redemption, the on-chain policies that constrain what the agent may touch, and the key-management system that guards the agent's signing key. You do not trust _gamma with custody, because it never has it.

Key management

Each G.E.A. signs its transactions through Google Cloud KMS. The signing keys are hardware-backed keys managed in Google Cloud KMS; key material is never exposed to application code, never written to disk, and never exported. Signing happens inside the KMS boundary.

This means a compromise of _gamma's application servers does not expose an agent key. The most an attacker in that position could attempt is to request a signature — and agent operations are governed by multisig-gated policies restricting which protocols and instructions agents may use, with every signing request recorded in an audit log. Keys can be rotated on a managed schedule, access to request signatures is scoped narrowly following least-privilege principles, and a valid signature still only authorizes actions the vault permits, not arbitrary transfers. No single failure — a leaked server credential or a compromised process — is enough to move user funds.

Protocol policies

A G.E.A. does not have free rein over the funds it manages. Its operations are governed by multisig-gated policies restricting which protocols and instructions agents may use, so the set of things an agent can do is a small, reviewed, enumerable list. Policy is expressed across several dimensions:

Dimension What it controls
Approved protocols Which programs and destinations the agent may interact with.
Operation types Which instructions/operations are permitted.
Position limits Caps on exposure to any given protocol or position.
Emergency controls The ability to pause activity if something goes wrong.

These policies are not something _gamma can change unilaterally at runtime. Adding a protocol, changing a limit, or altering what the agent may do is a multisig-gated action requiring multiple signers, which keeps the permission set reviewable and slow to change. Quantitative caps work together with the risk framework's provider tier caps and diversification constraints (see Risk management) to keep the portfolio from concentrating into any one venue, and emergency controls can halt agent activity if a protocol shows signs of trouble. The agent optimizes continuously and signs its own transactions, but its worst case is bounded by that reviewed permission set, not by trust in a single operator or key.

Smart contracts

User assets live in _gamma's on-chain vault programs on Solana. These programs enforce the properties above: only share holders can redeem, and the agent cannot pay funds to arbitrary destinations. Because so much of the platform's safety is enforced in these contracts, their correctness is foundational.

The contracts undergo independent security review; upgrades follow a controlled release process rather than instantaneous unilateral pushes — changes are multisig-gated so that no single key can alter the programs on its own. We deliberately do not enumerate specific firms or findings here so this page stays accurate over time; refer to the official _gamma channels for the current, dated details. If you believe you have found a security issue, please report it privately through the official contact channels rather than disclosing it publicly.

You do not have to take the security model on faith:

Property How to verify
Vault holdings Read the vault's on-chain positions directly.
Share price / NAV Recompute NAV / total shares from chain state.
Your position Your share balance and withdrawal receipt are on-chain.

Risk management

Earning yield in DeFi means taking on real risks — smart-contract, market, and protocol risk among them. _gamma's approach is not to eliminate risk but to measure it continuously and constrain exposure so no single failure dominates a vault, automatically, as part of every rebalance.

Each protocol a G.E.A. can use is scored on an ongoing basis — audit history and code maturity, TVL history and stability, incident record, and liquidity depth. These scores feed the ML solver, which optimizes yield against risk rather than chasing the highest headline rate. To prevent concentration, providers are grouped into tiers with caps on how much of a vault can sit with any one provider, forcing diversification even when one venue temporarily offers the best yield. Staleness filters on ingested rates, prices, and liquidity, on-chain cross-checks of provider-published data, and NAV freshness gates in the vault program guard against bad data. Where strategies use leverage (for example leveraged staking loops on the SOL vault), the agent continuously monitors position health factors and automatically deleverages if liquidation risk rises — a mechanical response that does not wait for human intervention.

Risk Mitigation
Smart-contract Independently reviewed programs, vetted protocols, responsible disclosure.
Market Risk-adjusted sizing, hedged strategies, position limits.
Protocol Continuous scoring, diversification, provider tier caps.
Data / pricing Staleness filters, on-chain cross-checks, NAV freshness gates.
Leverage Health-factor monitoring, automated deleveraging.

None of this makes a vault risk-free. Yields are variable and not promised, underlying protocols can fail, and market conditions can move against a position. What _gamma provides is disciplined, continuous, on-chain-verifiable risk control — exposure that is measured, capped, and diversified rather than left unmanaged.

Next: Getting started