Getting started as a validator on Spark testnet
To be a Spark validator, you first must see that you meet the pre-requirements:
- You know what it means to be a Spark validator.
- You have at least 100K SPARK tokens, or you will have an aggregated delegation of at least 100K SPARK tokens - To apply for SPARK test tokens, fill out this form
To quickly become a validator, follow these steps:
wget -O quickstart.sh https://raw.githubusercontent.com/fuseio/fuse-network/master/scripts/quickstart.sh
chmod 777 quickstart.sh
wget -O .env https://raw.githubusercontent.com/fuseio/fuse-network/master/scripts/examples/.env.validator.example
set "sudo" on `PERMISSION_PREFIX` if running docker/docker-compose requires root
add the following line:
(optional) set 'VAL_NAME' to display a custom name on health.fusespark.io (cannot contain spaces)
To stake SPARK tokens, all you should do is send your SPARK tokens to the Spark Consensus contract address over the Spark Network from the validator address.
The Spark Consensus contract address: 0xC8c3a332f9e4CE6bfFFcf967026cB006Db2311c7
The easiest way is to import your private key or key-store file to your favorite wallet (for example, Metamask), switch the network to Spark, and send the SPARK tokens (native testnet tokens) to the Consensus contract address.
You can find your key-store (containing your private key) and the password for the created account in:
To delegate, send the SPARK tokens from any address to the Consensus contract address with the data:
0x5c19a95c000000000000000000000000<address without 0x>.
For the address:
0x5c19a95c000000000000000000000000b8ce4a040e8aa33bbe2de62e92851b7d7afd52deas the data.
5c19a95cis for the
b8ce4a040e8aa33bbe2de62e92851b7d7afd52dein this example, is an address you're delegating to (without the
Wait until the next cycle is started.