Governance

Receipts and checks

Raw receipt log · Ballot package · Finalization check

Copies of the log and the collector's signed head are mirrored at github.com/qvotvm/qip-1-receipts.

Voting weight at B: ledger.json and ledger.csv, with the SHA-256 committed in the ballot package. The ledger at B replays the official RPC's Transfer and staking logs and must match balances read at B from rpc.nodeflare.app, the only public reader we found that serves that block's state; the independent check runs separate code against the same node, so the two readings do not come from independent sources.

Package hash

Unavailable

Log head

Unavailable

Anchor wallet

Unavailable

Collector public key

Unavailable

Proposal

Published for the QIP-1 ballot. No floor is active before its activation record.

In short

Each QUOTUM seat has an inference cap for the session: a maximum it can use, not a guaranteed grant. The contract sets that cap from measured input, roughly a day of net NVDA inflow into the sink, split across the seats at opening. Measured input has fallen, and caps fell with it: $50 per seat in session 10, $2.40 in session 23. The sink also holds a reserve, about $7,300 free on 21 October, that the contract does not turn into caps on its own.

QIP-1 asks whether quotum should give each seat at least $10 per session for up to 14 sessions, when safety checks pass, with the sink reserve absorbing the extra use and burns. The $10 is a cap for the seat, shared across the seat's keys, not a payment. On days when measured input already gives each seat $10 or more, nothing changes.

The vote signals a preference. It does not execute anything by itself. The team publishes execution receipts or a specific refusal, and passage cannot bypass the funding, accounting, provider or reserve checks.

Why now

Measured input fell from $754.83 in session 10 to $31.26 in session 23, while seats at opening grew from 5 to 13. Sessions 21 and 23 both opened with 13 seats, yet the cap dropped from $7.43 to $2.40, so the recent fall follows lower input, not more seats. A cap of a few dollars is too small to show what seats do with inference. The pilot tests whether a steady $10 per seat brings real use, with money the sink already holds.

Measured input is an approximate-day net inflow, after excluding transfers straight from the curve and pool and subtracting OPS claims. Manual transfers and claim timing can move it. It is not an audited daily fee total.

What changes

For an opening eligible under the pilot's activation and session rules, while no stop has latched and every check passes, the keeper passes the larger of measured input and $10 times its count of seats before open into TaxSink.open. The contract divides that input across the live seats, so each seat's cap is at least $10 unless the supply-value bound is lower. Otherwise the keeper passes measured input, with zero uplift. The on-chain tax24hUsd field stores this effective input, not measured input. Every session record shows measured input, effective input and the uplift between them. The uplift is not new revenue and not a separate transfer. It raises the input used for caps.

What stays the same

The $50 per-seat ceiling, the 0.25% supply-value bound, and the claim, report and bell routes. OPS keeps its existing 40% of ordinary claims, which is outside this vote, and the uplift creates no extra OPS claim. Team seat 1 still gets inference access under the same seat rules as every seat. There are no payouts, returns or fee sharing for holders. This is not a token price floor and not a payment to holders.

Cost

At the bell, recognized use by seats present becomes debt to the provider, and unused cap, even cap never handed out, buys and burns QUOTUM where free NVDA and price guards allow, as today. Raising caps can therefore raise burns without more inference use. That is a cost of the pilot, not a price promise.

With 13 seats throughout, no tighter supply-value bound and successful settlement, recognized use plus successful burns consume about $130 gross per session, about $1,820 over 14. Each new seat adds $10 per session. New inflow reduces the net draw. As an illustration only, with no new inflow, unchanged prices and no unreported liabilities, about $7,300 of free reserve on 21 October would end near $5,480. This is not a forecast or a promise of 14 boosted sessions.

Seats that join after opening get the same cap, so exposure grows with the seats at the bell. With 100 seats at the bell it is about $1,000 for that session before settlement guards.

When it stops

Before each boosted session, free reserve must be at least $2,000 plus $10 times the keeper's seat count before open for every pilot session still left, including this one. At 13 seats with all 14 sessions left that is $3,820; with one left it is $2,130. Equality passes, and the check does not lock reserve funds. After opening, the keeper compares the cap in the Open event with the cap it admitted. If the event cap is higher, uplift stops for the rest of the pilot. Seats leaving before open executes are one possible cause. That session's cap and settlement stay in force. Stale price or reserve data, unresolved provider accounting, a provider shortfall or the team's emergency stop also end the uplift. If input measurement fails, the session opening is postponed.

Before the first boosted session, a failed check only delays the start, within the approval window. After it, any stop is final for this pilot and resuming needs a new proposal. A stop never cuts the cap of a session already open.

