ΦQorum

V · Risks

What can go wrong

This is going to be read by people deciding whether to put money in it. Here is the part most projects leave out.

  1. The equities are the issuer's, not ours. Apple, Nvidia, S&P 500 and Tesla on this chain are beacon proxies: Robinhood can pause them, replace the implementation, and burn from any holder — the reserve included. No contract can fix that. What the code does do: a payout leg that refuses to move is booked as owed to you and retried later, so a frozen line can never block a claim or trap a stake.
  2. The frozen rate is irrevocable. If convene() is called at a bad moment, the flow is wrong forever. Nobody — including whoever deployed this — can revise it. That is the price of having no owner, and it cuts both ways.
  3. There is no redemption and no floor. QORUM is a claim on the flow, not a put on the reserve. You cannot burn it to take assets out, and the word "backed" on this site means the flow comes out of real assets — not that anyone will buy your tokens back.
  4. The launch position belongs to its deployer and can be withdrawn at any time. The table keeps whatever it has already collected and the flow is unaffected, but this site will not pretend the liquidity is permanent.
  5. A quiet market is a thin table. The rate is frozen from whatever the first 48 hours actually collected. If nobody trades during the window, the flow is small forever, and no later volume can raise it — later volume only lengthens the runway.
  6. Nothing accrues that the reserve cannot pay. A safeguard rather than a risk: each accrual is capped by what the reserve actually holds, so the table never writes a cheque it cannot honour. The flip side is that a reserve cut from under the flow simply stops the flow, and the parts that were never credited are never owed.

What has been checked

Everything below was run against the live chain or a fork of it, not against a mock of it.

  • 45 unit, fuzz and invariant tests, plus 5 that run on a fork of Robinhood Chain itself.
  • 10 deliberate mutations of the load-bearing lines — the accrual cap, the payout ledger, the neediest-line choice, the slippage guard, the toll's step-down — each one caught by the suite.
  • A full rehearsal on a fork: pool opened, swaps tolled, four real equities bought through the live Uniswap v3 pools, the levy stepping down by itself, the rate frozen, a seat taken, thirty days of flow claimed on all four lines, the stake returned, the position removed.
  • No owner, no admin, no upgrade path and no setter in any of the four contracts.

None of that makes it safe. It makes the failure modes the ones written above rather than the ones nobody looked for.