Orbit is the marketplace surface for the OpenClaw plugin economy on 0G Galileo testnet.
Orbit monetizes OpenClaw plugins on 0G: scaffold with orbit-init, publish to ClawHub + on-chain registry, charge per tool via registerOrbitUserBilling. Creators earn; users pay transparently on Galileo testnet
OpenClaw has a growing plugin ecosystem, but creators have no standard way to monetize extensions. There is no built-in flow to set install/usage pricing, charge users when a tool runs, or withdraw earnings on-chain. Every plugin team would need custom payment logic, wallet handling, and registry plumbing.
Orbit is a monetization layer for OpenClaw on 0G Galileo testnet, delivered as smart contracts plus @orbit-0g/sdk (TypeScript SDK + CLI).
Step | What happens |
|---|---|
Scaffold |
|
Publish |
|
Monetize |
|
Withdraw | Creators withdraw earnings from the billing contract |
One line in a plugin enables billing for all tools:
registerOrbitUserBilling(api);Stakeholder | Benefit |
|---|---|
Plugin creators | Set prices once, publish once, earn on real usage — no custom billing backend |
Users | One wallet |
Ecosystem | Sustainable plugins → more quality agent tools on OpenClaw + 0G |
Orbit turns OpenClaw from “free plugins only” into an open marketplace for agent tools — trustless pricing on 0G and a developer experience as simple as npm run orbit:publish.
Phase 1 — Smart contracts on 0G
- Deployed OrbitRegistry and OrbitBilling on 0G Galileo testnet (chain ID 16602)
- Integrated both contracts into the TypeScript SDK (viem)
Phase 2 — Core SDK
- Built @orbit-0g/sdk with registry, billing, publisher, and storage clients
- Hardcoded RPC, chain ID, and contract addresses in the SDK
Phase 3 — Creator CLIs
- orbit-init — scaffold OpenClaw plugin, ETH pricing, merge into existing projects
- orbit-publish — build, publish to ClawHub, register/update on OrbitRegistry, write orbit.pluginId to manifest
Phase 4 — User CLI
- orbit-install / openclaw orbit wallet setup — user private key in ~/.orbit/.env
Phase 5 — OpenClaw billing
- registerOrbitUserBilling(api) — install charge + before_tool_call → recordUsage
- Resolve orbit.pluginId from openclaw.plugin.json via api.rootDir
- Multi-plugin: wallet only in ~/.orbit/.env, plugin ID per manifest
Phase 6 — 0G Storage integration
- sdk.storage.upload() / sdk.storage.download(hash) in createOrbitSdk()
- HTTP client via ORBIT_STORAGE_URL /put, /get/{hash})
- Optional — billing/publish work without storage configured
Phase 7 — Publish pipeline fixes
- Switched to clawhub package publish with explicit --workdir
- Git metadata for ClawHub publish
Phase 8 — Demo & release
- echo-plugin end-to-end demo
- Published @orbit-0g/sdk to npm (v0.1.25)
- Unit tests for billing, publisher, user config, plugin ID
Current stage: Pre-seed / bootstrapped. No institutional funding or venture round closed to date.
Funding to date: Self-funded during the hackathon (development time, testnet gas, npm publishing). No paid customers or revenue yet — Orbit is on 0G Galileo testnet with a working SDK and demo plugin.
In progress: Actively engaging the OpenClaw and 0G communities for early support — feedback from plugin authors, gateway operators, and ecosystem programs (grants, hackathon prizes, builder funds). Conversations are ongoing; nothing finalized.
Use of funds (if raised): Mainnet contract audit, continued SDK and ClawHub integration, reference plugins, and developer docs/adoption in both ecosystems.
Ask: Community alignment and ecosystem grants rather than a traditional VC round at this stage. Open to partnerships with OpenClaw and 0G builder programs as we move from testnet demo to broader plugin adoption.