It's not possible unfortunately. You would have to co-sign every transaction and you would be limited to a small amount of wallets which support multisig.


I would go for the Green Wallet since I didn't experience any problems while using it, but it might be easier for you to explain her how to use the wallet over the phone if you choose Electrum since you have used it. Green Wallet's UI is much more appealing in my opinion.

You should be able to preview the transaction before broadcasting it. Check if any coins are sent to TrustedCoin's address. There are two ways to get rid of the 2FA. You can either create a new wallet and send your coins there (you will get a new seed which you will need to store in a secure place and you will be forced to pay a fee to TrustedCoin) or you can try to import your existing seed to Electrum. You should be able to spend your funds without the need to pay TrustedCoin if restore your wallet.

Does she have an Android or iOS phone? Samourai Wallet should be fairly easy to use if you set it up for her. It supports RBF which could come in handy in case she sent a transaction with a low fee (although it shouldn't happen). Blockstream Green Wallet should be even easier to use. It even supports hardware wallets but I don't think it's necessary in this case. Both wallets are available only on Android.

I would not recommend the mobile version of Electrum. I had a few problems with it, mostly crashes while trying to bump a transaction fee.

The fee is quite reasonable for such a transaction. However, you are using a 2fa wallet which means that you also have to pay TrustedCoin for signing the transaction. According to their FAQ, they charge 0,0005 BTC per transaction. I am quite sure it used to be 0,001 BTC, though.

Yes, your node hasn't been fully synced, yet. You will see your current balance once the sync finishes. There is no need to use -rescan in this case.

That's exactly what I meant. I assumed that you also didn't see your balance. Was the value of the unconfirmed transaction deducted from it?


You don't have to connect to the same server; select a random one. However, I don't think it's going to help since the 'blockchain' value I asked you for is correct. Reinstalling Electrum or trying the portable version are my last suggestions.

Click on the green dot and tell us what the third value ('Blockchain') is equal to. You can also try using a different server.


Thanks for pointing this out. As you can see, the sender can't do it at all times while the receiver can; that's why I forgot about it.

RBF can be used by the wallet which sent the transaction. CPFP can be used be the wallet which contains the destination address.


Theoretically, you can prepare your transaction in a watch-only wallet and then sign it using the recovered wallet, but if you managed to recover the same wallet from which you sent the coins then your transaction history should have been synchronized anyway. What version of Electrum do you have?

Did you use that wallet file while the node was synchronizing with the network? If not then you need to relaunch Bitcoin Core with -rescan parameter. Don't forget to remove it once the rescan is complete. If your node is synced properly then there is nothing wrong with your config.

That's actually interesting because it does not apply to my setup. When I open my wallet, the following message box is shown.

.

When I select 'No' or simply close the box, I can see the list of all transactions. Everything looks as if I were using a watch-only wallet.

Edit: I quickly found out that I can enable the encryption manually just like in a normal Electrum wallet.

Ledger Live lacks some features which are available if you pair your hardware wallet with Electrum. The most notable feature is coin control. Private keys are not exposed to the computer in any way.

iPhone'a można wziąć na raty, a portfela już nie A tak na serio, wiele osób idzie po linii najmniejszego wyboru i wybiera portfele pokroju Blockchain.info i Blockchain.com. Oba są darmowe, nie wymagają instalacji i niestety, ale jeżeli ktoś do nich się przyssa, to potem ciężko jest taką osobę od nich odessać. Pozostaje też kwestia tego ile ktoś ma monet. Mnie też bolało na początku wydać kilkaset złotych, a teraz jestem fanatykiem portfeli i mam aż trzy

If the devices were completely fake then you wouldn't be even able to use them with Ledger Live. If their software was modified, a warning would be displayed during the boot. You can also remove the chassis of the Nano S to see if there isn't any extra chip inside (reference). Most people lost their money because their devices were shipped from resellers who included a pregenerated seed. You should be safe since you ordered the pack from their official account.

Yes, the private keys, which are needed to spend the coins, are stored in the wallet file. They are not encrypted if there is no password set.


Once you update Bitcoin Core, launch it with -zapwallettxes=1 parameter to make sure that all the transactions which are not on the blockchain are removed. Right-click on the Bitcoin Core shortcut, select Properties and add that parameter after '.exe'. It won't cause any harm if it turns out to be redundant. The mempool should be emptied after such an upgrade.

To unstuck such a transaction, shut down bitcoin-qt and launch it with either -zapwallettxes=1 parameter or zapwallettxes=1 in the config. This will remove every transaction from your wallet which is not in the blockchain.

Yes, copy the wallet file to the other server. If you are running a Linux server then your wallet file should be located in ~/.bitcoin/ by default. You might need to run bitcoin-qt with -rescan parameter after pasting the wallet file but it shouldn't be necessary in your case.

I don't think that's the case here. In Electrum, user is prompted to provide a code generated by Google Auth during the setup in case something like this happened (example).

The whole process looks a bit complicated for Bitcoin Core. It's more common for its users to keep the wallet online in order to have all the (latest) blocks downloaded. Consider choosing Electrum instead, it will be much easier for you. No commands involved.

Well, he is not completely wrong. He is now able to receive coins over the Lightining Network. However, the other party can spend the coins which were pushed to them. This feature can be also useful in some other ways.


That's not it. The website he used generates invoices for the testnet. Take a look at the following piece of code.


htlc.cltv_expiry seems to be the culprit here. If you compare the 'Time Lock Delta' for both testnet and mainnet on 1ml.com, you will see that it is equal to 40 and 144 respectively. At the time of the recording, the blocks on the testnet were mined one after another. If you take both of these factors in the account then it seems that that's the reason why it didn't work. It's a bit late here so I will investigate it further tomorrow.

Note: It seems that some mainnet notes have set their 'Time Lock Delta' to 40 or lower. The blocks on the mainnet are mined not as fast as on the testnet so it shouldn't impact the mainnet Lightning Network transaction failure rate significantly.


I would appreciate if someone could link this post under that YouTube video.

TrustedCoin is the native 2FA provider for Electrum. You must have used it at some point since their codes show up in your Google Auth app. Try contacting TrustedCoin as TryNinja suggested.