Oasis Staking Guide: Stake Oasis (ROSE) with Ledger

<!--kg-card-begin: markdown--><p> </p> <!--kg-card-end: markdown--><p><em>Clorio wallet is in beta version with an open sourced codebase. It is highly recommended to verify the checksum of the application if using a desktop version.</em></p><p><a href="https://p2p.org/mina?ref=p2p.org">Mina</a> is a lightweight, highly efficient blockchain allowing network participants to seamlessly join the network to verify and secure the chain. On the Mina blockchain you can stake your MINA tokens to earn staking rewards - currently up to 24% APY. </p><p>The following guide walks you through Mina staking using <a href="https://clor.io/?ref=p2p.org">Clorio wallet</a>. Clorio is a Mina specific wallet which lets you store, send and stake your <a href="https://p2p.org/mina?ref=p2p.org">Mina</a> tokens.</p><hr><h2 id="staking-mina-protocol-mina-video-guide">Staking Mina Protocol (MINA): Video Guide</h2><p></p><!--kg-card-begin: markdown--><iframe width="560" height="315" src="https://www.youtube.com/embed/Pgbt-DXWX_A" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe><!--kg-card-end: markdown--><hr><h2 id="staking-mina-using-clorio">Staking MINA Using Clorio </h2><p></p><p>For more information, follow the steps below.</p><ol><li><strong>Creating a Mina Wallet</strong></li><li><strong>Staking Mina using Clorio</strong></li></ol><!--kg-card-begin: markdown--><p> </p> <!--kg-card-end: markdown--><h3 id="1-creating-a-mina-wallet">1. Creating a Mina Wallet<br></h3><p>It is possible to access Clorio using Ledger wallet if you have installed the <a href="https://docs.minaprotocol.com/en/advanced/ledger-app-mina?ref=p2p.org">Mina app</a>.</p><ol><li>Visit <a href="https://mainnet.clor.io/?ref=p2p.org"><strong>mainnet.clor.io</strong></a> and press <strong>Create</strong> <strong>wallet</strong>. Select your preferred way of accessing the wallet.</li></ol><figure class="kg-card kg-image-card"><img src="https://lh6.googleusercontent.com/uxaxr6vCdtp5Ey8JfYfkKrN3zov67lUyqNGylWldR1n2PxH0yO5f6ZpobmhKzgFPH270NHbn860d41GoUSdczbmH7mZsegxGEvaKLVlZg0fZ8x-5BdiZR2uJtbJxLFT0uDAcMMul" class="kg-image" alt loading="lazy"></figure><p>2. Save your private key in a safe place. Download a PDF paperwallet and press <strong>Continue</strong>.</p><figure class="kg-card kg-image-card"><img src="https://lh3.googleusercontent.com/G0CSbFS6gCocTHjnrEqb0t5N1gjWtCTbsqWYivolqbBlw2tQRo_OOSPxNrmDKkvSkjXtGcZ0PqVkiV0orpUA6a-13yQBFFwO74882yFH9pKPIgNhrQ33xbKGJvije702lS5rSs43" class="kg-image" alt loading="lazy"></figure><p>3. Verify your private key and press <strong>Continue</strong>.</p><figure class="kg-card kg-image-card"><img src="https://lh5.googleusercontent.com/5uMlUgP9jFsUiVd6rHZyX5vTrYDznK_3t59MS_ue5WrYHpI559hq_OAo9OW0SxMIKmyIpZ6OgzkrYyj1lJtwihA4xHtqaLTjjBJcJxld3UDDtRHFrX8G3a62utUDz4PEva187eGi" class="kg-image" alt loading="lazy"></figure><p>4. Transfer Mina to your address. Note that for the first transaction, 1 MINA will be taken by the protocol as a wallet creation tax.</p><figure class="kg-card kg-image-card"><img src="https://lh3.googleusercontent.com/ors6Ati_Uz4xLH3ZSXF7GOH4Hahcx9obpe3xx3Sbg_wtsXQASsR7OJygHoGFmkcBEnXVxODnH5qOtq7DbRi550KuE0KST2thuNX1syi0kcrBHIf21dLdRmHyC7eZ2waXzZQXDqia" class="kg-image" alt loading="lazy"></figure><p>Your Mina wallet is now live and you can manage your Mina assets on the blockchain.</p><hr><h3 id="2-stake-your-mina-tokens-with-p2p">2. Stake your MINA tokens with P2P </h3><p>To stake your <a href="https://www.p2p.org/mina?ref=p2p.org">MINA</a> tokens and earn staking rewards, follow the steps outlined below.</p><ol><li>Access your wallet if needed and go to the staking hub. Select <strong>P2P Validator</strong> and click <strong>Delegate</strong>.</li></ol><figure class="kg-card kg-image-card"><img src="https://lh6.googleusercontent.com/nj32r4V7V15HEwQ0cG8dskV6lgv0K4KNcSkiv7bGY_OY-5Fj9riesVov8gw5fsF7VCgVYGsZlYUILlVFvikOciLKd2nT8CEK9XVx6U_2mA3qdiQoqI7QkoluzqpE9_o2k6Y8GTqi" class="kg-image" alt loading="lazy"></figure><p>2. <strong>Confirm</strong> the action.</p><figure class="kg-card kg-image-card"><img src="https://lh4.googleusercontent.com/0RLBTMZ_V9i7YHKwffPYTwXu9NXY2bu9CKTbWmYtwr15AaS6i9xpxKtOFV-RVfoK_mYrqZsC10OOSVyMNXsyhgf79X3wTZtcUn6UFxMhAQc3poyEkA8ojBtzaRnWUFD5zpg9WnFE" class="kg-image" alt loading="lazy"></figure><p>3. Set the transaction fee and click <strong>Proceed. </strong>In most cases you can use a default value. It is possible to check <a href="https://feenow.minascan.com/?ref=p2p.org">feenow.minascan.com</a> to see the current state.</p><figure class="kg-card kg-image-card"><img src="https://lh3.googleusercontent.com/TG2ea1yagMJO8XF9K4jlUdbJvA35ojQLtgArLTKhv707FZRuDio3X2qJ7Eg6FP4bFgh8ePv3L1OS1IRJMX_bSICPUt47mFBRy7-tMLtxQhLVtzON7azUwja9sDdMCirZVdjOpVvI" class="kg-image" alt loading="lazy"></figure><p>4. Confirm the transaction using your Private Key.</p><figure class="kg-card kg-image-card"><img src="https://lh5.googleusercontent.com/4OVTlFVH4BAN1Qd3fJQ69G6KmuI-mhxIheb3cneH_Ge1dpPXJ-h_idoFlI5P4iJ0KyEZm9SEzHk3rP9YXBhmpQbPvBrfjxBP4hPC7R3KGXtqeKzWqyzgWQ1UOTc1U5eu_xMw9D5y" class="kg-image" alt loading="lazy"></figure><p>5. After the confirmation you will be able to see your current delegation. Also, you can go to the overview tab to check the transaction status.</p><figure class="kg-card kg-image-card"><img src="https://lh5.googleusercontent.com/HBddWKJjO-Su1ZUnbI7yUyQDHHZm6MqgxVkS3gnOIFwWJdCq3QacC5kvRdOlCoZBldVHvuazif9WtCdLga7tuHBpMBFmpWNYpRl7rfP8WnfZDxe0VhhvEHHQsiAwGYJ8oAf2d_mW" class="kg-image" alt loading="lazy"></figure><p>Congratulations! You have successfully delegated MINA to P2P Validator. You will now start earning regular staking rewards. </p><hr><p>Each block producer has own payout conditions, manually distributing staking rewards. Your delegation will start participating in the consensus after the next epoch (1 epoch is ~15 days). <strong>If you delegate from a locked account it is recommended to create a separate address, periodically transfer rewards and delegate from there as well</strong>. It increases the chances of receiving a supercharged coinbase (double block reward) benefitting all delegators of a particular pool.</p><hr><p><em>If you have any questions, please feel free to join our </em><a href="http://t.me/P2Pstaking?ref=p2p.org"><em>Telegram chat</em></a><em>. We are always open for communication.</em></p><hr><h3 id="about-p2p-validator">About P2P Validator</h3><p>P2P Validator is a world-leading staking provider with the best industry security practices and proven expertise. We provide comprehensive due-diligence of digital assets and offer only top-notch staking opportunities. At the time of the latest update, more than $3.2 billion is staked with P2P Validator by over 10,000 delegators across 25+ networks. </p><p>We are actively involved in <a href="https://p2p.org/mina?ref=p2p.org">Mina staking</a> since the first testnet being an early genesis member and mainnet seed peer provider.<br></p><ul><li><strong>Web</strong>: <a href="https://p2p.org/?ref=p2p.org">p2p.org</a></li><li><strong>Stake Mina with P2P</strong>: <a href="https://p2p.org/mina?ref=p2p.org">p2p.org/mina</a></li><li><strong>Twitter</strong>: <a href="https://twitter.com/P2Pvalidator?ref=p2p.org">@p2pvalidator</a></li><li><strong>LinkedIn</strong>: <a href="https://www.linkedin.com/company/p2p-org/?ref=p2p.org">linkedin.com/company/p2p-org/</a></li><li><strong>Telegram</strong>: <a href="https://t.me/P2Pstaking?ref=p2p.org">t.me/P2Pstaking</a></li></ul>

