Skip to content

Security

Email [email protected]. Please include:

  • what is affected: a program and its instruction, a page or an API path;
  • how to reproduce it, ideally as a test against a local copy of mainnet-beta, with the programs’ own test harness;
  • what an attacker could gain or break.

Test on a local copy, never against other people’s funds on the network itself. Give us a reasonable time to ship a fix before you publish. There is no managed bug bounty.

The same contact is published at docs.sagitta.broker/.well-known/security.txt in the RFC 9116 format. Every build regenerates it with an expiry date 180 days out.

Before each release the programs go through free analysis tools and adversarial review rounds:

  • unit, property and fuzz tests of every instruction against the programs’ real builds;
  • a sweep that swaps every account of every instruction for every other kind of account;
  • attack suites and a run of the whole platform on a copy of mainnet-beta, with real pools and feeds;
  • linting with every warning an error, a dependency audit, and size and compute budgets;
  • a reproducible build, whose hash is checked against the deployed program before its upgrade authority is removed.

There is no paid audit.

The launch settings (the market version, the price signers, the quotes, the Chainlink feeds, the stock tokens, the coins blocked from listing and the side tokens’ icon address) were applied once, before any market existed, by the deployer, who then sealed core. Core takes no market before that seal, it opened only once core itself was immutable, and after it the deployer has no power. Every change since goes through the 72 hours timelock:

  • Change settings within their bounds, add or switch off feeds and stock tokens, block a coin, pin a coin’s pool, keep the list of accepted quotes, and add or remove price signers or change their threshold, only through the timelock, on which a hardware key is the only account that can schedule or cancel. After the delay anyone may execute a scheduled operation, but only as it was scheduled; the executor chooses nothing but the moment. The settings are bounded in core: the minimum buy, the minimum cash-out, the executor bounty cap, the reading fee and the caller fee (see Parameters).
  • Set the burner and its spend, through the same timelock: the burner is the program that swaps the vault’s SOL for $SAGITTA, and it must be immutable. Core keeps every other rule of a burn, and a burn spends at most the smaller of 5% of the vault’s free balance and maxSpend, never above 10 SOL, once per period. A faulty burner could misroute at most that one spend per period, and core still requires the token’s supply to fall by at least the floor; never the SOL in pots, tickets, owed balances or markets’ burn shares. See The burn.
  • Pause new buys and tips at once, with the guardian key or the sentinel key, for every market, one version or one market. Only the timelock can unpause.
  • Remove a price signer at once, with the guardian key or the sentinel key. Only the timelock adds one back.
  • Sunset a market or a version. Anyone can then retire its markets: each one freezes at a reading taken after its retirement, and its holders cash out at that price.
  • Register a new version. The old version keeps taking buys until it is sunset, a separate timelock operation; then its buys stop, and its pots stay redeemable forever.
  • Touch the SOL in pots, in waiting tickets, owed to accounts or accrued as fees. No admin path reaches it, and the burn share, sweeps and closes can only go to the burn vault.
  • Change a deployed program. Every program’s upgrade authority is removed once deployed, and core takes new versions and burners only if they are immutable too.
  • Stop cash-outs, deliveries or claims. Cashing out, executing, delivering and claiming never read core’s settings, so no setting, pause or sunset can block an exit.
  • Cancel or change a ticket. A ticket committed before a pause or a sunset still fills at its own reading, buys included.
  • Lower the timelock’s delay below 72 hours, or execute an operation before its delay has passed.
  • Change a setting outside the timelock. The deployer’s one-time setup was sealed in core for good.

Stock token markets and relayed memecoin markets take their prices from readings signed by Sagitta’s price signers (see Relayed prices). That is a trust in the signers, and these are its bounds:

  • Who. Only keys on core’s signer list sign readings, and only the timelock adds one. The threshold is now 1, so one key’s signature is enough for a post. The guardian or the sentinel can remove a signer at once.
  • What. A signer can sign only targets core’s rules allow, each once, inside its window. The price it signs decides each reading’s move, and so how SOL moves between the pots. It can’t take SOL out of a market, change a ticket, choose a ticket’s target or rewrite a stored reading, and a ticket fills only at its own reading.
  • Checked. Every reading is public, listed with its signers and transaction by GET /api/readings, and computed by a fixed rule from the ledger or from Jupiter’s answer for a stated slot. Sagitta’s watchdog recomputes pool readings from the ledger and compares stock readings with its own record or sample of Jupiter’s answer, and on any mismatch the sentinel removes the signing keys and pauses new buys on every market. A reading it can’t check goes to Sagitta’s operators to check by hand.
  • If signing stops, relayed markets wait. Each freezes once its oldest waiting ticket, or its retirement, has had no reading for 7 days, and its holders cash out at the frozen price; a market with nothing waiting freezes 7 days after the first commit made during the silence.
  • Solana itself. The network can slow down, skip slots or halt. Tickets then wait, and readings computed from finished blocks resume where they left off; a market freezes only once its oldest waiting ticket has had no reading for 7 days.
  • The programs Sagitta reads. Raydium, Meteora, PumpSwap and Chainlink’s store can be upgraded by their owners. A pool history market whose observation account stops reading as expected waits, and freezes for silence once its oldest waiting ticket has had no reading for 7 days, with every exit open; a new version follows. Relayed readings are computed off chain, so the signer adapts to a venue change without a new program.
  • Stock token prices. A stock token is priced from its own trading, which can be thin outside its home market’s hours. Only fresh, liquid tokens list, and a listed token that stops qualifying is paused within the hour (see Stock tokens).
  • Payouts to an account that can’t receive them. The site, the CLIs and the API refuse a recipient that could never sign to collect. A payout committed to such an account directly stays owed to it.
  • Every Sagitta site lives on sagitta.broker or one of its subdomains, such as docs.sagitta.broker.
  • A side token’s name proves nothing, and neither does its mint authority: anyone can create a token with any name and hand its authority to any address, a market’s included. Check a token by its address before you trust it: its mint must be the one the market’s page, or the market account itself, lists for that side and epoch.
  • A coin, a stock token or a feed can carry several markets, each with its own pots. Check which one you are in: the site shows each one’s listing age, version and tag.
  • Nobody from Sagitta will ever ask for your key or seed phrase. Your wallet signs every transaction itself, and the CLIs sign on your machine.