Prerequisites
This document contains the requirements and instructions to run a W3bstream node.
Currently, W3bstream supports IoTeX, Ethereum, and any EVM-compatible blockchain.
Currently, there are no token balance or staking requirements to run a W3bstream node.
Because your W3bstream node will act as a network endpoint for devices to send their data, you should run it on a server that has a fixed IP address, publicly accessible from the Internet.
The minimum hardware requirements to run a W3bstream node are:
- 2 Cores, 2 GB RAM, 10 GB storage, 100 Mbps network
Recommended requirements to get started running a W3bstream node are:
- 4 Cores, 4 GB RAM, 100 GB storage, 100 Mbps network
Notice
The performances and storage requirements of your node are closely related to the number of client devices, the volumes of IoT data, the data retention policy, and the complexity of the application logic. It's recommended to accurately evaluate the hardware configuration based on the application-specific requirements.
The W3bstream runtime supports Linux, MacOS systems and Windows (WSL).
For your W3bstream node to be able to interact with a blockchain application (e.g., react to smart contract events, send proofs of real-world events to smart contracts), you will also need access to a blockchain gateway.
You can use official gateways or third-party's gateways to access the blockchain of your choice:
RPC Endpoints
IoTeX Developer Documentation
List of IoTeX's RPC endpoints
Ethereum Nodes
List of Ethereum's RPC endpoints
If you decide to run your own gateway, it's highly recommended that you run it on a separate server, to avoid affecting W3bstream's performance. Below, you can find links to the instructions on how to run your blockchain gateway for IoTeX and Ethereum:
Node Configuration
IoTeX Delegate Documentation
Run an IoTeX gateway node
Run a node | ethereum.org
ethereum.org
Run an Ethereum gateway node
Last modified 4mo ago