Search content
Sort by

Showing 14 of 14 results by Mobber
Post
Topic
Board Bitcoin Technical Support
Re: To coinjoin or not?
by
Mobber
on 17/11/2022, 00:55:47 UTC
I'm trying to decide whether I should coinjoin my coins or not. All coins are from kyc exchange and have been in cold storage a while. I've heard arguments for coinjoining and also why not to. I plan on just holding them for a while. Opinions? Maybe I should just focus on accumulating non kyc coins?
You can do several things to remove connection of your identity from coins you own, and coinjoin is just one of them, but you could also consider JoinMarket, and remember to improve your address management.
Coinjoin will split your coins in smaller denominations so be ready for that, and some centralized services could refuse to accept your if they suspect you are trying to hide something.
I would also consider using alternative options like Lightning Network if you run your own node, ChipMixer is great way to mix your coins, and there is privacy oriented wallet Mercury that is using Layer 2 solution.


Is chipmixer on LN? What process would you recommend to gain privacy using LN?
Post
Topic
Board Bitcoin Technical Support
Re: To coinjoin or not?
by
Mobber
on 17/11/2022, 00:22:39 UTC
All coins are from kyc exchange and have been in cold storage a while.
So, given that your coins were bought via a KYCed account on a centralized exchange, then it is safe to assume the exchange knows exactly how many coins you own, in which addresses you are storing them, and has linked all that information to your real name, address, and other personal information. By extension, all of this will have been shared with various blockchain analysis companies, most likely some branch of your government, and potentially a variety of third party data brokers or other interested parties who buy data from blockchain analysis companies.

So now you have to ask yourself how happy you are with all of this. Do you not care that all these entities know exactly how much bitcoin you own, exactly which addresses belong to you, will be able to track exactly any future movements, transactions, purchases, trades, etc., that you make, and potentially use this information against you in some way? If you don't care, then do nothing. If you do care, then continue reading.

Next ask yourself what coinjoining will achieve in this case. Let's say you split all your coins between multiple coinjoins, coinjoin everything thoroughly, and move all your coins back to a brand new wallet with no links to your previous addresses. This will prevent the entities above from knowing which addresses you are storing your coins on and from being able to track all your future transactions. They will still know that you own some bitcoin, but will also lose the ability to know exactly how much. Their estimates of how much you own will become less accurate as time goes on, as they won't know if you are spending or selling some of your stack.

If you continue to buy bitcoin via this KYCed account and then coinjoining it, then again they will not know where your coins are or what you do with them, but will still have the data on how much bitcoin you bought over time. If you instead choose to buy non-KYCed coins via a DEX, then they will not have this data, provided you are meticulous in keeping any non-coinjoined coins separate from your newly bought non-KYCed coins.

And of course, make sure you don't use Wasabi to do any of this, since they work hand in hand with blockchain analysis companies.

Just curious where the "wasabi is working with chain analysis" is coming from? I've heard other people say whirlpool shares all your wallet info with there server even if you run through your own node? Which coinjoin would you recommend or would you recommend something else?
Post
Topic
Board Bitcoin Technical Support
Topic OP
To coinjoin or not?
by
Mobber
on 15/11/2022, 00:48:37 UTC
I'm trying to decide whether I should coinjoin my coins or not. All coins are from kyc exchange and have been in cold storage a while. I've heard arguments for coinjoining and also why not to. I plan on just holding them for a while. Opinions? Maybe I should just focus on accumulating non kyc coins?
Post
Topic
Board Bitcoin Technical Support
Merits 1 from 1 user
Re: Sparrow wallet suddenly not connecting to node
by
Mobber
on 31/10/2022, 07:00:23 UTC
⭐ Merited by nc50lc (1)
So I had a very brief power outage today and now sparrow won't connect to the node again. So strange. My only guess is that because bitcoin core didn't shutdown properly it's causing some issue. Am I just going to have to reinstall bitcoin core everytime my pc shuts down abruptly?
If the issue only a corrupted file brought by the abrupt shutdown and only in Bitcoin Core, then --reindex might solve the issue.
It's a command-line option and not a command so; to use it, Bitcoin Core should be started with that parameter (instructions).

Ran the reindex but sparrow still wouldn't connect. Also tried rescan also with no luck. I was able to get sparrow to connect again by deleting the sparrow wallet folder in Bitcoin core.

C:\Users\username\AppData\Roaming\Bitcoin/wallet/sparrow

