Juicy Stake
Search
⌃K

Staking Guide

A step by step guide to staking to the Juicy Stake Validator Node

Introduction

This guide assumes you have the Radix Desktop Wallet installed, and have XRD available to stake. If you haven't already installed the wallet, jump over to the official site first and do that. If you need help with the wallet installation then head over to the official help page for a guide.
This guide is subject to change, please come back regularly for updated instructions

1. Login to the Radix Desktop Wallet

Open the Radix Desktop Wallet, input your password, then click 'Open Wallet'

2. Select the 'Stake & Unstake' tab

Select the 'Stake & Unstake' tab from the left-hand menu

3. Paste the Juicy Stake node address into the 'Validator' box

Copy the Node ID below and paste it into the 'Validator' box
rv1qfjqequ27v2x8nsa5zcumrffkjf0fg8wh7344h7usqa6rdkr2aqtk4daacw

4. Enter the amount of XRD you wish to stake

Enter the amount of XRD you wish to stake into the 'Amount' box and then click the 'Stake' button
Remember not to stake your entire balance as you need a small amount of XRD for transaction fees
The minimum amount of XRD you can stake is 90 XRD

4. Authorize the stake request

After a short delay your wallet will ask for your PIN to authorize the stake request. Enter your PIN and click 'Confirm'

5. Review your staked tokens

After a few seconds you should be presented with a 'History' tab showing your recent staked token transfer
Congratulations, you've now successfully staked your tokens to the Juicy Stake Validator node! You can always check your current staking status by going to the 'Stake & Unstake' tab and viewing the right hand panel
From this panel you can also add more stake to the node or reduce your stake (which is covered in a separate tutorial, see link below)
Please remember there will be a delay when unstaking (approximately 2 weeks). The purpose of this delay is to allow the network sufficient time to determine confidently that the validator those tokens were delegated to hasn’t done anything malicious - no need to worry though, this is a totally normal procedure in DPoS networks.