To force bitcoind to use only Tor I've the following in my bitcoin.conf file: listenonion=1
onlynet=onion And bitcoin-cli -netinfo yields only incoming and outgoing connections via Tor onion addresses. If you need inbound connections, add -listen=1 command line option or follow the suggestion above, in your "bitcoin.conf" file.
You'll need it since -proxy disabled listen.
Take note that onlynet=onion will prevent you from connecting to nodes on clearnet.
Have you tried in bitnodes if your node is reachable?
If it is now, you'll eventually get inbound connections after a while.
Thank you both! I have added -listen=1 option. I haven't added the onlynet=onion option because I want to receive and send all kind of connections. However, it looks like I still don't get incoming transactions. BUT in bitnodes it looks like my onion address is discoverable. ----EDIT----
I am so happy! Thank you! Look: Bitcoin Core v22.0.0 - 70016/Satoshi:22.0.0/
ipv4 ipv6 onion total block
in 0 0 4 4
out 10 0 0 10 2
total 10 0 4 14
Local addresses
<my onion address>.onion port 8333 score 5
|
|
|
|
At the moment my -netinfo is as follows: Bitcoin Core v22.0.0 - 70016/Satoshi:22.0.0/
ipv4 ipv6 onion total block
in 0 0 0 0
out 9 1 0 10 2
total 9 1 0 10
Local addresses
<my onion address> port 8333 score 4
I have run bitcoin core using: .\bitcoind.exe -datadir=<bitcoin core path> -externalip=<my onion address> -proxy="127.0.0.1:9050" -debug="tor" Tor is running as a service on my system. |
|
|
|
is remembering 12 words that hard?
But what if, you have 1,000 Bitcoins in your wallet, and you forget one word, JUST ONE WORD, and you have no copies of your seed phrase anywhere because "remembering 12 word is not that hard". You'll definitely know the true meaning of manual brute-forcing. Hahaha.  OP, have both physical copies, and digital copies. Put the physical copy in a tightly sealed pack, and store it under lock+key in a safe. Encrypt the digital copy in a USB Drive and place it in nested directories, with each layer encrypted, and with different passwords. If it's the last word, you are lucky, because it derives from the previous 11 haha! It's a joke, I totally agree that we should never rely on our memory! Our brain is extremely vulnerable. |
|
|
|
So far I have never used Wallet Sparrow, but after you discussed this, I think I need to try to learn Wallet Sparrow as well as do a trial run.
Sparrow is a very good wallet. I am still learning its features. There are many conveniences that we can get from Blue Wallet, but what you need to know is that Blue Wallet will immediately close its LN node service until the end of this month. If their LN node service shuts down, Blue Wallet will look like any other open source Bitcoin wallet. Despite that, I personally am very comfortable with Blue Wallet on android. Oh yeah. Don't forget to replace a newer laptop when you have enough money to buy it so it's easier to work  I am also using bluewallet on android. I use it to "monitor" my wallets and to send transactions using my airgapped signing device. Perhaps I can buy a webcam. For the time being, as long as I can do all my transactions using BlueWallet, I am ok! |
|
|
|
Hello! I am running bitcoind using my terminal. I am on a windows machine. When I run I get the following response: ipv4 ipv6 onion total block
in 0 0 0 0
out 8 2 0 10 2
total 8 2 0 10
I know that in order to get incoming connections I need to do portforwarding and allow connections on my firewall. So, let me say in advance that I can't do this!Could you help me allow anonymous connections? I suppose that in this manner, I won't have to care about port forwarding. Thanks in advance! |
|
|
|
Hello! does anybody know if BlueWallet offers timelocked transactions?
I am not certain about this, but I do not think so. If you want use timekock, I have seen it on Electrum while making transaction, but only on desktop Electrum. Or use https://coinb.in/#newTimeLocked. Thank you! I have used timelocked transactions yesterday using Sparrow. Actually it was only yesterday when I learned about them and I needed to try it out. I was interested in BlueWallet since I use cold storage and my signing device really struggles with scanning the QR code from Sparrow and vice-versa. My laptop's camera is not so good. |
|
|
|
|
Hello! does anybody know if BlueWallet offers timelocked transactions?
|
|
|
|
Sorry, that's not my area of expertise, so I can't check the code. Alright, however randomness is a very fascinating subject in my opinion. Sometimes I wonder what is truly random. |
|
|
|
Unless you made a mistake somewhere, and the random isn't as random as you think.
If you have the technical knowledge, feel free to check it here: https://bitcointalk.org/index.php?topic=5432897.0 although I have deleted the repository. "Vampobit" was my original account here, but for personal reasons, I don't want to be "vampobit" anymore. I may still have access to it though. As far as randomness is concerned, I have decided to follow a very simple approach. I roll a dice 256 times and if it's 4-6 I sign it as 1, else I sign it as 0. Then I have my entropy like 100010101.... Of course Having a dedicated system for offline signing is easier than getting one each time you need it. And if you have said system already, it's easy to import a paper wallet when you need it. I like to use a wide variety of wallets, depending on my needs at the moment. Sure! I have a 2-of-3 multisig and a singlesig with passphrase personally. But I totally agree with you. EDIT: I still have the code on my PC. If you 're interested, I could re-create a repository for you to check it. |
|
|
|
I strongly advise you not to use paper wallets. Paper wallets are fine, as long as you know what you're doing. That includes knowing that almost all websites that offer paper wallets will scam you. Even when you use them offline, they can produce a compromised private key if the source is compromised. I have written a program in Java which creates old-school paper wallets. Therefore I am almost certain of the source code's validity. However, I believe it is much easier to use an airgapped device for signing transactions. Paper wallets are fine, as you said. I think though that nowadays, it's better to use more modern approaches. Anyway! |
|
|
|
Do you think there may be a way to broadcast a transaction automatically though? Generally speaking. There may be, but it's not worth the time and the potential drawbacks. You should rely on your daughter to do this individually, and not to some third party or local computer. Also, I'd teach her some security basics before handing over anything. Unless she practices software engineering and knows from malicious factors, I'd tell her how to setup an air-gapped computer (or give her hardware wallet instructions for the sake of simplicity), tell her a few obvious things about Bitcoin wallets etc. It'd really be a pity to lose much money, and I'd be responsible for that. Yes I agree! I don't have a daughter actually. I was simply inspired by the OP's thread and it got me very interested, that's why I asked. |
|
|
|
No, I don't think he meant that. You can broadcast the signed transaction individually. You make it, set a certain block height as the requirement, sign it, and once the height is such, it can be broadcasted and mined. All this time, the signed transaction can be kept somewhere safely.
Yeah most probably he/she meant what you said. Do you think there may be a way to broadcast a transaction automatically though? Generally speaking. Obviously! I did it both in testnet and with real money however  Great post btw, I will check it. |
|
|
|
However, who was going to broadcast the transaction in case I died before the block height 786243 was reached? The person receiving the coins. This is why I said above that after you have created the timelocked transaction, you should give a copy to your heir for safe keeping. This is so they can broadcast it after the timelock has expired. You can also keep a copy yourself, such as in a safe at home or a safe deposit box at a bank or somewhere else your heir will gain access to after you die. If you are still alive, then before the timelock expires you move one of the inputs in the timelocked transaction to a new address, therefore rendering the timelocked transaction invalid and unable to be used. You then create a new timelocked transaction and give this to your heir. Rinse and repeat. So is there an automatic broadcast option? It doesn't really make sense to be able to set it up automatically, considering the technical aspects behind it. I will try to manually cancel a timelocked transaction following the process you mentioned. |
|
|
|
If so, why not give someone (your daughter) your seed phrase instead? Because then they could clear out your accounts before you die, and you also have the added risk of them storing a copy of your seed phrase and it being vulnerable to theft. Timelocked transactions avoid all of that. Is this option available using timelock? Because if you can cancel it, then I understand that this is different from sharing your seed phrase. Yes. You simply spend any one of the inputs before the timelock expires and the timelocked transaction become invalid and therefore useless. I have heard many people in my life, claiming that Bitcoin inheritance is extremely difficult. Using this feature, however, it seems INCREDIBLY EASY. The only argument that I can accept from now on, regarding inheritance, is that the person who will inherit the money need to already have a wallet (and know some stuff already). -- EDIT --I really needed to test it, so: I am using Sparrow upon my bitcoin node. I have just signed a transaction using my signing device. I have set it to be able to be broadcasted after block height 786243. The current block height is 786238. So the transaction was not broadcasting until we reached block 786243. Then I broadcasted it successfully. However, who was going to broadcast the transaction in case I died before the block height 786243 was reached? |
|
|
|
Hello! The purpose of this feature is to provide inheritance to someone? If so, why not give someone (your daughter) your seed phrase instead? And that I am able to cancel that transaction.
Is this option available using timelock? Because if you can cancel it, then I understand that this is different from sharing your seed phrase. |
|
|
|
Hear me out guys.
Paper can be really fragile, and all it takes is a tear or water spill or defacing to deny you access to your BTC forever.
So, you should make a second copy of your seed phrase that is identical to the first, and store it on a different place from the first seed so that they both cannot go down together except in extreme circumstances like a natural disaster.
Personally, I have two backups in two different locations. In each location I maintain: 2x: { 1 piece of paper with my seed phrase written upon it, in black ink. I have put the paper in a plastic card sleeve. I have put the sleeve in a plastic zip bag. } So I have in total 4 backups actually, but placed in two different places. So, 2 places guard me against physical disaster on the specific place and 2 backups in each place guard me against physical damage on a specific piece of paper (which is highly unlikely). Thoughts: 1. I know my system is ultra redundant, but I sleep well at night. 2. I maintain paper backups, so putting 2 of the aforementioned packages in a single place, requires less space than using other possible backup media. |
|
|
|
|
One more question! For signing transactions, which one is more easy and convenient?
Let's say I want to sign a transactions using 2 cosigners from my 2-of-3 multisig, which one is easier to use?
How easy is it to use a signing device to sign a transaction?
How easy is it to sign with one cosigner and then wait till I get to where the other cosigner is in order to sign too?
|
|
|
|
Ahh, I see. I misunderstood your previous post - I thought you were saying you had already set up an Electrum server, when you were actually saying you already have Sparrow pointed at your own node. In that case, I would just use Sparrow for the use cases you described in your first post. It is more than capable of doing all of those, and you will maintain your privacy since it will only sync via your own node. Whirlpool is a coinjoin implementation, run by Samourai, which is accessible via Sparrow. You can read more about it here: https://sparrowwallet.com/docs/mixing-whirlpool.html. Essentially, you pay a small fee and then coordinate with other users to create transactions which send the same amount of bitcoin you put in back to you, but in a way which obfuscates which bitcoin actually belong to you. If you are interested in anonymizing your bitcoin so entities such as centralized exchanges and blockchain analysis companies cannot trace it, then you could look in to this. If you do plan to use Whirlpool, make sure you also connect to the coordinator via Tor (explained in the link I just shared). Τhanks! yeah I am in the middle of watching this https://www.youtube.com/watch?v=6TcUY2yU41w&t=1101s&ab_channel=BTCSessions to make it work. |
|
|
|
If you are already familiar with Electrum and already have a server set up, then I see no reason to change unless you wanted to use Whirlpool.
Ok, so now you got my attention with Whirlpool. I have Sparrow running over my Bitcoin Node. So I don't run an Electrum Server personally. |
|
|
|
|
Show Posts
