7EAV7 DEVELOPERS

Build on EAV7.

A Rust L1 with BFT finality, hybrid post-quantum signatures and an EAVM surface for EVM wallets. Read the chain with a curl; sign your first transaction with the SDK.

Start now API reference

Chain ID 72020REST :6070EAVM :707058 tx types

Where to start

Three ways into the network

Each solves a different problem. You are not picking forever — the node and the SDK talk to the same API you can already call today.

01Read the chain nowNothing to install. The public API answers JSON on every read endpoint: state, blocks, accounts, tokens, validators.Quickstart 02Sign transactionsThe Rust SDK builds the canonical envelope, signs locally with secp256k1 + ML-DSA-44 and submits it. No consensus rule reimplemented.Rust SDK 03Follow a recipeStep-by-step guides for the tasks that actually come up: sign and broadcast, transfer, issue a token, prove a balance.Guides 04Understand the modelAddress, hybrid key, nonce, energy, finality. Four concept pages that head off most integration mistakes.Concepts 05Run a nodeeav7-core syncs, validates and — with enough stake — produces blocks. Listener at home, validator on a VPS.Core

First call

Sixty seconds to your first JSON

Every read is plain HTTP, no key and no special header. /status returns the current height, the finalized height, the chain head and the active validator set.

Monetary values come back as integer strings in e7 — the smallest unit of the coin. Reading a balance is reading an integer; formatting is your presentation layer's problem.

Follow the quickstart

curl -s https://eavscan.com/status \
  -H 'Accept: application/json'

{
  "chain": "EAV7",
  "height": 1284391,
  "finalizedHeight": 1284389,
  "headHash": "9f2c4a…",
  "supply": "72000000000000",
  "validators": 27,
  "blockReward": "16000000"
}

Surfaces

One node, three ports

The same chain serves three audiences: HTTP integrators, EVM wallets and consensus participants.

:6070HTTP APINative-scheme reads and writes, in JSON. The surface the explorer and the SDK use.:7070EAVM JSON-RPCCompatible with MetaMask, Trust Wallet and EVM tooling. Chain ID 72020.P2PP2PBlock and transaction gossip between nodes. How the Core syncs.

Units

1 EAV7 = 1,000,000 e7 on the HTTP API (CHAIN.UNIT). On the EAVM surface wallets assume 18 decimals, so each e7 is 10¹² wei (CHAIN.EAVM_WEI_PER_E7). Mixing the two scales is the most expensive integration mistake.

Index

The whole portal

Twenty-three pages, one subject each.

Start

QuickstartFrom your first read to your first signed transaction.NetworksMainnet and local endpoints, ports, chain id and the protocol parameters.

Concepts

Accounts and keysThe E7 address, the hybrid key pair, the nonce and the mapping to the 0x world.Resources and feesEnergy, bandwidth, what actually gets burned and how stake buys exemption.Transaction lifecycleFrom build and sign to confirmed and final — and what each stage guarantees.FinalityfinalizedHeight, the BFT rule behind it and when a credit can be released.

Guides

GuidesStep-by-step recipes, each with prerequisites and code that runs.Sign and broadcastThe canonical payload, the hybrid signature, offline signing and nonce reservation.Send a transferThe shortest path from a wallet file to a confirmed TRANSFER.Stake and voteLock weight, elect validators, claim rewards and exit through unbonding.Issue an EAV20 tokenTOKEN_CREATE parameters, token transfers and the admin transaction types.Light clientTrusted root from a verified header and a balance proved by Merkle path.Connect MetaMaskEAVM network parameters, address mapping and the decimals trap.Run a nodeBuild eav7-core, sync as a listener and stand for election.

Reference

HTTP APIRead and write endpoints, units, pagination and admin access.EAVM JSON-RPCImplemented methods with params and returns, batching, gas and error codes.TransactionsThe signed envelope and all 58 protocol types, each with its fee limit.EAVMEVM-wallet compatible surface: params, JSON-RPC methods and what is still missing.Errors and limitsHTTP codes, rejection reasons, SDK error variants and the request limit.Rust SDKEav7Client: reads, Merkle proofs, signed writes and batched sending.CoreRun a node, stand for election and keep the service alive.

Operate

IntegrationsWallet, exchange, indexer, oracle — what each role needs to call.TroubleshootingSymptom, cause and fix, plus four commands that close in on it.

The network is up. Your code is the missing part.

Start with a read, finish with a transaction confirmed in a block.

Open the quickstart See the API