Notice: Polkadot has migrated to AssetHub. Balances, data, referenda, and other on-chain activity has moved to AssetHub.Learn more
[Small Spender] Parasnaps Maintenance Follow-up for Market Correction
This is a follow-up proposal on Referendum 170.
Since we originally created the retroactive Parasnaps maintenance proposal, the market experienced a significant downturn from the EMA7 specified in the proposal (KSMUSD @ $31.345). Despite accounting for some market volatility and 5% slippage in the proposal, the resulting difference between our costs and the payout is large in this case and therefore, we would like to follow up with this proposal.
Please find here a screenshot showing our sale of the KSM at a price of $24.75. This proposal is to cover the remaining $5748.15, or 223.02 KSM at an EMA7 of $25.774 for KSMUSD.
We would also like to address one concern that was raised in our previous proposal regarding providing snapshot only for Polkadot. During the entire time that the Parasnaps service was live, we provided daily snapshots for both paritydb and rocksdb on the Polkadot and Kusama relay chains. Unfortunately, we cannot prove this through the Wayback Machine, but would appreciate if those that used the service could vouch for our statement.
Comments (2)
Requested
Proposal Passed
Summary
0%
Aye
0%
Nay
Aye (213)0.0 DOT
Support0.0 DOT
Nay (34)0.0 DOT
Hey tugy,
As an end user of parasnaps.io in the past, I'm vouching here my support related to your statement.
I can confirm that parasnaps.io was giving support for Polkadot and also Kusama on both databases (paritydb and rocksdb). The service served me well when I most needed a fast and reliable snapshot provider and also when testing around a few hosting providers for my validators. The service also provided a simple to use interactive shell where the user could select the chain, database and location (6/7 location options) from where the snapshot would be downloaded from.
Many Thanks for the service provided.
paulo // turboflakes.io
Hello,
We are in the process of validating a true need for a service to assist teams with crafting and completing successful treasury proposals, so they can focus on building. We would love to hear about your experience with this proposal. If you are willing to take a few minutes, please fill out this form about your experience with the OpenGov treasury proposal process: https://forms.gle/MwDij4adXEQd7Um79
Feel free to leave out any details that your team is not comfortable with sharing, but the more info you can provide, the better we will be able to assess the potential need for our services.
For more info, follow us on Twitter/X: https://twitter.com/OpenGovAssist