š
Original date posted:2014-10-01
š Original message:-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 1 October 2014 14:34:33 GMT-07:00, Gavin Andresen <gavinandresen at gmail.com> wrote:
>On Wed, Oct 1, 2014 at 5:04 PM, Alan Reiner <etotheipi at gmail.com>
>wrote:
>No, the burner would supply the funding transaction plus the redeeming
>script as the proof-of-burn to whoever needed the proof.
No, the redeemScript has to be provably published to miners for the sacrifice to be valid; if not you can exploit the scheme by hiding the redeemScript and having a big miner mine it at lower-than-face-value cost when it unlocks.
>Only after at least one confirmation, if there was some risk that
>revealing
>the redeeming script would make miners refuse to mine that first
>transaction because they want to get it plus the CHECK TIME BLOCK VERIFY
>"burn"
>transaction.
Yes, you could do that in a followup tx containing the redeemScript in an OP_RETURN output to prove publication. That said as I said to Luke-Jr, the sacrifices need to unlock pretty far into the future, so I don't see miners bothering to do this.
-----BEGIN PGP SIGNATURE-----
Version: APG v1.1.1
iQFQBAEBCAA6BQJULJiDMxxQZXRlciBUb2RkIChsb3cgc2VjdXJpdHkga2V5KSA8
cGV0ZUBwZXRlcnRvZGQub3JnPgAKCRAZnIM7qOfwhTwKCACD+GWzID7Qhn2no1p9
KYNiYlQVNt+DPZY0QB7MujL8riAmyJBliF9zptfjEdvglShoIzonJien/DOCjp9S
Lw2wMvPhtZGgSttJEvlr3wclty6TfWygd4Y+v/MR8TnYC99su7HhiQ1pkqohkklv
RxeF9jXhcJMERzN6wPUyeowfziBAfbWw+M5CwiXRlzLLBWO37eoDTXzUD0Np5Nia
nFxQ7sAsSbLijVpvigh9uIi3/1347VqwMc+0ZsZoZ2AnMICA8Q+XKNHv7DKpChxw
Xa+P532Di34uu8dlG/Z/UwYdENvb15P1yUZ7CEDfqNqrZp0RM7x+XKMA7QPwhuz3
YSBp
=mvKP
-----END PGP SIGNATURE-----
Peter Todd [ARCHIVE] /
npub1m2ā¦a2np2
2023-06-07 15:26:06
in reply to nevent1qā¦7yyr
Author Public Key
npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2Published at
2023-06-07 15:26:06Event JSON
{
"id": "1d7f366538d6525e1c20244e5eb9c7dd6c928d32cb7f9f4a030410b7e8546667",
"pubkey": "daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa",
"created_at": 1686151566,
"kind": 1,
"tags": [
[
"e",
"b0d4dbe43a898155b6750ed1dce6a700ce007fe7f2dce49b1bbfe7e2cca60c4c",
"",
"root"
],
[
"e",
"1107064c88b6026898ea36d6c370bdf4511735b17f194d753d232d28928b4bc5",
"",
"reply"
],
[
"p",
"857f2f78dc1639e711f5ea703a9fc978e22ebd279abdea1861b7daa833512ee4"
]
],
"content": "š
Original date posted:2014-10-01\nš Original message:-----BEGIN PGP SIGNED MESSAGE-----\nHash: SHA256\n\n\n\nOn 1 October 2014 14:34:33 GMT-07:00, Gavin Andresen \u003cgavinandresen at gmail.com\u003e wrote:\n\u003eOn Wed, Oct 1, 2014 at 5:04 PM, Alan Reiner \u003cetotheipi at gmail.com\u003e\n\u003ewrote:\n\u003eNo, the burner would supply the funding transaction plus the redeeming\n\u003escript as the proof-of-burn to whoever needed the proof.\n\nNo, the redeemScript has to be provably published to miners for the sacrifice to be valid; if not you can exploit the scheme by hiding the redeemScript and having a big miner mine it at lower-than-face-value cost when it unlocks.\n\n\u003eOnly after at least one confirmation, if there was some risk that\n\u003erevealing\n\u003ethe redeeming script would make miners refuse to mine that first\n\u003etransaction because they want to get it plus the CHECK TIME BLOCK VERIFY\n\u003e\"burn\"\n\u003etransaction.\n\nYes, you could do that in a followup tx containing the redeemScript in an OP_RETURN output to prove publication. That said as I said to Luke-Jr, the sacrifices need to unlock pretty far into the future, so I don't see miners bothering to do this.\n\n\n\n\n\n-----BEGIN PGP SIGNATURE-----\nVersion: APG v1.1.1\n\niQFQBAEBCAA6BQJULJiDMxxQZXRlciBUb2RkIChsb3cgc2VjdXJpdHkga2V5KSA8\ncGV0ZUBwZXRlcnRvZGQub3JnPgAKCRAZnIM7qOfwhTwKCACD+GWzID7Qhn2no1p9\nKYNiYlQVNt+DPZY0QB7MujL8riAmyJBliF9zptfjEdvglShoIzonJien/DOCjp9S\nLw2wMvPhtZGgSttJEvlr3wclty6TfWygd4Y+v/MR8TnYC99su7HhiQ1pkqohkklv\nRxeF9jXhcJMERzN6wPUyeowfziBAfbWw+M5CwiXRlzLLBWO37eoDTXzUD0Np5Nia\nnFxQ7sAsSbLijVpvigh9uIi3/1347VqwMc+0ZsZoZ2AnMICA8Q+XKNHv7DKpChxw\nXa+P532Di34uu8dlG/Z/UwYdENvb15P1yUZ7CEDfqNqrZp0RM7x+XKMA7QPwhuz3\nYSBp\n=mvKP\n-----END PGP SIGNATURE-----",
"sig": "c5eb1c99cb9fab764e680f295e0fb07846fef33a5155efb1471892ac4cf641e749d6fe045a15d1b421d8de9dd93fcc78a240fb3564c3663c9803d31a25e7066b"
}