📅 Original date posted:2014-06-16
📝 Original message:Oh yes the other thing we need to decide is how to extend BIP70.
Protocol buffers have an extend keyword. But I'm not sure it's what we
really want. IMHO a simpler solution is to have a single "living" version
of the protobuf (where? in a new git repo?) which has all the fields
defined by all the accepted BIPs in a single place. Otherwise the build
process and so on for wallet implementors would get unnecessarily
complicated for no real reason. Also if you wanted to pick a new number for
fields, you'd end up having to read *all* BIPs to figure out what is
available. Simpler seems better.
If we do that then I suggest just using field number 8 or 9 or whatever
rather than 1000. IMHO fields 1000+ should be for private extensions that
are unlikely to collide with other users.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140616/136ce782/attachment.html>;
Mike Hearn [ARCHIVE] /
npub17t…4qgyd
2023-06-07 15:22:43
in reply to nevent1q…fchr
Author Public Key
npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgydPublished at
2023-06-07 15:22:43Event JSON
{
"id": "b18852e10ab2674ed79d11989ae36a161340909abb5e950b67c5ad7473ba0933",
"pubkey": "f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2",
"created_at": 1686151363,
"kind": 1,
"tags": [
[
"e",
"ed0eede28e160c2ef8ddd5af1ee3069fdb0eb5f4c939c1c09a1a5f338c30c628",
"",
"root"
],
[
"e",
"5cd2f0041061cbcb129dee773c397c45ba649e475f20520a9dc8c6d6e76d34f9",
"",
"reply"
],
[
"p",
"f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2"
]
],
"content": "📅 Original date posted:2014-06-16\n📝 Original message:Oh yes the other thing we need to decide is how to extend BIP70.\n\nProtocol buffers have an extend keyword. But I'm not sure it's what we\nreally want. IMHO a simpler solution is to have a single \"living\" version\nof the protobuf (where? in a new git repo?) which has all the fields\ndefined by all the accepted BIPs in a single place. Otherwise the build\nprocess and so on for wallet implementors would get unnecessarily\ncomplicated for no real reason. Also if you wanted to pick a new number for\nfields, you'd end up having to read *all* BIPs to figure out what is\navailable. Simpler seems better.\n\nIf we do that then I suggest just using field number 8 or 9 or whatever\nrather than 1000. IMHO fields 1000+ should be for private extensions that\nare unlikely to collide with other users.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140616/136ce782/attachment.html\u003e",
"sig": "3319d5f818f283332dc9ebd67fc8fa3327fe72e1b738c2c7029fb4a4f57f8c2e79b2444e94f1a16d5f2464a4d2b97245de082fd10df6ccbf36dc7b6f80e432d2"
}