Vote Nay - Maintenance for the substrate-api-client Jan-25 to Jun-25
2 years ago
development
Rejected
Based on the feedback to this proposal, we created a new proposal asking for USDT:
https://polkadot.polkassembly.io/referenda/1355
Please vote NAY on this one
Comments (2)
Requested
3.86K DOT
Proposal Failed
Lucky Friday would like to provide the following feedback from our team members. We have been specifically solicited to provide feedback on this particular referendum, collectively offering it and hope that it will help the proposer(s) of this referendum moving forward. As noted previously, we have unanimously voted NAY.
The reason is simple and quite clear: it does not conform to our voting philosophy in following the broad social consensus in asking for stable coins, as noted HERE.
Should this ref fail and be resubmitted asking for USDT or USDC, we will happily support the future refendum.
Lucky Friday votes as a collective based on the results of our internal voting procedures and enacted on chain via the OpenGov server bot. No single team member is required to provide any feedback about why he or she has voted in a particular direction, although it is highly encouraged and happens often. With respect to our team members' right to anonymity and the private format in which we conduct our votes, we will not be sharing the names of individuals who have chosen to provide said feedback.
We encourage all members of the Polkadot community to join our OpenGov Public Forum on Telegram, and we respectfully ask that all proponents of referenda interact with us here for the sake of transparency: https://t.me/+559tyPSfmGg0NzUx
On behalf of the Polkadot Hungary DAO:
We have voted Nay on this proposal. Considering that the requested funds are likely to be used for salary and infrastructure payments, we suggest asking for stablecoins instead. The use of stablecoins offers greater stability and predictability for such expenses and reduces the need to resubmit a top-up proposal in case of price volatility.
You can view how the Polkadot Hungary DAO evaluated ref. 1332 on our public page [here].
@yooo we weren't aware, that this would be a reason to vote against us.
We handle the price volatility not with top-up proposals, but by adjusting the scope. Once the money is in for a proposal, we calculate the amount of hours it is equivalent to and that's the amount of work we will put into it. Our priorization is always:
So, in the end, we adjust the amount of issues from 3. we implement within a package.
Thank you for this feedback, though. In case there are more who vote NAY because of this, we'd be happy to know.
Polkassembly is now a read-only archive. Commenting is disabled.