Tomas [ARCHIVE] on Nostr: 📅 Original date posted:2015-12-30 📝 Original message:> The specification itself ...
📅 Original date posted:2015-12-30
📝 Original message:> The specification itself looks like an inefficient and bloaty reinvention
> of
> version bits.
The actual assignment of version bits isn't clear from the
specification. Are you saying that any implementation that wants to
propose a change is encouraged to pick a free version bit and use it?
Furthermore, my proposal addresses the danger of forward-incompatible
changes; a hard-fork can no longer occur as every implementation will
agree on the active the set of rules even if it has not implemented
them. This seems to be lacking in the version bits proposal.
Tomas
Published at
2023-06-07 17:47:26Event JSON
{
"id": "1e6463e66c9cdfe24181ab0394205a04d38418d8495ae832314afd1d0c8f0267",
"pubkey": "1c03575343555d1132a621c49466190d680da4a306ba8b992e8b87e267609cdd",
"created_at": 1686160046,
"kind": 1,
"tags": [
[
"e",
"72184028f716f31c551d71b38ec4806452735f1ca31eac4be63f90ad3d90ae28",
"",
"root"
],
[
"e",
"ae79cda2770d124b48f792ec7061a97f140e400e39092ab0dc5a9e2709b83780",
"",
"reply"
],
[
"p",
"5a6d1f44482b67b5b0d30cc1e829b66a251f0dc99448377dbe3c5e0faf6c3803"
]
],
"content": "📅 Original date posted:2015-12-30\n📝 Original message:\u003e The specification itself looks like an inefficient and bloaty reinvention\n\u003e of \n\u003e version bits.\n\nThe actual assignment of version bits isn't clear from the\nspecification. Are you saying that any implementation that wants to\npropose a change is encouraged to pick a free version bit and use it?\n\nFurthermore, my proposal addresses the danger of forward-incompatible\nchanges; a hard-fork can no longer occur as every implementation will\nagree on the active the set of rules even if it has not implemented\nthem. This seems to be lacking in the version bits proposal.\n\nTomas",
"sig": "9b3391b13b28d5f7dcf1e864ed33885d53f10b8585b161445ad9744f14096e9884c7136e2e6fb2372815a05e004512133630069713ac7901545112bd2bb98d16"
}