0 sats \ 0 replies \ @025738dda8 6h \ parent \ on: [TECHNICAL] Initial draft of my [personal] summary on part #2 of HD-wallets /ECC bitcoin_beginners
Yes, you can. At least according to your answers below...
Explain why or show how to do it š.
š
Well, depends, publishing xpub generally breaks privacy.
...and assuming that no related private key would leak in the future.
I believe that these exercises cover the most important parts of bip39 well. If you can answer them with confidence, you understood it enough. If you have a question, just ask...
Interesting reading. Well, it's difficult to follow because the natural language is often very inaccurate and it is not always clear what you refer to. But, it looks like a transcript of your mind. And in this sense, good job...
If you don't mind, here are few exercises that might help you in your way:
-
if you know someone's master chain code, is it sufficient to compute any related addresses or private keys?
-
given an xpub and an indexed utxo set, how reasonable is to find all related funds (compute total balance)?
-
which of the following derivation paths do not make sense? xpub/1/0/2, xpub/1/2h/0, xpriv/1h/2h/3, xpriv/4/1/0h, xpub/0h/1h, xpriv/1/2/3
-
what inputs (components) do you need to compute a subkey for a given hardened derivation path (e.g. /0h/2h/1h/0h)?
-
if I give you (any) 2 private keys and a chain code, under what circumstances can you tell me whether are those two private keys related?
-
if I give you my xpub and a related private key (for a public key at derivation path xpub/1/0/2), which funds could you steal from me?
-
if I give you my xpub and a related private key at derivation path xpriv/1h/0/1, where xpriv is unknown to you, what can you steal and/or discover? (xpub is counterpart of the unknown xpriv)
-
is it safe (or how much safe is) to give your xpub to anybody?
Maybe, ask more specific questions. Do you mean BIP39? Or what do you refer to?
BIP39 key derivation performs HMAC512 and then some ECC addition. Nothing that much complex.
Bitcoin is asynchronous and decentralized system. Once you push a valid transaction into the network, there is no way how to 'unpush'. The nodes just have it and share it with others, nobody controls this. You cannot force them to delete it. So the only way that works is to override it by a 'better' transaction that the miners would prefer over the old one (which would invalidate it). And that's by RBF or CPFP.
Lots of UI/UX changes. Not that much of changes in internals (good? bad?). There is quite a lot of hype around. I am missing some more technical explanation of the changes. I did not study the code very deeply however.
I think that vps+neutrino+lnd is a good way to run a watch tower for my other nodes running elsewhere. However, the (C/G)UI for watch towers seems to be pretty bad for understanding whether it works properly. Moreover, how can I test that the watchtower really do its job?
Any ideas or pointers?
How the mined bitcoins come from the coinbase tx into the miner's pocket. I.e. it's said you can get the so called "vanilla coin", however, there anyway few other tx hops to get the reward. How different pools payout your subsidy? Do you need registration? What about subsidy via lightning? How much non-KYC mining really is? (Hosting and ownership of miners, pools, IP addresses, etc.). What about security, miner remote hacks, dos attacks?
Thanks! What about nvme support? I am running my node on the waveshare ups cm4 baseboard with nvme ssd disk. And, any idea how to integrate ina219 to safely shutdown on low batteries?
I am looking for possibilities to migrate from umbrel... However, I like its docker-based design.
Can you, please, explain what are the advantages, goals, differences, ...? What do you solve that others dont?