[Tutorial] BlueWallet - Bitcoin Wallet Discussion

[Zaguru12]

Another thing I do not like about Bluewallet is that it will not show the last thing you have done in the wallet. Like if you send bitcoin, it will not show it until you close the app and open it again.

That’s synchronization issue, you don’t necessarily need to go out of the wallet to get this done. You just go to the top of the wallet and drag it down to allow it to reload, it will immediately update everything.

The third thing is that the fee is not accurate, it is 1 sat/vbytes lower than mempool estimation.

I have also experienced this but it is actually not a problem because they use different estimators just like others have said. On most occasions they usually set the high priority fee higher than that on the mempool. I had paid 15sats/vbyte for transaction that could be confirmed fast for 9sats/vbyte. So what I do is to check the estimators and then customize my fees to my preferred rate.


One thing I would like the app on IOS to address is whenever you exit the app it should request for a password to login again even though it is immediately you exit. Most at times if you exit immediately you can get back into the wallet freely without it requesting a password.

[_act_]

As an Android ^[v13] user who did some tests in the past, I never experienced it, so it might have something to do with your device or its operating system ^{[did it happen in iOS?]}.

I am using Bluewallet on two phones. The first phone is running Android 12 while the second phone is running Android 13. I have noticed this on Android 12 but recently I thought the error has been fixed until I used Bluewallet yesterday on Android 13 and I noticed the bug. I will make transaction on the Android 12 anytime I have coin on the wallet and see if it is not like that. If it is like that, I think the same bug should not affect the same phone which are not small phones.

That’s synchronization issue, you don’t necessarily need to go out of the wallet to get this done. You just go to the top of the wallet and drag it down to allow it to reload, it will immediately update everything.

You are using the iOS but I am using Android.

[aylabadia05]

The third thing is that the fee is not accurate, it is 1 sat/vbytes lower than mempool estimation.

Same as SFR10, tapping the green button or tapping the send button, the fee can change if you cancel sending, I mean when you repeat it again by pressing the send button the amount of the fee changes again or is no longer the same as the fee as on the first try you did.

It is a good wallet but it would be good if those things are corrected.

Apart from the technical answers that have been answered, I think the three weaknesses that you think developers need to improve can be tried to suggest to them via their github considering that bluewallet is an open source bitcoin wallet.

[_act_]

Same as SFR10, tapping the green button or tapping the send button, the fee can change if you cancel sending, I mean when you repeat it again by pressing the send button the amount of the fee changes again or is no longer the same as the fee as on the first try you did.

It is hosseinimr93 that gave me the perfect answer which is that wallets do not have good fee estimation. If I look at mempool.space, the fee is always 1 sat/vbye higher than the fee estimation on Bluewallet. There are times that this can cause you a problem. An example is when the fee is not going below 10 sat/vbyte recently during last weekend but Bluewallet is estimating 9 sat/vbyte. If you used 10 sat/vbyte, the transaction that would have gotten confirmed at 10 sat/vbyte will not get confirmed at 9 say/vbyte and you will noticed that the transaction do not get confirmed throughout that day. Go to last weekend on mempool to know what I am talking about. You can use https://jochen-hoenicke.de/queue/#BTC,1w,weight for it, I have set it to a week already. There was 10 sat/vbyte also on mempool.space, the day I am talking about but Bluewallet estimated 9 sat/vbyte. If you are using Bluewallet frequently, you will understand what I am talking about. There was a time it was 14 sat/vbyte but Bluewallet was estimating 13 sat/vbyte.

[aylabadia05]

UPDATE: Releases Blue Wallet Version 6.4.9
Blue Wallet official download link: App Store | Google Play

BlueWallet released a new version update.
I missed notifications regarding several of the latest releases after I last informed you about the release of version 6.4.6 here. There should be two releases that I need to inform you about, namely v6.4.7 and v.6.4.8.
Yesterday, BlueWallet released version 6.4.9 which was announced via github.com.
In this version, namely v.6.4.9, there are 11 points included in the update.