After deleting that and restarting Bitcoin core sparrow is connected again. I've also ordered an ups battery backup to run the node and router/modem off of so hopefully this problem is resolved now.
Post
Topic
Board Bitcoin Technical Support
Re: Sparrow wallet suddenly not connecting to node
by
Mobber
on 30/10/2022, 06:29:39 UTC
An update:

I uninstalled sparrow and Bitcoin core and deleted all associated files. I then reinstalled them and sparrow is now connecting to the node perfectly. I guess we'll see if this issue comes up again in a few weeks. Maybe something got corrupted in Bitcoin core? Idk but thank you everyone for the suggestions!

So I had a very brief power outage today and now sparrow won't connect to the node again. So strange. My only guess is that because bitcoin core didn't shutdown properly it's causing some issue. Am I just going to have to reinstall bitcoin core everytime my pc shuts down abruptly?
Post
Topic
Board Bitcoin Technical Support
Re: Sparrow wallet suddenly not connecting to node
by
Mobber
on 28/10/2022, 20:24:45 UTC
I setup a full node a few weeks ago and successfully connected sparrow wallet from a different PC but on same network. It connected fine until yesterday and now sparrow won't connect. When I setup the node I followed the tutorial on bitcoin.org and did the port forwarding. The node I still receiving incoming connections fine. I followed the sparrow tutorial and all info is still correct.

The node is running on a PC with windows 10 and sparrow is on a pc with windows 11. I haven't changed anything but sparrow just won't connect now. Any suggestions?
Since you mention port forwarding, I assume you set up your node in a home network behind NAT. Such networks sometimes get their IP address reassigned by the ISP.
Can you check whether your external IP address has changed?

Otherwise, I generally recommend against port forwarding and for Tor tunneling instead. Sparrow has built-in Tor support, so you just need to install tor on the node machine and tunnel the Bitcoin port through it.

Something like this (change port number and hidden service name):
[5] Log back out into your sudo account, and open the Tor config file.
Code:
exit
sudo nano /etc/tor/torrc

[6] Add the following contents, preferably in the right section (somewhere where there's HiddenServiceDir stuff commented out).
Code:
HiddenServiceDir /var/lib/tor/electrs_hidden_service/
HiddenServiceVersion 3
HiddenServicePort 50001 127.0.0.1:50001

ExitPolicy reject *:* # no exits allowed

[7] Start up Tor and fetch your electrs Tor hostname. The hostname can then be entered in wallets like Wasabi and BlueWallet settings.
Code:
sudo systemctl enable tor.service
sudo service tor restart
sudo cat /var/lib/tor/electrs_hidden_service/hostname

If you followed this guide, you just port forwarded port 8333 though, which shouldn't give you remote access from Sparrow. That should require access to the 8332 RPC port, which you should never port forward to the internet. That's why I'm wondering that your setup ever worked in the first place.

I'd recommend to install electrs and tunnel it through Tor as described above, for better security.

Eventually I'd like to setup a private electrum server. Is that viable to run on a windows PC? And do you have any recommended guides to setup an electrum server? I also have no experience with tor so any recommendations for that? I'm assuming that's a straight forward verify and install?
Post
Topic
Board Bitcoin Technical Support
Merits 1 from 1 user
Re: Sparrow wallet suddenly not connecting to node
by
Mobber
on 28/10/2022, 07:36:08 UTC
⭐ Merited by dkbit98 (1)
An update:

I uninstalled sparrow and Bitcoin core and deleted all associated files. I then reinstalled them and sparrow is now connecting to the node perfectly. I guess we'll see if this issue comes up again in a few weeks. Maybe something got corrupted in Bitcoin core? Idk but thank you everyone for the suggestions!
Post
Topic
Board Bitcoin Technical Support
Re: Sparrow wallet suddenly not connecting to node
by
Mobber
on 27/10/2022, 19:57:58 UTC
OP you can try updating Sparrow wallet that just released new version 1.7.0 few hours ago, with lot of bug fixes and new features.
I am not sure if this will fix all your issues, but you could also contact developers or write your issue on their github page.
This is a cool wallet and best alternative for Electrum I found so far:
https://github.com/sparrowwallet/sparrow/releases


I just updated sparrow and still won't connect. I think I'm going to try completely uninstalling Bitcoin core and sparrow and then reinstalling them and see if that works.
Post
Topic
Board Bitcoin Technical Support
Re: Sparrow wallet suddenly not connecting to node
by
Mobber
on 27/10/2022, 06:35:45 UTC
When I setup the node I followed the tutorial on bitcoin.org and did the port forwarding. The node I still receiving incoming connections fine. I followed the sparrow tutorial and all info is still correct.

The node is running on a PC with windows 10 and sparrow is on a pc with windows 11. I haven't changed anything but sparrow just won't connect now. Any suggestions?
How about the guide above it about setting a static IP: bitcoin.org/en/full-node#configuring-dhcp?

By saying "still receiving incoming connections", do you mean you're still getting "Inbound" Peers or not?
Because if not, my best guess is your set 'rpcbind' IP address didn't match after getting a new IP address.

The node is definitely receiving incoming connections. It has 21 inbound right now and bitnodes shows it as accepting incoming. The WAN ip is automatic and has changed since I setup the node. But it looks like the internal ip's for the two PC's are static. Should I change that WAN ip to static?
Which IP do you use to connect Sparrow to Bitcoin Core? Your external / WAN IP or your local IP (192.xx... or similar)?
Again; opening ports in your router improves your node, since it can now accept incoming connections - by other Bitcoin Core nodes, speaking Bitcoin protocol. Not by light clients trying to do RPC.

Sparrow can use the RPC interface running on 8332 to connect to a Bitcoin node but you don't (or at least definitely shouldn't) expose that to the public internet, as it would give everyone full access to your node (e.g. spending funds).

