In this article we will guide you through the process of staking Agoric governance token (BLD) using the Keplr wallet.
To begin, head over to the Keplr wallet website.
1. You will be prompted to install the Keplr browser extension. Once you have done so, open the extension and either create an account or login by importing an account already created.
2. Once your account is set up, you now need to navigate to the Agoric section and select Stake. Click Manage to proceed with delegation.
3. Press Delegate.
4. Input the amount and press Delegate.
5. Confirm the transaction in Keplr Wallet to start staking!
P2P Validator is a world-leading non-custodial staking provider with the best industry practices and proven expertise. We provide comprehensive due-diligence of digital assets and offer only high class staking opportunities securing more than 3 billion of USD value at the time of the latest update.
P2P Validator is trusted by over 24,000 delegators across 25+ networks. We are a major player in all networks we support because of our experience, commitments and our reputation. We pay special attention to the process of governance. P2P invested in Agoric with intention to contribute and provide long term support to the network.
Want to stake Agoric (BLD) with us? Visit https://p2p.org/agoric to find out more about Agoric staking.
If you have any questions, feel free to join our Telegram chat, we are always open for communication.
Get the latest posts delivered right to your inboxSubscribe
<h2 id="tldr"><strong>TLDR</strong></h2><p><br>Due to a sudden spike of transactions, mainnet validator node ran out of disk space, leading to inability to produce blocks and corruption of the node state.</p><h2 id="what-happened"><strong>What happened?</strong></h2><p><br>Disk usage grew quite fast and mainnet pool p2p-org.poolv1.near stopped producing blocks since ~07:00 UTC on 16th of January. Epoch ended ~10:00 UTC and by that time the node had surpassed the epochal kick-out threshold for downtime. Therefore, it was scheduled for temporary kick-out for the next two epochs. While resolving the issue, the validator remained offline for the following epoch resulting in one additional forfeit epoch. Overall, the node was offline for ~3,25 epochs and the validator pool lost 4 full epochs of staking rewards.</p><h2 id="what-went-wrong"><strong>What went wrong?</strong></h2><p><br><strong>The potential impact of the issue was underestimated.</strong></p><p>It was expected to rely on a recent state snapshot that would be readily available. We had no cold backup of a recent node state while available backup nodes were subject to the same issue leading to a loss of access to a synced node. In fact, the official public back-up archives were corrupted too. A <a href="https://github.com/near/nearcore/issues/6095?ref=p2p.org">GitHub issue</a> was created afterwards.</p><p><strong>Monitoring was insufficient.</strong></p><p>Near validation infrastructure was undergoing an overhaul, some monitoring facilities were offline. It was expected that the amount of space used on disk would grow more or less linearly. With ~100 GiB of free space it could last for a month. Space clogged up in a matter of days while disk monitoring was not set appropriately to catch the spike and warn in advance.</p><h2 id="what-went-well"><strong>What went well?</strong></h2><p><br>It was immediately notified that node stopped producing blocks and the root cause was identified almost simultaneously. Quite a few validators were affected by the issue, and the community was very helpful.</p><h2 id="impact-on-clients"><strong>Impact on clients</strong></h2><p><br>All our Near delegators were affected and lost four epochs of staking rewards. To compensate our delegators in full and mitigate their loss, P2P waived the fees until the end of February.</p><h2 id="lessons-learned"><strong>Lessons learned</strong></h2><p><br>We should have had better monitoring and collecting disk usage metrics from all nodes at all times including mainnet, backup and Near RPC node. It is important to ensure that back-up nodes are running & synced at all times. In addition, it is important to establish the process of making cold snapshots of the node state on a regular basis and spread this practice to all available networks.</p><p>P2P takes full responsibility for the event that led to the weak performance and we are sorry for the inconvenience. Please be assured that P2P is taking actions to eliminate even a small probability of such an event occurring in future.</p><hr><p><em>If you have any questions feel free to join our</em><a href="https://t.me/P2Pstaking?ref=p2p.org"><em> Telegram chat</em></a><em>, we are always open for communication. </em><br><em>Special thanks to Evgeny Kuzyakov & DenysK for providing a state snapshot and general support.</em></p><hr>
from p2p validator
from p2p validator