📅 Original date posted:2013-10-21
📝 Original message:I believe a better solution would to use a github clone such as gitlab,
which sits on top of the git repo, and allows for custom code around the
BIP process. Potentially one could even build Bitcoin into such a BIP
system. If somebody wants to support a BIP he donates Bitcoins to that
proposal. Somebody who actually implements the BIP can receive some percent
of the bounty, while some percentage goes to the Bitcoin foundation. Via
such a platform one could create assurance contracts to kickstart BIP
developments or Bitcoin extensions (public infrastructure which is not part
of the core, such as opensourced exchanges).
On Mon, Oct 21, 2013 at 9:47 PM, Luke-Jr <luke at dashjr.org> wrote:
> On Monday, October 21, 2013 7:38:37 PM Jean-Paul Kogelman wrote:
> > 1) Should the protocol specification page also be codified into BIP(s)?
>
> Probably wouldn't hurt, but it'd likely need a rewrite in a more modular
> and
> formal form.
>
> > 2) Should the current wiki pages be taken down / forwarded to the git
> repo
> > or be auto updated from the git repo?
>
> Since it's the same format, I'd keep it up there, maybe with a link to the
> git
> repo on the main BIP index wiki page.
>
> > 3) Even though the information in BIP 50 is valuable, should it really be
> > considered a BIP?
>
> It's a hardforking protocol change, so IMO yes.
>
>
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most
> from
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20131021/35473229/attachment.html>;
Benjamin Cordes [ARCHIVE] /
npub1tl…a7saj
2023-06-07 15:07:43
in reply to nevent1q…lhe5
Author Public Key
npub1tljc28ulnxfxmx538t4adqtlqhm68sec9hxq47g4u4clq0s28h7sqa7sajPublished at
2023-06-07 15:07:43Event JSON
{
"id": "c1af472282027d9de664293ec3ea9e6a6d43d407a4cfed388eb6fe23623283bd",
"pubkey": "5fe5851f9f99926d9a913aebd6817f05f7a3c3382dcc0af915e571f03e0a3dfd",
"created_at": 1686150463,
"kind": 1,
"tags": [
[
"e",
"7825845c40e7246842c64e1640ea39dcb04d6d8f430fae7ba311b465db0e4d0f",
"",
"root"
],
[
"e",
"75c743ba8bcd15e1082a4b4985b81fe473ab1b05bd1ef83c28e7dc379069fe6f",
"",
"reply"
],
[
"p",
"5fe5851f9f99926d9a913aebd6817f05f7a3c3382dcc0af915e571f03e0a3dfd"
]
],
"content": "📅 Original date posted:2013-10-21\n📝 Original message:I believe a better solution would to use a github clone such as gitlab,\nwhich sits on top of the git repo, and allows for custom code around the\nBIP process. Potentially one could even build Bitcoin into such a BIP\nsystem. If somebody wants to support a BIP he donates Bitcoins to that\nproposal. Somebody who actually implements the BIP can receive some percent\nof the bounty, while some percentage goes to the Bitcoin foundation. Via\nsuch a platform one could create assurance contracts to kickstart BIP\ndevelopments or Bitcoin extensions (public infrastructure which is not part\nof the core, such as opensourced exchanges).\n\n\nOn Mon, Oct 21, 2013 at 9:47 PM, Luke-Jr \u003cluke at dashjr.org\u003e wrote:\n\n\u003e On Monday, October 21, 2013 7:38:37 PM Jean-Paul Kogelman wrote:\n\u003e \u003e 1) Should the protocol specification page also be codified into BIP(s)?\n\u003e\n\u003e Probably wouldn't hurt, but it'd likely need a rewrite in a more modular\n\u003e and\n\u003e formal form.\n\u003e\n\u003e \u003e 2) Should the current wiki pages be taken down / forwarded to the git\n\u003e repo\n\u003e \u003e or be auto updated from the git repo?\n\u003e\n\u003e Since it's the same format, I'd keep it up there, maybe with a link to the\n\u003e git\n\u003e repo on the main BIP index wiki page.\n\u003e\n\u003e \u003e 3) Even though the information in BIP 50 is valuable, should it really be\n\u003e \u003e considered a BIP?\n\u003e\n\u003e It's a hardforking protocol change, so IMO yes.\n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e October Webinars: Code for Performance\n\u003e Free Intel webinars can help you accelerate application performance.\n\u003e Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most\n\u003e from\n\u003e the latest Intel processors and coprocessors. See abstracts and register \u003e\n\u003e http://pubads.g.doubleclick.net/gampad/clk?id=60135991\u0026iu=/4140/ostg.clktrk\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20131021/35473229/attachment.html\u003e",
"sig": "ed089c76e8ad579bd255a84011b6a26e733180f07e5be6bde16247b2518285e9e1f50c383e6f8913dae5d05d3d323fc83fb87b41447129cc05e46c81e00da6f6"
}