Electrum & BitAddress Wallets Creation

Can anyone please tell me if my procedure is correct and enough.
I’ve always heard and read that I must disconnect from the internet when creating Electrum Wallets, to keep away from hacks, viruses, malware or having my bitcoins stolen.

I have created electrum wallets and bitaddress paper wallets yesterday. Though I dont know much about its technicalities, I just followed simple procedures I’ve read online.

  1. downloaded electrum exe installer and bitaddress (from github)
  2. save them in my usb
  3. disconnected my laptop from the internet
  4. uninstall and reinstall Windows 10 (I have windows installation files too, in my usb)
  5. created Electrum wallet, write the seed in a paper. save the wallet file in my usb.
  6. created bitaddress paper wallet, write the Public Key and Private Key in a paper (not print). have checked the spellings, capitalizations multiple times.
  7. uninstall and reinstall windows 10 again, scanned my usb, then connect again to the internet.

Thanks for any advice / clarifications,
Elena

How to reference different wallets with curl JSONRPC requests Bitcoin core

I have a headless Bitcoin core 0.17.1 running on Debian 10, and have created a second wallet “johns-wallet”.

I’d like to get the walletinfo (or any wallet request) of that specific wallet via curl, not the cli.

The Bitcoin core API reference doesn’t offer an example of how to target different wallets when not using the CLI (and neither did my Google search).

I’ve tried:

curl --user johnsmith --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getwalletinfo", "params": () }' -H 'content-type: text/plain;' bitcoind:18332/wallets/johns-wallet/

and also

curl --user johnsmith --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getwalletinfo", "params": ("/wallets/johns-wallet/") }' -H 'content-type: text/plain;' bitcoind:18332

And also variations on the path itself to the wallet – none of them return a result, let alone an error.

Running without trying to specify a wallet returns:

{"result":null,"error":{"code":-19,"message":"Wallet file not specified (must request wallet RPC through /wallet/<filename> uri-path)."},"id":"curltest"}

(In case it matters, the Bitcoind is running in a docker container, with a named volume)

bip 32 hd wallets – Is there a simpler form of BIP32-like key derivation?

I’ve read about BIP32 key derivation functions, and also:

Any Elliptic Curve could work in the BIP32 scheme. The only property
of a Curve that BIP32 relies on is that a * G + b *G = (a + b mod N) *
G, which is true for any Elliptic Curve.

(from Is BIP 32 Technology Cryptographic Curve Agnostic?.)

Are there simpler forms of weak-child-only key derivations? (I’m guessing that the HMAC, splitting and concatenation is unneeded for a simpler/weaker scheme. Such a scheme would just have a large number of weak children and no layers/tree.)

Is a simpler scheme possible? (I’m asking about cryptography generally, not whether it’s a good idea for Bitcoin.)

What are best practices around toggling between multiple wallets in bitcoind?

I’ve created a couple wallets on Core to experiment with and want to dedicate one wallet as a live one. What is the best way to move between those wallets inside the command line? When I toggle to a wallet that is not the default in the GUI and try some bitcoin-cli wallet commands it get an error

Wallet file not specified (must request wallet RPC through /wallet/<filename> uri-path)

Is it just a matter of passing a wallet file name into the command? Or is there a better way to manage multiple wallets? Other best practices to a multi-wallet setup (i.e. don’t)?

Can a Ledger Nano X hold multiple BitCoin Wallets?

If I recall, you can access different wallets by using a different passphrase, which is added to the seed phrase as a “25th word”, resulting in a completely different entropy seed and different key-pairs at every index in every path.

https://support.ledger.com/hc/en-us/articles/115005214529-Advanced-passphrase-security

So you could have one passphrase with your “actual” money in it, and a second passphrase with just a couple of bucks in and out. If you are held at gun point and forced to unlock your ledger, you can enter the second password and show the attackers how broke you are :-]

Disclaimer: hypothetical dramatization only

binance – Sent old ERC-20 THETA tokens to mainnet wallets

I recently sent my old Theta token to Binance as well as the Theta Wallet online (wallet.thetatoken.org), and have yet to see a balance in either wallet despite confirmations. I realize now that I sent the old tokens that hadn’t been swapped to mainnet wallets. Is there any hope of recovering my old tokens and swapping them for mainnet THETA and TFUEL?

Are HD wallets private keys any different than regular private keys

Aside from the fact that HD wallets derive them deterministically, is it correct to state that keys driven at any path or index under BIP32 isn’t any different from a private key that’s derived randomly in a non-HD wallet?

In other words, its theoretically possible for someone to derive a private key that’s at a particular node under your master key in HD wallets, irrespective of how small the probability is, and actually the same probability that there is for generating a private key (non-deterministically) that’s already in use by someone else?

Essentially, private key being just a number in a specific range, you can either guess it randomly every single time or have a mechanism of generating random numbers, it essentially means the same thing and is possible to arrive at the same number from either of the ways.

Correct?

multiple wallets on same mobile device

Yes, there is no nothing preventing you to doing that as long as you use different private key, but usually your mobile wallet will generate an HD wallet for you so you wont have to deal with that problem.

Just be sure to use recognized mobile wallet like those here https://bitcoin.org/en/choose-your-wallet?step=1

Also notice that some mobile wallet will offer you to have separate wallet inside their own software, like electrum

Why do most HD wallets require choosing either all Segwit or all Legacy but Bitcoin Core can support both simultaneously?

Electrum and the mobile wallets I’ve used can only support one type of address per HD wallet, but Bitcoin Core can support both at the same time.

Is that simply a choice that Bitcoin Core made or is there something unique about Bitcoin Core in this case since it’s a full-node wallet?