How the vote works

Voting weight is liquid QUOTUM plus attributable staked QUOTUM, including queued stakes, counted once. It is read at snapshot block B, the latest finalized block before this proposal is published, so nobody can buy weight after reading it. Moving tokens after B does not change a ballot's weight. OPS on seat 1 is the only team wallet left out. Protocol accounts such as the sink, pools and staking escrow do not vote, and tokens held in pools give no one voting weight. Every other eligible wallet votes as an ordinary holder, without labels.

Voting is a gasless signature on quotum.org/governance. It is not a transaction and approves or moves no tokens. Only ordinary addresses with no code at B can vote under the fast rules. App wallets that use EIP-7702 delegation, such as FOMO, and contract wallets such as Safe cannot vote on QIP-1. Support for delegated addresses is planned for the next version of the rules. The charter has the exact policy. QIP-1 passes if For weight exceeds Against weight, final eligible ballots across For, Against and Abstain carry at least 1% of supply at B, and at least five distinct eligible positive-weight addresses have a counted final ballot. Addresses are not people, and large holders can decide the result.

Passing is not starting. QIP-1 runs in the charter's bootstrap class: voting runs 2 hours, then 1 hour for objections to the count and 1 hour to check the proofs, so the earliest final result comes 4 hours after opening. The count is published when voting closes. Discussion runs in one public discussion thread linked from this page. The pilot starts only if the ledger, objections and every check pass and a scheduled 20:00 UTC boosted opening succeeds at least 2 hours and no later than 168 hours after the final result. Otherwise approval expires. Dates are not set yet. The full voting rules are in the charter, and common questions are in the FAQ.

Words used below

• Session: one daily cycle, from open to the bell.
• Measured input: approximate-day net NVDA inflow into the sink, in USD.
• N: the keeper's count of seats before it sends open.
• M: the number of pilot sessions left, including the one being checked.
• Effective input: what the keeper passes to open. For an eligible pilot opening while checks pass and no stop has latched, the larger of measured input and $10 times N; otherwise measured input.
• Uplift: effective input minus measured input.
• B: the snapshot block that fixes voting weight.
• S0: the first boosted session. The pilot covers S0 through S0+13.
• OPS: the team wallet on seat 1.

Voting rules

Draft. These rules are frozen before any ballot opens and apply to QIP-1 and later proposals until a vote adopts a replacement. They replace the earlier draft charter's 72-hour vote, 48-hour challenge period and closing snapshot.

In short

Votes signal a preference. They do not execute themselves and give holders no right to move reserve funds. A vote can ask for changes existing code already allows, such as opening input, which models seats can use, compute experiments or session timing. OPS's 40% share of ordinary claims, creator fees and marketing spend are outside voting. When a proposal passes, the team publishes execution receipts or a specific refusal, and passage cannot bypass funding, implementation, accounting, provider or reserve checks.

A vote takes 18 hours from opening to the earliest final result: 6 hours of voting, 6 hours for objections to the count, 6 hours to check the proofs. The first proposals, published before 1 November 2026, run in a shorter bootstrap class: 2 hours of voting, 1 hour for objections and 1 hour to check the proofs, 4 hours in all. The count is published when voting closes, and the result takes effect only after the proof check. The windows are short so the first decisions can take effect within a day of opening, while the rules are new and caps are small; from 1 November every proposal uses 6, 6 and 6 hours again. Time alone never finalizes a count. An unresolved objection or a failed evidence check holds the result until it is resolved.

Voting weight is liquid QUOTUM plus attributable staked QUOTUM, including queued stakes, counted once, read at the snapshot block B. B is the latest finalized block before the proposal is published, so nobody can buy weight after reading the proposal. Moving tokens after B does not change a ballot's weight. Buying before B can still capture weight, and addresses are not people. OPS on seat 1 is the only team wallet left out. Protocol accounts do not vote, and tokens held in pools give no one voting weight. Every other eligible wallet votes as an ordinary holder, without labels.

You vote by signing a message on quotum.org/governance. It is not a transaction and never grants a token approval, allowance, transfer or claim. Under these rules only ordinary addresses with no code at B can vote. App wallets that use EIP-7702 delegation, such as FOMO, and contract wallets such as Safe cannot vote yet. Support for delegated addresses is planned for the next version of these rules. You can replace your ballot before voting closes with a higher nonce. The highest valid uncontested nonce counts.

