Getting started

EmpoorioChain is the shared blockchain behind the Empoorio ecosystem. Public testnet is live. Mainnet is planned, not active — there are no public mainnet endpoints today.

This guide uses only published URLs and packages from projects/EmpoorioChain.

Public testnet endpoints

Service	URL
RPC (HTTPS)	https://testnet.empooriochain.org
WebSocket	wss://testnet.empooriochain.org
Explorer	https://testnet.explorer.empooriochain.org
Chain name	empoorio-testnet-1
SS58 format	2026
EVM chain ID (Frontier)	27777

What we do not publish here

Private validator IPs, internal bootnodes, keystore paths, or credentials. Node operators should follow the operator documentation in the EmpoorioChain repository — not copy unpublished infrastructure from third-party docs.

Typical builder path

1. Install Eoonia Wallet or use a development keypair locally.
2. Connect to testnet using the endpoints above.
3. Request test DMS from the faucet (when available on testnet — see release notes).
4. Use @empoorio/sdk, empoorio-sdk, or emp-cli to send a transaction.
5. Confirm the result in EmpooScan testnet explorer.

TypeScript SDK

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

npm install @empoorio/sdk

import { EmpoorioChain } from '@empoorio/sdk';

const client = new EmpoorioChain({
  endpoint: 'wss://testnet.empooriochain.org',
});

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

TIP

The SDK connects via Polkadot.js-compatible APIs. Use testnet endpoints until mainnet is announced with audited releases.

Rust SDK

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

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.

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

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

Command	Purpose
emp domains	Register and resolve .emp domains
emp nft	NFT flows (e.g. music NFT mint/stream)
emp fund	Tokenized fund create/invest
emp ai	AI model register and inference
emp staking	Nominate validators, withdraw unbonded
emp ouranoos	Storage provider and renter operations
emp walletconnect	WalletConnect v2 pairing (requires project config)

Full examples: CLI documentation.

Local development (your machine only)

For a node on your laptop — not public infrastructure:

Service	Default
RPC	http://localhost:9933
WebSocket	ws://localhost:9944
Explorer (local stack)	http://localhost:3000

Build and start from the EmpoorioChain repo:

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 in the EmpoorioChain repository:

• 36 pallets are active on the public testnet today (spec 103, indexes 0–35).
• 93 pallets exist in the full runtime source; additional indexes ship as spec upgrades land.

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

Next steps

• Architecture overview — how the chain fits together in plain language
• Public testnet notes — what is published vs operator-only
• API reference — JSON-RPC basics
• SDK registry — packages and endpoints in one place

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