Therefore, Sparrow connection to a Bitcoin node (without Electrum) works when both are on the same machine and also if they're on a LAN & the 8332 port is opened in the node's own firewall. Then you can access it through its local IP.
Here are the official instructions by the Sparrow team: https://www.sparrowwallet.com/docs/connect-node.html
Notice how they always mention local IPs; since connecting to Bitcoin Core's RPC interface remotely is basically completely out of the picture, anyway, they don't even mention that.

More on this here: https://bitcoin.stackexchange.com/a/88948/119879

I also just tried installing sparrow on the node PC and it won't connect to node either.
That's very weird. Is Bitcoin Core still running, fully synced and has the settings in its config file that are mentioned in the official guide?

Here is all that is in my bitcoin core config file

server=1

rpcuser=bitcoin
rpcpassword=yourpassword

[main]
rpcbind=127.0.0.1
rpcbind=node ip
rpcallowip=127.0.0.1
rpcallowip=sparrow ip

I've triple checked these are correct and they worked before. It's so strange that even sparrow on the same pc as the node won't connect. I might try just reinstalling bitcoin core and see if that fixes it.
Post
Topic
Board Bitcoin Technical Support
Re: Sparrow wallet suddenly not connecting to node
by
Mobber
on 27/10/2022, 03:12:06 UTC
Also make sure any anti-virus software didn't wake up and decide that the incoming connection is an attack.
This has nothing to do with the firewall. Even after you opened the port and said 'let connections in' some AV software will STILL think that it knows better then you.
I have had this happen at times when a definition update changes something. And then, a while later after the next update, it starts working again with no issues.

-Dave

This would make sense that AV is causing an issue. I just have windows defender. How would I check that is causing an issue? And any way to resolve apart from waiting for a new windows update to fix?
Post
Topic
Board Bitcoin Technical Support
Re: Sparrow wallet suddenly not connecting to node
by
Mobber
on 27/10/2022, 03:02:19 UTC
Let's clear out something: Your full node has synced. Right in top. Initial block download has finished, and it now verifies chain tips. Correct?

In Windows 11, the Sparrow application directory should be in %APPDATA%/Sparrow. Can you see a sparrow.log there? Please remove any potentially sensitive information (such as WAN IP addresses) and post it here so we can see the problem.

The node should be all synced. It's been running for a few weeks now. How do I confirm it verifies chain tips and the initial block download has finished?

Here is the last two logs from sparrow.

2022-10-26 19:52:04,426 ERROR [JavaFX Application Thread] c.s.s.p.ServerPreferencesController [null:-1] Connection error
com.sparrowwallet.sparrow.net.ServerException: Check if Bitcoin Core is running, and the authentication details are correct.
   at com.sparrowwallet.sparrow@1.6.6/com.sparrowwallet.sparrow.net.ElectrumServer$ConnectionService$1.call(Unknown Source)
   at com.sparrowwallet.sparrow@1.6.6/com.sparrowwallet.sparrow.net.ElectrumServer$ConnectionService$1.call(Unknown Source)
   at javafx.graphics@18/javafx.concurrent.Task$TaskCallable.call(Unknown Source)
   at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
   at javafx.graphics@18/javafx.concurrent.Service.lambda$executeTask$6(Unknown Source)
   at java.base/java.security.AccessController.doPrivileged(Unknown Source)
   at javafx.graphics@18/javafx.concurrent.Service.lambda$executeTask$7(Unknown Source)
   at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
   at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
   at java.base/java.lang.Thread.run(Unknown Source)
