Author

Topic: Bitcoin Node SPV Function / Android Bitcoin Wallet Issue (Read 108 times)

legendary
Activity: 2870
Merit: 7490
Crypto Swap Exchange
Unfortunately however it seems that finding a wallet that allows you to specify your own nodes is getting harder and harder as time goes on (which you would think would be the opposite).

That's true, but most developer not interested to add such feature when there's no demand or possible financial benefit to do it.

This leads me to believe that while although the app shows its connected to my app it is in fact connected to other nodes and not my own app. 

Rather than believe, you can verify it by yourself. There are software to monitor network activity of an application such as "Net Monitor" and "Net Guard".
HCP
legendary
Activity: 2086
Merit: 4361
I really don't know why the community at large hasn't been more vocal about these core principals being upheld in some of the largest wallet implementations.  This seems to me to a coordinated attack on the self sovereignty prospects for our peaceful revolution that is bitcoin.
For one... a vast portion of the "community at large" seem happy to use Exchange and web wallets etc due to either laziness and/or ignorance Roll Eyes They simply want to "cash in" on the huge gains they have seen over the last few years and want to participate using the "path of least resistence".

The tools (wallets and information) are freely available and there if people want to use them to maintain their "self sovereignty"... but as they saying goes... "you can lead a horse to water, but you can't make it drink". Undecided


And I'm not quite sure how you equate peoples laziness and/or ignorance as "a coordinated attack"??!? Huh
legendary
Activity: 1568
Merit: 6660
bitcoincleanup.com / bitmixlist.org
After further investigating the issue I'm experiencing with my node and the Android wallet app with SPV functionality may have something to do with my cell carrier seemingly only offering IPV6 addresses yet my router only allowing IPV4 through and the IP4 being mapped to an IP6 address.

Then your carrier must be routing your, and everyone else's, IPV6 address through NAT to represent a single IPV4 address for everybody, using different ports internally for each user, opened on the networking hardware.

Having only IPV6 supported makes it impossible to connect to IPV4 servers, and vice versa. It is different from running an IPV6 device behind IPV4 NAT because your pc/phone's network stack doesn't know about the IPV4 address.

Your node probably doesn't have an IPV6 address. That's why carriers should be offering both protocols, because mainstream is not ready to only use IPV6 yet.
member
Activity: 104
Merit: 120
After further investigating the issue I'm experiencing with my node and the Android wallet app with SPV functionality may have something to do with my cell carrier seemingly only offering IPV6 addresses yet my router only allowing IPV4 through and the IP4 being mapped to an IP6 address.  I was able to surmise this after putting up my IPV4 VPN on my cell phone and confirming it's VPN IP was showing up in the list of connected IP addresses and when off it showed up another IP V4 address that isn't found in my phone anywhere but I can only assume is some kind of IP6 carrier IP to IPV4 format conversion and that since I didn't see this converted IP 4 address in my cell phone anywhere I didn't realize it was what was used to connect to it.  There are a lot of assumptions here however as I am not an expert with IP6 and IP4 networking.  Thanks.
member
Activity: 104
Merit: 120
Hello fellow Bitcoiners,

As most of you may know, one of the main benefits with bitcoin is the self sovereignty that comes from HODLing your own keys and being able to independently audit and transact on the bitcoin network by running your own node.  That said I have been doing both for many years now and have always been able to use my own node on a Windows box that I purchased exclusively for that reason several years ago  and use the peerbloomfilters=1 option to enable SPV wallet transactions.  Anyway, that all said, I have previously used this option in combination with the bitcoin wallet app on the Google Play store for years without any issue.  Unfortunately however it seems that finding a wallet that allows you to specify your own nodes is getting harder and harder as time goes on (which you would think would be the opposite).

All that said, I have gone through and attempted to specify  my node IP address and it does show as connected in my android wallet app whether I'm on the local network or on the cell network.  When on the local WIFI network I'm using an IP V4 address and when I'm on the cell network I use an IP6 address.  Now here's the thing.  Historically I've noticed that when connecting to my own personal node that synchronization took quite a while as opposed to when connecting to all the other random nodes through the application by default.  I noticed that my synch times were much faster recently however I can see that while although my app shows that it is connected to my node in the android app interface, it does not show connected in my node' console window. This leads me to believe that while although the app shows its connected to my app it is in fact connected to other nodes and not my own app. 

While the original idea of this message was to inquire as to whether other folks are having problems using their own node as SPV clients in their own wallets, I think the bigger issue raised here is why exactly there aren't a set of basic standards for wallets in 2021 that uphold the self sovereignty aspects of what bitcoin was started for.   I mean is it not essential to the community at large to have the ability to send and receive their own transactions and sign and verify P2PKH messages ?  I really don't know why the community at large hasn't been more vocal about these core principals being upheld in some of the largest wallet implementations.  This seems to me to a coordinated attack on the self sovereignty prospects for our peaceful revolution that is bitcoin.
Jump to: