This guide will help you setup a NEAR validator node on Guildnet. We provide step by step instructions to assist even those new to validating. We'd appreciate your contribution and feedback on this guide.
- Server Requirements
- Launch validator node
- Create a wallet
- Install Near-Cli
- Setting up Environment
- Authorize NEAR-Cli
- Create Staking Pool
- Delegate Tokens
- Monitor Validator Status
- Running as a docker container
To become a validator your server will need to meet these minimum requirements:
At least 2-Core (4-Thread) Intel i7/Xeon equivalent
At least 16GB RAM
At least 100GB SSD (Note: HDD will not work)You'll be working with two machines, a server for the validator node, and your personal machine/monitor machine to install near-cli, create the wallet, monitor and control the validator node.
To use Nearup On the Server:
sudo apt install python3 git curlsudo apt install python3-pip -yTo use Compile Script and Systemd:
sudo apt install python3 git curl snapd- There are 2 ways to install nearcore currently. You can use Nearup or you can compile the source and use systemd to manage it.
- Step 1.Install Nearup
Clear nearup folder
rm -Rf ~/.nearup
On the Server: The Prerequisite has python3, git and curl toolset, which have been installed in previous step. Run the following commmand.
pip3 install --user --upgrade nearup
USER_BASE_BIN=$(python3 -m site --user-base)/bin
export PATH="$USER_BASE_BIN:$PATH"```
On each run, nearup self-updates to the latest version.
- **Step 2. Choose a staking-pool AccountId**
On the first run, nearup will ask you to enter a staking-pool AccountId, please choose a name for your staking-pool AccountId, it must end with ".stake.guildnet", e.g. *MyStakingPool.stake.guildnet*.
You should go to [https://near-guildnet.github.io/staking-pool-factory](https://near-guildnet.github.io/staking-pool-factory/) to check if the name is available.
/!\ Don't create your staking-pool contract yet, just check if the name is available. /!\
- **Step 3. Start nearup guildnet**
We recommand to use Officially Compiled Binary to launch a validator node, which is suitable to run on VPS. Then, input your staking pool ID in the prompt by this command:
```bash
nearup run guildnet
Check validator_key.json is generated for staking pool.
ls ~/.near/guildnet
validator_key.json node_key.json config.json data genesis.json
cat ~/.near/guildnet/validator_key.json | grep public_keyTake note of the validator public_key
"public_key": "ed25519:**TAKE-NOTE-OF-THIS**"Check running status of validator node. If "V/" is showning up, your pool is selected in current validators list.
nearup logs -fOn your personal machine: You will need a wallet.
- Create a GuildNet Wallet go to: https://wallet.openshards.io be sure to record your wallet address and seed phrase (12 words)
- Request 75,000 GuildNet tokens from the faucet GuildNet Faucet
On your personal machine:
NEAR CLI is a Node.js application that relies on near-api-js to generate secure keys, connect to the NEAR platform and send transactions to the network on your behalf.
note that Node.js version 10+ is required to run NEAR CLI
Note: You don't need to install Near-Cli on the server. We reccomend to install near-cli on your personal machine or a separate machine for increased security and performance. However it still can be installed on the same machine.
Nodes.js and npm can be install by
curl -sL https://deb.nodesource.com/setup_15.x | sudo -E bash -
sudo apt install build-essential nodejs
PATH="$PATH"node -v
v15.X.X
npm -v
7.X.Xnpm install -g near-cliTo use the guildnet network you need to update the environment via the command line.
Open a command prompt and run
export NODE_ENV=guildnetAdd (export NODE_ENV=guildnet) to the end of the ~/.bashrc file to ensure it persists system restarts.
echo 'export NODE_ENV=guildnet' >> ~/.bashrc To authorize NEAR-Cli access to your GuildNet wallet account we need to login via the command prompt.
near loginSubsequently, the browser will be opened, if it does not simply copy and paste the generated link into the browser. You may need to restore your wallet account via Seed Phase. This action will authorize NEAR-cli access to main account via the shell.
We recommend using <your account>.guildnet as main accountId and <your pool>.stake.guildnet as pool ID below.
Now, You can manage your main wallet account and smart contract with the NEAR CLI.
For account:
near login # logging in through NEAR protocol wallet
near create-account <accountId> # create a developer account with --masterAccount (required), publicKey and initialBalance
near state <accountId> # view account state
near keys <accountId> # view account public keys
near send <sender> <receiver> <amount> # send tokens to given receiver
near stake <accountId> <stakingKey> <amount> # create staking transaction (stakingKey is base58 encoded)
near delete <accountId> <beneficiaryId> # delete an account and transfer funds to beneficiary account
near delete-key [accessKey] # delete access key
For smart contract:
near deploy [accountId] [wasmFile] [initFunction] [initArgs] [initGas] [initDeposit] # deploy your smart contract
near dev-deploy [wasmFile] # deploy your smart contract using temporary account (TestNet only)
near call <contractName> <methodName> [args] # schedule smart contract call which can modify state
near view <contractName> <methodName> [args] # make smart contract call which can view state
near clean check your public key file of main account.
ls ~/.near-credentials/guildnet
staketest.guildnet.jsonYou need to setup a staking pool, the easiest way is to go back to https://near-guildnet.github.io/staking-pool-factory/ with the staking-pool AccountId you selected, and the validator public_key you got while starting nearup and complete the process to create the staking-pool contract.
You can also setup a staking pool from the command line using the create_staking_pool method. Check public key from ~/.near/guildnet/validator_key.json on your validator server:
cat ~/.near/guildnet/validator_key.json | grep public_keynear call stake.guildnet create_staking_pool '{"staking_pool_id": "<Pool ID need to be generated>", "owner_id": "<Master Account ID>", "stake_public_key": "<public_key in validator_key.json>", "reward_fee_fraction": {"numerator": 10, "denominator": 100}}' --accountId="<Master Account ID>" --amount=30 --gas=300000000000000
example:
near call stake.guildnet create_staking_pool '{"staking_pool_id": "testpool", "owner_id": "staketest.guildnet", "stake_public_key": "ed25519:4x1LrkFvxnh8Aeh8NQc9cn15XuYAVHA2aN6WVhFfCdaE", "reward_fee_fraction": {"numerator": 10, "denominator": 100}}' --accountId="blaze.guildnet" --amount=30 --gas=300000000000000- As a user, to deposit and stake NEAR tokens
near call <validator pool ID> deposit_and_stake --amount <amount of tokens> --accountId <main account ID>
example:
near call testpool.stake.guildnet deposit_and_stake --amount 70000 --accountId staketest.guildnet- To update current rewards:
near call <validator pool ID> ping '{}' --accountId <main account ID>
example:
near call testpool.stake.guildnet ping '{}' --accountId staketest.guildnetOnce the 75K tokens are delegated faucet to the node, additional toekns can be requested for delegation in the Tokens channel on Discord.
To be a validator, you can execute Near-cli to monitor and manager validator pool by your main account.
- Check if your pool is in proposals at first.
near proposals | grep testpool.stake.guildnet- Check if your pool is in current validators list.
near validators current | grep testpool.stake.guildnet- Check if your pool is in next validators list.
near validators next | grep testpool.stake.guildnet- Check the validator seat price.
near validators current | grep "seat price"If your stake is not enough to get a seat, please participate in the following challenges to get more tokens. (Coming Soon...)
We are working on it