-
Yes. Actually, you can do DAO with Bitcoin, not even with RGB.
When we have Taproot, you can create a DAO with particular voting rights you want to have there (whatever they are), structure it as ta…
-
RGB functionality is not dependent on Taproot deployment, though is already compatible with it.
However, RGB will benefit from Taproot, but it’s benefit is purely bitcoin-based benefit (i.e. indire…
-
I remember watching a talk about miniscript, and the witness malleability issue was discussed (Unfortunately I don't have the link to this talk).
IIRC, It was said that because preventing witness m…
-
Just tried to go step-by-step through your [Tapscript example using Tap](https://github.com/kallewoof/btcdeb/blob/taproot/doc/tapscript-example-with-tap.md). Installed/compiled and started with the fo…
-
Review comment by @gmaxwell: instead of describing the tapscript signature message as a "patch" of the taproot one, describe a common "base signature message" in bip-taproot (in a separate section), a…
-
Review comment by @gmaxwell.
Some of the text can be misinterpreted to mean that empty signatures cause an abort of the script.
(on mobile currently, i'll edit later to show the exact section)
-
According the scripts in the section a simple SHA256 hash is used over concatenated internal public key and tapbranch merkle root, which (as I assume) prevents multiple script commitments. However, a…
-
Discussion group 6 agreed largely with these notes I'd made about this section of the BIP; I would PR but I don't think that's appropriate, since it's kind of central to what the author(s) are writing…
-
Review comment by @gmaxwell.
The text is clear about it having precedence over the 520 byte limit, but not that it also overrides the 1000 stack element limit and other things.
-
A few observations on things that confused workshop particiapnts:
- `OP_RIPEMD160` is an unusual opcode. I think `OP_HASH160` is more commonly used (eg lightning HTLCs use `OP_HASH160`). We should …