Supported Chains

Supported Blockchains in Roru Labs

Roru Labs supports multiple blockchains through a unified adapter layer. This document lists all supported chains and their specific implementations.

Currently Supported Chains

Ethereum

Chain ID: 1 (Mainnet), 5 (Goerli), 11155111 (Sepolia)

Features:

  • Native ETH support

  • ERC-20 token support

  • Layer 2 support (Arbitrum, Optimism)

  • Gas optimization

  • EIP-1559 support

Adapter Implementation:

  • Ethereum JSON-RPC

  • Web3.js integration

  • Gas estimation

  • Transaction formatting

Settlement:

  • Standard Ethereum transactions

  • Gas fees in ETH

  • Confirmation time: ~15 seconds

  • Finality: 12+ blocks

Solana

Network: Mainnet, Devnet, Testnet

Features:

  • Native SOL support

  • SPL token support

  • Fast transactions

  • Low fees

  • Program integration

Adapter Implementation:

  • Solana Web3.js

  • RPC integration

  • Transaction building

  • Account management

Settlement:

  • Solana transactions

  • Fees in SOL

  • Confirmation time: ~400ms

  • Finality: 32 slots

Bitcoin

Network: Mainnet, Testnet, Signet

Features:

  • Native BTC support

  • SegWit addresses

  • Lower fees

  • Privacy maintained

Adapter Implementation:

  • Bitcoin Core RPC

  • Transaction building

  • UTXO management

  • Fee estimation

Settlement:

  • Bitcoin transactions

  • Fees in BTC

  • Confirmation time: ~10 minutes

  • Finality: 6+ blocks

Polygon

Chain ID: 137 (Mainnet), 80001 (Mumbai)

Features:

  • EVM compatible

  • Fast transactions

  • Low fees

  • ERC-20 tokens

Adapter Implementation:

  • Ethereum-compatible adapter

  • Polygon-specific optimizations

  • Gas price management

Settlement:

  • Polygon transactions

  • Fees in MATIC

  • Confirmation time: ~2 seconds

  • Finality: 12+ blocks

Avalanche

Chain ID: 43114 (C-Chain Mainnet)

Features:

  • EVM compatible

  • Fast finality

  • Low fees

  • Native AVAX

Adapter Implementation:

  • Avalanche Web3

  • C-Chain integration

  • Transaction building

Settlement:

  • Avalanche transactions

  • Fees in AVAX

  • Confirmation time: ~1 second

  • Finality: 1 block

BNB Chain

Chain ID: 56 (Mainnet), 97 (Testnet)

Features:

  • EVM compatible

  • BEP-20 tokens

  • Low fees

  • Fast transactions

Adapter Implementation:

  • BSC Web3 integration

  • BEP-20 support

  • Transaction formatting

Settlement:

  • BNB Chain transactions

  • Fees in BNB

  • Confirmation time: ~3 seconds

  • Finality: 15+ blocks

Arbitrum

Chain ID: 42161 (One), 421613 (Goerli)

Features:

  • Layer 2 Ethereum

  • Low fees

  • Fast transactions

  • EVM compatible

Adapter Implementation:

  • Arbitrum SDK

  • L2 transaction handling

  • Bridge integration

Settlement:

  • Arbitrum transactions

  • Fees in ETH

  • Confirmation time: ~1 second

  • Finality: 1 block

Optimism

Chain ID: 10 (Mainnet), 420 (Goerli)

Features:

  • Layer 2 Ethereum

  • Low fees

  • Fast transactions

  • EVM compatible

Adapter Implementation:

  • Optimism SDK

  • L2 optimizations

  • Transaction building

Settlement:

  • Optimism transactions

  • Fees in ETH

  • Confirmation time: ~2 seconds

  • Finality: 1 block

Chain Adapter Architecture

Adapter Interface

Common Interface:

pub trait ChainAdapter {
    async fn get_balance(&self, address: &str) -> Result<u64>;
    async fn send_transaction(&self, tx: Transaction) -> Result<TxHash>;
    async fn estimate_gas(&self, tx: &Transaction) -> Result<u64>;
    async fn get_confirmation(&self, hash: &TxHash) -> Result<Confirmation>;
}

Adapter Implementation

Ethereum Adapter:

  • Web3 provider integration

  • Gas estimation

  • Transaction signing

  • Event listening

Solana Adapter:

  • Solana Web3.js

  • Account management

  • Transaction building

  • Program interaction

Bitcoin Adapter:

  • Bitcoin Core RPC

  • UTXO management

  • Transaction building

  • Fee estimation

Cross-Chain Operations

Unified Interface

Multi-Chain Abstraction:

  • Single API for all chains

  • Automatic chain selection

  • Unified error handling

  • Consistent data formats

Cross-Chain Bridges

Bridge Implementation:

  • Lock on source chain

  • Proof generation

  • Mint on destination

  • Privacy maintained

Adding New Chains

Adapter Development

Steps:

  1. Implement ChainAdapter trait

  2. Add chain-specific logic

  3. Test with sandbox

  4. Deploy to network

  5. Update documentation

Requirements

Chain Requirements:

  • Smart contract support (for some features)

  • RPC endpoint

  • Transaction format

  • Fee structure

  • Confirmation mechanism

Chain-Specific Features

Ethereum Features

  • ERC-20 token support

  • Smart contract interaction

  • Layer 2 integration

  • Gas optimization

Solana Features

  • SPL token support

  • Program interaction

  • Fast settlement

  • Low fees

Bitcoin Features

  • UTXO model

  • SegWit support

  • Lower fees

  • Privacy features

Performance Characteristics

Transaction Speed

By Chain:

  • Solana: ~400ms

  • Arbitrum: ~1s

  • Optimism: ~2s

  • Polygon: ~2s

  • Avalanche: ~1s

  • Ethereum: ~15s

  • Bitcoin: ~10min

Fee Structure

By Chain:

  • Solana: Very low

  • Polygon: Very low

  • Arbitrum: Low

  • Optimism: Low

  • Avalanche: Low

  • Ethereum: Variable

  • Bitcoin: Variable

Conclusion

Supported chains provide:

  • Multi-Chain Support: Multiple blockchains

  • Unified Interface: Consistent API

  • Cross-Chain: Seamless operations

  • Extensibility: Easy to add chains

  • Performance: Optimized per chain

Roru abstracts chain differences while maintaining chain-specific optimizations.

PreviousSystem DiagramNextReference Implementations

Last updated