Topic: [Tutorial] BlueWallet - Bitcoin Wallet Discussion - page 3. (Read 3576 times)

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.

---

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

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.

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

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?

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;

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

Hope it's useful.

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.

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.

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.

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.

You are using the iOS but I am using Android.

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.


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.

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?]}.

In addition to hosseinimr93's comment, if you tap the green 1 sat/vByte button you'll get a different set of fees that are closer to what's listed on the mempool.space.

To avoid such mistakes, disable "Read Clipboard". To do so, tap on the 3 dots button at top right corner of the screen and after that go to "General settings" and then "Privacy".

Different wallets and tools use different methods for fee estimation and take note that none of them are accurate.

What I will like Bluewallet developers to improve:

If you copy an address of a receiver, as you open Bluewallet, the wallet will ask you if you want to paste the address so that it can be used for sending bitcoin. Let us say you have more than one wallet on the wallet app and you last opened the second wallet. After you close the wallet, it can be in your mind that you last open the second wallet and if you want to use it to send bitcoin, you will think that you can just copy and paste from clipboard as Bluewallet ask you, if you paste, it will paste the address on the first wallet sending space. I almost wanted to make a mistake with it but my first wallet was not funded, I would have made the mistake by sending from the first wallet instead of the second.

The second thing is that paste what is on clipboard that it is asking by Bluewallet is annoying. You may copy the address for other thing but it will ask you about it. If I want to use Blue wallet to verify a message and I copy the address that I want to verify its message, it will not asked that than to paste the address on the sending space.

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.

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

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

It seems so. But simple switching on and back off the offline mode didn’t change anything.
Thank you, it has helped. I’ve chosen the server from your screenshot (coinucopia), and now BlueWallet can find all my transactions, so the current balance is also calculated correctly.

By default, BlueWallet chooses the server automatically. Try manually filling in the Electrum server in BlueWallet's Network settings (you can see the server list in the Electrum Wallet in the Tools-Network-Overview menu), then restart BlueWallet.

In the following example, I manually selected a server in BlueWallet and activated the Use SSL option:



You can see the history of the servers you have selected manually in Server History.

The problem is probably from the server you have connected to.

Tap on the three dot button at top right corner of the window. Go to "Network" and then "Electrum Server". Enable "offline Mode" and then disable it.
With enabling and disabling "Offline mode", you will connect to a different electrum server and you will probably see your transactions and your correct balance.

The address is the same. I see all the transactions of this address on mempool.space, but not in the BlueWallet.No, I don’t have a full Bitcoin node. I check my transactions via a public blockchain explorer. Now I also can check and find all of them via Electrum wallet. It’s weird because both wallets (BlueWallet and Electrum) seem to use the same Electrum server as a source of information about transactions.

Is the Bitcoin address used for transactions in other software the same as that in BlueWallet?

I assume that the other wallet is a Hierarchical Deterministic wallet so that during transactions, it can use a different address to process the return of unused funds, and it is not connected to the BlueWallet when you import it using the private key instead of using the seed phrase.

Hi. Are you using your own node? Or someone else's?

My BlueWallet fails to synchronise with the network. It shows me that the Electrum server is connected, but the last transaction it can find was 16 days ago. After that day I had four transactions with the address linked to Bluewallet. I made those transactions via another software. And Bluewallet doesn’t know anything about them. It still consider my TX-output from Aug-27 as unspent. Of course, when I try to spend it from Bluewallet, it says that the coin cannot be used, but it does not renew the balance and the transactions list even after such transaction attempt.

I’ve imported the private key to the Electrum wallet on the same device, and it shows correct amount.

Does anyone have the same issue with BlueWallet?

You can't.
If you set it up with a hardware wallet you need to sign it with that.
If you set it up as a multisig there is no standard for signing with multisig as far as I know. Could have changed but last I looked it was not there.

And it's also a security thing. If you have a 2 of 3 multisig any 2 people can sign but you would never know which 2. Since they can spend the BTC it does not matter from that view but you would never be able to prove more then that.

-Dave