Skip to main content

EVM Compatibility

Orbinum is fully EVM-compatible, enabling seamless deployment of Ethereum dApps, smart contracts, and tooling without modifications.


Overview

Orbinum provides complete compatibility with the Ethereum ecosystem:

  • 100% EVM bytecode compatibility - Deploy Solidity contracts as-is
  • Ethereum JSON-RPC - Use MetaMask, Hardhat, Foundry, Remix
  • EIP-1559 fee market - Dynamic base fee with priority tips
  • Standard precompiles - ecRecover, BN254 pairings, Blake2, and more
  • Ethereum tooling - All standard development tools work out of the box
Standard EVM Features

Orbinum implements the complete Ethereum Virtual Machine specification, including all standard opcodes, transaction types (Legacy, EIP-2930, EIP-1559), and precompiled contracts.


Network Parameters

Orbinum is registered on Chainlist under Chain ID 270 (Mainnet) and 2700 (Testnet).

Mainnet

FieldValue
Network NameOrbinum
Chain ID270
Native CurrencyORB (18 decimals)
RPC URLhttps://rpc.orbinum.io
Explorerhttps://explorer.orbinum.network
Info URLhttps://orbinum.network

Testnet

FieldValue
Network NameOrbinum Testnet
Chain ID2700
Native CurrencyORB (18 decimals)
RPC URLhttps://testnet-rpc.orbinum.io
Explorerhttps://testnet-explorer.orbinum.network
Info URLhttps://orbinum.network

Both networks are EIP-3091 compliant (transaction links from block explorers follow the standard format).

Local Development

When running a local --dev node with Frontier, the default development Chain ID is 1281. Use the testnet or mainnet parameters above only when connecting to the respective live networks.


Custom Precompiles

In addition to standard Ethereum precompiles, Orbinum will introduce custom precompiles for privacy-focused operations:

  • Poseidon Hash - ZK-friendly hash function
  • Shielded Pool Interface - Privacy operations
  • ZK Proof Verification - On-chain proof verification
Coming Soon

Custom precompile interfaces and documentation will be published during testnet phase (Q2 2026). Addresses and APIs are subject to change before mainnet launch.


Use Case Example: Autonomous AI Agents

Here's a quick example of deploying an ERC-8004 autonomous agent on Orbinum, demonstrating full EVM compatibility:

// SPDX-License-Identifier: MIT
pragma solidity ^0.8.20;

interface IZKVerifier {
function verifyProof(bytes calldata proof, bytes32[] calldata inputs)
external view returns (bool);
}

contract PrivateAIAgent {
IZKVerifier constant verifier = IZKVerifier(0x802);
address public owner;

constructor() {
owner = msg.sender;
}

// Autonomous action: execute strategy with ZK proof
function autonomousAction(
bytes calldata proof,
bytes32[] calldata inputs,
bytes calldata strategyData
) external {
require(verifier.verifyProof(proof, inputs), "Invalid proof");

// Execute private strategy
_executeStrategy(strategyData);
}

function _executeStrategy(bytes calldata data) internal {
// Private DeFi operations, oracle updates, etc.
}
}

This agent can:

  • Execute private DeFi strategies autonomously
  • Verify ZK proofs for confidential operations
  • Interact with other contracts while preserving privacy
  • Update its logic based on proven conditions
Why This Works

Standard Solidity contracts work unchanged on Orbinum. The only addition is access to privacy precompiles (like IZKVerifier) for enhanced functionality.


Learn More

For detailed technical specifications and integration guides, documentation will be expanded during the testnet phase (Q2 2026).