IoTeX Delegate Documentation
  • Introduction
    • 👋 Welcome
    • What is a Delegate
    • Benefits and Rewards
    • Delegate Requirements
    • Hardware Specs
  • Get Started
    • Profile registration
      • Delegate Accounts
      • Name Registration
      • Staking Bucket
      • Server Information
      • Rewards Policy
      • Profile Data
    • Node Configuration
      • Acquire a server
      • Install requirements
      • Install the node software
      • Run the node
      • Verify the node status
    • Advanced
      • Server provider
      • Edge Proxy
      • Kubernetes
      • High Availability
      • Gravity Chain Binding
      • Improvements
    • Hosted Service
    • Delegate Endorsement
      • Delegate Sponsorship Program
      • Tutorials
  • Delegate Management
    • Access the portal
    • Delegate Performance
    • Delegate Rewards
    • Profile settings
    • Advanced Configuration
  • Addendum
    • Profits Projections
    • Glossary
Powered by GitBook
On this page
  1. Get Started
  2. Advanced

Gravity Chain Binding

PreviousHigh AvailabilityNextImprovements

Last updated 3 years ago

This documentation only applies if you are syncing your node from a block height 1 or anyway prior to Mainnet 1.0 height (5157001). You can ignore this if you are syncing your node starting from an .

Before the final release of IoTeX 1.0, the blockchain relied on the delegate election result fetched from the IoTeX staking contract deployed on Ethereum. As a consequence, if you intend to sync your node from the very first block, you will need to provide a list of Ethereum JSON-RPC endpoints for the node to consume the relevant data from Ethereum.

While we provide a list of default JSON-RPC endpoints, delegates are encouraged to set up their own endpoint, to be more decentralized, secured, and performant.

There are two approaches that have been experimented:

  • Setup your own Ethereum node. No need to mine, just use it as an Ethereum API Getheway ( and ), and expose the JSON-RPC endpoint.

  • Use Ethereum blockchain infrastructure. Signing up for an account and creating a project. The JSON-RPC endpoint would be . For more details of setting up the Infura endpoint, please check .

After getting your own JSON-RPC endpoint, you can add it into your node configuration fileconfig.yamland restart your server. Then, your IoTeX server will read from this endpoint to get Ethereum data. You could also create and add multiple endpoints for the sake of robustness.

...
chain:
  ...
  committee:
    ...
    gravityChainAPIs:
      - [YOUR JSON-RPC ENDPOINT]
      ...
    ...
  ...
...
geth
parity
Infura
https://mainnet.infura.io/v3/YOUR-PROJECT-ID
here
official snapshot