Decentralized Pixa Fund
The fund held 249,307.037 PXS on 2026-10-05, read at 15:52 UTC. One proposal was being paid.
The Decentralized Pixa Fund (DPF) is the community's treasury. It is held by pixa.omnibus, an account with no keys, and it pays only proposals that stakeholders vote for. This page explains where the fund's money comes from, how it decides what to pay, what it pays today, and how to propose or vote.
Where the money comes from
| Source | Since genesis, to 2026-10-05 15:00 UTC |
|---|---|
| Seed at genesis | 245,098.039 PXS |
| Share of issuance: 15% nominal, converted to PXS in every block | 1,778.751 PXS; 57.6 PXS a day then, about 78 since hardfork 30 |
| Proposal fees, which are paid into the fund | 3,661.000 PXS from three proposals |
| PIXA sent to the fund, converted to PXS at once | none so far |
| Paid out to proposals | −1,232.827 PXS |
| Balance | 249,304.963 PXS |
What the fund actually receives from issuance. The fund's share is converted to PXS at the median feed. Until hardfork 30 each block's share was rounded down to 0.001 PXS: at 51.833 PIXA per PXS the fund received 0.002 of the 0.0027 PXS due, about 74% of its nominal share, and a median above about 140 PIXA per PXS would have rounded it to nothing. Since 2026-10-07 consecutive blocks pay the exact share between them, 0.002 or 0.003 PXS each, about 78 PXS a day (Supply, Inflation and Yield). Hourly proposal payments stopped losing their rounding the same way; before, a proposal paying less than 0.024 PXS a day received nothing.
How it pays
- Once an hour, the chain counts the votes on every active proposal and ranks them.
- The budget is 1% of the fund's balance per day, spread over the hours: about 2,493 PXS a day on 2026-10-05.
- Payment runs down the ranking. Each proposal receives its daily pay for the hour, starting with the most-voted, until the budget runs out.
- The return proposal sets the threshold. Proposal 2 pays its receiver, the fund itself, and asks for 1,000,000 PXS a day, so it takes whatever budget is left. Any proposal with fewer votes than it receives nothing. Its vote total is therefore the funding threshold. Its payments to the fund, 25,946.984 PXS so far, cancel out.
The fund cannot be spent any other way. No person, company or foundation holds its keys (System Accounts).
Proposals on 2026-10-05
| Aspect | Proposal 1 | Proposal 2 |
|---|---|---|
| For | Account creation fees and SMS verification for new accounts | The funding threshold: this is the return proposal |
| Receiver | rex |
pixa.omnibus, the fund itself |
| Pay | 110.000 PXS a day | 1,000,000.000 PXS a day, returned to the fund |
| Runs | 2026-09-24 to 2026-12-31 | 2026-09-24 to 2036-09-24 |
| Votes | 11.217 million VESTS, from 4 accounts | 7.761 million VESTS, from 1 account with stake |
| State | Funded | Threshold |
- Proposal 1 had received 1,232.827 PXS by 15:00 UTC, paid as 4.583 PXS every hour. Its pay is about 4% of the daily budget. The rest of the budget returns to the fund.
- Proposal 0, a one-day proposal in September 2026, has expired.
- The fund is shrinking slowly. Since hardfork 30 it receives about 78 PXS a day (57.6 before) and pays out 110, so it shrinks by about 32 PXS a day while proposal 1 runs.
Proposing
- Write the proposal as a post. In the app, write it in the Proposals portal (
portal-156480). Set the daily pay and the dates, and the app creates the proposal on chain after publishing the post. - Or create it directly. Broadcast
create_proposal, signed with your active key. It names:- a creator and a receiver
- a start date and an end date
- a daily pay in PXS
- a subject of at most 80 bytes
- the permlink of a post by the creator or the receiver
- Pay the fee. It is 10 PXS, plus 1 PXS for each day the proposal runs beyond 60 days. A ten-year proposal costs 3,603 PXS. The fee goes into the fund.
- Change it later. With
update_proposalyou can lower the daily pay, bring the end date forward, or change the subject and post. You cannot raise the pay or extend the end date. Withremove_proposalyou can withdraw the proposal.
Voting
- How. In the app, use the proposals tab under Governance → Viability Management (step by step). Directly, broadcast
update_proposal_voteswith your active key. It covers up to 5 proposals at a time, all approved or all unapproved. - Weight. The same governance weight as witness votes: your own Pixa Power, less stake still in its 30-day wait, plus any proxied to you (Witnesses and DPoS). If you have named a proxy, your proxy's proposal votes count for you and your own do not.
- Limits. You cannot vote for a proposal that has ended. Votes lapse with 365 days of governance inactivity.
What to keep in mind
- Few voters. On 2026-10-05, four accounts voted for the funded proposal, and a single account set the threshold (Decentralization and Safeguards).
- The fund pays in PXS. PXS promises no price. A recipient who converts PXS receives PIXA at the median feed in force 3.5 days later, less any haircut. On 2026-11-03 that median still rested on a placeholder price for PIXA (Oracle and Price Feed, Haircut, Corridor and Settlement). PXS paid out of the fund also counts in the debt ratio, which the fund's own PXS does not (why it matters).
- A proposal is a public promise, not a contract. The chain pays a proposal while it ranks above the threshold. It does not check that the work is done. Stakeholders can withdraw their votes at any hour.
Inherited → changed
| Aspect | Steem / Hive | Pixa |
|---|---|---|
| Name | Steem Proposal System; Decentralized Hive Fund | Decentralized Pixa Fund |
| Account | steem.dao, then hive.fund |
pixa.omnibus, which has no keys |
| Share of issuance | Hive: 10% | 15%, paid exactly since HF30; reduced by rounding before |
| Paid in | HBD | PXS |
| Return proposal | id 0 | id 2 |
| Seed at launch | Hive: Steem's treasury balance, plus the balances of 328 excluded accounts | 245,098.039 PXS |
| Budget, fee, voting rules | 1% a day; 10 + 1 a day beyond 60; 5 proposals per vote | same |
Sources
- Hive whitepaper, §II.5.
- Code, at commit
48f75a2:- vote counting and ranking: dhf_processor.cpp:88-136
- budget and payments: dhf_processor.cpp:145-286
- creating, changing and voting on proposals: dhf_evaluator.cpp:32-211
- the fund's share of issuance: database.cpp:1781-1800
- constants: Chain Parameters
- Live chain, read on 2026-10-05:
database_api.list_proposalsanddatabase_api.list_proposal_votes- the history of
pixa.omnibus:dhf_funding,proposal_feeandproposal_payoperations
- App: the proposal fee in
SettingsPanel.js:29-36; the return proposal and the budget figures inGDVMProposals.js:68-72and1082-1103.