Suncex Docs
  • Summary
  • DOCUMENTATION
    • Learn about the Fuse Platform
      • Fuse Overview: vision, strategy and platform components
      • The Fuse Network Blockchain
        • Discovering the Network
        • Fuse Network Consensus
        • Delegation through Staking with Validators
        • Ethereum (EVM) Compatibility and Smart Contracts
        • Boosting Fuse's Scalability
      • Fuse Token (FUSE)
        • FUSE Tokenomics
        • Exchanges, Wallets, On-Ramps and DeFi Tools Supporting FUSE
        • FUSE on Other Chains
      • Interoperability
      • Fuse Governance and Development
        • Fuse Assembly
        • Fuse Improvement Proposals (FIPs)
      • Wallets supporting Fuse Network
    • Fuse for Business
    • Things you can do on Fuse
      • Interacting with the Fuse Network Blockchain
      • Fuse Ecosystem
      • Community
      • Grants and Bounties
    • Fuse Mobile Infrastructure Use Cases
  • Developers
    • Network Details
      • Fuse Network Mainnet
      • Fuse Network Testnet Spark
      • Token Faucets
      • Network Upgrades
        • Upgrade Guide
        • Upgrade Guide (explorer nodes)
        • Block 13,800,000 Fork
        • FIP's
    • Fuse Consensus
      • Contracts Overview
      • Stake, Delegate and Withdraw
      • Vote
      • End-of-Cycle Flow
      • Contract Addresses
    • How to run network nodes
    • Resources & Tools
      • TheGraph
      • WalletConnect on Fuse
    • Important smart contracts
      • Fuse Token
      • Fuse Dollar
      • Major Deployed Contracts
      • Bridges
        • Ethereum ↔ Fuse GoodDollar Token
        • Ethereum ↔ Fuse ERC20 Tokens
        • BSC ↔ Fuse BNB
        • BSC ↔ Fuse Native
        • BSC ↔ Fuse ERC20
        • Ethereum ↔ Fuse Native
    • How to become a validator
      • Getting started as a validator
      • Getting started as on the Spark testnet
  • Links
    • Discord
    • Facebook
    • GitHub
    • LinkedIn
    • Medium
    • Telegram
    • Twitter
    • YouTube
    • Join our mailing list
Powered by GitBook
On this page
  • Pre-requirements
  • How to become a Fuse validator
  • Step 1: Download the `quickstart.sh` script and an `.env` example file:
  • Step 2: Update the `.env` file:
  • Step 3: Run the script as a validator:
  • Step 5: Stake and/or delegate!
  • Step 6: Wait for 1 cycle (approximately 48 hours).
  1. Developers
  2. How to become a validator

Getting started as a validator

PreviousHow to become a validatorNextGetting started as on the Spark testnet

Last updated 2 years ago

Pre-requirements

In order to be a Fuse validator, you first must see that you meet the pre-requirements:

  • You know what it means to be a Fuse validator - How to become a validator

  • You have at least 100K FUSE tokens or you will have an aggregated delegation of at least 100K FUSE tokens (you can purchase FUSE token on ).

  • You have an always-on hardware that meets the pre-requisites -

How to become a Fuse validator

To quickly become a validator, follow this steps:

Step 1: Download the `quickstart.sh` script and an `.env` example file:

mkdir fuse-validator
cd fuse-validator
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

Step 2: Update the `.env` file:

set "sudo" on `PERMISSION_PREFIX` if running docker/docker-compose requires root

(optional) set 'VAL_NAME' to display a custom name on health.fuse.io (cannot contain spaces)

Step 3: Run the script as a validator:

./quickstart.sh

Step 5: Stake and/or delegate!

Stake

To stake FUSE tokens, all you should do is send your FUSE tokens to the Fuse Consensus contract address over the Fuse network from the validator address.

The Fuse Consensus contract address: 0x3014ca10b91cb3D0AD85fEf7A3Cb95BCAc9c0f79

The easiest way to do so, is to import your private key or key-store file to your favourite wallet (for example Metamask), switch network to Fuse and send the FUSE tokens (native tokens) to the Consensus contract address.

You can find your key-store (containing your private key) and the password for the created account in:

$HOME/fusenet/config/keys/FuseNetwork/UTC--xxxx

$HOME/fusenet/config/pass.pwd

Delegate

To delegate, just send the FUSE tokens from any address to the Consensus contract address with the data: 0x5c19a95c000000000000000000000000<address without 0x>.

Example:

For the address: 0xb8ce4a040e8aa33bbe2de62e92851b7d7afd52de Use: 0x5c19a95c000000000000000000000000b8ce4a040e8aa33bbe2de62e92851b7d7afd52de as the data.

5c19a95c is for the delegate(address) function signature.

b8ce4a040e8aa33bbe2de62e92851b7d7afd52dein this example is an address you're delegating to (without the 0x prefix)

Step 6: Wait for 1 cycle (approximately 48 hours).

Wait until the next cycle is started.

After running the script successfully, you will see your address in the site.

You can see that you are validating both in the site and on the site.

For live support, contact us on or . Good luck and happy validating!

Uniswap
How to run network nodes
health
health
explorer
Telegram
Discord