Reproducible. Not an issue as Electrum won't run if it is a critical problem.

In your terminal, install pip and then upgrade requests.


Electrum uses requests-2.25.1 but Debian 10 doesn't have that.

I wouldn't install anything sensitive without verifying its authenticity first. Apple doesn't allow sideloading apps and thus you can't validate the binaries before installing it. For Android, at least you can validate the signature before pushing the apk to your phone.

The problem with those apps is that they don't usually contain any malware or exploit but steals the key in a very obscure way such that it is hard to detect without any reports.

Brass will be a better choice than copper as it is more corrosion resistant.

Brass will still corrode more than stainless steel and has a lower melting point and softer. In Jlopp's tests most of the higher rated ones uses stainless steel or titanium except one which used copper and you can see that it corroded quite badly.

Oh, I didn't edit that part. It took me quite some time to demonstrate and get the syntax right.

It's working perfectly. The only part that is not working is getting it to work in the UI.
You don't have to strictly backup your wallet (in the case of Electrum) using the seed phrase. If you want, you can back it up in a method similar to Core using the wallet file encryption with the seed and the addresses all being encrypted in the wallet file.

You can either encrypt the file fully (which is enabled by default) or only encrypt the keys.

It doesn't hurt to just try to open it first.

Aluminium is fairly weak and oxidises. No such thing as fireproof, only fire resistant.

That being said, if you're doing any etching, try to find some forms of alloy. Most non-alloys are fairly soft and have a comparably lower melting point. If the security is of any concern to you, you can probably sandwich two plates of metal together with the seeds facing each other. If not, there are commercially available solutions which are not so eye-catching.

It is not a cold wallet. It is merely a form of backup.

Steganography is not uncommon. You can obviously do so yourself but putting it on a vinyl disk is probably one of the most terrible ideas; expensive and short life span. I'd rather etch mine on a metal, probably cheaper and more durable by far. I really doubt the general population has a working vinyl disk, not even something that can write on it.

Electrum supports mini private key. Casascius's mini keys were 22 characters instead of the usual 30. Electrum will support anything more than 20 if it is valid.

It's simple to actually just do the whole process of obtaining a standard WIF yourself. Just SHA256 it and you'll get an ECDSA private key which can easily be converted into a WIF.

MyCelium is a wallet and coinbase is primarily an exchange. Coinbase can and will collect personal data about you, have certain level of control over your coins as well.

Coinbase also does not offer any sort of discounts for on chain transactions as well. MyCelium, though being less polished, still offers far more security as well as privacy.

It's completely possible, though I'm currently having difficulty doing so but that is on testnet so I'm not too sure about main net.

On your offline computer, go to Help>Console and key in this:


You should get an output with loads of info. And take note of that field.


Generate another receiving address and transfer both the desc and that receiving address to the online Bitcoin Core.


Next, go to your online Bitcoin Core and key in this:

after that,

Use the code below

Afterwhich, you'll have a long string. Copy that and save it to a file and transfer it to the offline computer.



On the offline computer, go to the file and copy the string again. Then go to Bitcoin Core, File>Load PSBT from clipboard.

A dialog will show up with the information, double check that the change address specified is from your offline wallet, the destination is as intended as well as the amount. If everything checks out, press sign TX. Press Copy to clipboard and save it to a file for transfer to your online computer.

After moving it to your online computer, open the file and copy its contents to clipboard. On the online Bitcoin Core, go to File>Load PSBT from clipboard and check it one final time before pressing Broadcast TX.

---

Personally, I don't think Bitcoin Core is designed for airgapped storage as it doesn't offer master public keys to easily create a watch-only wallet or is the UI that optimized for such a thing as well.

Coinbaseaux flags has been empty and it's omission doesn't affect the scriptsig. The structure of the scriptsig, except for the block height being specified at the start won't affect the validity of it.


The omission of it *probably* won't result in any changes and probably being due to the fact that I don't have sufficient resources to mine a block for myself and attest to that statement. If you cannot review the code in its entirety and check if the changes would affect any other components, it would be better to just go and run 0.19.1 and save any potential headaches. As for the link in that post, the flag is 062f503253482f which decodes to /P2SH/, which was also removed in 2015 as it was previously used to monitor for P2SH signalling.

