📅 Original date posted:2019-03-13
📝 Original message:On Fri, Mar 08, 2019 at 03:20:49PM -0500, Matt Corallo via bitcoin-dev wrote:
> To make testing easier, it may make sense to keep the existing block header
> format (and PoW) and instead apply the signature rules to some field in the
> coinbase transaction.
Maybe make the signature be an optional addition to the header, so
that you can have a "light node" that doesn't download/verify sigs
and a full node that does? (So signatures just sign the traditional
80-byte header, and aren't included in the block's tx merkle root, and
the prevHash reflects the hash of the previous block's 80-byte header,
without the signature)
I think you could do that by adding a p2p service bit to say "send me
signatures if you have them / I can send you signatures", which changes
the p2p encoding of the header from (ver, prev, mrkl, time, bits, nonce)
to (ver, prev, mrkl, time, 0, nonce, bits, sig), and change header
processing to ignore headers from nodes that don't have the service
bit set?
If you did this, it might be a good idea to enforce including the previous
block's header signature in the current block's coinbase.
Cheers,
aj
Anthony Towns [ARCHIVE] /
npub17r…x9l2h
2023-06-07 18:16:57
in reply to nevent1q…e3cm
Author Public Key
npub17rld56k4365lfphyd8u8kwuejey5xcazdxptserx03wc4jc9g24stx9l2hPublished at
2023-06-07 18:16:57Event JSON
{
"id": "d7d7dad3aea646d3328b7cea1ac72eedbaac57e7e3fda99d2be72470a0a76a13",
"pubkey": "f0feda6ad58ea9f486e469f87b3b9996494363a26982b864667c5d8acb0542ab",
"created_at": 1686161817,
"kind": 1,
"tags": [
[
"e",
"f0b191175970ba449e04c08697984a76127f709cae9df3689bbc43a1ea87cc8e",
"",
"root"
],
[
"e",
"b2a6be5efe45105ba15bd2f8cbe5a6eac302a08c2f855e36f293013d10e371d0",
"",
"reply"
],
[
"p",
"f61d6f5f7a545bba4c32170f8630a5adeb1b2ad9ecf2881dde3988cfe447b801"
]
],
"content": "📅 Original date posted:2019-03-13\n📝 Original message:On Fri, Mar 08, 2019 at 03:20:49PM -0500, Matt Corallo via bitcoin-dev wrote:\n\u003e To make testing easier, it may make sense to keep the existing block header\n\u003e format (and PoW) and instead apply the signature rules to some field in the\n\u003e coinbase transaction.\n\nMaybe make the signature be an optional addition to the header, so\nthat you can have a \"light node\" that doesn't download/verify sigs\nand a full node that does? (So signatures just sign the traditional\n80-byte header, and aren't included in the block's tx merkle root, and\nthe prevHash reflects the hash of the previous block's 80-byte header,\nwithout the signature)\n\nI think you could do that by adding a p2p service bit to say \"send me\nsignatures if you have them / I can send you signatures\", which changes\nthe p2p encoding of the header from (ver, prev, mrkl, time, bits, nonce)\nto (ver, prev, mrkl, time, 0, nonce, bits, sig), and change header\nprocessing to ignore headers from nodes that don't have the service\nbit set?\n\nIf you did this, it might be a good idea to enforce including the previous\nblock's header signature in the current block's coinbase.\n\nCheers,\naj",
"sig": "04a82b3babf7d2559e89735ab7fc83b0474c4b8311cc00a7c72b41e62d6fa26baea0896c443a846fc9408f71649d1262478ca434f7cce51e7142e560f9be95e5"
}