Visitor guide
Frequently asked questions
A short answer page for teams deciding whether OPTN Labs is the right fit for their BCH product, wallet, or infrastructure work.
What is OPTN Labs?
OPTN Labs builds Bitcoin Cash wallets, developer tools, infrastructure, and programmable transaction systems. OPTN Wallet is the shipped user product, while the broader platform work focuses on tools and transaction controls for BCH applications and software-operated funds.
Is OPTN only a wallet?
No. OPTN Wallet is the shipped user product, but OPTN also builds developer tools, Bitcoin Cash infrastructure, CashToken integrations, and programmable transaction systems for product teams.
What is OPTN Wallet?
OPTN Wallet is our BCH wallet and reference implementation. It proves the wallet UX, token flows, app connections, add-ons, and advanced transaction behavior we want to make easier for other teams.
What does OPTN build?
OPTN builds wallet software, CashTokens support, token indexing, Bitcoin Cash infrastructure, covenant-aware transaction flows, and integration support.
What is TokenIndexer?
TokenIndexer is OPTN's token data layer for balances, holders, metadata, and app-facing APIs.
What Bitcoin Cash services are available?
The public service surface includes Electrum, Chaingraph, BCMR, IPFS, and token data access, with public status for what is currently exposed.
Can OPTN help with CashTokens?
Yes. CashTokens are a core part of the stack, from wallet support to metadata and token-aware app flows.
Can OPTN help with covenants?
Yes. We help with covenant patterns, transaction planning, and product flows that depend on constrained spend behavior.
Do I need to know CashScript?
No. If you already know CashScript, great. If not, OPTN can still help with the design and implementation path.
What does outcome control mean?
It means the app can shape what a valid transaction is allowed to do, not just who can authorize it.
What should I send when I reach out?
Send what you are building, the part of the stack you need help with, your timeline, and any repo or architecture notes that will help us understand the scope.
Still unsure?
Send a short note and we will point you to the right route or the right part of the stack.