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
  1. Orbs VM

Step by Step Overview

PreviousExample Use CasesNextDevelopment Requirements

Last updated 2 years ago

The development process of a new Orbs VM service includes the following steps:

  1. Select a unique ID for your service (alpha-numeric characters and dashes).

  2. Create a local git repository conforming to the appropriate project structure.

  3. Implement the logic of your service in any language and wrap it as a single docker image.

  4. Write a simple test suite to verify your service logic locally.

  5. Push your docker image to a public docker registry such as .

  6. Deploy your service by creating a PR (git pull request) to the official Orbs repo on GitHub.

  7. Wait until service is deployed by the system, errors and feedback will appear on the PR.

  8. Analyze execution of your service in production by examining the network .

DockerHub
status page