omnilaboratory / obandroid

OBAndroid is a self-custodial OmniBOLT Lightning wallet for android devices. It provides a platform for simple, instantaneous Bitcoin/Omnilayer asset payments

OBAndroid

OBAndroid is a self-custodial OmniBOLT Lightning wallet for android devices. It provides a platform for simple, instantaneous Bitcoin/Omnilayer asset payments. OBAndroid is now in developer beta, and will be in public beta in Nov/Dec 2022, available on Android only.

Features

• Self-custodial

• obd-lnd on Android

• Mainnet, testnet, regtest

• Bitcoin/Omnilayer wallet(layer 1): store, pay, receive, backup, restore

• Bitcoin lightning payment(layer 2)

• Omnilayer assets lightning payment(layer 2), e.g. OMNI, USDT, etc

• Manage local and remote nodes

• Create and fund channels by any Omnilayer assets

• Management liquidity

• Create, manage invoices( OmniBOLT 7)

• Pay invoices ( OmniBOLT 7)

• Cloud and local backup for channels

• DEX in wallet

• Marketplace

• Trading histroy

System Requirements

• Android 8+ 64bits

Compatibility

Bitcoin and Omnilayer addresses

For onchain transactions, the receiving address of omni assets must be p2pkh, that is:

1. Mainnet: address starting with 1
2. Testnet: address starting with 'm' or 'n'
3. Regtest: address starting with 'm' or 'n'

BECH32 addresses(pubkey hash or script hash starting with bc1 on mainnet, tb1 on testnet) are not supported(OmniBOLT 2), and sending omni assets to BECH32 addresses will result in permanent fund loss. OBAndroid protects users from such dangerous operations.

Bitcoin transactions support all legal BTC receiving addresses, including bech32 (starting with bc) addresses.

Invoice format

The currently supported invoice format is OmniBOLT 7.

BOLT 11 lacks asset awareness and is not supported by OBAndroid at this stage, paying BTC/satoshi to a BOLT 11 invoice will cause the payment to fail.

obd and lnd versions

Full OBAndroid functionality depends on running a certain version of obd on mobile devices. View the table below to ensure that you run the correct version of obd with the relevant OBAndroid release. The bundled version will always come with the correct, compatible versioning. To connect to remote obd nodes, you should check the compatibility dependency below.

OBWallet	obd
v0.1-alpha	to be added

Token/Bitcoin Testnet Faucets

token faucet: http://43.138.107.248:9090/swaggerTool/?surl=http://192.144.199.67:8090/openapiv2/foo.swagger.json#/tools/tools_SendCoin
token-property id: 2147485160  

btc-testnet faucet: https://testnet-faucet.com/btc-testnet/ 

Get Help

If you encounter any issues please report the issue in this repo or on discord with screenshots and how to reproduce the bug/error.

License

This project is open source under the MIT license, which means you have full access to the source code and can modify it to fit your own needs. See LICENSE for more information.

obandroid's Issues

Press on input box, but the keyboard did not popup

The "BTC" area covers the input area, so the keyboard cannot pop up

Number does not match progress bar when syncing on-chain data

the installation progress bar flickers and the download cannot continue

If the network is interrupted during the download process, after the network is restored, the installation progress bar flickers and the download cannot continue

Long press the QR image to allow the user to save the image.

Long press the QR image (of invoice, lucky packet) to allow the user to save the image.

Prevent payment of invoice created by lnd

When paying invoice, need to use prefix filtering to ensure that only obd invoice can be paid, so as to prevent users from using OBWallet to pay lnd invoice. See specification:

https://github.com/omnilaboratory/OmniBOLT-spec/blob/master/OmniBOLT-07-Hierarchical-Deterministic-(HD)-wallet.md#human-readable-part

fail to send usd token

Change some text at the page that leads user to create a channel

Change to:

"You have not created a channel for this asset, please create at least one channel with enough funds, and then continue to proceed (pay, create an invoice, collect a gift, etc)."

In the “create invoice” page, click “max”, the calculated result is the capacity of the channel, not “Can Receive”.

In the “create invoice” page, click “max”, the calculated result is the capacity of the channel, not “Can Receive”. It has to be the value of "Can Receive".

Error found when sending BTC

1. An error will be reported if the input is greater than 8 digits after the decimal point, but the error message is not clear. Appropriate prompt information needs to be added here, and local verification is required before calling the interface.

2. When entering address nickname after transfer, input space fails

Scan to pay token onchain, showed "success", but nothing sent out.

Please use OBWallet to scan to pay this QR code. Status is pending for hours.

My bitcoin is 0.0002. Is it insufficient?

MUST lock the wallet if there is no activities for like 5 minuts.

It won't lock even if I don't use it for a few days.

Need to confirm before delete a record on the "to be paid" list

The keyboard blocks the text box, making it impossible to click the text box on the next line to enter

Change "BACK" to "SAVE"

an invoice can be paid twice

Steps to reproduce:

