Fonta1n3 / FullyNoded

Self sovereign, secure, powerful, easy to use wallet that utilizes your own node as a backend. Powered by PSBT's and descriptors. Acts as an offline signer using your node as a watch-only wallet. C-Lightning compatible for instant, unfairly cheap payments.
https://fullynoded.app
Other
197 stars 37 forks source link

Incoming/outgoing transactions do not show up #174

Closed Lobbelt closed 2 years ago

Lobbelt commented 2 years ago

I created a Fully Noded wallet using the iOS Fully Noded app (iPhone 11 Pro). For context: my Fully Noded app is connected to a Raspiblitz full node.

I created an invoice using the app and sent some BTC to it. It does not show up in the wallet under transactions or unlocked UTXO's. Then I noticed under "advanced" that there are actually 2 different wallets: "wallet.dat" and the Fully Noded wallet.

When I activated "wallet.dat" instead of the Fully Noded wallet, the transaction still did not show up but the UTXO was available under the "utxo's" tab.

Not sure what I did wrong or how I can make sure ALL transactions are shown in my wallet, and not just in the UTXO list of only one specific (separate?) wallet (wallet.dat) that I did not create?

Fonta1n3 commented 2 years ago

Is your node fully synced? If it isn't then transactions and utxos will not show up.

The wallet.dat is the default wallet bitcoin core automatically creates for you, it is confusing and annoying but rather then hide it I prefer to allow users to access this wallet incase they need to.

By the sounds of it you did not have the FN wallet toggled on when you created the invoice which is why the utxo is showing up in your default wallet (as the invoice that was generated was clearly for the default wallet if the utxo is showing up there). You should just be able to tap refresh on the active wallet view and the balance and transaction ought to show up. Please do try again and let me know if the issue is resolved.

Fonta1n3 commented 2 years ago

closing as I do not think this is an actual bug. If you can reliably reproduce this issue please reopen and share a screen recording.