Mike Hearn [ARCHIVE] on Nostr: 📅 Original date posted:2014-06-25 📝 Original message:> > I agree. It would be ...
📅 Original date posted:2014-06-25
📝 Original message:>
> I agree. It would be even sillier to start specifying container formats
> for random one-off "that would be kind of nice, I guess" features.
>
No, it'd be sensible.
Here's a list I drew up a long time ago of features I imagined adding to
the payment protocol:
https://bitcointalk.org/index.php?topic=270055.msg2890147#msg2890147The protocol is there to contain features! There is zero benefit to
slavishly following some religious notion of purity or minimalism here. The
shared resource in question is just varint encoded integers. So, we should
be guided by what will help our users and what will help adoption.
Anyway, Gavin asked me to start handling more BIP 70 stuff a few weeks ago.
I want to use something simple to set up the extensions process more
formally. IMO we need a "living document" version of the payment protocol
with all the different extensions out there folded into it, to simplify
programming tasks and ensure field numbers don't collide.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140625/bc9bd69b/attachment.html>
Published at
2023-06-07 15:23:18Event JSON
{
"id": "746bc33fc7c93009a7681f7f244a7ac46767cff0de79e3a31b81bd6824e3bea3",
"pubkey": "f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2",
"created_at": 1686151398,
"kind": 1,
"tags": [
[
"e",
"9815d098bc7f4989718551eb052a860bc92caef6ef36f2244b5fda76fe0b928a",
"",
"root"
],
[
"e",
"bddc24fb65dc5465b431bac54d3b36321cae35bb1fa0c618f737cefdb9183437",
"",
"reply"
],
[
"p",
"5df7f6f5f6998cb4543e81f7c82eb7c60674e3fc4b9a3ef6e28a50e8e835de2d"
]
],
"content": "📅 Original date posted:2014-06-25\n📝 Original message:\u003e\n\u003e I agree. It would be even sillier to start specifying container formats\n\u003e for random one-off \"that would be kind of nice, I guess\" features.\n\u003e\n\nNo, it'd be sensible.\n\nHere's a list I drew up a long time ago of features I imagined adding to\nthe payment protocol:\n\nhttps://bitcointalk.org/index.php?topic=270055.msg2890147#msg2890147\n\nThe protocol is there to contain features! There is zero benefit to\nslavishly following some religious notion of purity or minimalism here. The\nshared resource in question is just varint encoded integers. So, we should\nbe guided by what will help our users and what will help adoption.\n\nAnyway, Gavin asked me to start handling more BIP 70 stuff a few weeks ago.\nI want to use something simple to set up the extensions process more\nformally. IMO we need a \"living document\" version of the payment protocol\nwith all the different extensions out there folded into it, to simplify\nprogramming tasks and ensure field numbers don't collide.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140625/bc9bd69b/attachment.html\u003e",
"sig": "4707683d5a4aa930302b830ba1c1372332c4ad3663823a2ee8a466272b0bc24f4c0ec34fd32f0715d44186798d683661816c54225bd1aa125ee13bf38788ebff"
}