docs
Get startedTroubleshootingPaymentsWebhooksAgent paymentsSwop MCPOviIdentity (swop.id)SwivyRPC (preview)API reference

Status & roadmap

The November 1, 2026 testnet release, published SDKs, and remaining production gates.

Testnet preview — November 1, 2026

Swivy is a staging/testnet preview using software custody, not a production custody service. All six public SDK packages are available at 1.0.1. Use test assets only. Set up the preview or request project access.

Available now

  • Public documentation: developer reference, OpenAPI JSON, and the dashboard.
  • SDK 1.0.1: @swivy/core, @swivy/web, @swivy/react, @swivy/expo, @swivy/node and @swivy/viem are published. Version 1.0.1 is under next; latest remains 1.0.0. Pin 1.0.1 explicitly and follow the consumer setup.
  • Schema 21: API and worker are deployed with versioned database migrations, verified backup/restore, delegated execution gas limits, cumulative encoded EVM limits and queued-work policy checks.
  • Authentication: developers choose email, SMS and passkey login for their environment. Configure delivery for enabled methods; hosted login follows the app's settings. Console account security is a separate flow.
  • Server integrations: app-owned wallets, environment-scoped user management, session verification, webhook retries and delivery replay are part of the current API.
  • Wallets and signing: managed EVM and Solana wallets, signing and transaction intents, sponsorship modes, delegated grants and the viem adapter are available for preview integration. Capabilities remain subject to environment policy and enabled test networks.
  • MCP self-service: registered OAuth clients can list and create their user's wallets with explicit scopes. This does not grant signing, transfers, export or delegation. See MCP setup.

Production gates

The current deployment uses software custody. A managed_tee API value, a healthy signer, published SDKs or a successful database migration does not establish production enclave custody.

Independent owner authority, real enclave and transport acceptance, recovery escrow and full signer recovery remain production gates. An external security review and production acceptance are still required before general availability.

A Swivy release does not establish that an existing Swop application has migrated. Integrate and validate each application separately; existing users' wallets must not move without their authorization.

Longer term

Production rollout and application migration follow those gates. Native split-custody parity, device-held keys or threshold signing, multi-region operation and compliance certification are separate milestones, not claims of this preview.

On this page