What's new

Community Treasury Payouts - how it works?


New Pivian
Hello, Developers and others!

I haven't find any detailed information about how the payouts are performed.

For example, the case 1:
Total 43200 PIV and 3 proposals for 10000, 20000, 30000 (in order of their submission). Each of them have sufficient YES votes.
How will they be payed out? I assume that the last 30000 will not be payed out? If not, will it be suspended or go to the next round?
Does the order of their submission affects or the maximum YES votes?

the case 2:
Total 43200 PIV and 3 proposals for 43200, 10000, 5000 (again, as in order of their submission). Each of them have sufficient YES votes.
What will be payed out and what will not?

It would be appreciated if someone describes the algo of the payout.


Staff member
For a proposal to be 'passing' the Net Yes votes (So, Yes votes - No votes = Net Yes votes) needs to be greater than 10% of the total Masternode count. Currently that is approx 1,820 Masternodes, so the Net Yes must be greater than 182.

Passing proposals are ordered from highest to lowest Net Yes votes, and those votes are locked randomly during the 2 days prior to the Superblock.

At Superblock, they are paid in order until there is not enough PIV left to pay, or until there are no more passing proposals.
The 43,200 PIV are created only if they are to be paid out. That means sometimes, LESS than 43,200 PIV is created.

Any unspent balance in the 43,200 is not created and is not carried forward to the next month.

Hope this helps!


New Pivian
Thanks! Now it's more clear to me :)

So, for passed proposals 1000, 2000, 40000 and 5000 PIV (in order from highest to lowest Net Yes votes) all except 40k will be payed and the 40k proposal will be expired, right? Or 40k will be transferred to the next superblock?

What if some of proposals will have the same Net Yes votes, but the budget left is only for one of them. Which will be payed? In which order (maybe timestamp of the proposal or anything else / random)?

and those votes are locked randomly during the 2 days prior to the Superblock
Two days according timestamp or particular block count?

Thanks a lot!


Staff member
Then the 3 proposals of 1,000 , 2,000 and 5,000 would be paid from newly created PIV, and the 40,000 would not be paid. The balance of 35,200 (43,200 - 8,000) would not be created and not carried forward. The proposal may have not expired if it is a multi-month proposal, in which case it remains and is part of the voting process the next month.

Good question about how a tie in votes is resolved. I don't know.

Everything is according to block number, not date.


New Pivian
I'm exploring PIVX sources, successfully started a blockchain (using another port number) and trying to reproduce the budget payment. But still no luck.
@Eric_Stanek Are you a developer or maybe you can point someone out to this message? I definitely need some explanations. Thanks in advance!

What do I have:
Started blockchain network, 14 masternodes on it.
Activated sporks - the same as in PIVX network (except cold staking maintenance).
The chain works and produces blocks.

consensus.nBudgetCycleBlocks = 300;
consensus.nProposalEstablishmentTime = 3 * 60;
in budgetmanager.cpp I set
int finalizationWindow = 64; (as it's for testnet)

I successfully submitted a proposal, voted using 14 masternodes as yes.
getbudgetprojection shows this proposal.

But on superblock nothing happens. RemainingPaymentCount of the proposal becomes 0.
Maybe some conditions are not met or am I doing something wrong?


Staff member
Hello Alexxiy,

I have done development in the past, but I have not written a single line of code for PIVX (Or any crypto project for that matter).

Sorry, but our developers are slammed for time and can only support PIVX.

Good luck!