📅 Original date posted:2017-06-28
📝 Original message:Hi Luke,
On 6/28/2017 1:20 AM, Luke Dashjr via bitcoin-dev wrote:
> 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 is one of the assumptions which BMM exploits, see #4 of:
http://www.truthcoin.info/blog/blind-merged-mining/#focus
The idea is that this is a safe assumption, because it is already the
case today. If we assume that miners revenue-maximize, and further that
the "bidder" frames his payments in tx-fees, then a willing buyer can
control the next block by simply filling it with high tx-fee spam.
Anyone who is willing to pay the most can already 'get' the next
mainchain block (only, indirectly).
>
>> 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?
Yes, it is unclear, but Chris' email is specific to blind merged mining
(BMM), which is kind of a "sidechains +". So this does not directly
enable any sidechains. Instead, it enables the "+" part.
--Paul
Paul Sztorc [ARCHIVE] /
npub10t…w9uu9
2023-06-07 18:03:41
in reply to nevent1q…a20e
Author Public Key
npub10tqt6wdc2neye0cxwyphtre6n5uccgur94khtqjdry9wxhrvywlq6w9uu9Published at
2023-06-07 18:03:41Event JSON
{
"id": "2c06e62c58d81a448d2f548d301919aa61fb4926e6fb4b3564a674d4129dbdac",
"pubkey": "7ac0bd39b854f24cbf067103758f3a9d398c23832d6d75824d190ae35c6c23be",
"created_at": 1686161021,
"kind": 1,
"tags": [
[
"e",
"ceb90cc04617646a4ed9dd447660214398effadc094de82e24452613b40f4a5e",
"",
"root"
],
[
"e",
"b75f358a797ef64dece7a970524188335e467dc1a312903393860e207d67fbed",
"",
"reply"
],
[
"p",
"ee0fa66772f633411e4432e251cfb15b1c0fe8cd8befd8b0d86eb302402a8b4a"
]
],
"content": "📅 Original date posted:2017-06-28\n📝 Original message:Hi Luke,\n\nOn 6/28/2017 1:20 AM, Luke Dashjr via bitcoin-dev wrote:\n\u003e On Wednesday 28 June 2017 12:37:13 AM Chris Stewart via bitcoin-dev wrote:\n\u003e\u003e BRIBEVERIFY redefines the existing NOP4 opcode. When executed, if the given\n\u003e\u003e critical hash is included at the given vout index in the coinbase\n\u003e\u003e transaction\n\u003e\u003e the script evaluates to true. Otherwise, the script will fail.\n\u003e\u003e\n\u003e\u003e This allows sidechains to be merged mined against\n\u003e\u003e bitcoin without burdening bitcoin miners with extra resource requirements.\n\u003e \n\u003e I don't see how. It seems like the logical outcome from this is \"whoever pays \n\u003e the most gets the next sidechain block\"... That's not particularly useful for \n\u003e merge mining.\n\nThis is one of the assumptions which BMM exploits, see #4 of:\nhttp://www.truthcoin.info/blog/blind-merged-mining/#focus\n\nThe idea is that this is a safe assumption, because it is already the\ncase today. If we assume that miners revenue-maximize, and further that\nthe \"bidder\" frames his payments in tx-fees, then a willing buyer can\ncontrol the next block by simply filling it with high tx-fee spam.\nAnyone who is willing to pay the most can already 'get' the next\nmainchain block (only, indirectly).\n\n\u003e \n\u003e\u003e This enables sidechains in Bitcoin.\n\u003e \n\u003e There are different kinds of sidechains...\n\u003e \n\u003e Federated peg: this already works on Bitcoin.\n\u003e SPV/SNARK peg: this isn't enabled by your BIP.\n\u003e Drivechains: this isn't enabled by your BIP.\n\u003e \n\u003e How do you say this enables any kind of sidechain?\n\nYes, it is unclear, but Chris' email is specific to blind merged mining\n(BMM), which is kind of a \"sidechains +\". So this does not directly\nenable any sidechains. Instead, it enables the \"+\" part.\n\n--Paul",
"sig": "bd83abccbc8b3efe7785efd1c4fe253a44b4b68548eb5755d272abc9584e631834101f054356f8fa9ef8f48595d165a8f6b69e4fe2f82b4f380cf836c56d0193"
}