That's not it. If you can't find any other file then consider trying the symlink method which I mentioned earlier. It would all be much easier on Windows.

The debug.log should be located in the datadir. You can check if the data directory was created on the external drive or check the default one on your Mac. I doubt that you will find anything.

Since you cannot set the datadir in the configuration file and modify the startup parameters on macOS, you have to create a symbolic link to your HDD or reinstall Bitcoin Core (only if you were prompted to select the data directory on the first startup; blockchain data might get deleted if you don't move it before uninstalling Bitcoin Core; if you weren't asked to select it, follow the former suggestion).

Select 'View -> Show Coins' and right-click on specific coins in the 'Coins' tab to either spend from or freeze them. You can do the same in the 'Addresses' tab if you enable it.


You can freeze every address and UTXO individually. @Down: I'll keep that in mind.

Your node can't connect to any of the DNS seed nodes which share the IP addresses of other Bitcoin full nodes. Do you have any firewall enabled and what are your Bitcoin Core startup parameters? You could try to mitigate this issue by manually connecting to a specific node for some time by adding '-connect=ip_address' to the startup parameters.

Yes, there is even a mobile version of Electrum so you can use it if you don't want to bother with looking for another option. Select 'Wallet -> Private Keys -> Export' to get your keys.

Install the missing module by typing in sudo python3 -m pip install dnspython

Data Loss Protection, it was mentioned in the LND v0.6 changelog which you quoted.


Actually, you don't have to run a full Bitcoin node if you are using LND! LND supports neutrino which lets you interact with the blockchain using third-party nodes. Keep in mind that it's still experimental but it's been vastly improved since it was released. You might give it a try. Thanks for clarifying your previous message.

Yes, it's a privacy enhancement. You can reuse old addresses. Go to 'View -> Show Addresses' and you should see 'Addresses' tab where you will find all of your addresses, including the already used ones.

I totally forgot about this method, sorry! Since SCBs make use of a feature built into the protocol, they should be reliable. Personally, I have never had a chance to restore my node from such a backup. Once the DLP is initiated, the remote node sends the latest commitment transaction and forcefully closes the channel. The only problem with your proposal is that your NFS backup might become invalid anytime unless you stop participating in the payment routing. How often would you backup the file? Every time it was modified?

TCP should be enough just like for a Bitcoin full node.


Same as above.


There is no safe method of channel backup at the moment. It's much easier for private channels since they don't participate in payment routing. If you lose a backup and don't want to try using the old one, the only "solution" is to wait for the other party to close the channel.


Watchtowers do not store any backups of your channel. They simply monitor the network in case the other party of your channel attempted to cheat by broadcasting an old state of the channel. They store and publish justice transactions when needed.

Every time a Lightning Network transaction is settled, a commitment transaction (a transaction which settles the current balance of the channel) is signed and the revocation key for the previous transaction is shared. The commitment transaction also states what happens if the other party revokes the transaction or if they don't do it in x blocks (x=144 by default). A justice transaction revokes the outdated commitment transaction.

It executes the code downloaded from an external website. I can't really tell you what it exactly does because I am unable to view the contents of the link. I don't think that they have stolen your Electrum password.

Bitcoinmixer.eu is listed as a scam on this list which is maintained by a trusted member.


Since the console returned an error, I don't think it did any harm to your wallet. You might want to move your coins to a new wallet, just in case. If the code had been executed correctly, I am sure that your funds would have been transferred out.

There is no need to back up the wallet file again as long as you don't import any private keys. I don't think you are going to do it. Back up your wallet once, copy the file to multiple devices, optionally encrypt them and don't forget the passphrase.

So the destination address is not the one as it was suppossed to be? It seems be a similiar issue to this thread which I answered a few minutes ago. What version Electrum do you have and where did you download it from?

You either need you wallet file + passphrase or only private keys to spend your funds. The wallet file contains your private keys and it is encrypted with your passphrase.


One or a few of your addresses will participate in the transaction depending on the number of coins you want to spend. Let's say you want to send 0.15 BTC but you received 0.1 BTC to two different addresses. Both of these addresses will participate in the transaction and the remaining 0.05 BTC minus the transaction fee will be returned to your change address.

Yes, you will need your private keys to spend the coins. The corruption Lauda mentioned affects the blockchain data; not your wallet. It might be easier for you to copy the wallet file to a few different data storage devices after encrypting them with VeraCrypt than writing the Master Private Key down. Other wallets give users a mnemonic passphrase (12/24 words) which can be used for wallet recovery.

Ledger Live supports legacy addresses. You should be able to add a new Bitcoin account with this kind of addresses.



It sounds like the address has been replaced by a malware or the Electrum itself. What version of Electrum do you have and where did you download it from?

Spróbuj wyczyścić cache w ustawieniach przeglądarki. Nie przypominam sobie, żeby na telefonach był odpowiednik CTRL + F5 lub CTRL + SHIFT + R.

Manager: Zwei
Nazwa kampanii: WOLF.BET
Jakie rangi: 5x Sr. Member
Ile do zarobienia/tydzień / ilość postów: 0.00010 BTC/post; maksimum 40, minimum 15 postów na tydzień.
Dodatkowe informacje: Minimum 7 postów tygodniowo w Gambling, maksymalnie 7 postów w lokalach.