Skip to content

Getting started

EmpoorioChain is the shared blockchain behind the Empoorio ecosystem. Public testnet is in operational hardening — connection details are not published yet. Mainnet is planned, not active — there are no public mainnet endpoints today.

This guide uses only published packages from projects/EmpoorioChain; it deliberately does not publish a testnet RPC/WebSocket/explorer/faucet URL, chain name, or SS58 format as confirmed-safe, because testnet genesis has not been relaunched yet.

Testnet connection details — not published yet

We are holding back specific RPC, WebSocket, explorer, and faucet URLs until the testnet genesis has been relaunched and a single, stable, publicly-peered node is confirmed live. Several candidate URLs and chain-ID values have circulated across internal project docs at different times; none should be treated as authoritative without a fresh live check.

  • Native chain ID: candidate value 2026 — not yet independently confirmed for the currently-running network.
  • EVM chain ID (Frontier): candidate value 27777 in current runtime source — other project docs have cited different numbers for the same network at different times, so verify via a live eth_chainId RPC call before deploying.
  • RPC / WebSocket / explorer / faucet: no URL is published here yet.

What we do not publish here

Private validator IPs, internal bootnodes, keystore paths, or credentials — nor an unverified public RPC/explorer/faucet URL. Node operators should follow the operator documentation in the EmpoorioChain repository; builders should follow the EmpoorioChain repository's release notes for the official "testnet live" announcement rather than reusing an old or third-party endpoint.

Typical builder path

  1. Install Eoonia Wallet or use a development keypair locally.
  2. Watch the EmpoorioChain repository release notes for the public testnet launch announcement and its verified endpoints.
  3. Once published, request test DMS from the faucet.
  4. Use @empoorio/sdk, empoorio-sdk, or emp-cli to send a transaction.
  5. Confirm the result in the public explorer, once its URL is published.
  6. In the meantime, build and run a node locally (see below) to develop against the real runtime.

TypeScript SDK

Package name in the repository: @empoorio/sdk (projects/EmpoorioChain/sdk/ts).

bash
npm install @empoorio/sdk
javascript
import { EmpoorioChain } from '@empoorio/sdk';

const client = new EmpoorioChain({
  // Use the verified testnet endpoint from the release notes once published —
  // do not hard-code a candidate URL from old docs.
  endpoint: process.env.EMPOORIOCHAIN_WS_ENDPOINT,
});

await client.connect();
console.log('Connected to EmpoorioChain testnet');

TIP

The SDK connects via Polkadot.js-compatible APIs. Point it at a verified testnet endpoint (see release notes) — never at mainnet, which does not exist yet.

Rust SDK

Crate workspace path: projects/EmpoorioChain/sdk/rust/empoorio-sdk.

bash
cd projects/EmpoorioChain
cargo build -p empoorio-sdk

Example capabilities (see crate docs for the full API):

  • Connect via HTTP RPC and WebSocket
  • Read chain height and account balances
  • Submit native DMS transfers
  • Subscribe to new blocks

CLI (emp)

Binary package: emp-cli in projects/EmpoorioChain/sdk/rust/emp-cli.

bash
cd projects/EmpoorioChain
cargo build -p emp-cli --release
./target/release/emp --help

Top-level command groups (from the CLI source):

CommandPurpose
emp domainsRegister and resolve .emp domains
emp nftNFT flows (e.g. music NFT mint/stream)
emp fundTokenized fund create/invest
emp aiAI model register and inference
emp stakingNominate validators, withdraw unbonded
emp ouranoosStorage provider and renter operations
emp walletconnectWalletConnect v2 pairing (requires project config)

Full examples: CLI documentation.

Local development (your machine only)

For a node on your laptop — not public infrastructure:

ServiceDefault
RPChttp://localhost:9933
WebSocketws://localhost:9944
Explorer (local stack)http://localhost:3000

Build and start from the EmpoorioChain repo:

bash
cargo build --release -p empooriochain --features with-runtime,vm-evm,rocksdb,networking
# See scripts/deploy/ in the repo for local network scripts

Runtime scope (honest)

Per docs/PALLET_NAMES.md and the compiled runtime (construct_runtime!) in the EmpoorioChain repository:

  • 36 pallets are documented as targeted for the public testnet (spec 103, indexes 0–35) — testnet itself is not confirmed publicly live today, see the note above.
  • 134 pallets exist in the full compiled runtime source; additional indexes ship as spec upgrades land.

We do not quote TPS or mainnet performance here without published benchmark evidence.

Next steps

Identity (did:emp, verifiable credentials) is documented on KryptoOS — EmpoorioChain anchors identity state where the runtime supports it.