🗃️Blockchains

Predefined blockchain configurations

0xWeb includes some blockchain configurations and default public RPC endpoints for:

Chain slug

Name

Modify the configuration

🙏 Change the RPC endpoints for those chains in configuration.

Edit the configuration yml by running:

0xweb config -e

A default configuration will be copied into the new configuration file, which should be opened with your default editor for yml files, if the file is not opened automatically, open the file manually, the file path will be printed in the terminal.

Add custom EVM-compatible chain

1 Add a new platform to the web3 section, for example:

web3:
  foo:
    chainId: 5555
    chainToken: FOO
    endpoints:
      - url: 'https://foo-rpc-example'
      - url: 'wss://foo-socket-url-example'
      - url: 'https://some-other-url'

2 Add the Blockchain Explorer configuration optionally to read the ABI and the sources.

0xWeb supports Etherscan and Blockscout forks, if there is one for your custom chain, add that information to the blockchainExplorer section

blockchainExplorer:
  foo:
    key: YOUR_KEY
    host: 'https://api.bscscan.com'
    www: 'https://bscscan.com'

Node Rate Limit Guard

The Endpoints accept the rate limit configuration so that the clients' pool hander can handle better select and manage the Web3 Clients and Requests. For example: `100/1s` - means 100 requests per 1 second. You can also set multiple guards. Example:

web3:
  eth:
    endpoints:
      - url: 'https://myendpoint-url'
        rateLimit: 100/1s;5000/1m
      # - ... other urls

## AD

PreviousInstallation NextFolder structure

Last updated 1 year ago