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
  • Stake
  • Delegate
  • Withdraw
  1. Developers
  2. Fuse Consensus

Stake, Delegate and Withdraw

PreviousContracts OverviewNextVote

Last updated 2 years ago

The basic requirement to become a Fuse chain validator is to have a stake amount of at least 100,000 Fuse tokens. The stake amount is the sum of staked and delegated Fuse tokens of the address. This guide walks trough the process of using MEW (MyEtherWallet.com) in the process of using Fuse network.Roadmap - Those functionalities will be built into our Studio and will not require any technical knowledge in the future.

Stake

There are two options to stake (both should be called from the address which would be the validator)

  1. 1.Send Fuse tokens to the - 0x3014ca10b91cb3D0AD85fEf7A3Cb95BCAc9c0f79 on the fuse network.

  2. 2.Call the `stake` function on the - 0x3014ca10b91cb3D0AD85fEf7A3Cb95BCAc9c0f79 on the fuse network.

Delegate

Fuse token holders who don't want to run a node by themselves but still wish to participate in governing the network can delegate any amount to one of the validators.Delegating is done by calling the `delegate` function on the with the validator address as data (see screenshot from MEW).

delegate

Withdraw

Both stakers and validators can withdraw their Fuse tokens, up to the staked/delegated amount, at any time. The withdrawn amount will be deducted from the validator stake amount, and if the stake amount becomes below the minimum stake amount - the validator will be removed from the Fuse chain validators list.There are two options to withdraw:

1.Call the `withdraw` function on the with one parameter - the amount to withdraw. This call is for stakers, and will reduce the stake amount of the sender address.

2.Call the `withdraw` function on the with two parameters - validator address and amount to withdraw. This call is for both stakers (who can use their own address as the parameter) and for delegators to withdraw their delegated stake on a specific validator.

withdraw option no. 1
withdraw option no. 2
consensus contract
consensus contract
consensus contract
consensus contract
consensus contract