A proposal passes when For weight exceeds Against weight, ballots across For, Against and Abstain carry at least 1% of supply at B, and at least five distinct eligible addresses with positive weight have a counted ballot. A tie fails. Large holders can decide the result. Ballots, receipts and the full tally are published so anyone can recount. Two transactions on chain 4663 record the hashes of the signed receipt log and the tally: one after voting closes, one with the final result, even when the tally did not change.

Several proposals can run at once. Each has its own ballot, receipts, tally and result. Proposals published together share one B. A ballot for one proposal never counts for another.

Anyone can post a draft for discussion. To go to a vote, a proposal needs sponsors with eligible weight of at least 0.25% of supply at its B. The first proposals, QIP-1 to QIP-4 when first published before 1 November 2026, are sponsored by the team from seat 1. OPS's weight still counts in no vote.

Disclosure

Draft. QIP-1 has not passed. The proposal and the charter hold the binding rules.

One session, step by step

1. Before open, the keeper measures input: approximate-day net NVDA inflow into the sink, after excluding transfers straight from the curve and pool and subtracting OPS claims, in USD. It is not an audited fee total. Say it measures $31.26. 2. It runs the safety checks. Free reserve must be at least $2,000 plus $10 times its seat count before open for every pilot session still left, including this one. At 13 seats with 14 sessions left that is $3,820. If measurement fails, opening is postponed. Before the first boosted opening, a failed check can only defer activation within the approval window. After activation, a failed check is a stop: uplift ends for this pilot and resuming needs a new proposal. 3. If the opening is eligible under the pilot's rules, no stop has latched and every check passes, effective input at 13 seats is $130, the larger of $31.26 and $10 times 13, and the uplift is $98.74. The uplift raises the input used for caps. It is not revenue and not a transfer. The Open event and tax24hUsd show $130. Otherwise effective input is $31.26, the uplift is zero, and the event and field show $31.26. The session record lists measured input, effective input and uplift separately. 4. The contract sets each seat's cap to the lowest of $50, effective input divided by seats at opening, and, when it applies, 0.25% of QUOTUM supply value. With 13 seats and no tighter supply-value bound, the cap is $10 at $130 effective input, or $2.40 at $31.26, shared across the seat's keys. A cap is not a guaranteed grant. 5. After opening, the keeper compares the cap in the Open event with the cap it admitted. If the event cap is higher, uplift stops for the rest of the pilot. Seats leaving before open executes are one possible cause. That session's cap and settlement stay in force. 6. Seats use inference. Real use is reported as spend, capped at each seat's cap. 7. At the bell, recognized use by seats still present becomes debt to the provider. Use by seats that left before the bell can stay outside what the sink recognizes, and the floor does not fix that gap. Unused or unissued cap buys and burns QUOTUM where free NVDA and price guards allow. Failed burns are published and the NVDA stays in the sink. 8. The session record publishes measured input, effective input, uplift, reserve reads, caps, spend, burns and any stop reason.

What this does not do

It does not set a price for QUOTUM, pay holders, or pay anyone. Raising caps can raise burns without more inference use. Seats that join late get the same cap, so exposure grows with the seats at the bell. A fall in NVDA lowers the reserve's USD value. A fall in QUOTUM can lower the supply-value bound on caps. Caps do not prove that the provider is funded, and the pilot can stop early.

Questions

Draft. These answers describe a proposal, not something already running. The proposal and charter hold the full rules, and they apply if an answer here differs.

What am I voting on?

Whether each seat should get at least $10 per session, for up to 14 sessions and only while safety checks pass. The extra use and burns this allows are absorbed by NVDA the sink already holds.

Where do I vote?

Votes happen only on quotum.org/governance, and we never ask you to vote or connect a wallet anywhere else. A post asking you to vote for a listing or to connect a wallet on another site is not from quotum.

Is that $10 paid to every seat?

No. The $10 is the seat's inference cap for the session, shared across its keys. It is not a distribution and nothing is paid out. The keeper sets the opening input to at least $10 times the seats, so the contract gives each seat a cap of at least $10 unless the supply-value bound is lower. Actual grants can be lower and depend on provider funding checks.

Where does the money come from?

From NVDA the sink already holds. No new sponsor or provider top-up is promised. OPS keeps its existing 40% share of ordinary claims, which is outside this vote, and the uplift creates no extra OPS claim. Team seat 1 still gets inference access under the same seat rules.

Does tax24h still mean fees?

It never meant audited fees. It stored measured input, an approximate-day net inflow. During the pilot it stores effective input: the larger of measured input and $10 times the seats while checks pass, otherwise measured input with zero uplift. Each session record lists measured input, effective input and uplift separately. The uplift changes the cap calculation. It is not new revenue or a transfer, but the use and burns it allows do consume reserve.

What happens to cap nobody uses?