Me: create an invoice, and close wallet(keep offline).

Payer 1: scan to pay the invoice, succeed. And I received the payment.

Two hours later:

Payer 2 scan to pay the same invoice, succeed. And i did not receive the second payment(which is correct at the payee side). The money is collected by the liquidity node. This is wrong. This payment MUST not be successful. Payer 2 MUST get information that the invoice can not be paid twice.

Fail to create tls.cert and tls.key on Android 13

Fail to create tls.cert and tls.key on Android 13 so that the app can not enter "create wallet" after syncing all chain data

When trying to pay 3 times without success, the mark should be changed to a failed symbol

The confirmation buttom is missed when closing a channel

The user must confirm "YES" or "NO" to prevent the user from touching the button by mistake.

User needs to be prompted to create a channel

When the wallet pays (or creates an invoice), if the user has not created an asset channel, the user needs to be prompted to create a channel. Because people don't know the principle of Lightning Network, just want to use a convenient wallet. So this is from a user perspective.

When restore password using mnemonic words, presss on "PASTE", the app crashes.

When restore password using mnemonic words, presss on "PASTE", the app crashes.

Change "NEXT" to "CONFIRM"

The testnet wallet displays a wrong "mainnet"

After sending USD token, the "Account Activities" page is empty.

After sending USD token, the "Account Activities" page is empty. It should display the transactions i made.

"Reserved wallet balance invalidated" when creating a channel

code = Unknown desc =  reserved wallet balance invalidated: transaction would leave insufficient funds for free bumping anchor channel closings(see debug log for details)

Liduidity nodes list should not be hard coded.

The list, which shows on the "create channel" page, where user will select one to build channels, should be dynamicly updated from git repo.

Textbox is hard to edit text

Exception after saving an empty name as a contact.

Save an address to contact list with an empty name. Then when i enter wallet again and press "send" (or scan a qr code to make onchain payment), the wallet crashes.

Invoice QR code is too dense and too small

Error found when creating Dollar channel

1. The text is too long causing the text to overlap
2. The content entered by memo is not judged before calling the interface, and there is no input limit
3. Is it because the estimated value of the channel creation fee is too large, and the channel cannot be created when the balance is still 0.0003

There is no "StarBucks"

If the address/node_id has an alias/name, use the alias/name.

When showing value in dollar, 2 decimal is enough.

When showing value in dollar, 2 decimal is enough. There is no need to show a value in 8 decimal.

But the amount should be 8 decimal.

For example: the bitcoin amount is 0.01023376, the value to display in dollar is 242.95 ( 242.9494624 ).

gRPC proxy unable to listen on 127.0.0.1:8080 on some adroid 13 phones.

log reports:

LTND: gRPC proxy unable to listen on 127.0.0.1:8080 2023-02-04 16:15:44.819 [ERR]
LTND: Shutting down because error in main method: error starting REST proxy: listen tcp4 127.0.0.1:8080: bind: address already in use

On the main page, if the dollar balance is 0, the corresponding dollar channel will not be displayed. However, the dollar channel has a balance.

On the main page, if the dollar balance is 0, the corresponding dollar channel will not be displayed. However, the dollar channel has a balance.

The two networks MUST be the same

The closing channel transaction blocks the whole application.

In the transaction history, "Yesterday" needs to be displayed in full,

When the value is down, the arrow should be pointing down and the color should be red

Channel is closed, but the tokens are missing

In issue 37, i killed the app, and opened again, the channel is closed. But the balance is incorrect: the tokens in the channel are not returned back to my account(wallet address).

The sentence on the "forget password" screen has to be changed to

The sentence on the "forget password" screen has to be changed to: "Please enter the seed (24 words) to restore your wallet"

The font is too large, which makes users uncomfortable

When swipe up and down on the screen, need to refresh the balance of your account

Update the Invoice detail page when check a history invoice.

The URL in token info is not "baidu"

The URL info should read from the token issuance address. If there is no URL, then leave it blank.

The text format is messed up

The transaction to close the channel has been started for an hour, but it has not been successful, and the application has been stuck here.

Screenshot is in issue 36

Error found when sending Dollar

1. Entering 20 digits after the decimal point will not report an error. Appropriate prompt information needs to be added here, and local verification is required before calling the interface.
2. The pop-up window opened by dollar, the token of the default transaction is not dollar.
3. Close the confirmation window after clicking send, the amount may be changed to the BTC amount, and the balance is incorrect.

block_head, manifest, meutrino.db are at wrong folder

When i run on Testnet, i found that the block_head, manifest, neutrino.db are downloaded to the Regtest folder of my phone:

Txs in Channel actitivies MUST be ordered by date.

Today's txs must be on the top.

When sending a lucky packet, allow the sender to edit a short message to those who collect the packet.

When sending a lucky packet, allow the sender to edit a short message to those who collect the packet. The default message is "Wish you good health". The number limit of the words is 24.

"New version found" page

Users need to be notified that a new version has been found.