Archived Expenses 2022 (Q1-Q2)

[Eric_Stanek]

Title: Expenses 2022 (Q1-Q2)
Name: Expenses_2022_Q1Q2
Term: 6 Cycles
Cycle Amnt: 600 PIV
Total Amnt: 3600 PIV
Author: Eric Stanek
Receiver: Eric Stanek
Address: DCRsh9cm2vfQBXE8gPc9nzgQKM6L9J1qzj
Created: 2022-01-14
Status: Active
Vote Hash: fd4f5acac0118090a55b92b44644384fea6e1f8167d55d05ba53b148a66ef48b

Legacy:

This proposal adds an expense for iStockPhoto, but is basically a continuation of expenses for Domains, and Web Servers described in detail in this prior proposal.

https://forum.pivx.org/threads/pivx-web-servers-jul-dec-2021.956/


Expenses:

All prices are in USD.

The 3 VPS web server instances are $60 per month, plus $10 per month for backups.
The prices for the 30 domains vary, but average at $10 per year each.
The subscription for iStockPhoto.com is $115 USD per month.

I am including the 50 PIV cost for submitting this proposal as well.

So, we have:

3 x ($60 + $10) x 12 = $2,520 per year for the VPS web server instances.

30 x $10 = $300 per year for the domains.

1 x $115 x 12 = $1,380 per year for iStockPhoto.

The total is then $4,200 per year, or $350.00 per month for PIVX Expenses.

The current price for PIVX is $0.53, so that works out to 660 PIV per month.

Making the math simple, by only adding 8 PIV per month to pay for the 50 PIV proposal submission fee over 6 months, we get:

660 + 8 = 668 PIV per month.

I will round it DOWN to 600 PIV per month for simplicity and to again bias in favor of PIVX.


Notes:

I have no time to track any differences in expenses compared to actual fiat value of PIV received in this proposal. Given the price dropped significantly for the last 2 versions of this proposal (3 months each) and have certainly not recovered my costs for those, and there were many years prior to that these expenses were completely out of my pocket, this should not be an issue. As such, unless the PIVX price jumps well over $2.00 USD, I will not be calculating any credit etc. But, at that point, we can vote this proposal down and update the math for a new one to replace it. However, it the price drops dramatically, I will absorb the loss as I have done before.


Reporting:

I will not be reporting out any further details.


Voting:

To Vote Yes:

mnbudgetvote many fd4f5acac0118090a55b92b44644384fea6e1f8167d55d05ba53b148a66ef48b yes

To Vote No:

mnbudgetvote many fd4f5acac0118090a55b92b44644384fea6e1f8167d55d05ba53b148a66ef48b no

 

[Eric_Stanek]

This proposal should now be voted DOWN! A replacement proposal is coming.

I have handed off the servers to a trusted PIVian with also trusted PIVian(s) as backup.

Probably 5 or 6 times over the past 4 years or so, I have tried to hand off this responsibility to others. Finally the 'stars aligned' with the right people to help make this happen and someone trusted to step up and take over the responsibility.

I will leave it to the new person and backup people to submit their own proposal to cover their costs, and 'announce' themselves. But, please note that 14 members of the PIVX Core Team voted to support this transition.

NOT included in this transition is the subscription to iStockPhoto. I will research how well that is being used currently. If it is, I will submit a new one time proposal to cover those costs.

Also NOT included in the transition are the costs for the 'related domains' that we hold to prevent 'scammers' from grabbing them and impersonating PIVX. When I submit a proposal to cover the costs of those, I will first ask people to vote on what they feel are closely enough related to warrant continuing ownership of them, and which to discard. I likely also will ask for enough funds to renew them until 2030 or something like that, and then we can work to transfer ownership of them to a new person/entity (Perhaps the PIVX Foundation) without the need to worry about any accounting for the next 8+ years.

Thank you everyone!

 

[Eric_Stanek]

Currently, this proposal is passing, but I asked it be voted down as it has been replaced.
If it does end up getting funded, I will donate the funds to the 'Slush Fund' handled by @Sparrow .