Referendum #90 · general admin · preliminary
Should the Vara community have its own treasury?
Original title: Does the Vara community need its own treasury?
Governance: Deciding · Not executed
Submitted 2026-10-19T11:58:36.000Z · Final date unavailable
Verification date in this record: 2026-10-21T16:28:27.202Z. This is not a live chain status check.
What this referendum means
What was proposed?
Referendum #90 asks whether Vara should have a network-owned pool of funds spent by referendum, by VARA holders. It is a consultation about that principle, not a proposal to approve a particular budget, tax, token allocation, beneficiary or operating team. The authenticated proposal says the runtime already has treasury software and spending tracks, and asks holders whether they want that capability put to work. The decoded call is system.remark: a short on-chain reference to the proposal text, not an instruction to create a treasury, move VARA or change the network's rules.
Why it mattered
A community treasury could give holders a shared way to choose and fund priorities. The corresponding questions are where its money would come from, who could propose spending, how decisions would be checked, and how recipients would be held accountable. This referendum does not settle those questions. Its significance is whether holders endorse the direction before any concrete funding and operating arrangements are proposed—not whether a particular spending plan is ready.
An Aye vote meant…
Aye supports the principle described in this consultation and, if the referendum succeeds and is enacted, authorizes its remark call. It does not approve a budget, tax, token allocation, beneficiary, operating team or automatic transfer. Those would need separate, explicit decisions.
A Nay vote meant…
Nay rejects this particular consultation and supports not enacting its proposal. It does not move funds, switch off existing treasury software or permanently prohibit future treasury proposals. A later, different proposal would have to be judged on its own terms.
What happened or is happening
At finalized block 37074910 (0xc5e5cfb8874179fb539873c07cd0154a2bcc5eebec542435d281183ef8a830a7, 2026-10-21T16:28:09.000Z), #90 is Deciding on General Admin track 13, with a decision deposit and no active confirmation timer. Its decision period accepts voting, subject to the normal account/balance/lock rules; VoteVara does not submit votes. The interim on-chain tally is 0 weighted Aye, 0 weighted Nay and 0 support, not a final result or a count of people. The runtime decision-timeout boundary is block 37446948; confirmation could conclude it sooner. No wall-clock countdown is inferred. The original 78-byte preimage hashes to 0xd183f4414528efc246797785af47329fc1efb3d296504733c875d3483ca21f49 and decodes to system.remark. BLAKE2b-256 of exact UTF-8 title + LF + body reproduces 0x2277eb6f6191c431c2a3cc52b217e85a3f3040ef49bd91494560c0ef5e5c6588, the reference in the remark. The separate metadataHash 0xe8c71a50b66a5c37786797e998cf7179f785b05d440fa8815ab3afe1c4c9fd7d identifies the JSON context envelope, a different hash input. Runtime metadata independently exposes Treasury spending/payment calls and spending tracks; availability is not evidence of a funded operating community treasury. The older VaraGov history response was incomplete; current status comes directly from finalized storage. There has been no approval or dispatch through this ongoing referendum at the verification block.
The verified call is system.remark. Its payload is a VaraGov hash reference to the proposal's exact title and body. It does not call Balances or Treasury, transfer VARA, allocate a budget or change spending permissions. The referendum result records the governance decision; the remark is not a treasury implementation or a separate yes/no statement.
The verified call is system.remark. Its payload is a VaraGov hash reference to the proposal's exact title and body. It does not call Balances or Treasury, transfer VARA, allocate a budget or change spending permissions. The referendum result records the governance decision; the remark is not a treasury implementation or a separate yes/no statement.
Any later implementation would need concrete proposals defining the funding source and amount, permitted spending and approval controls, administration and accountability. Depending on their design, those proposals may use existing runtime mechanisms or require additional governance actions. None is automatically submitted, funded or guaranteed by this consultation.
A system.remark records information or intent. It does not itself transfer funds or complete an external objective.
Verified outcomes
- Finalized-chain observation: Deciding at block 37074910; no approval or dispatch through this referendum.
Follow-up: unverified
- The source, size and timing of any future treasury funding or token allocation are unspecified.
- Detailed spending eligibility, beneficiaries, controls, administration and accountability arrangements are unspecified.
- This verification did not audit treasury balances, every privileged origin or whether an operational community fund is already established.
- Neither outcome guarantees which later proposals will appear, how they will be decided, or when implementation could happen.
Still unknown
- The source, size and timing of any future treasury funding or token allocation are unspecified.
- Detailed spending eligibility, beneficiaries, controls, administration and accountability arrangements are unspecified.
- This verification did not audit treasury balances, every privileged origin or whether an operational community fund is already established.
- Neither outcome guarantees which later proposals will appear, how they will be decided, or when implementation could happen.
- Text binding authenticates exact wording, not its policy assumptions, author identity or future implementation.
Further explanation and reporting
What are we actually voting for?
The question is whether the community should have a network-owned treasury governed by VARA-holder referendums. Supporting that principle is different from approving a specific budget, tax, allocation, spending beneficiary or operating mechanism.
Sources: proposal-text-expedited
Does this referendum move any VARA?
No. The verified call is system.remark, containing a reference to the proposal text. It has no funds-transfer or treasury-spending instruction. Ordinary voting locks or transaction fees are separate from allocating treasury funds.
Sources: finalized-chain-expedited
Does Vara already have treasury functionality?
Yes. The verified runtime contains a Treasury pallet with spending and payment calls, and governance tracks for Treasurer, tippers and spenders. Those are available software mechanisms—not proof of a funded, operational community treasury, or proof that every spending permission matches the proposal's desired model.
What happens if it passes?
Successful approval and enactment allow the remark to execute. The result can express support for the treasury principle, but no fund is created or financed automatically. Funding, spending rules, controls, administration and accountability would need concrete follow-on proposals or other appropriate governance decisions.
What happens if it fails?
This consultation does not proceed to approved enactment. It allocates no funds and establishes no permanent ban on a treasury. A future proposal with different terms remains a separate question. The vote does not automatically remove existing runtime treasury capabilities.
Why is this being discussed?
The proposer frames this as a choice about using treasury capabilities that already exist. The potential case for a community pool is collective priority-setting and funding; the corresponding concern is committing to a direction before financing, safeguards and accountability are specified. These are considerations raised by the proposal's scope, not attributed community quotations, a measured consensus or a prediction of how holders will vote.
Details and evidence
Participation
Participation
Calculation status: partial. Address-level figures are not counts of distinct people or organizations.
- Direct finalized interim weighted tally, not a final result. Address-level participation, electorate and raw capital were not reconstructed; unknown is not zero.
| Direct addresses | Unavailable |
|---|---|
| Delegating addresses | Unavailable |
| Raw capital (VARA) | Unavailable |
| Weighted Aye power (VARA) | 0 |
| Weighted Nay power (VARA) | 0 |
| Approval (%) | Unavailable |
| Raw capital / captured electorate (%) | Unavailable |
| Support capital (VARA) | 0 |
| Top-one share (%) | Unavailable |
| Top-three share (%) | Unavailable |
| HHI (0–10,000) | Unavailable |
| Gini (0–1) | Unavailable |
Proposal history
Proposal history
| Referendum | Governance | Execution | Direct addresses |
|---|
Timeline
Timeline
- Submitted · 2026-10-19T11:58:36.000Z · block 37022133
- DecisionStarted · 2026-10-20T09:27:21.000Z · block 37043748
- DecisionDepositPlaced · 2026-10-20T09:27:21.000Z · block 37043748
Technical call tree
Technical call tree
At finalized block 37074910 (0xc5e5cfb8874179fb539873c07cd0154a2bcc5eebec542435d281183ef8a830a7, 2026-10-21T16:28:09.000Z), #90 is Deciding on General Admin track 13, with a decision deposit and no active confirmation timer. Its decision period accepts voting, subject to the normal account/balance/lock rules; VoteVara does not submit votes. The interim on-chain tally is 0 weighted Aye, 0 weighted Nay and 0 support, not a final result or a count of people. The runtime decision-timeout boundary is block 37446948; confirmation could conclude it sooner. No wall-clock countdown is inferred. The original 78-byte preimage hashes to 0xd183f4414528efc246797785af47329fc1efb3d296504733c875d3483ca21f49 and decodes to system.remark. BLAKE2b-256 of exact UTF-8 title + LF + body reproduces 0x2277eb6f6191c431c2a3cc52b217e85a3f3040ef49bd91494560c0ef5e5c6588, the reference in the remark. The separate metadataHash 0xe8c71a50b66a5c37786797e998cf7179f785b05d440fa8815ab3afe1c4c9fd7d identifies the JSON context envelope, a different hash input. Runtime metadata independently exposes Treasury spending/payment calls and spending tracks; availability is not evidence of a funded operating community treasury. The older VaraGov history response was incomplete; current status comes directly from finalized storage. There has been no approval or dispatch through this ongoing referendum at the verification block.
{
"call": {
"section": "system",
"method": "remark",
"args": [
{
"name": "remark",
"type": "Bytes",
"value": "0x56617261476f763a307832323737656236663631393163343331633261336363353262323137653835613366333034306566343962643931343934353630633065663565356336353838"
}
]
},
"nestedCalls": [],
"limitations": [
"Text binding authenticates exact wording, not its policy assumptions, author identity or future implementation."
]
}Historical track parameters
Historical track parameters
{
"maxDeciding": 10,
"preparePeriodBlocks": 2400,
"decisionPeriodBlocks": 403200,
"confirmationPeriodBlocks": 3600,
"minimumEnactmentBlocks": 200,
"decisionDeposit": {
"planck": "750000000000000000",
"vara": "750000"
},
"approvalCurve": {
"reciprocal": {
"factor": 222222224,
"xOffset": 333333335,
"yOffset": 333333332
}
},
"supportCurve": {
"reciprocal": {
"factor": 49586777,
"xOffset": 90909091,
"yOffset": -45454546
}
}
}Deposits
Deposits
Governance deposits are not proposal spending.
{
"submission": {
"depositor": "kGgQqLXhVVMv85XDy1v5AE6HVBG1tkAwURrdmq1ewbmGMCaGH",
"amount": {
"planck": "1500000000000000",
"vara": "1500"
}
},
"decision": {
"depositor": "kGhAjUA3Uke6UmWwMRRwFHuxisCgm7dab61sL1tKqA15NXQVX",
"amount": {
"planck": "750000000000000000",
"vara": "750000"
}
},
"outcome": "unknown"
}Sources
Sources
- subsquare · retrieved 2026-10-21T00:15:31.232Z · block 37058500
Fresh recognized governance indexer evidence. Last-state block is not a claim about the current finalized chain head.
- other · retrieved 2026-10-21T01:21:58.272Z
Current title/body independently match the original remark hash and the current on-chain JSON metadata preimage. Authentication of wording does not establish policy implementation.
- other · retrieved 2026-10-21T01:21:58.791Z
Still reports Preparing without event blocks; contradicted by finalized Deciding storage and DecisionStarted. Backend cause is unverified, not a remaining lifecycle-status ambiguity.
- vara-chain · retrieved 2026-10-21T01:21:51.026Z · block 37059620
Direct read-only finalized JSON-RPC evidence; requires JSON-RPC POST, not browser GET. https://rpc.vara-network.io corroborated genesis and this block hash. Complete preimages were retrieved in memory and hashed; the capture retains compact trees and runtime-code hashes rather than multi-megabyte bytecode. The fixed admin HTTP checker may mark this RPC host not_checked; reproducible chain verification is in the archived evidence, with no allowlist or release-gate change.
- vara-chain · retrieved 2026-10-21T16:28:25.164Z · block 37074910
Read-only finalized storage, original hash-verified call, current runtime Treasury/ConvictionVoting metadata and track constants. RPC requires POST; the fixed admin HTTP checker may report not_checked. No claim of a treasury-balance or complete permission audit.
- proposer-material · retrieved 2026-10-21T16:28:27.202Z
Exact current title/body independently reproduce the original on-chain remark reference. Authenticates wording, not real-world author identity or the truth of all policy assertions.
Corrections
Corrections
No corrections recorded.