<h3 id="summary">Summary</h3><p>115 validators of different staking providers received "unapplied slash" during the era 2249 in Kusama due to not sending "I'm online" signal. 45 out of 115 validators are P2P validators where a possible slash would be around 0.6% of active stake.</p><p>Unapplied status means that it can be reverted through governance action, which is exactly what happened in that case.</p><h3 id="customer-impact">Customer Impact</h3><p>All slashings have been reverted and no customer funds are impacted thanks to councils who supported the request and voted for the <a href="https://kusama.polkassembly.io/motion/295?ref=p2p.org">motion 295</a> to cancel the slashing.</p><h2 id="what-happened">What Happened</h2><p>Almost all of the active P2P Validator nodes were running <strong>0.9.0 version</strong>. Monitoring showed perfect performance although sometimes we detected CPU spikes during the election.</p><p>On May 13, there was a release note issued for the <a href="https://github.com/paritytech/polkadot/releases/tag/v0.9.1?ref=p2p.org">0.9.1 version</a>. The release had “Low (upgrade at your convenience)” upgrade priority. P2P started to roll out this version gradually because this is our SoP for low priority upgrades.</p><p>On May 14, we got a notification via Kusama Validator Lounge chat which said: <em>“Just a heads up that the<strong> </strong>9010 runtime upgrade will happen in ~55 minutes at block 7,468,792. If your node is not on at least version v0.9.0, it will not be able to sync after that”</em></p><p>After the runtime 9010 had been applied, part of our monitoring services based on @polkadot-js/api stopped working due to it being an older version than required with the fresh runtime upgrade. We had an alert which would  have been triggered if all CPU cores had 95%+ load at once, but as only one core had been overloaded, it didn't fire. Therefore, we didn’t figure out that a  number of our nodes would get slashed. It took about 40 mins to understand what exactly had happened.</p><p><strong>See diagrams:</strong></p><p>CPU time of node under v0.9.0 that experienced CPU load during the election.</p><figure class="kg-card kg-image-card"><img src="https://lh4.googleusercontent.com/xbMcNNQasSYF-CWTDqRaczqDUKVhZcf2FFbTC5_ubeGcZs1mpMGCES6MOxYgZxW0NtLCNl4Nzcb5qNp5IzYk0BcgHQCrp2s0qVazGGMvct2QbkIgbpMlDX0dfNGcSPE373RGV0pJ" class="kg-image" alt loading="lazy"></figure><p>CPU time of node under v0.9.1 - no spikes</p><p></p><figure class="kg-card kg-image-card"><img src="https://lh5.googleusercontent.com/uqe0ePHHepSaTDa5rueOthMvifsFhezANDS7Y-vkQ5QxbfSO1QuPJbHiqVcwf9I8Xshh7pd2uzS-VWtzbZEGtJzgO02JojrjRAAaOEZwpaVdiAMNg835F0KHctcxPkuSUEab1XGO" class="kg-image" alt loading="lazy"></figure><p>Logs records nodes running on v0.9.0</p><p></p><p>Looking at logs it becomes clear that after the runtime upgrade, nodes were experiencing some issues with performance. We caught 61780 events, which is a huge number and very unusual.</p><figure class="kg-card kg-image-card"><img src="https://lh3.googleusercontent.com/bQTU71RRrNxVcfTAW8tKOgg-FQmrsrbYq3k5v2DeFqyyh4rWq3oyb-hbUq30BfzL5QdeuCda8XisWvr1C5i62oYkFPMpADfKWv5zhcdzbYGrC6tieoJzZXwTHDd2syjP0qB2Xk9l" class="kg-image" alt loading="lazy"></figure><figure class="kg-card kg-image-card"><img src="https://lh6.googleusercontent.com/tyErRh-yx8nhKGrEDIWdEcEwdmMKQfH-bv0w0VCNaZ_kG3yFmS2-7wNJq-EJmERFnoiUl1tV8LWSXpINXw8lt6hOoJ_Zyf5z9QoQpmTplkZUNfNLAHs2HalIv42I7QvVeE4PYT59" class="kg-image" alt loading="lazy"></figure><p><br>During CPU spikes, our validators were not able to send "heartbeat" events. Therefore all 115 validators got slashed due to the concurrent unresponsiveness of a bunch of validators, see offence <a href="https://wiki.polkadot.network/docs/en/learn-staking?ref=p2p.org#slashing">Level 2</a>.</p><p></p><p><strong>In order to avoid further slashing, P2P team undertook the necessary steps as follows:</strong></p><p><strong>May 14, 21:30:00</strong></p><ul><li>Fix monitoring service</li></ul><p><strong>May 15, 00:30:00</strong></p><ul><li>Validation is recovered on all P2P validators</li></ul><p><strong>May 15, 00:40:00</strong></p><ul><li>Investigation in collaboration with other nodes operators and the Kusama dev team occurred.</li></ul><p><strong>May 15, 05:00:00</strong></p><ul><li>All Kusama nodes have upgraded to v0.9.1 that solved CPU spikes issue</li></ul><p><strong>May 15, 19:00:00</strong></p><ul><li>Set “--wasm-execution Compiled” flag for all Kusama nodes<br></li></ul><p>----</p><p>Slashing was reverted by one of council member Raul Romanutti who proposed cancellation of slash submitting the <a href="https://kusama.polkassembly.io/motion/295?ref=p2p.org">motion 295</a> and no user funds were affected.</p><p>----</p><h3 id="lessons-learnt">Lessons Learnt</h3><ul><li>We should have  more resilient monitoring for our nodes and infrastructure</li><li>Follow polkadot-js releases to upgrade libraries on time</li><li>Look closely at network status during runtime upgrades</li></ul><h3 id="what-s-next">What’s Next</h3><ul><li>We are going to work on new infrastructure and improvements for monitoring services that will help us to avoid such cases.</li></ul>