The Next Generation Network
A next-generation blockchain ecosystem designed for creating, exchanging and exploring digital assets.
Build. Launch. Exchange. Explore.
Every milestone is listed with its real status. The team updates statuses as work is completed, and no dates are committed.
An EVM-compatible network designed so existing Solidity contracts and standard wallets work without changes. The testnet is under development and no live endpoints are published yet.
Testnet data unavailable
Testnet data unavailable
Testnet data unavailable
Testnet data unavailable
Development target: Arbitrum Nitro / Arbitrum chain. EVM execution, Ethereum-compatible tooling, sequencer + validator infrastructure, canonical parent/child messaging and a future indexed explorer. Production deployment remains pending testnet validation and security review.
Solidity and Vyper contracts, standard JSON-RPC, and common EVM tooling are the compatibility target.
RPC, faucet, explorer API and SDKs are planned. See the Developers section.
Deploy a fixed-supply ERC-20 token through the EthernexLaunch factory on Ethereum Mainnet. This uses real ETH for gas and transactions are irreversible.
0xCd1FB9eFd8D1E27504b6185F2C9eACF790396451
Current factory: fixed supply, 0–18 decimals, full initial supply sent to the connected creator wallet. No minting, pausing, transfer tax, blacklist, liquidity lock or ownership controls are implemented by this factory. Contract has not been independently audited.
The swap interface is prepared for a reviewed Ethereum DEX router integration. Wallet and token balance reads are live; transaction execution remains gated until live route/quote validation and liquidity checks are connected.
This screen does not request token approvals or submit swap transactions. Quotes shown as unavailable are intentionally not fabricated.
Connect a wallet to read balances. Live swaps remain disabled while router integration is under development.
Ethereum Mainnet balance reads are live. The production integration target is a reviewed external DEX router; this build intentionally does not create approvals or swaps until live quote and liquidity validation are connected.
0x3c1c...f662Bridge preparation is now structured around Ethereum Mainnet and the future Ethernex Network. Transfers stay disabled until an independently reviewed bridge and live Ethernex network exist.
No token approval, deposit or cross-chain transaction can be submitted from this version. No bridge fee or arrival time is invented.
Ethernex Network is not live. This bridge cannot move assets yet.
The future Ethernex explorer is not live yet. This foundation can classify Ethereum addresses, transaction hashes and block numbers, then open verified Ethereum Mainnet data on Etherscan without fabricating Ethernex activity.
Reads use your connected EVM wallet provider.
Connect wallet to read.
No Ethernex RPC/indexer has been published.
Network metrics appear only after real infrastructure is connected.
ETHNX is the planned native asset of Ethernex Network. Potential functions include paying network gas fees and supporting utility across ecosystem products.
ETHNX is not offered for sale and nothing here promises value or returns. Testnet tokens have no monetary value.
One view of what is working now and what still requires infrastructure.
Ethereum Mainnet factory deployed.
Wallet/balance layer ready; execution gated behind live quote/liquidity validation.
Ethereum lookup tools ready; Ethernex indexer pending.
Transfer UI prepared; execution disabled.
Blockchain infrastructure
Token creation
Decentralized exchange
Blockchain explorer
Cross-chain connectivity
APIs, SDKs and documentation
Live Ethereum Mainnet balances from your connected wallet. Read-only.
Tokens launched from this browser are saved locally after confirmed factory transactions.
Confirmed Ethernex Launch transactions recorded by this browser.
No price, liquidity or route is fabricated. Execution unlocks only after a live quote source and pool/liquidity validation are connected.
The development architecture is now defined. Public RPC/chain parameters remain unpublished until the Ethernex testnet actually exists.
Install an EVM wallet and a toolchain such as Foundry or Hardhat. Network parameters will be published here when the testnet launches. Planned configuration:
networks: {
ethernex_testnet: {
url: "RPC_URL (published at testnet launch)",
chainId: "CHAIN_ID (to be announced)"
}
}Current engineering target: an Arbitrum Nitro-based EVM chain. Testnet comes first. The chain ID, RPC, explorer URL, sequencer endpoints and bridge addresses will only be published after deployment.
Standard EVM bytecode is the target, so Solidity contracts built with OpenZeppelin should deploy unchanged. Upgradeable contracts will be used only where necessary and documented with their admin and timelock.
Tokens created with Ethernex Launch are planned to follow ERC-20, with permissions such as minting and pausing shown clearly before creation.
Ethernex has not been audited. No audit is claimed until an independent audit is completed and published.
Planned before any mainnet launch.
Planned. Not yet active.
Planned for the public testnet.
Planned through the explorer.
Contact address to be published.
Each service is checked from your browser using the endpoints in the site configuration. Services without an endpoint show as not deployed.
What is deployed, who can change it, and what has been reviewed. Entries stay empty until they are real.
Planned policy: contracts are immutable by default. Any upgradeable contract will be listed here with its admin, timelock delay and the reason it needs upgrades.
To be published: multisig address, signers and approval threshold.
Contact address to be published.