Did anyone loose the ability to talk to their own lightning node through TOR when you are on the same local network as the node itself?
If I am on 5G I can use TOR to get to it.
When I am on the same network as the machine running LND hub it will not connect using TOR but will using the local 192.168.x.x. IP
Don't know if it's bluewallet, TOR or something else.
The other side is I don't remember the last time I used BlueWallet local to the node I usually just use my laptop to connect to REL on the IP.
-Dave
Topic: [Tutorial] BlueWallet - Bitcoin Wallet Discussion (Read 2940 times)
The developer continues to try hard to create a more powerful bluewallet as a Bitcoin wallet.
And his efforts are focused on that creation at all times. A few days later new v6.6.1 has followed:
- ADD: Do not start analytics native code if disabled
- ADD: Allow user to cancel reminder in case they are not ready to decide
- ADD: SSL connection to Widget calls
Plus six fixes.
UPD. New v6.6.2 is available
- ADD: Slide up animation for FloatButton
- FIX: Multiple UI fixes for PSBT screen
- FIX: Some screens had Button styling was broken
"Blue is the color of trust, responsibility, and relaxation"
UPDATE: Releases Blue Wallet Versi v6.6.0
BlueWallet official download link: App Store | Google Play
Bluewallet was available version 6.6.0 which was updated 2 days ago. In version 6.6.0, there are 2 ADD and more FIX and only 3 REF.
The developer continues to try hard to create a more powerful bluewallet as a Bitcoin wallet. For me this is a very worthy wallet to be recommended.
Hopefully this notification is useful.
*Carefully guard and protect your seed phrase for asset safety.
BlueWallet official download link: App Store | Google Play
Bluewallet was available version 6.6.0 which was updated 2 days ago. In version 6.6.0, there are 2 ADD and more FIX and only 3 REF.
The developer continues to try hard to create a more powerful bluewallet as a Bitcoin wallet. For me this is a very worthy wallet to be recommended.
Quote from: github.com/BlueWallet
ADD: Save File Button
ADD: Allow amount and memo to have hold to copy
FIX: Unconfirmed txs would always show "a few seconds ago" on watchOS
FIX: ListItem UI would slightly jump when applying chekmark
FIX: on android doesn't highlight addresses that belong to user in tx details #6348
FIX: Buttons were blocked by keyboard in multisig edit
FIX: Dark mode vs Light mode display issues with memos. #6307
FIX: Notifications alert was not working on desktop
FIX: Receive periodic checker didnt clean up on dismiss
FIX: Dont show alert if user cancels willingly
FIX: Wallet export reminder was not visible on macOS
FIX: Unable to scroll wallets list
FIX: Custom fee alert was not visible on macOS
FIX: Select All was hijacked by Add Wallet
FIX: wrong import for isDesktop
FIX: Bio restore Text was cropped
FIX: Unlock button width
FIX: bugsnag connection at startup #5688
REF: Update balance view to new UX
REF: Change source API for some fiat
REF: Use Pressable instead of TouchableOpacity for Android The onPress was inconsistent if inside a child component on some android APIs
ADD: Allow amount and memo to have hold to copy
FIX: Unconfirmed txs would always show "a few seconds ago" on watchOS
FIX: ListItem UI would slightly jump when applying chekmark
FIX: on android doesn't highlight addresses that belong to user in tx details #6348
FIX: Buttons were blocked by keyboard in multisig edit
FIX: Dark mode vs Light mode display issues with memos. #6307
FIX: Notifications alert was not working on desktop
FIX: Receive periodic checker didnt clean up on dismiss
FIX: Dont show alert if user cancels willingly
FIX: Wallet export reminder was not visible on macOS
FIX: Unable to scroll wallets list
FIX: Custom fee alert was not visible on macOS
FIX: Select All was hijacked by Add Wallet
FIX: wrong import for isDesktop
FIX: Bio restore Text was cropped
FIX: Unlock button width
FIX: bugsnag connection at startup #5688
REF: Update balance view to new UX
REF: Change source API for some fiat
REF: Use Pressable instead of TouchableOpacity for Android The onPress was inconsistent if inside a child component on some android APIs
Hopefully this notification is useful.
*Carefully guard and protect your seed phrase for asset safety.
Developer is working so hard. v6.5.8 is available to download and improve BlueWallet.
Behind this update is a large work done. This is evidenced by comparing what has been changed in v6.5.8 relative to v6.5.7
UPD. New v6.5.9 release
- "ADD: Discard changes prompt in view/edit multisig keys"
- "ADD: Northern Lori language (#6223)"
- "FIX: Multisig Forget alerts where visible after closing modal (macOS)"
Behind this update is a large work done. This is evidenced by comparing what has been changed in v6.5.8 relative to v6.5.7
UPD. New v6.5.9 release
New v6.5.7 release for BlueWallet has fixed two bugs that irritated users of previous versions:
Previous one namely v6.5.6 has added explanations for AirDrop usage and iOS supports passcode.
Gradually moving ahead to the point of the perfect wallet
Maybe in the future there will be more updates to improve this wallet if there are issues that need improvement.- "Security screen froze on load"
- "could not scan cosigner when creating a multisig vault"
Previous one namely v6.5.6 has added explanations for AirDrop usage and iOS supports passcode.
Gradually moving ahead to the point of the perfect wallet
While using BlueWallet, the only oddity I experienced was a confusing double icon, although it didn't take long for attention to be fixed.
With every MacOS and iOS update, I don't pay much attention to it because I don't use these two devices.
Btw, thanks.
New v6.5.7 release for BlueWallet has fixed two bugs that irritated users of previous versions:
Previous one namely v6.5.6 has added explanations for AirDrop usage and iOS supports passcode.
Gradually moving ahead to the point of the perfect wallet
- "Security screen froze on load"
- "could not scan cosigner when creating a multisig vault"
Previous one namely v6.5.6 has added explanations for AirDrop usage and iOS supports passcode.
Gradually moving ahead to the point of the perfect wallet
BlueWallet was available again with the v6.5.0 update.
What a fast development!
Within several days we faced v6.5.1 and v6.5.2 updates which added "export individual private keys for addresses" (v6.5.1), "support more wallet export files from Coldcard" ( (v6.5.1) and " Trigger Haptic feedback on Copy Priv Key" (v6.5.2 ) not to mention epy whole host of important fixes like " crash when editing multisig cosigners" , "Biometrics unlock", etc..
Version [v6.5.3] FIX: Mac crash and FIX: Scan button on Broadcast tool.
In [v6.5.4] which was released a few hours ago it concerns ADD: Don't allow macOS app to run if OS is unsupported, FIX: plus/minus icon in quorum settings is reversed, and FIX: Pull to refresh.
Yeah I agree with you about the complexity, but I am curious why people do it.
I think some of them are just afraid (or lazy) to make transactions from the old wallet addresses to addresses on new wallet.
The others may have received BTC as a gift. Consider as a case the physical coins or pieces of paper accompanied by engraved/ etched or printed private keys on them.
I don't identify myself with those adherents who get used to doing the individual private keys export into wallets as, in my believe, this greatly complicates the process of wallets backup. However, I have met ( on various occasions) in my crypto-path people who do this at changing their wallets.
Yeah I agree with you about the complexity, but I am curious why people do it. Have they told you any info in regards with that? I mean, my question is genuine, I don't see a reason to do it, but it's a feature and of course it is not mandatory. Therefore, it's nice-to-have but I don't find it very useful. The other features are good! I like it. BlueWallet is a very good wallet in my opinion, so kudos to the devs.
What a fast development!
Within several days we faced v6.5.1 and v6.5.2 updates which added "export individual private keys for addresses" (v6.5.1), "support more wallet export files from Coldcard" ( (v6.5.1) and " Trigger Haptic feedback on Copy Priv Key" (v6.5.2 ) not to mention epy whole host of important fixes like " crash when editing multisig cosigners" , "Biometrics unlock", etc..
Within several days we faced v6.5.1 and v6.5.2 updates which added "export individual private keys for addresses" (v6.5.1), "support more wallet export files from Coldcard" ( (v6.5.1) and " Trigger Haptic feedback on Copy Priv Key" (v6.5.2 ) not to mention epy whole host of important fixes like " crash when editing multisig cosigners" , "Biometrics unlock", etc..
Yes it was fast indeed. Let me ask something though. What would be a good use case for this: "export individual private keys for addresses" ? With HD wallets, I would argue that individual private keys aren't very useful, are they? I mean one key for all addresses, isn't it better? Unless you want to use the individual key for security reasons, so as if someone gains access to (let's say) 3 of they keys, they don't gain access to your entire wallet.
I don't identify myself with those adherents who get used to doing the individual private keys export into wallets as, in my believe, this greatly complicates the process of wallets backup. However, I have met ( on various occasions) in my crypto-path people who do this at changing their wallets.
What a fast development!
Within several days we faced v6.5.1 and v6.5.2 updates which added "export individual private keys for addresses" (v6.5.1), "support more wallet export files from Coldcard" ( (v6.5.1) and " Trigger Haptic feedback on Copy Priv Key" (v6.5.2 ) not to mention epy whole host of important fixes like " crash when editing multisig cosigners" , "Biometrics unlock", etc..
Within several days we faced v6.5.1 and v6.5.2 updates which added "export individual private keys for addresses" (v6.5.1), "support more wallet export files from Coldcard" ( (v6.5.1) and " Trigger Haptic feedback on Copy Priv Key" (v6.5.2 ) not to mention epy whole host of important fixes like " crash when editing multisig cosigners" , "Biometrics unlock", etc..
Yes it was fast indeed. Let me ask something though. What would be a good use case for this: "export individual private keys for addresses" ? With HD wallets, I would argue that individual private keys aren't very useful, are they? I mean one key for all addresses, isn't it better? Unless you want to use the individual key for security reasons, so as if someone gains access to (let's say) 3 of they keys, they don't gain access to your entire wallet.
BlueWallet was available again with the v6.5.0 update.
What a fast development!
Within several days we faced v6.5.1 and v6.5.2 updates which added "export individual private keys for addresses" (v6.5.1), "support more wallet export files from Coldcard" ( (v6.5.1) and " Trigger Haptic feedback on Copy Priv Key" (v6.5.2 ) not to mention epy whole host of important fixes like " crash when editing multisig cosigners" , "Biometrics unlock", etc..
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. 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.It’s probably time to prepare such a release and present it to users
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.
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
It’s probably time to prepare such a release and present it to users
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:
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.
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.
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.
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.
Quote from: github.com/BlueWallet
ADD:
REF:
- Crash detection on watchOS app (#6060)
- 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.
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.6.4.16 release, which appeared a few days after 6.4.15, has fixed this bug.
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.
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.
Jump to: