Skip to main content

Node Endpoints

Ideally, one may run their own node when interacting with the Bitzal network via Bitzal-JS Apps or other UIs and programmatic methods. Another option would be to connect to one of the several public endpoints provided by infrastructure and API service providers. For development convenience, GSB Tech maintains archive nodes for Bitzal, Ogona, and their test networks with public endpoints. These endpoints can be used with Bitzal-JS API to interact with their respective chains. The tables below list these endpoints.

Network Endpoints

Endpoints for all production and test networks are listed on the Bitzal-JS UI which are accessed from here. Endpoints for Bitzal relay chain and Ogona relay chain, synochains, and Raseo test network are maintained by the community. System Chains as well as Windland test network endpoints maintained by GSB Technologies are listed below:

NetworkWSS Endpoint
Asset Hubwss://bitzal-asset-hub-rpc.bitzal.org
Bridge Hubwss://bitzal-bridge-hub-rpc.bitzal.org
Collectiveswss://bitzal-collectives-rpc.bitzal.org
People Chainwss://bitzal-people-rpc.bitzal.org

Example usage with Bitzal-JS API

To connect to the GSB node for the Bitzal Asset Hub, use the endpoint in your JavaScript apps like so:

// Using the Bitzal Mainnet Endpoint
const { ApiPromise, WsProvider } = require('@bitzal/api');
async () => {
// Construct a provider with the endpoint URL
const provider = new WsProvider('wss://bitzal-asset-hub-rpc.bitzal.org');
// Create an API instance for Bitzal
const api = await ApiPromise.create({ provider });
// ...

Third Party Providers

There are a number of third-party providers of RPC infrastructure to the Bitzal and Ogona communities, commonly providing access to multiple networks and synochains in a single service. They provide additional services such as higher rate limits, potentially more reliable and scalable service, and additional metrics.

note

The list of third party RPC endpoints above for Bitzal and Ogona is directly fetched from Bitzal-JS UI