At the bell, unused or unissued cap buys and burns QUOTUM where free NVDA and price guards allow. Failed or uncovered burn amounts stay in NVDA and are published separately. Unused cap is never paid to holders and creates no balance they can spend. Higher caps can mean more burns without more use, and none of this is a price promise.

Is spending capped at $10 a seat?

No. Days when measured input gives more than $10 per seat stay higher, up to the $50 ceiling. Seats that join after opening get the same cap, so with 100 seats at the bell a $10 session is about $1,000 before settlement guards. A falling NVDA price shortens how long the reserve lasts.

Who can vote, and does the team?

Liquid plus attributable staked QUOTUM, including queued stakes, counted once. OPS on seat 1 is the only team wallet left out. Protocol accounts do not vote, and for QIP-1 pool balances are not attributed to individual voters. One person can hold several addresses, and the tally publishes how concentrated the vote was.

Does buying before the snapshot and selling right after still count?

It counts. Under the fast rules weight is read once, at snapshot block B, the latest finalized block before the proposal is published. Selling after B does not reduce a ballot's weight, and tokens bought after B add nothing. Because B comes before anyone can read the proposal, buying weight for a specific vote means buying before it is announced.

Which wallets can vote?

Under the fast rules, only ordinary addresses with no code at B. App wallets that use EIP-7702 delegation, such as FOMO, and contract wallets such as Safe cannot vote yet. Support for delegated addresses is planned for the next version of the rules.

Can I vote with QUOTUM held in the FOMO app?

Not on QIP-1 under the fast rules. A FOMO address carries an EIP-7702 delegation, so it has code at B and is not admitted, even if you export its key. To vote, move your tokens to an ordinary address, one that has never set a delegation, before the proposal is published. A move after publication comes after B and cannot make that address eligible for this vote. Publication times are announced in advance in the linked public discussion thread and on X.

Is anything recorded on chain?

Voting weight is read from the chain at block B. Ballots are gasless signatures collected off chain. After voting closes, one transaction on chain 4663 records the SHA-256 hashes of the exact signed receipt-log head file and close tally file. A second transaction records the final head and tally after objections and proof checks, even when the tally is unchanged. Later edits to those files would fail to match the recorded hashes. The receipt log is checked against the signed head, and anyone can recount from the published evidence. A matching commitment does not establish that the count is correct. If an objection to the count is accepted, the final result waits until a separately reviewed correction process exists; no objection is rejected to reach a result. Every version stays published.

When does it start and end?

Dates are not set yet. The schedule rules fix how they are chosen, and a separate activation record will publish them after the vote. The pilot runs from session S0 through S0+13, and skipped sessions do not extend it. QIP-1 is one of the first proposals, which run in the charter's short bootstrap class: voting runs 2 hours, objections 1 hour and proof checks 1 hour, so the earliest final result comes 4 hours after opening. The count is published when voting closes. Proposals published from 1 November use 6, 6 and 6 hours. The pilot starts only if the vote passes, every objection is decided, every check passes, and a scheduled 20:00 UTC boosted opening succeeds at least 2 hours and no later than 168 hours after the final result. Otherwise approval expires. It does not renew.

Can it stop early?

Yes. Before each boosted session, free reserve must be at least $2,000 plus $10 times the keeper's seat count before open for every pilot session still left, including this one: $3,820 at 13 seats with all 14 sessions left, $2,130 with one left. Equality passes, and this check does not lock the reserve. An Open event cap above the admitted estimate, bad price or reserve data, unresolved accounting, a provider shortfall or the team's emergency stop also stop uplift. Before the first boosted opening, a failed check only defers activation within the approval window. After activation, a stop is final for this pilot and resuming needs a new proposal. If input measurement fails, that opening is postponed. No stop cuts the cap of a session already open.

Does my vote pay me or control funds?

No money. Inference access still follows the existing stake, seat and cap rules. The vote creates no payment, fee share or ownership. It cannot move reserve funds freely or change contract constants. The team publishes receipts or a specific refusal. The one thing a vote leaves behind is a first voters seal on the record for every address whose ballot is accepted in the rehearsal or in QIP-1. The seal is permanent, pays nothing and changes no cap. A seat holder's stake of 2,500,000 QUOTUM also clears the 0.25% sponsorship line in the charter, so a seat can put a later QIP to a vote.

Receipts and checks

Raw receipt log · Ballot package · Finalization check

Copies of the log and the collector's signed head are mirrored at github.com/qvotvm/qip-1-receipts.

Package hash

Unavailable

Log head

Unavailable

Anchor wallet

Unavailable

Collector public key

Unavailable