Dev's Monthly Compensation


#1

Hello Everyone… :slight_smile:

I will be submitting a proposal shortly for the compensation of the entire Dev team on a monthly bases. This is a long time coming as we worked to fix the budget issues.

I will be asking for 1k PIV per month for each Dev. We have many improvements to come, which entails many hours of hard work. I hope you all will follow me and vote yes on this proposal.

s3v3n

core-dev-fuel+2;

hash= 320231e842396327cade674fb6e9552028fb87c5b2eeee8e910285a50fe05682

“mnbudget vote-many 320231e842396327cade674fb6e9552028fb87c5b2eeee8e910285a50fe05682
yes” to vote in favor

“mnbudget vote-many 320231e842396327cade674fb6e9552028fb87c5b2eeee8e910285a50fe05682
no” to vote against

"mnbudget getinfo core-dev-fuel+2” to check the status


Pre-proposal discussion - zerocoin update
How to check & vote on current active proposals
3 month rolling PIVX payment reviews
#2

How many devs are we talking about here?

I think you should get 10 piv each and make it last!

Just kidding of course, you’ll have my backing, keep up the great work guys!


#3

PAY THE DEVS!!! without them there is no PIVX!


#4

Definitely need to pay the DEV team well. The question is how will this change as DEVS are added or subtracted? The total PIV monthly budget per month is 21,600 PIV (assuming 30 days) after we hit 5 PIV per reward block in under a month. So if paying up to 10 Devs 1,000 PIV each that is almost half the monthly budget. If we flex and add 5 more for a special project (as an example) that is nearly 75% of the budget during that time, if we keep the payment a flat 1,000 per Dev, regardless the number.

Perhaps instead of a flat 1,000 PIV per dev, we do a mix match? Maybe a flat 500 PIV per dev PLUS 20% of the entire monthly budget divided by current # of devs? Just throwing out ideas here. Not sure what is the best way to incentivize the dev team to the max and still have funds available for other important things so the community can also be involved (and of course marketing and some sort of knowledge reference library).

Also, will the number of PIV each dev earns change based on price? If PIVX is $10 or $20 per PIV, will we keep the monthly PIV allocation exactly the same? If not, at what price points should it change? Surely if we are at $100 per PIV the devs aren’t suggesting they earn $100k USD per month right? Again I don’t have the right answer here, just asking the questions aloud.


#5

@cryptosi There will be 6 devs in this proposal afaik.


#6

Any other Dev’s either Volunteers, or Project work will need to be compensate through proposal for work they submit through the Governance system.


#7

core-dev-fuel;

hash= ed2f83cedee59a91406f5f47ec4d60bf5a7f9ee6293913c82976bd2d3a658041

“mnbudget vote-many ed2f83cedee59a91406f5f47ec4d60bf5a7f9ee6293913c82976bd2d3a658041 yes” to vote in favor

“mnbudget vote-many ed2f83cedee59a91406f5f47ec4d60bf5a7f9ee6293913c82976bd2d3a658041 no” to vote against

"mnbudget getinfo core-dev-fuel” to check the status


#8

So are we just pretending like I didn’t ask this question then? Look, if the answer is price is irrelevant, the devs will be paid 1,000 PIV regardless of the price - so be it. I would just like to know up front. With 6 devs, that is 6,000 PIV or 27.8% of the total budget after we hit the 5 PIV emission rate.

In general I am okay with this number, but the most important thing is TRANSPARENCY. The devs need to be rewarded for their great work, obviously, but it doesn’t mean we can’t question the proposals and expect an up front answer, right?


#9

Good Point Mate, Id be interested in the answer since i can cast many votes :slight_smile:


#10

Price is not irrelevant and will be reevaluated every 12 months, based on previous work. As of this moment, none of the Dev’s have been paid from the budget, so we are essentially paying in the rears.

To me, this shows a level of trust from the Dev’s, as the budget can be cancelled at any if the Masternodes choose to change their votes.


#11

Thank you for the response.


#12

I voted yes today and I have 3 nodes. Pay the developers!


#13

I would personally say that if we did reach $5 per piv and the devs didnt lower the amount they asked for, it’s unlikely they would get funded. I am calculating based on the assumption that they are based in America and this is less than a full-time salary, so currently very good value. However at 5K USD each per month the question would be very different and I’m certain they would ask for a lower PIV amount. But I think we should cross that bridge at $5. It’s one of those good problems to have.


#14

12 months for the backbone of PIVX is a contract of trust…and motivation…I think this is a totally reasonable proposal.


#15

If PIVX crosses $5, then we should probably update all of the proposals payouts accordingly (not just the developers). It would allow PIVX more room to expand.


#16

Thats the idea. Most proposals are reviewed on a monthly or so basis or should be IMO. Helps keep waste at bay.


#17

I think allocating funds to compensate the core development team is a necessary must. My votes are in.

I also think we should aim to have a clear roadmap broken down by projects to have full visibility of efforts and strategic/technical direction of the core development.

When talking about the developer’s salaries, we could decide to set a cap in dollar terms if we think this may be a sensible thing to address extreme currency upwards moves.

Aside from the exact monetary value assigned to this project, I think it is critical to give visibility on the % of the yearly proposal fund that is allocated to core development.

I put together this framework to compile the “Definition of the Currency” and current execution plan: https://docs.google.com/document/d/1bHdV9ZeDIDaaadiHCy_HbxM4b61D1CzCjANOwE3HVlA/edit?usp=sharing

I wonder if there would be interest in trying to fill this up. We can have it as a work-in-progress reference document. It could be valuable for internal and external comms. Maybe there is already a place with all this compiled information.

I will submit a couple of proposals today.

Could someone remind me the how voting periods are opened and closed?

Thanks


#18

#19

If you don’t pay the Dev’s then PIVX dies. This one seems pretty obvious as they’ve done a great job already and the new features in the roadmap need to be implemented in order for PIVX’s price to rise.


#20

We have just added some more Dev’s… :stuck_out_tongue: Please vote yes… :slight_smile:

core-dev-fuel+2;

hash= 320231e842396327cade674fb6e9552028fb87c5b2eeee8e910285a50fe05682

“mnbudget vote-many 320231e842396327cade674fb6e9552028fb87c5b2eeee8e910285a50fe05682
yes” to vote in favor

“mnbudget vote-many 320231e842396327cade674fb6e9552028fb87c5b2eeee8e910285a50fe05682
no” to vote against

"mnbudget getinfo core-dev-fuel+2” to check the status