Yes, Electrum will be able to find all of them. However, if you created new accounts in the Ledger Live or the Chrome app before, you will have to create a new wallet and modify the derivation path slightly for each account separately. If you want to see a list of about 20 addresses then go to 'View -> Show Addresses' and you should see a new tab called 'Addresses'. Since there is nothing on your default account (I assume that there is no transaction history), I don't think if there is any point in checking other accounts.

Also, don't use legacy addresses. Nested SegWit addresses (starting with 3) ensure full compatibility while letting you save on fees. Not as much as if you were using native SegWit (bc1...) but it is not supported by some exchanges and services yet.

The thing is that you don't have to. I have already linked a guide in the first post which shows how to obtain a nested SegWit wallet with any Electrum seed. Even if this method stops working in the future, it will be possible to use old versions to export private keys.


It was not supposed to be that.



Sure, that's why I pointed it out (quote below). Still, this 'hack' is a much better choice than using niche wallets or legacy addresses.

You probably have an address starting with bc1, don't you? Unfortunately, many services still don't support this kind of addresses even though users would benefit from lower fees. You can either create a new wallet and select Legacy type of wallet or follow this guide in order to generate addresses starting with 3. You will save a little bit on fees if you do the latter one. If you don't mind it and don't want to mess up anything, do the former one.

No, there is nothing you can do with the testnet. However, you might find regtest mode useful for your test. Bitcoin.org seems to be down for some reason so I linked a different website. Here's the Bitcoin.org link, try to open it later if the previous one doesn't provide you any useful information.

Przyjrzałem się bliżej podlinkowanemu wcześniej forum i zauważyłem parę rzeczy. Użytkownicy nie mają przypisanego ID (prawdopodobnie jest to widocznie wyłączenia dla administracji), linki do profili zawierają nazwę użytkownika. Została dodana możliwość ustawienia wyświetlanej nazwy użytkownika. Pojawia się ona obok nazwy wybranej podczas rejestracji, której nie można zmienić. Wyszukiwanie użytkowników działa sprawnie. Forum ma także wbudowane powiadomienia o wspomnieniu.

The chrome extension might be deprecated anytime and it still relies on Ledger nodes. Pairing the Nano S with Electrum would be a much better recommendation.


He wouldn't see that the transaction hasn't been confirmed yet if he hadn't done that.

There seems to be a problem with Ledger Live. Go to the settings, select 'Help' and click on 'Clear cache'. This will force a resynchronization with the blockchain.

Every block explorer clearly shows that you received 0.00710868 BTC. Can you ask them where did they get the Bitcoin price from? They should have already mentioned withdrawal fees if there were any, so it looks more like a difference in the exchange rate of Bitcoin.

Without a miner, you won't be able to recover your coins. It's not worth the hassle unless you lost a lot of coins. You can try looking for one on the BitcoinSV subreddit. Don't share your private keys with anyone. They won't be needed for such operation.

Now, the question is more clear to me.


Unless the vast majority of LN users exclude or lower the priority of large HUBs, it won't make that much of a difference. It's kind of 'vote with your wallet'. I don't think that's an issue since more layers are going to be built on top of the Lightning Network, so an avarage Joe will use different layers while more experienced users will know about priorities.

It looks like LND allows to ignore certain nodes while querying possible routes (ignored_nodes parameter). The outputs can be used in SendToRoute, so it's already possible to do what you suggested manually using LND. SendPayment does not have such feature but it is possible to select the first node which will route the payment.

You didn't receive 0.0096 BTC. Bovada sent you exactly 0.00710868 BTC in this transaction. Then, you spent 0.00232704 BTC and the remaining 0.00467278 BTC was sent to your change address. Everything seems to be fine. It looks like you were charged a fee for the withdrawal. Their website is unavailable in my region, but here's their Bitcoin FAQ - you might find information about fees there.

Jeżeli chodzi o funkcje, to będzie ciężko. Więcej rzeczy brakuje niż zostało dodanych. Podejrzewam, że utrzymanie forum kosztuje krocie, a przeniesienie się na silnik, który wspiera wydajniejsze rozwiązania, pozwoli na zmniejszenie kosztów działania forum. Działa ono zdecydowanie szybciej oraz dobrze dopasowuje się do urządzeń mobilnych. Dlaczego sam go nie przetestujesz? To forum wygląda na dosyć aktywne.

What type of address your Bitcoin address is? Does it start with 1, 3 or bc1? Both Bitcoin Cash and BSV don't support SegWit so recovering your coins won't be easy if it starts with bc1 or 3 (assuming it's not a multisig). As far as I remember, someone used to recover coins of Bitcoin Cash users for a small fee, but I am not sure if he also does the same thing for BSV.

Node operators are already able to create private channels which are not announced to the rest of the network. This is why mobile wallets do not route payments. I don't think that it affects decentralisation in a positive way, but forcing someone to route payments is pointless and could be frustrating.


What if some nodes somehow faked (lowered) the number of their channels? A channel is considered not capable of routing when it is offline. What if it could be exploited in some way?


Wallets would have to have some sort of protection against overcharging (Eclair Mobile allows you to stop the payment if the fee is higher than 3% of payment's value). Some invidual nodes might have their fee policy set to ridiculously high values. Most big HUBs will offer low fees and short routes at least at the beginning.

Can't he generate a new wallet in Electrum, save the mnemonic phrase, obtain the master private key from the wallet file and import it into Bitcoin Core? I am not sure if Bitcoin Core allows only to import individual keys. Edit: It doesn't. Importing a few address would do the trick but might not be worth it.

Blame the service for not letting you set the transaction fee. 1 sat/byte has been enough for most of the time. You would have paid around 0.00000226 BTC for such a transaction (you have to take a lot of factors into consideration, though). The Lightning Network which is built on top of Bitcoin offers instant transactions for less than 1 satoshi (0.00000001 BTC)


It would, so that's why I suggested that it was a synchronization problem. Click on the red/green dot in the bottom-right corner and try changing the server. You can also post your address here so that we could look it up if you don't mind it.

Many services and exchanges charge a fixed fee for withdrawing BTC. The network might have been busy at the time. A 0.0007 BTC fee wouldn't be that much in such a case.


What version of Electrum do you have and where did you download it from? After the reinstallation, your Bitcoin unit must have changed from BTC to mBTC. You can change it in the settings. Have you tried connecting to a different server? There might be a synchronization problem.

There are plenty of ways. Look for Bitcoin ATMs in your local area, visit localbitcoins.com and make an appointment with someone or buy it via a credit card (example). ATMs and credit card services charge you a bit extra, so if you want to buy a lot of BTC then consider using a local, online exchange. It won't be instant, though.

The address does not show up in any block explorer. The maximum amount of confirmations a transaction can get in only an hour is about six. It's not even close enough to over 3000. He fabricated the screenshot.

Take a look at the Bitcoin difficulty chart. As you can see, the difficulty increased more times than it decreased (otherwise we would have reached the minimum difficulty at some point). What happened before the difficulty increased each time? More than 2016 blocks were mined in a two weeks time. Your calculations are off because you assume that every two weeks, 2016 blocks are mined.