📅 Original date posted:2012-10-21
📝 Original message:On Sat, Oct 20, 2012 at 7:55 PM, Pieter Wuille <pieter.wuille at gmail.com> wrote:
> In order to make the Bitcoin network rules more well-defined, I'd like
> to propose strict rules about what is acceptable, and which do not
> depend on OpenSSL's implementation.
I strongly support this too. It is good to make the protocol as
well-defined as possible in a self-contained way, ie define all the
parsing and processing without referring to specific current
implementations of other libraries such as OpenSSL.
What always bothered me is that OpenSSL can change their API to accept
new obscure key encodings at some point, or change their
interpretation, and bitcoin will automatically change with it. As
bitcoin happily links against any OpenSSL version you provide it, in
worst case, this can result in forks and unexpected behavior
completely out of our control.
Wladimir
Wladimir [ARCHIVE] /
npub1xq…ymc2p
2023-06-07 12:36:45
in reply to nevent1q…zwjy
Author Public Key
npub1xqshkqv2g7uea4xzqwvmgjcz7u8vfavw6aazs999v0azsv3w7u3qpymc2pPublished at
2023-06-07 12:36:45Event JSON
{
"id": "8218a017bce3c4df2f4c6c01806d6212f43b87ea454d4497985a5d0813a2cc7a",
"pubkey": "30217b018a47b99ed4c20399b44b02f70ec4f58ed77a2814a563fa28322ef722",
"created_at": 1686134205,
"kind": 1,
"tags": [
[
"e",
"e6aa7fbaaa7e7d74d5666350a27b91ddee9c36dc79c3f6a87c5fb48a932331ef",
"",
"root"
],
[
"e",
"0225d7f8f3e6edd56acf3d340d0a70162d998c95533ca9488b5e37b96bfcc07c",
"",
"reply"
],
[
"p",
"4aa6cf9aa5c8e98f401dac603c6a10207509b6a07317676e9d6615f3d7103d73"
]
],
"content": "📅 Original date posted:2012-10-21\n📝 Original message:On Sat, Oct 20, 2012 at 7:55 PM, Pieter Wuille \u003cpieter.wuille at gmail.com\u003e wrote:\n\u003e In order to make the Bitcoin network rules more well-defined, I'd like\n\u003e to propose strict rules about what is acceptable, and which do not\n\u003e depend on OpenSSL's implementation.\n\nI strongly support this too. It is good to make the protocol as\nwell-defined as possible in a self-contained way, ie define all the\nparsing and processing without referring to specific current\nimplementations of other libraries such as OpenSSL.\n\nWhat always bothered me is that OpenSSL can change their API to accept\nnew obscure key encodings at some point, or change their\ninterpretation, and bitcoin will automatically change with it. As\nbitcoin happily links against any OpenSSL version you provide it, in\nworst case, this can result in forks and unexpected behavior\ncompletely out of our control.\n\nWladimir",
"sig": "78ca33e52fa88ca482094988b3fd5c8799004044c235256e112a84bcc6e4e38c63f229fcc597376cd69eba4eb10ee748e08d216018f7ba3774f088381da6e98c"
}