I should clarify: the current proposal already achieves the first part
needed for coin pools: removing some data from the merkle tree (I was
indeed referring to the embedded data, not the taptree).
The thing that is missing is removal of a public key from the taproot
internal key, but as mentioned
Just like we have BIPP38 encrypted keys for singular private keys, I was
wondering if it would be possible to come up with a way to encrypt an extended
private key using reversible encryption.
BIP38 was designed with physical coins in mind, and in particular covers the
cases for lot and sequenc
Hi David,
> A block template is an ordered list of raw transactions that can all be
> included in the next block (with some space reserved for a coinbase
> transaction). A full node can validate those transactions and calculate
> how much fee they pay. A Nostr relay can simply relay almost[1] a
Hi Joost, David,
In my mind, weak blocks' main benefit would be that it improves block relay
by giving PoW-hints on what are in miner's mempools. Non-standard
transactions could even be cached(even if not validated until block
inclusion), which would tolerate more heterogeneity in policies without
