Bitcoin : What is the difference between OP_DATASIGVERIFY and plain ol’ multisig?
I admit I don’t really know that much about DSV. When it first came out, I read the description, and kinda understood what it did, but not exactly. I only knew enough to know it’s not something I’m going to use.
I don’t gamble, or do any of the other activities that are commonly listed as being enabled by DSV, so I don’t really care if it gets into the protocol or not, as long as I can opt out of ever using it. It doesn’t seem to alter bitcoin’s economics code, so I’m not going to waste energy being against it.
Lately there has been talk of DSV being used as a way to “replay protect” BCH from “another network” (who are actually just the other half of the same network) that might end up with more hashpower. This changes everything. DSV is no longer the obscure thing that I can safely ignore. Its now something I have to think about and understand because my money is going to go into it in a few days.
My understanding is that OP_DATASIGVERIFY evaluates to true if the message that is supplied has been properly signed by a key specified in the scriptPubKey (made by the sender). This sounds very much like plain ol’ P2SH multisig, which I also know not much about because I have no use for.
Bitcoin is a distributed, worldwide, decentralized digital money. Bitcoins are issued and managed without any central authority.
FindCrypto scans the web for the latest Bitcoin news, so you can find all the latest and breaking news in one convenient location.
Don’t forget to share the post if you love it !