FAQ

Short answers. Where a short answer would be misleading, the answer says so and links the long one.

Is this a security, a share, or a dividend?#

No. RUNTIME ($RUN) carries no equity, no share, no dividend, and no claim on any company. Holding it entitles you to nothing except what these pages describe: weekly usage credits from ongoing inflows (revocable policy) and the right to burn tokens for Workbench credits. Classification under any given law is a matter for regulators and courts, not for our website; what we can state is what the token does, and that it does nothing else.

Is this affiliated with Robinhood or Sunrun?#

No, and no. The token runs on Robinhood Chain, a public, permissionless network; that is the whole relationship. The tokenized Sunrun Inc. equity happens to trade under the symbol RUN on the same chain and has nothing to do with this project. There will never be a liquidity pool between the two. See Verify It Yourself for how to tell them apart by address.

Can I redeem for money?#

No, never, and this is a design invariant rather than a current limitation. The reserve owes work, not dollars. Credits cannot be cashed out, transferred, or sold. If you want dollars, the only path is selling tokens on the open market at whatever the market pays.

Is the backing a price floor?#

No. We never use the words "price floor" except to deny them. The net backing defines a redemption value: what burned tokens buy in machine work. It binds only for someone who wants machine work, at capped daily rates. If trading volume dies, the market price converges toward the backing from above, making it a ceiling, not a floor. If demand for machine work dies too, the economic value is zero regardless of what the reserve holds. The long version is in Risks, point 3.

What exactly do I get for holding?#

If your time-weighted balance over a weekly epoch is at least 1,000,000 tokens: a pro-rata share of that epoch's drip pool, paid as Workbench credits. The pool is at most 25% of that epoch's inflows and shrinks quadratically when backing is below target. Zero inflows, zero drip. Unclaimed drip expires after 180 days. The drip is operator policy and is revocable; a documented fallback replaces it with a usage rebate if legal counsel requires that.

What exactly do I get for burning?#

An irrevocable on-chain claim, credited as Workbench credits worth rho * b per token burned, where b is the current net backing and rho is between 0.85 and 0.98 depending on coverage. Credits are displayed in Runtime Minutes, never expire, and are spendable on jobs, agents, and chat in the Workbench. Caps: $200 per wallet per day, and globally the larger of $500 or 1% of net reserve per day.

Is there a team allocation?#

No token allocation, and not as a promise but as an impossibility: the launcher places 100% of the fixed 1,000,000,000 supply into the pool at launch and burns the liquidity position in the same transaction. No mint, no freeze, no admin key exists. What the team does receive, stated plainly: one third of the project's fee income, 1.00% of trade volume, split off by the same immutable contract that routes two thirds to the reserve. That funds operations from revenue rather than from dilution; there is no premine, and the team earns nothing unless the token trades. The one declared exception on the token side is a pre-announced dev buy of at most 3% of supply, executed inside the launch transaction as a real market purchase at the same fee anyone pays, and locked for 180 days followed by a 360-day linear release, in a contract with no revoke and permissionless release.

Why would I use this instead of a provider's free tier?#

For most people: you would not, and we say so. If you occasionally want to chat with a model, a free tier serves you better. The system is for people who want finished jobs metered in machine time, for wallets and agents that pay for compute without an account, card, or KYC, and for holders who want their drip as usage. See Risks, point 11.

Why is there no staking?#

Any staking yield would be a liability uncovered at zero volume and would break the core invariant that backing per token cannot fall from protocol operations. What exists instead (documented, not yet live) is lock-for-boost: locking tokens multiplies your weight in the existing drip pool without creating any new liability.

Why does the reserve sit in plain USDC instead of earning yield?#

Because we checked, and the honest answer is on The Reserve: the advertised 7% on this chain was unreachable in practice (deposits return maxDeposit = 0 for external addresses) and mostly a promotional subsidy, and at current reserve sizes the realistic ~4% elsewhere earns roughly $1,800 a year against a class of vault failure that actually occurred three times in twelve months in the ecosystems we evaluated. A credibility anchor does not moonlight.

What is a Runtime Minute?#

1 RM = 20,000 input tokens plus 4,000 output tokens on the Sonnet-class reference model at its current published list price. Every RM figure comes with its model range (the same credits run longer on cheaper models) and its labelled dollar basis. Full definition: The Runtime Minute.

How do I know a token calling itself RUNTIME is really you?#

Only by the contract address published on this site. Names and symbols on this chain can be freely copied; no launch venue deduplicates them. Until an address is published here, no RUNTIME ($RUN) token exists and anything offered under the name is a fake. After publication, verify with the commands in Verify It Yourself.

What happens if I send tokens directly to the contract or the dead address?#

They are destroyed without credit. Only the approve-plus-burn flow through the BurnRedeemer creates a claim. Tokens sent directly are forwarded to the dead address by a permissionless sweep, explicitly without crediting anyone, and are not recoverable. The redemption screen never shows a copyable address for exactly this reason.

Is the system decentralized?#

The claim registry is: burns and claims live on-chain, append-only, with no owner, no admin, and no upgrade path, independent of us and of our database. Everything else in v0 is not: valuation, caps, custody, the drip, and the weekly controller are operated by the team against published formulas. A documented hardening path moves valuation attestation and the controller on-chain. Anyone telling you the whole system is trustless today is wrong, and that includes us if we ever say it.

Where do I check your numbers?#

Verify It Yourself. The short version: the burned supply and reserve balance are on-chain reads anyone can make, the open /api/stats endpoint returns every input to the backing calculation with per-field provenance, and the controller formulas are published so you can recompute next week's parameters before we post them.