Orbs Network
  • Overview
    • What is Orbs?
    • Layer 3 Protocol
    • Running on EVM and TON
    • Enhanced Execution
    • L3 for Advanced Trading
    • Network Diagram
    • White Papers and Spec
  • Orbs Lambda
    • What is Orbs Lambda?
    • Network Diagram
    • Example Use Cases
    • Step by Step Overview
      • Development Requirements
      • Select Unique ID
      • Project Template
      • index.js Implementation
        • Execution Environment
        • Allowed Packages
        • Supported Networks
        • Execution Triggers
        • Sending Transactions
      • Testing Locally
      • Deploying to Production
      • Analyzing Execution
  • Orbs VM
    • What is Orbs VM?
    • Network Diagram
    • Example Use Cases
    • Step by Step Overview
      • Development Requirements
      • Select Unique ID
      • Docker Image Implementation
        • Execution Environment
        • Working Directory
        • Entry Point
        • Health Check
        • status.json
      • Testing Locally
      • Deploying to Production
      • Analyzing Execution
  • Powered by Orbs
    • Liquidity Hub
      • Integration Spec
    • Perpetual Hub
    • dTWAP Protocol
      • Integration Spec
      • Network Diagram
      • dTWAP Tutorial
      • FAQ
    • dLIMIT Protocol
      • Integration Spec
      • dLIMIT Tutorial
      • FAQ
  • Community Projects
    • Notification Protocol
      • Integrate a New Project
      • Network Diagram
    • TON Access
      • Network Diagram
    • TON Vote
Powered by GitBook
On this page
  • EVM
  • Ethereum mainnet
  • Polygon mainnet
  • BNB Chain mainnet (previously Binance Smart Chain)
  • Avalanche mainnet
  • Fantom mainnet
  1. Orbs Lambda
  2. Step by Step Overview
  3. index.js Implementation

Supported Networks

PreviousAllowed PackagesNextExecution Triggers

Last updated 4 months ago

EVM

When defining triggers for lambda execution, you must define which blockchain network the lambda executes on. To execute the lambda over multiple networks side by side, define multiple triggers side by side. Upon execution, the trigger event handler will receive an initialized web3 object that allows to make queries and send transactions on this network.

The following EVM networks are supported:

Ethereum mainnet

Network ID: ethereum Explorer:

Polygon mainnet

Network ID: polygon Explorer:

BNB Chain mainnet (previously Binance Smart Chain)

Network ID: bsc Explorer:

Avalanche mainnet

Network ID: avalanche Explorer:

Fantom mainnet

Network ID: fantom Explorer:

https://etherscan.io
https://polygonscan.com
https://bscscan.com
https://snowtrace.io
https://ftmscan.com