ZmnSCPxj [ARCHIVE] on Nostr: š
Original date posted:2018-04-20 š Original message: Good morning Tyler, ...
š
Original date posted:2018-04-20
š Original message:
Good morning Tyler,
Offhand, I am uncertain the first script given in "Technical Proposal" works as a "check proof-of-work" script.
Are the "[]" comments? Or are they pushes of actual data embedded in the SCRIPT? It seems to be comments...?
OP_CheckLockTimeVerify is absolute time, not relative time. Why blockheight 52560 in particular? I believe this was in 2010? Or are you thinking OP_CHECKSEQUENCEVERIFY which imposes a relative timelock?
Locking funds for a time may be enough without pulling in proof-of-work, especially since the Bitcoin blockchain itself is already proof-of-work. See my half-baked ideas for proof-of-mainstake, where locking funds in the mainchain is used as voting rights for correctness of the sidechain, avoiding normal proof-of-stake problems since the stake that backs the chain is on a separate proof-of-work chain.
Regards,
ZmnSCPxj
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20180419/d006b840/attachment.html>
Published at
2023-06-09 12:49:53Event JSON
{
"id": "1cc2473ff2ce86287302b89fe15005b12a4170d95bfa1e1c614f756f814ce18e",
"pubkey": "4505072744a9d3e490af9262bfe38e6ee5338a77177b565b6b37730b63a7b861",
"created_at": 1686314993,
"kind": 1,
"tags": [
[
"e",
"736008c232741b8decdf9f95728faffcd9d7125cd1f2107774595fb5ac55d871",
"",
"root"
],
[
"e",
"65be3ea49f8f5e38ea466863ebc7153fb195f686220285e70ce29b83ee1c8ed2",
"",
"reply"
],
[
"p",
"acfc3f4626878e4c0c434f44ed5c2b8e3d9cc37ce751de945a6d00b781eb5cb0"
]
],
"content": "š
Original date posted:2018-04-20\nš Original message:\nGood morning Tyler,\n\nOffhand, I am uncertain the first script given in \"Technical Proposal\" works as a \"check proof-of-work\" script.\n\nAre the \"[]\" comments? Or are they pushes of actual data embedded in the SCRIPT? It seems to be comments...?\n\nOP_CheckLockTimeVerify is absolute time, not relative time. Why blockheight 52560 in particular? I believe this was in 2010? Or are you thinking OP_CHECKSEQUENCEVERIFY which imposes a relative timelock?\n\nLocking funds for a time may be enough without pulling in proof-of-work, especially since the Bitcoin blockchain itself is already proof-of-work. See my half-baked ideas for proof-of-mainstake, where locking funds in the mainchain is used as voting rights for correctness of the sidechain, avoiding normal proof-of-stake problems since the stake that backs the chain is on a separate proof-of-work chain.\n\nRegards,\nZmnSCPxj\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20180419/d006b840/attachment.html\u003e",
"sig": "91c35b3013e85240107fcbaf90accd9c8f86a3f37e7846ef5e55db3040a75599412433d825a8b06a5925c21e3bd4aa685416cb8f8cc1b7dfcbdafb8d5fa576ad"
}