It doesn't. A seed phrase is used to generate a BIP32 seed which can then be used to generate the private keys for the addresses that you need. As mentioned, it is one of the variables when generating your addresses and keeping it constant allows the same addresses to be generated again, provided that the way that you're generating it remains the same.

Seed phrase cannot serve as a backup to anything else other than the addresses generated using the seed phrase. Some things that are not covered by this includes your address labels, transaction descriptions, LN channels, etc. If you send funds to and from your addresses and everything else is unimportant, you can choose to only backup your seed phrases using a piece of paper or any other physical backup methods (metal etching). If the labels and other miscellaneous stuff is also important, you can choose to keep another encrypted backup of the wallet file. The wallet file is prone to mechanical failure due to the fact that it's stored on an electronic medium unlike the seed phrase which is usually stored on a physical medium.

Works only with 0.19.1 and below. Software expects a coinbase aux flags from the RPC with Bitcoin Core which was removed in version 0.20.0. Modify it to remove the flags[1] that are expected which should be fine. I've never used it in a production scenario so exercise caution and avoid doing it unless you know what you are doing exactly.

[1] https://bitbucket.org/ckolivas/ckpool/src/b8f66852483542326de8c5705a3e36242347ad12/src/bitcoin.c?at=master#bitcoin.c-95,102,147:148,150

I don't think 2 and 3 are particularly strong arguments. While others may have changed their own ratings, it doesn't necessarily mean that the user who left that rating has changed his mind though there really isn't anything to prove otherwise either. If the forum maintains its position of not interfering with trust ratings, I highly doubt anything can be done about that. There are probably tons of ratings like this and would probably result in people wasting loads of time trying to gather all the evidence and making an impartial judgement after.

Your post probably mainly highlights the shortcomings of trust system. Most trust ratings are not correctly used anyways; I have seen too many negatives that don't necessarily point to the fact that "trading with this person is high-risk". I agree that the first point could have some form of review though, it is not difficult to get the signed message from the hacked account and restore it.

The parameter has to be the absolute path (ie. D:/WalletDump).

The GUI doesn't display change addresses in the receiving addresses Window, AFAIK so that'll probably not include everything. Try using listaddressgroupings by going to Help>Console. Unlock it with walletpassphrase PASSWORD 600 before that command if you have it password protected. Of course, the only way to be sure of the exact amount is by synchronizing Bitcoin Core fully.

Exactly 100 times less? Did you check the denomination used in Electrum?

No. The most that could happen is that the transaction gets stuck and/or the transaction cannot get broadcasted.
Did you use the seed and import into Electrum?

I think @ETFBitcoin is talking about the process of sending the funds to the scripthash address with the CLTV condition? The transaction won't be in the mempool in the first place as it's non-final and having a signed transaction intended for so far in the future comes with a plethora of risks and vulnerabilities as well.

I don't find OP_CLTV that suitable for long term holding.

Most people that are holding Bitcoins for a long period of time tend to have a significant amount of Bitcoins and could use those funds in the case of emergency. Having it locked up would freeze up some available funds at least. Let's the realistic, the reason why Bitcoin is priced as it is now is mainly because of the institutional buying and general acceptance (not adoption) of it as an alternative currency. It hasn't increased exponentially due to time and if it did, it would align more with the deflation rate. Holding Bitcoin longer means that you're trusting that it would go big sooner or later but the time will NOT guarantee this to happen. Any change in the general perception of Bitcoin either due to unfavourable policies or discovered network weaknesses would result in a steep price job. As such, since OP_CLTV is designed to lock it for a specified period of time, unless you're betting on the price of Bitcoin to increase in the long term due to external factor, then it is fine.

The more glaring issue is the problem with network weaknesses. If for some reason, quantum computers becomes an imminent threat, you'll probably want to move your funds elsewhere and you can't because it hasn't expired yet.

Electrum does have different types of wallet, 2FA and normal (segwit/legacy) for example. Having a method to identify the type of seed it is will reduce any confusion if the user forgets the type of seeds that it has. Using a seed created with TrustedCoin will result in Electrum automatically restore it as such with the 2 main keys needed for signing, detecting if the user used segwit or legacy, etc. Perhaps not ideal for but better[1].



[1] https://electrum.readthedocs.io/en/latest/seedphrase.html#motivation

Bitcoin Core is the GUI and it doesn't run alongside bitcoind. You either run bitcoind or Bitcoin Core.

Don't use killall. Killing the process forcefully can result in database corruption.