📅 Original date posted:2017-05-24
📝 Original message:On Wed, May 24, 2017 at 9:50 AM, Tier Nolan <tier.nolan at gmail.com> wrote:
> OP_BRIBE_VERIFY could then operate as follows
>
> <block height> <sidechain_id> <critical hash> OP_BRIBE_VERIFY
>
> This causes the script to fail if
> <block height> does not match the block height, or
> <critical hash> is not the hash for the sidechain with <sidechain_id>, or
> there is no hash for that sidechain in the block's coinbase
>
>
I was thinking more on the process for these transactions.
I assume that the process is
- sidechain miner broadcasts transaction with OP_BRIBE output
- this transaction ends up in the memory pool of miners
- Miners add the transaction to their next block
- Miners add a transaction which spends the output to one of their own
addresses
I think you need an additional rule that OP_BRIBE checks fails unless the
output is locked 100 or more blocks.
The output script would end up something like
IF
<block height> <chain_id> <critical hash> OP_BRIBE_VERIFY
ELSE
<public key> OP_CHECKSIG
ENDIF
This output acts like "anyone can spend" for the one block height.
Otherwise, only the sidechain miner can spend the output.
This allows the sidechain miner to reclaim their coins if the transaction
ends up in a different block.
OP_BRIBE_VERIFY would have an additional rule
The script to fails if
one or more of the transaction outputs start with something other than
the template
<block height> does not match the block height, or
<critical hash> is not the hash for the sidechain with <sidechain_id>, or
there is no hash for that sidechain in the block's coinbase
The template is
<100> OP_CHECKSEQUENCE_VERIFY
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170524/02094798/attachment.html>;
Tier Nolan [ARCHIVE] /
npub1g6…sl5wd
2023-06-07 20:01:31
in reply to nevent1q…v59p
Author Public Key
npub1g6vxlp4e0nyhs2dqxxcryztyf5f5hyuaq93nw4r87zcnv0sdsa0qqsl5wdPublished at
2023-06-07 20:01:31Event JSON
{
"id": "56b3951efaa9c17b88d0c20cb998dbf31a0ab9a0525de03a6667b81171ea8b52",
"pubkey": "46986f86b97cc97829a031b03209644d134b939d0163375467f0b1363e0d875e",
"created_at": 1686160891,
"kind": 1,
"tags": [
[
"e",
"13aad30f7ecbcd37c38d151da19b0bb97f1dbccd9f86dce3131cc3b52530ea2a",
"",
"root"
],
[
"e",
"13d6de871c723b9e500a9389dbec27f9d9b97a0300b0e66a8a85cfa14f50b527",
"",
"reply"
],
[
"p",
"46986f86b97cc97829a031b03209644d134b939d0163375467f0b1363e0d875e"
]
],
"content": "📅 Original date posted:2017-05-24\n📝 Original message:On Wed, May 24, 2017 at 9:50 AM, Tier Nolan \u003ctier.nolan at gmail.com\u003e wrote:\n\n\u003e OP_BRIBE_VERIFY could then operate as follows\n\u003e\n\u003e \u003cblock height\u003e \u003csidechain_id\u003e \u003ccritical hash\u003e OP_BRIBE_VERIFY\n\u003e\n\u003e This causes the script to fail if\n\u003e \u003cblock height\u003e does not match the block height, or\n\u003e \u003ccritical hash\u003e is not the hash for the sidechain with \u003csidechain_id\u003e, or\n\u003e there is no hash for that sidechain in the block's coinbase\n\u003e\n\u003e\nI was thinking more on the process for these transactions.\n\nI assume that the process is\n\n- sidechain miner broadcasts transaction with OP_BRIBE output\n- this transaction ends up in the memory pool of miners\n- Miners add the transaction to their next block\n- Miners add a transaction which spends the output to one of their own\naddresses\n\nI think you need an additional rule that OP_BRIBE checks fails unless the\noutput is locked 100 or more blocks.\n\nThe output script would end up something like\n\nIF\n \u003cblock height\u003e \u003cchain_id\u003e \u003ccritical hash\u003e OP_BRIBE_VERIFY\nELSE\n \u003cpublic key\u003e OP_CHECKSIG\nENDIF\n\nThis output acts like \"anyone can spend\" for the one block height.\nOtherwise, only the sidechain miner can spend the output.\n\nThis allows the sidechain miner to reclaim their coins if the transaction\nends up in a different block.\n\nOP_BRIBE_VERIFY would have an additional rule\n\nThe script to fails if\n one or more of the transaction outputs start with something other than\nthe template\n \u003cblock height\u003e does not match the block height, or\n \u003ccritical hash\u003e is not the hash for the sidechain with \u003csidechain_id\u003e, or\n there is no hash for that sidechain in the block's coinbase\n\nThe template is\n \u003c100\u003e OP_CHECKSEQUENCE_VERIFY\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170524/02094798/attachment.html\u003e",
"sig": "b6fbcb99522af6da9d82a7e747330bbb4873ed8ffd67f3f98eb60ea3eb18054bd93f6bc57c361ba2d2af2d4f5e27abb98888d11f6a1443911c2b244da13951b2"
}