OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Wallets

Obandroid

OBAndroid is a self-custodial OmniBOLT wallet for Android that handles on-chain Bitcoin and Omni Layer assets and supports Lightning payments, invoices and channel management.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Obandroid — OpenViST project profile in Wallets.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Consider OBAndroid when an Android wallet needs both on-chain Bitcoin or Omni asset transfers and OmniBOLT Lightning workflows. Check the receiving-address and invoice-format requirements before making a payment.

Who it is for

  • Android users who want to hold and transfer Bitcoin and Omni Layer assets from a self-custodial wallet.
  • Users who need OmniBOLT Lightning invoices, asset payments or channel and liquidity controls.

Documented uses

  • Store, send, receive, back up and restore Bitcoin and Omni Layer assets.
  • Create, manage and pay OmniBOLT 7 invoices for Lightning transactions.
  • Manage local or remote nodes, fund channels with Omni Layer assets and manage liquidity.
  • Back up channels locally or through the cloud.
Before you choose

Requirements & limits

The README specifies Android 8 or later on 64-bit devices.

  • Omni asset on-chain transfers require P2PKH receiving addresses; Bech32 addresses are supported for Bitcoin transactions but not Omni asset transfers.
  • The supported Lightning invoice format is OmniBOLT 7; BOLT 11 is not supported.
  • Full functionality depends on the obd version. The README says the bundled version is matched, while remote-node connections require checking compatibility.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Check OBAndroid compatibility before using payments

Prepare to use OBAndroid by verifying Android requirements and checking supported address and invoice formats.

Before you start

  • Android 8 or later on a 64-bit device.

Steps

  1. Confirm the device runs Android 8 or later and is 64-bit.

  2. For on-chain Omni Layer asset receipts, use a P2PKH address: mainnet addresses start with 1; testnet and regtest addresses start with m or n.

  3. Use OmniBOLT 7 invoices; BOLT 11 invoices are not supported and payment to one will fail.

  4. Before connecting to a remote obd node, check its compatibility with the relevant OBAndroid release.

Expected outcome

The device and intended payment formats are checked against the compatibility requirements described for OBAndroid.

Guide limitations

  • Omni Layer assets cannot be sent on-chain to BECH32 addresses; doing so can cause permanent fund loss.
  • BOLT 11 invoices are unsupported.
  • The README's obd version table lists the v0.1-alpha dependency as “to be added,” so it does not specify a remote-node version.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
16 October 2026
Original website title
omnilaboratory/OBAndroid · Official homepage title · retained in its source language
How we review sourcesSuggest a correction