📅 Original date posted:2017-06-28
📝 Original message:On Wednesday 28 June 2017 12:37:13 AM Chris Stewart via bitcoin-dev wrote:
> BRIBEVERIFY redefines the existing NOP4 opcode. When executed, if the given
> critical hash is included at the given vout index in the coinbase
> transaction
> the script evaluates to true. Otherwise, the script will fail.
>
> This allows sidechains to be merged mined against
> bitcoin without burdening bitcoin miners with extra resource requirements.
I don't see how. It seems like the logical outcome from this is "whoever pays
the most gets the next sidechain block"... That's not particularly useful for
merge mining.
> This enables sidechains in Bitcoin.
There are different kinds of sidechains...
Federated peg: this already works on Bitcoin.
SPV/SNARK peg: this isn't enabled by your BIP.
Drivechains: this isn't enabled by your BIP.
How do you say this enables any kind of sidechain?
> A new block rule is added which requires that the miner's coinbase reward
> be at index 0 in the coinbase transaction's output vector.
>
> It also fixes the witness commitment output to be at index 1 of the
> coinbase transaction's output vector.
This is unacceptable, for reasons Greg already pointed out.
> This document is placed in the public domain.
Note that this is not acceptable for BIPs anymore.
https://github.com/bitcoin/bips/blob/master/bip-0002.mediawiki#BIP_licensing
Luke Dashjr [ARCHIVE] /
npub1tf…rfq0n
2023-06-07 18:03:40
in reply to nevent1q…sh9u
Author Public Key
npub1tfk373zg9dnmtvxnpnq7s2dkdgj37rwfj3yrwld7830qltmv8qps8rfq0nPublished at
2023-06-07 18:03:40Event JSON
{
"id": "8a985cf7f936ed4e45f01f3621c57e9384eede1db4b840556145a16ae3b480c7",
"pubkey": "5a6d1f44482b67b5b0d30cc1e829b66a251f0dc99448377dbe3c5e0faf6c3803",
"created_at": 1686161020,
"kind": 1,
"tags": [
[
"e",
"ceb90cc04617646a4ed9dd447660214398effadc094de82e24452613b40f4a5e",
"",
"root"
],
[
"e",
"d12ff8a60a5c63090146bcc528391407a7042431ebc5b9e41dced2e5ac70df0e",
"",
"reply"
],
[
"p",
"7ac0bd39b854f24cbf067103758f3a9d398c23832d6d75824d190ae35c6c23be"
]
],
"content": "📅 Original date posted:2017-06-28\n📝 Original message:On Wednesday 28 June 2017 12:37:13 AM Chris Stewart via bitcoin-dev wrote:\n\u003e BRIBEVERIFY redefines the existing NOP4 opcode. When executed, if the given\n\u003e critical hash is included at the given vout index in the coinbase\n\u003e transaction\n\u003e the script evaluates to true. Otherwise, the script will fail.\n\u003e \n\u003e This allows sidechains to be merged mined against\n\u003e bitcoin without burdening bitcoin miners with extra resource requirements.\n\nI don't see how. It seems like the logical outcome from this is \"whoever pays \nthe most gets the next sidechain block\"... That's not particularly useful for \nmerge mining.\n\n\u003e This enables sidechains in Bitcoin.\n\nThere are different kinds of sidechains...\n\nFederated peg: this already works on Bitcoin.\nSPV/SNARK peg: this isn't enabled by your BIP.\nDrivechains: this isn't enabled by your BIP.\n\nHow do you say this enables any kind of sidechain?\n\n\u003e A new block rule is added which requires that the miner's coinbase reward\n\u003e be at index 0 in the coinbase transaction's output vector.\n\u003e \n\u003e It also fixes the witness commitment output to be at index 1 of the\n\u003e coinbase transaction's output vector.\n\nThis is unacceptable, for reasons Greg already pointed out.\n\n\u003e This document is placed in the public domain.\n\nNote that this is not acceptable for BIPs anymore.\n\nhttps://github.com/bitcoin/bips/blob/master/bip-0002.mediawiki#BIP_licensing",
"sig": "83a605bbb108beafc6336cd9608352456a8b314ae1e2158d2750357d2c251f3bcf84314129df6a18964577fd6fe1127a44e9fe22d4ec364e151e058bf558dd9f"
}