Orderly Network API Authentication for Openclaw

A comprehensive technical guide for implementing Orderly Network's dual-layer authentication system, covering wallet-based account registration and Ed25519-signed API requests.

tarnadas
v1.0.0
Mar 7, 2026
0
774
0

Install & Download

1. ClawHub CLI

The fastest way to install a skill directly from the registry.

npx clawhub@latest install orderly-api-authentication

2. Manual Installation

Copy the skill folder to one of these locations

Global
~/.openclaw/skills/
Workspace
<project>/skills/

Priority: Workspace > Local > Bundled

3. Prompt Installation

Copy this prompt to OpenClaw to install it automatically.

Help me install orderly-api-authentication using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).

Prefer to download?

Get the raw skill files in a ZIP archive.

What is Orderly Network API Authentication?

Orderly Network utilizes a sophisticated two-layer authentication framework designed for high-performance decentralized trading. This skill from Openclaw Skills provides developers with the logic to handle Layer 1 Wallet Authentication—using EIP-712 for EVM or Ed25519 for Solana—and Layer 2 API Authentication using locally generated Ed25519 key pairs.

By separating account-level permissions from trading operations, Orderly ensures that sensitive wallet signatures are only required for account management and withdrawals, while high-frequency trading actions are authorized via fast, local Ed25519 signatures. This architecture is essential for building secure, low-latency trading bots and institutional-grade integrations.

Orderly Network API Authentication Use Cases

  • Programmatically registering new Orderly accounts using EVM or Solana wallets.
  • Generating and authorizing Ed25519 API keys with specific permissions like read, trading, or asset management.
  • Developing secure server-side trading bots that interact with Orderly's omnichain liquidity.
  • Implementing direct, authenticated WebSocket connections for real-time private account data.
  • Automating cross-chain asset management and settlement on the Orderly L2 ledger.

How Orderly Network API Authentication Works

  1. The user connects their wallet (EVM or Solana) to prove ownership of a blockchain address.
  2. The wallet signs a specific message (EIP-712 or Ed25519) to register an account with a Broker ID and retrieve a unique Orderly Account ID.
  3. A local Ed25519 key pair is generated on the client or server to act as the trading identity.
  4. The wallet signs a secondary message to authorize the Ed25519 public key, defining its scope and expiration.
  5. All subsequent API calls use the Ed25519 private key to sign a payload consisting of the timestamp, HTTP method, path, and body.
  6. The signature is encoded in base64url format and included in the HTTP headers for server-side verification.

Orderly Network API Authentication Setup

To begin using this Openclaw Skills resource, ensure you have Node.js 18+ and the necessary cryptographic libraries installed:

npm install @noble/ed25519 @orderly.network/default-solana-adapter @solana/web3.js

You will also need a valid Broker ID (e.g., woofi_dex) and access to either the Mainnet (https://api.orderly.org) or Testnet (https://testnet-api.orderly.org) environment.

Orderly Network API Authentication Data Schema & Taxonomy

Authenticated requests must include the following metadata in the header schema:

Header Requirement Description
orderly-timestamp Mandatory Current Unix timestamp in milliseconds.
orderly-account-id Mandatory The unique account ID generated during registration.
orderly-key Mandatory Public key prefixed with ed25519:.
orderly-signature Mandatory Base64url-encoded Ed25519 signature of the request payload.

All signatures follow the format: timestamp + method + path + body.

Orderly Network API Authentication Advanced Features

  • Support for both Off-chain (Account/API keys) and On-chain (Withdrawals/Settle PnL) EIP-712 domains.
  • Native Solana wallet integration using the Ed25519 message signing adapter for omnichain support.
  • Fine-grained API key scoping allowing restricted access to 'read', 'trading', or 'asset' permissions.
  • IP restriction capabilities for Ed25519 keys to provide an additional layer of server-side security.
  • Comprehensive error handling for signature mismatches (10016) and timestamp synchronization issues (10017).
  • Optimized WebSocket authentication flow within Openclaw Skills for low-latency private data streaming.

SKILL.md


Loading

Related Openclaw Skills

METADATA

Github Stars: 0
forks: 0

Featured*