Bitcoin Forum
November 04, 2024, 10:39:44 PM *
News: Latest Bitcoin Core release: 28.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Bitcoin Improvement Proposals  (Read 2817 times)
Gavin Andresen (OP)
Legendary
*
qt
Offline Offline

Activity: 1652
Merit: 2301


Chief Scientist


View Profile WWW
October 18, 2011, 07:04:04 PM
 #1

Amir started the "get more formal about changes to bitcoin" ball rolling by creating BIP 0001, starting from the Python "PEP" / BitTorrent "BEP" processes.

The idea is to use BIPs for changes that may or will affect every bitcoin implementation (not to use them for proposed changes to one particular implementation).

I'd like to propose some minor changes to the process:

  • I propose that BIPs be wiki pages, with a social convention that the Author gets final word if any editing wars break out.
  • If he's willing, I propose that Amir take the role of BIP editor.
  • I think bitcoin is still too small to have a specialized "bitcoin-ideas" mailing list; I propose that new potential BIPs be discussed either here or on the bitcoin-dev mailing list.


How often do you get the chance to work on a potentially world-changing project?
kokjo
Legendary
*
Offline Offline

Activity: 1050
Merit: 1000

You are WRONG!


View Profile
October 18, 2011, 07:41:54 PM
 #2

+1

"The whole problem with the world is that fools and fanatics are always so certain of themselves and wiser people so full of doubts." -Bertrand Russell
nibor
Sr. Member
****
Offline Offline

Activity: 438
Merit: 291


View Profile
October 18, 2011, 08:41:50 PM
 #3

Gavin,

Could you list some example BIP's to get the ball rolling and ensure everyone understands the sort/scale of changes you were thinking of.

Would:
Add GetHeaders and ability to get 100's at a time to allow faster blockchain download for new clients.

be an example?

Thanks
Gavin Andresen (OP)
Legendary
*
qt
Offline Offline

Activity: 1652
Merit: 2301


Chief Scientist


View Profile WWW
October 18, 2011, 09:43:12 PM
 #4

Example possible BIPs:

URL syntax for bitcoin payments

New OP_EVAL scripting opcode for receiver-specifies-transaction

New bitcoin address format to support OP_EVAL

(I'm actually working on those two)


Informational:

Process for announcing/scheduling/implementing a potentially block-chain-splitting change.

-----------

You can browse through the PEP's at http://www.python.org/dev/peps/  to get some idea of the kinds of things that might be good BIPs; changes to the on-the-wire protocol to make blockchain downloads faster would certainly be appropriate.

How often do you get the chance to work on a potentially world-changing project?
Isosceles
Member
**
Offline Offline

Activity: 71
Merit: 10


View Profile
October 19, 2011, 02:29:14 AM
 #5

+1 for bitcoin URLs

This would definitely improve accessibility for new users. Giving someone a address like btc://152LaGV4xS9SzUTu2yKb6nGwyuxqJEkFZA is more user-friendly and you have the potential for extending the address protocol, eg. btc://MyReadablePublicBTCAddress or btc://username.mtgox for MtGox tokens
finway
Hero Member
*****
Offline Offline

Activity: 714
Merit: 500


View Profile
October 19, 2011, 03:25:03 AM
 #6

Finally.

Stephen Gornick
Legendary
*
Offline Offline

Activity: 2506
Merit: 1010


View Profile
May 13, 2012, 02:03:08 AM
 #7

Which feature additions warrant a BIP and which don't?

I see a lot of pull requests and not very often a BIP, so I'm guessing there's a threshold there somewhere..

 - https://github.com/bitcoin/bitcoin/pulls

Unichange.me

            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █
            █


gmaxwell
Moderator
Legendary
*
expert
Offline Offline

Activity: 4270
Merit: 8805



View Profile WWW
May 13, 2012, 02:24:05 AM
 #8

Which feature additions warrant a BIP and which don't?

Bips are for things with network wide impact or at least are client interface features that would be implemented by multiple clients.

Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!