1. What are DBCs, how are they different from other types of commitments (OP_RETURN, P2C, S2c)?
- is it that the hardware wallets don’t need to tweak the output now or they already need to tweak the normal Taproot tweaking in the first place, so we’re basically delegating the tweaking complexity that hardware wallets would be facing to the taproot abilities themselves, but in a way if you spend a Taproot output which the end user Tapscript with or without the OP_RETURN inside the tap script, you will need the hardware wallet to tweak the general taproot key?
2. Huffman Merkle tree.
- Can we just duplicate the commitment on both sides of the branch?