2022-10-26 19:52:35,664 ERROR [JavaFX Application Thread] c.s.s.n.ElectrumServer [null:-1] Failed to start BWT
dev.bwt.libbwt.BwtException: JSON-RPC error: JSON decode error: missing field `keypoololdest` at line 1 column 334
   at com.sparrowwallet.merged.module@1.6.6/dev.bwt.libbwt.daemon.NativeBwtDaemon.start(Native Method)
   at com.sparrowwallet.sparrow@1.6.6/com.sparrowwallet.sparrow.net.Bwt.start(Unknown Source)
   at com.sparrowwallet.sparrow@1.6.6/com.sparrowwallet.sparrow.net.Bwt.start(Unknown Source)
   at com.sparrowwallet.sparrow@1.6.6/com.sparrowwallet.sparrow.net.Bwt$ConnectionService$1.call(Unknown Source)
   at com.sparrowwallet.sparrow@1.6.6/com.sparrowwallet.sparrow.net.Bwt$ConnectionService$1.call(Unknown Source)
   at javafx.graphics@18/javafx.concurrent.Task$TaskCallable.call(Unknown Source)
   at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
   at javafx.graphics@18/javafx.concurrent.Service.lambda$executeTask$6(Unknown Source)
   at java.base/java.security.AccessController.doPrivileged(Unknown Source)
   at javafx.graphics@18/javafx.concurrent.Service.lambda$executeTask$7(Unknown Source)
   at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
   at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
   at java.base/java.lang.Thread.run(Unknown Source)
Post
Topic
Board Bitcoin Technical Support
Re: Sparrow wallet suddenly not connecting to node
by
Mobber
on 26/10/2022, 19:20:02 UTC
I setup a full node a few weeks ago and successfully connected sparrow wallet from a different PC but on same network. It connected fine until yesterday and now sparrow won't connect. When I setup the node I followed the tutorial on bitcoin.org and did the port forwarding. The node I still receiving incoming connections fine. I followed the sparrow tutorial and all info is still correct.

The node is running on a PC with windows 10 and sparrow is on a pc with windows 11. I haven't changed anything but sparrow just won't connect now. Any suggestions?

By same network, do you mean both PC is on same LAN/local area network? If yes, either try
1. Configure DHCP (which already suggested) and make sure you entered correct local IP of your node on your sparrow wallet.
2. Check firewall configuration on both device. There's rare case where Windows Firewall broken or it's rule changed after Windows update.

Yes same LAN network. I configured the DHCP on the node PC. The local ip's are correct according to my router. The WAN ip is changing though.

The firewall has allowances for both Bitcoin core and sparrow. Do I need do more indepth config than just the "add program" option? I also just tried installing sparrow on the node PC and it won't connect to node either.
Post
Topic
Board Bitcoin Technical Support
Re: Sparrow wallet suddenly not connecting to node
by
Mobber
on 26/10/2022, 19:09:58 UTC
When I setup the node I followed the tutorial on bitcoin.org and did the port forwarding. The node I still receiving incoming connections fine. I followed the sparrow tutorial and all info is still correct.

The node is running on a PC with windows 10 and sparrow is on a pc with windows 11. I haven't changed anything but sparrow just won't connect now. Any suggestions?
How about the guide above it about setting a static IP: bitcoin.org/en/full-node#configuring-dhcp?

By saying "still receiving incoming connections", do you mean you're still getting "Inbound" Peers or not?
Because if not, my best guess is your set 'rpcbind' IP address didn't match after getting a new IP address.

The node is definitely receiving incoming connections. It has 21 inbound right now and bitnodes shows it as accepting incoming. The WAN ip is automatic and has changed since I setup the node. But it looks like the internal ip's for the two PC's are static. Should I change that WAN ip to static?
Post
Topic
Board Bitcoin Technical Support
Merits 1 from 1 user
Topic OP
Sparrow wallet suddenly not connecting to node
by
Mobber
on 25/10/2022, 21:29:59 UTC
⭐ Merited by ETFbitcoin (1)
I setup a full node a few weeks ago and successfully connected sparrow wallet from a different PC but on same network. It connected fine until yesterday and now sparrow won't connect. When I setup the node I followed the tutorial on bitcoin.org and did the port forwarding. The node I still receiving incoming connections fine. I followed the sparrow tutorial and all info is still correct.

The node is running on a PC with windows 10 and sparrow is on a pc with windows 11. I haven't changed anything but sparrow just won't connect now. Any suggestions?