OPTN

Products and infrastructure for Bitcoin Cash

Wallet software, token data, and hosted services for Bitcoin Cash

OPTN Labs builds products and infrastructure for the BCH ecosystem, from end-user wallet software to developer tooling and hosted backend services.

Wallet
A BCH wallet with token creation, app connections, and an add-on marketplace.
Token data
TokenIndex for address portfolios, holder data, and token metadata.
Hosted access
Electrum, Chaingraph, BCMR, IPFS, and related BCH backend services.

We also help teams build wallet products, token systems, contracts, and backend services on BCH.

What we do

We build for the BCH ecosystem from three angles: end-user products, developer tooling, and company infrastructure.

Products
OPTN Wallet, TokenIndex, and a hosted BCH stack built around the same ecosystem.
Focus
Wallet UX for users, developer surfaces inside the wallet, and backend services for BCH apps.
Support
Direct engineering help for wallets, token systems, contract flows, and backend integrations.

Live services

A few services we run today. Status appears when the service exposes a usable health check.

Products

The main things we offer today.

OPTN Wallet

OPTN Wallet

A BCH wallet for end users and a reference app for developers.

  • Create and manage CashTokens
  • Connect to web apps through WalletConnect
  • Add-on marketplace inside the wallet
TokenIndex

TokenIndex

A token data service that ties CashTokens to addresses and portfolios.

  • Address-based token portfolios
  • Holder and balance data
  • Open source and self-hostable
Hosted BCH Services

Hosted BCH Services

Hosted BCH infrastructure for teams that need backend access without running the full stack.

  • Electrum, Chaingraph, BCMR, and IPFS
  • Public endpoints and request-based access
  • Built to support wallet and app teams
Engineering Support

Engineering Support

Direct engineering help for teams building products on BCH.

  • Wallet and token integration work
  • Contract and transaction flow design
  • Backend architecture and launch support

Use cases

The kinds of products we most often support.

Payments & App Backends

Payments & App Backends

Wallets, payment products, and app backends that need BCH monitoring, metadata, and history.

  • Index and query on-chain activity
  • Serve token metadata and media
  • Monitor payments and confirmations
Covenant-Powered Workflows

Covenant-Powered Workflows

Escrow, staged spends, restricted transfers, and other custom transaction flows.

  • Escrow and conditional releases
  • Restricted spends and recipient controls
  • Multi-party or staged transactions
Token Launch & Control

Token Launch & Control

CashTokens projects that need metadata, issuance controls, and lifecycle visibility.

  • BCMR + metadata distribution
  • Media hosting via IPFS gateway patterns
  • Issuance and lifecycle monitoring

Product proof from OPTN Wallet

The wallet is not separate from the Labs story. It is where advanced BCH transaction flows, token UX, and covenant-oriented patterns get tested before they become guidance, product decisions, or reusable implementation patterns for teams.

Writing & code

Recent writing, source code, and a few references tied to our work.

CashTokens Kickoff: Tokens & Covenants on Bitcoin Cash – A Practical Alternative for Web3 Builders

2026-01-26 • Introduction to CashTokens and covenants on BCH. Explore the UTXO token model and transaction constraints as an option beyond EVM gas costs, state management issues, and Solana reliability concerns. With ongoing upgrades and growing community momentum, BCH is positioning itself as an emerging contender with significant upside.

Contact

If you are building on Bitcoin Cash, send a short note about the product and what you need.

Send a note

This opens a pre-filled email to `info@optnlabs.com`.

Good fit

  • BCH products with a defined launch or delivery timeline
  • Wallet, CashTokens, or covenant-related product work
  • Projects that need hosted BCH infrastructure

When you write

  • What you are building and whether it targets mainnet or chipnet
  • Expected usage, launch timing, and key blockers
  • Repo links or architecture notes if you have them