Developer documentation

Build on Electroneum with Electroneum | Smart Chain Wallet.

A practical integration guide for connecting EVM wallets, reading Electroneum Smart Chain data and preparing transactions without handling user secrets.

Start building Browse documentation topics

Electroneum MainnetChain ID 52014

electroneum.config.tsTS

export const electroneum = {
  id: 52014,
  name: Electroneum Mainnet,
  nativeCurrency: { symbol: ETN },
  rpcUrls: {
    default: { http: [https://rpc.electroneum.com] }
  }
}

RPC configuration ready

Architecture overview

A familiar EVM stack, with user-controlled signing

Electroneum | Smart Chain Wallet is an interface layer. Public data comes from an Electroneum node, while approvals and signatures stay in the compatible external wallet selected by the user.

EVM compatible

Use established Ethereum tooling, 0x accounts and familiar smart-contract patterns.

JSON-RPC data

Read balances, blocks, gas estimates and transaction receipts through an Electroneum node.

Non-custodial

Request signatures from the external wallet. Never collect a recovery phrase or private key.

Quick start

From project to first network read

Configure

Add Electroneum Mainnet to your EVM client using the verified network values below.

Connect

Request the public account address through the user’s compatible wallet provider.

Read

Use a public client for balances, block numbers, contract calls and fee estimates.

Sign

Send the prepared transaction to the wallet and let the user review and approve it there.

Network configuration

Verified connection details

Treat network configuration as deploy-time data and verify it against the official documentation before production releases.

Mainnet

Production

Network: Electroneum Mainnet
RPC URL: https://rpc.electroneum.com
Chain ID: 52014
Currency: ETN
Explorer: blockexplorer.electroneum.com

Testnet

Development

Network: Electroneum Testnet
RPC URL: rpc.ankr.com/electroneum_testnet
Chain ID: 5201420
Currency: ETN
Explorer: testnet-blockexplorer.electroneum.com

Confirm the connected chainJSON-RPC

curl https://rpc.electroneum.com \
  -H "Content-Type: application/json" \
  --data '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

Wallet integration

Prepare in the app. Approve in the wallet.

Keep read-only network access separate from account authorization and transaction signing.

Connect account

Request only the public 0x address and current chain.

Prepare request

Validate recipient, amount, calldata, chain and estimated gas in the interface.

User approval

The external wallet displays the final payload and produces the signature after approval.

Secret-free integration boundary

Electroneum | Smart Chain Wallet screens, support forms and developer integrations must never request a recovery phrase, private key, wallet password or remote device access.

Core JSON-RPC

Methods used by wallet interfaces

These standard EVM methods cover the common read and transaction lifecycle. Use a maintained client library where appropriate.

Method	Purpose	Access
`eth_chainId`	Confirm the active network before every state-changing request.	Read
`eth_getBalance`	Read an account’s native ETN balance at a selected block.	Read
`eth_estimateGas`	Estimate the gas required by a prepared transaction.	Read
`eth_sendTransaction`	Ask the connected wallet to review, sign and submit a transaction.	Wallet
`eth_getTransactionReceipt`	Track inclusion and execution status after submission.	Read

Knowledge base

Electroneum concepts, available here

The essential foundational and development information is summarized below so you can continue learning without leaving Electroneum | Smart Chain Wallet.

Accounts and keys

An account is identified by a public 0x address and can hold ETN or interact with contracts.

The public address can be shared safely
The private key authorizes spending
A recovery phrase can restore all derived accounts
Secrets must remain inside the user’s wallet

Transactions and gas

A transaction changes network state by transferring ETN or calling a smart contract.

Every transaction includes a sender, destination and value or calldata
Gas measures the computation required
Fees are paid in native ETN
The sender signs before the transaction is broadcast

Blocks and confirmation

Validators group valid transactions into blocks and maintain a shared network state.

A transaction hash identifies the submitted request
A receipt records status and gas used
Block inclusion provides confirmation
Applications should handle pending and failed states

EVM and smart contracts

Electroneum Smart Chain executes EVM bytecode and supports established Ethereum development patterns.

Contracts are programs stored at network addresses
Calls can read state without creating a transaction
Writes require gas and user authorization
Production contracts should be tested and audited

Client APIs

Applications connect to an Electroneum node through stateless JSON-RPC requests.

Quantities use compact 0x-prefixed hexadecimal
Addresses and hashes use fixed-size hex data
Read methods query state or history
Submission methods broadcast signed transaction data

Development workflow

Build and verify the integration in stages before enabling production transactions.

Start with Testnet and read-only requests
Check chain ID before signing
Estimate gas and display the complete payload
Track the receipt and show the final status

Opening Electroneum | Smart Chain Wallet

Electroneum | Smart Chain Wallet could not be opened