Here he is;

• ADD: airdrop ms cosigner (#5682)
• FIX: Only make call if watch is reachable
• FIX: better tx list update when transactions actually changed (rel #5615)
• FIX: pull-to-refresh while inside the wallet doesnt update the tx list (closes #5615)
• FIX: incorrect fees occasionally (for some electrum servers); better fee estimation
• FIX: unable to delete faulty wallet (rel #5661)
• FIX: Settings was not fully visible on newer iPhone models
• FIX: round circles on Multisig screen
• FIX: stateURL default value
• FIX: import single-sig wallet descriptor (closes #5637)
• REF: Camera Authorization Request

Edit to warn; Maintain and protect the seed phrase properly for asset safety.

Hope it's useful.

[EL MOHA]

Today I faced a challenge while trying to make a transaction out of my BlueWallet. With the mempool less congested and the estimated fee rate from mempool.space was 2sats/vbyte same was shown as the top priority on the BlueWallet with 1sat/vbyte been the minimum I decide not get greedy although I didn’t wasn’t in hurry for the transaction so I customized fee rate 1.5sats/vbyte, and I got an error so I opted for the high priority fee rate of 2 sats/vbyte but still the I got the error in the image below. I thought it was sync error and I logged out and log into the BlueWallet again and sync it but same thing occurred at that 2sats/vbyte fee rate, I was only able to get my transaction broadcasted with a 3 sats/vbyte.

Does this mean BlueWallet doesn’t allow a transaction to proceed with a fee of 300 sats less. If at all the mempool was congested and the purging fee rate was above my fee rate I would have thought other wise although it wouldn’t still be proper. But I wan snyc the mempool then and 2sats/vbyte was ok to get my transaction confirmed in the next block but BlueWallet didn’t allow me to proceed.

Has anyone else experienced similar problem before?

[SFR10]

Has anyone else experienced similar problem before?

IIRC, there was a user who mentioned the same thing in the past but I couldn't find his/her post. The good thing is that this issue isn't directly related or rather limited to BlueWallet only and to find the answers to your questions, you can refer to the following thread: Mempool min fee

[hosseinimr93]

Does this mean BlueWallet doesn’t allow a transaction to proceed with a fee of 300 sats less.

300 sats? Do you mean 3 sat/vbyte?
No, the minimum fee rate you have to use, so that your transaction can be broadcasted depends on the network state.

Since different nodes can have different setting and different purging fee rate, you could probably broadcast your transaction with connecting to a different server.

According to mempool.space, the purging fee rate for nodes that use default setting is now 1.76 sat/vbyte.

[aylabadia05]

UPDATE: Releases Blue Wallet Version 6.4.10
Blue Wallet official download link: App Store | Google Play

Yesterday, BlueWallet released version v6.4.10 a week after the release of v6.4.9.
I just got this information on the github.com BlueWallet account which was updated by the account marcosdz.

If in the v6.4.9 release there were 11 points included in the update, now in the v6.4.10 release there are 7 points included in the latest update including REF: Privacy screen.

• FIX: Check if theres a string before triggering the clipboard alert
• FIX: The scrolling behavior after deleting a wallet was not natural. Let the component figure it out
• FIX: iOS version is showing wallets' balance on Home Screen even when option is disabled #5500
• FIX: Bug: CNY price is wrong #5705
• FIX: View controller-based status bar appearance
• FIX: Notifications Permission issues on newer Android APIs
• REF: Privacy screen

Hopefully this notification is useful.
*Carefully guard and protect your seed phrase for asset safety.

[aylabadia05]

UPDATE: Releases Blue Wallet Version 6.4.12
Blue Wallet official download link: App Store | Google Play

Oct 25, releases version update v6.4.10 announced by marcosrdz via github account as I attached previously.

Yesterday, without any release of version v6.4.11, now there is a direct update to version v.6.4.12.
As of v.6.4.12, there are 13 points included. 3 of the points in v6.4.12, bluewallet added RON currency for widget, See currency when tap and hold on balance, and tool to generate last mnemonic word.

• ADD: RON currency for widget
• ADD: See currency when tap and hold on balance
• ADD: tool to generate last mnemonic word (#5722)
• FIX: better tracking opt out (related #5688)
• FIX: correct merge of params when navigating between screens
• FIX: Lightning wallet CSV export does not differentiate between paid and expired invoices #5835
• FIX: Sometimes would crash due to lack of initialParams
• FIX: Wrong Suite was being targeted
• FIX: Call dismiss on ActionSheet to avoid duplicate firing
• FIX: Re-enable groups on watch app
• FIX: Show alert with error message when a selected file isn't valid
• FIX: Apple Watch app not working #5470
• FIX: Wait for transitions to finish before showing sheet

Hopefully this notification is useful.
*Carefully guard and protect your seed phrase for asset safety.

[aylabadia05]

UPDATE: Releases Blue Wallet Version 6.4.14
Blue Wallet official download link: App Store | Google Play

Fixed two things in the v6.4.14 version update which was done about two days ago.
Fixed the exception trying broadcast after scanning PSBT from QR and correctly work with addresses funded by coinbase transactions.

• FIX: exception trying broadcast after scanning PSBT from QR
• FIX: correctly work with addresses funded by coinbase transactions

Before version v6.4.14 which only fixed two things, in version v6.4.12, the addition of tool to generate last mnemonic word, is very good for BlueWallet.

Hopefully this notification is useful.
*Carefully guard and protect your seed phrase for asset safety.

[aylabadia05]

UPDATE: Releases Blue Wallet Version 6.4.15
Blue Wallet official download link: App Store | Google Play

Around 12 items included in the Bluwallet update version v6.4.15.
For MacOS version of Bluewallet users, in this version of update there are additional Wallet item menus.
Since I am not a bluewallet user on MacOS, I don't know how to do this.

Three additions, one Wallet menu item on MacOS, two more additions related to Haptic Feedback on Android and the other allowed to import the QR code from other sources.
This is the source of Bluewallet update version v6.4.15.

ADD:

• macOS Add Wallet menu item
• Haptic feedback on Android
• Allow importing a QR Code image from other sources

FIX:

• Dismissing Scanner would result in undefined reject
• There is a bug when using the scanning function when creating a multi-signature signature#5869
• Transactions List component does not update on setParams #5844
• Clipboard toggle was not visible in Settings
• Wallet change macOS app UI fixes
• Startup crash on macOS app
• Sensitive onPress when using tooltip
• Rare crash on startup if not in offline mode (closes #5898) (#5964)

REF:

• Haptic feedback into a class with power state verification (#5954)

Hopefully this notification is useful.
*Carefully guard and protect your seed phrase for asset safety.

[satscraper]

UPDATE: Releases Blue Wallet Version 6.4.15

6.4.15 Blue Wallet release, having a bunch of noticeable fixes,  was not long for this world due to the flaw which prevented the selection of  "Settings" from "macOS or iPadOS UIMenu".

6.4.16 release, which appeared a few days after 6.4.15, has fixed this bug.

[aylabadia05]

6.4.15 Blue Wallet release, having a bunch of noticeable fixes,  was not long for this world due to the flaw which prevented the selection of  "Settings" from "macOS or iPadOS UIMenu".

6.4.16 release, which appeared a few days after 6.4.15, has fixed this bug.

Correct. A few days after updating version 6.4.15, BlueWallet updated version 6.4.16 with two fixes for macOS or iPadOS UIMenu and Android 13.
By the way, thank you for sharing the version 6.4.16 update here.
I'll report on this in another topic I created locally.

[aylabadia05]

UPDATE: Releases Blue Wallet Versi v6.5.0
BlueWallet official download link: App Store | Google Play

BlueWallet was available again with the v6.5.0 update. [two days ago]
The addition to version v6.5.0 lies in detecting damage to the watchOS application.

Apart from adding crash detection to the watchOS application, there are 7 fixes starting from floating button accessibility issues (scan, send, receive), regarding the RON currency not displaying the correct transaction value, regarding the create wallet screen to the SearchBar wasnt visible on Currency screen.

ADD:

• Crash detection on watchOS app (#6060)

FIX:

• Improve accessibility of floating buttons (scan, send, receive) #5389
• add BQI locale
• The create wallet screen is not working when I go back after create a wallet #6030
• Update Widget code for BNR
• Newly added Ron currency does not display correct value of transactions. #5940
• showUpdateStatusIndicator was not working well when no connection available
• SearchBar wasnt visible on Currency screen

REF:

• watchOS app code optimization
• Search moved to Reorder screen (#6037)

I have updated from the previous version to version v.6.5.0 because I did not use the automatic application update settings as shown in this screenshot;


Hopefully this notification is useful.
^*Carefully guard and protect your seed phrase for asset safety.

[bayu7adi]

On this page, each application should only display one icon. However, after updating to the latest version of the BlueWallet app through the Play Store, why do I have two BlueWallet icons? Honestly, I'm starting to worry if one of these apps is fake. It's a bit suspicious because other apps have never experienced this double icon issue.

I searched in Settings > App Management > and looked for BlueWallet in the search bar, but I only found one app under the name 'BlueWallet'.

Is this a bug from MIUI? Or is it a bug from BlueWallet? Has anyone else experienced what I'm experiencing? Honestly, I'm starting to see this as a threat because I'm sure no one wants their device to be infected with malware or viruses.

[AprilioMP]

On this page, each application should only display one icon. However, after updating to the latest version of the BlueWallet app through the Play Store, why do I have two BlueWallet icons? Honestly, I'm starting to worry if one of these apps is fake. It's a bit suspicious because other apps have never experienced this double icon issue.

Allow me to help answer because I have experienced the same thing where two bluewallet application icons appeared on an Android mobile device. After updating to the latest version, the double application icon disappeared.

I found a solution regarding the dual application problem on Android when visiting GiftHub Bluewallet. This problem is contained in the new version update.

Code:

Double Android app icon (#6082)

image:

[BVeyron]

 I like this wallet and use it on mobile phones.  It is especially convenient to present wallets in the form of multi-colored imitation plastic cards.  However, the other day I came across the fact that the wallet does not accept Taproot privatekey.  And accordingly, this functionality is missing.  Is there any information whether the Bluewallet devs are planning to finally add the full functionality of Taoroot, as is done in many other wallets.
 It’s probably time to prepare such a release and present it to users

[aylabadia05]

And accordingly, this functionality is missing.  Is there any information whether the Bluewallet devs are planning to finally add the full functionality of Taoroot, as is done in many other wallets.
 It’s probably time to prepare such a release and present it to users

There is no information regarding Bluewallet's plans to add the Taproot feature. It can be seen from issue on GitHub. On their github, there are already around 337 issues with 38 labels and no suggestions regarding Taproot.
You can try to suggest if it is possible for you to do it in the new issue section. Who knows, if you are willing to propose, Bluewallet could add the Taproot feature.

[Pmalek]

However, the other day I came across the fact that the wallet does not accept Taproot privatekey.  And accordingly, this functionality is missing.  Is there any information whether the Bluewallet devs are planning to finally add the full functionality of Taoroot, as is done in many other wallets.

A request to introduce support for Taproot was made as early as 2021, and it's still not there. I have personally never used it, and I am not sure what benefits it will give you if you are not going to use a multisig setup. I know that Muun wallet is one mobile wallet that supports Taproot. Check it out if you are interested. But take note that they do things a bit differently, and don't have the standard recovery phrases we are used to see in other bitcoin wallets.