Web3 & blockchain orchestration

Une seule API pour tous les chaînes.

Web3 backend in the same uniform Osage Cloud surface.

What we ship

Multi-chain web3 orchestration as a first-class capability domain in Osage Cloud. Same SDK, same auth (Osage IAM at osage.id), same KMS, same observability stack as the rest of the platform. Embedded directly in the Osage Cloud Go binary — no separate web3 service to run.

Core APIs

• Multi-chain JSON-RPC proxy — POST /v1/rpc/{chain} · one endpoint, every chain we support.
• Real-time subscriptions — WS /v1/ws/{chain} · pending tx, blocks, logs, head, with backpressure.
• Token balances & metadata — GET /v1/tokens/{chain}/balances/{address}
• NFT ownership & metadata — GET /v1/nfts/{chain}/owned/{address}
• Event-driven webhooks — POST /v1/webhooks · signed deliveries with retry and replay.
• ERC-4337 smart wallets — POST /v1/wallets/create · account abstraction across every supported EVM chain.
• UserOp bundling — POST /v1/bundler/{chain} · gas-optimised bundlers per chain.
• Gas sponsorship — POST /v1/gas/sponsor · paymaster policies, allowance enforcement.

Supported chains

L1: Ethereum, BNB Chain, Avalanche, Solana, Bitcoin, Osage Network.
L2: Arbitrum, Optimism, Base, Polygon, zkSync, Scroll, Linea, Blast.
Additional chains added on standing customer request.

Cryptographic posture

All signing keys are custodied in Osage KMS(HSM-backed, FIPS 140-3 boundary). For high-value or institutional workloads, signing routes through Osage Pulsar(threshold lattice signing) rather than single-key custody. Smart wallets are MPC-capable for shared custody scenarios. See /crypto for the post-quantum stack underneath.

Settlement anchor

Every operation that requires audit anchoring writes a content-addressed hash to Osage Network via the SettlementRegistry contract. This gives an immutable, post-quantum-secure record across every chain operation.

Tenancy and operations

• One sign-in at osage.id; orgs and projects are Supabase-style isolations.
• Rate limits, allowances, and quota per project; standing-pricing for committed workloads.
• OpenAPI spec + SDK in TypeScript, Python, Go, Rust. CLI: osage web3 …
• Self-hostable in air-gapped deploys; the web3 capability is part of the single Osage Cloud Go binary.

Web3 desk: [email protected].