Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add "Capacity increases" page with initial signatures #1165

Merged
merged 15 commits into from Dec 21, 2015
Merged

Conversation

@harding
Copy link
Contributor

@harding harding commented Dec 20, 2015

2015-12-21-145148_652x151_scrot

Link: Capacity increases for the Bitcoin system

If you're a known contributor and want to add your signature, please make a comment saying "ACK statement" and I will add your name as provided on your GitHub profile.

@maaku
Copy link

@maaku maaku commented Dec 20, 2015

ACK statement

@TheBlueMatt
Copy link
Contributor

@TheBlueMatt TheBlueMatt commented Dec 20, 2015

ACK Statement.

@adam3us
Copy link

@adam3us adam3us commented Dec 21, 2015

ACK statement

2 similar comments
@CodeShark
Copy link
Contributor

@CodeShark CodeShark commented Dec 21, 2015

ACK statement

@btcdrak
Copy link
Contributor

@btcdrak btcdrak commented Dec 21, 2015

ACK statement

@maaku
Copy link

@maaku maaku commented Dec 21, 2015

Note if you want your name added to the list, use "ACK statement"

@jonasschnelli
Copy link
Contributor

@jonasschnelli jonasschnelli commented Dec 21, 2015

ACK statement

@laanwj
Copy link
Contributor

@laanwj laanwj commented Dec 21, 2015

ACK statement, this is duly needed.

@kanzure
Copy link
Contributor

@kanzure kanzure commented Dec 21, 2015

ACK statement

@greenaddress
Copy link
Contributor

@greenaddress greenaddress commented Dec 21, 2015

ACK statement

disclaimer: we intend to use/support SW; not sure if the ACK is only valid for 'core' contributors or for any contributor in the space but there you have it.

@harding harding force-pushed the capacity-increases branch from 9492cc1 to 942f98d Dec 21, 2015
@harding
Copy link
Contributor Author

@harding harding commented Dec 21, 2015

Statement has been revised by request to remind readers that work on scalability has been on going. I have not moved any signatures from the old version to the new version, so @maaku will need to post again if they want to add his signature. Sorry for the inconvenience.

2015-12-21-145148_652x151_scrot

@harding harding force-pushed the capacity-increases branch from 942f98d to 6a1d260 Dec 21, 2015
@greenaddress
Copy link
Contributor

@greenaddress greenaddress commented Dec 21, 2015

ACK statement

1 similar comment
@instagibbs
Copy link
Contributor

@instagibbs instagibbs commented Dec 21, 2015

ACK statement

@laanwj
Copy link
Contributor

@laanwj laanwj commented Dec 21, 2015

re-ACK statemenet

@kanzure
Copy link
Contributor

@kanzure kanzure commented Dec 21, 2015

re-ACK statement

@jonasschnelli
Copy link
Contributor

@jonasschnelli jonasschnelli commented Dec 21, 2015

re-ACK statement

1 similar comment
@btcdrak
Copy link
Contributor

@btcdrak btcdrak commented Dec 21, 2015

re-ACK statement

@sipa
Copy link
Contributor

@sipa sipa commented Dec 21, 2015

re-ACK

@morcos
Copy link

@morcos morcos commented Dec 21, 2015

ACK statement

@CodeShark
Copy link
Contributor

@CodeShark CodeShark commented Dec 21, 2015

re-ACK statement

@coblee
Copy link

@coblee coblee commented Dec 21, 2015

ACK statement

@paveljanik
Copy link

@paveljanik paveljanik commented Dec 21, 2015

ACK statement

@FinalHash
Copy link

@FinalHash FinalHash commented Dec 22, 2015

UnACK statement -- Marshall Long of FinalHash
Now i think this is a bad idea. Edited: jan.5 2015

@MarcoFalke
Copy link
Contributor

@MarcoFalke MarcoFalke commented Dec 22, 2015

ACK statement

@obi
Copy link

@obi obi commented Dec 22, 2015

ACK statement - As a UK based bitcoin exchange, Coinfloor feels that the direction outlined in the original statement is in the best interests of Bitcoin and the Bitcoin community in the short, medium and long run.

Although not core contributors, we think it is important to show that there are bitcoin exchanges that are happy to use and support Segregated Witness, Lightning Network, etc.

@dexX7
Copy link
Contributor

@dexX7 dexX7 commented Dec 22, 2015

ACK statement

(Infrequent contributor to Bitcoin Core, contributor to Mastercoin/Omni -- this ACK is on behalf of myself.)

@ghtdak
Copy link

@ghtdak ghtdak commented Dec 22, 2015

ACK statement

@harding
Copy link
Contributor Author

@harding harding commented Dec 22, 2015

Note: if you speak for an organization or product (such as a miner or wallet), you may add that into your ACK (or edit your existing ACK). We will assume by default that you are ACKing only on behalf of yourself.

@Kixunil
Copy link

@Kixunil Kixunil commented Dec 22, 2015

Not contributor but I like segwit and other ideas seem reasonable to me too. Keep up good work and thank you!

@arowser
Copy link

@arowser arowser commented Dec 22, 2015

ACK statement

2 similar comments
@flix1
Copy link

@flix1 flix1 commented Dec 22, 2015

ACK statement

@maraoz
Copy link

@maraoz maraoz commented Dec 22, 2015

ACK statement

@ghost
Copy link

@ghost ghost commented Dec 22, 2015

ACK statement on behalf of Bitcoinpaygate

@voisine
Copy link
Contributor

@voisine voisine commented Dec 22, 2015

ACK statement on behalf of breadwallet

(We intend to implement segwit to launch simultaneously with the roll out. I'd also like to put emphasis on "but they [hard-fork max block size increases] will be critically important long term", from the statement. We must be extremely conservative and keep the network functioning as it has been, with fees incentivized through prevailing relay policy and miner tx selection policy, not hard blocksize limits.)

@rubensayshi
Copy link
Contributor

@rubensayshi rubensayshi commented Dec 22, 2015

ACK statement on behalf of Blocktrail

@NicolasDorier
Copy link
Contributor

@NicolasDorier NicolasDorier commented Dec 23, 2015

NBitcoin will be updated as soon as segwit is merged, so .NET bitcoin software will be able to enjoy it very quickly.

@raulyaoyuan
Copy link

@raulyaoyuan raulyaoyuan commented Dec 23, 2015

ACK statement

@bip32JP
Copy link

@bip32JP bip32JP commented Dec 23, 2015

ACK statement on behalf bitbank Inc.
https://bitcoinbank.co.jp/
(Wallet, exchange, and crypto-news outlet based in Tokyo, JP)

Writing up Japanese translation right now.

@SuperHanZi
Copy link

@SuperHanZi SuperHanZi commented Dec 25, 2015

ACK Statement, by ZhangLian.info

@gabridome
Copy link
Contributor

@gabridome gabridome commented Dec 25, 2015

ACK statement

@raulyaoyuan
Copy link

@raulyaoyuan raulyaoyuan commented Dec 29, 2015

ACK statement on behalf bw.com.

@aawilliams
Copy link

@aawilliams aawilliams commented Dec 30, 2015

ACK statement

@ABISprotocol
Copy link

@ABISprotocol ABISprotocol commented Dec 31, 2015

I'm keeping an open mind so have declined to sign on to statements as much could occur in the near future.

@petertodd
Copy link
Contributor

@petertodd petertodd commented Dec 31, 2015

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

ACK statement re: Gregory Maxwell's "Capacity increases for the Bitcoin system"
post on bitcoin-dev, Dec 7th 2015

-----BEGIN PGP SIGNATURE-----

iQGrBAEBCACVBQJWhb49XhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDAwODE5YTE0NGYyNmZhOGVlNjQ0OTMyYWNhZmFkMGZmYzUw
NDY5NDRkN2ZjNzY4MWIvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQwIXyHOf0udwEtwf9EhT2qYLyudj3MAi8jZKlQzMQ
fgfk83Sswm/PbvjWLJWFlWDCPbacv3hyPjMV/qwkpz4N/4Pnw9WhtSO74MR9DWl0
SsD4KILvC6zXSrHG2wbOhwtZ4TSyoA+eT/6PT9/WWpWq6aSllSdP80bFVzEWKmJa
E4u/H/X4Ogqxvm6IfkUl5m7SZe/6gD5Z2whSCFGovtePlbUzMDfWOTFt1zLQbyyr
5YTlk4fv6RpRMCKSVWQK4zf6XGntu+NDM4c/+dS+IUOmtBlbJunDN99nTVEnSrgP
ICfB/ujoK5U732II7YObnar7QIUVaYInsbwB7qHAZYxSa2DTEzn1YGD7XcScmA==
=CoCP
-----END PGP SIGNATURE-----

@AvatarX001
Copy link

@AvatarX001 AvatarX001 commented Jan 1, 2016

ACK statement

@evoskuil
Copy link
Contributor

@evoskuil evoskuil commented Jan 1, 2016

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

ACK statement

https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-December/011865.html
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBCAAGBQJWkYSyAAoJEDzYwH8LXOFOWXMH+waxYK2U/teWOMOH4dPrh2ED
hoSMqBZYb9jTfENsAJSc9s7bLySg9Fd43d/s1WrtDGoNgT4n/Y0vj1V082TqrA5O
lbihE4XPNs3XQ13THR8sqsmSbfDaPUSar3TgwT36BMRUHEhDTti0n1hjAJD2XNbH
OuizhXcZDpjyfmJbh0ZjK4evjc8fFsGjmIznTO4whqJfvPmF1PoU9bRLCtheht2r
45FDLSbk7u2dGJb5edK+EaW2z9bI6ghciMzoLmGq0g8dg4zX10HTiWhyjitDjWi+
weSWpg7SpM2AJLiRCjpojcp7l+2GrfxBc56p+TPy3T2yb8lTZ7ob5douWDUUE7g=
=ii4a
-----END PGP SIGNATURE-----

@vxst
Copy link

@vxst vxst commented Jan 17, 2016

ACK statement

PS. not a contributor, just a Bitcoin user. Developing some product related to Bitcoin.

@rebroad
Copy link

@rebroad rebroad commented Jan 17, 2016

NACK statement while it focuses on "increases"... if it said "capacity adjustments" then I'd ACK it, as at points in the future it may be that to scale capacity needs to be decreased, and I'd rather the roadmap was open-minded enough to that possibility also.

NACK, also for these reasons: https://chrispacia.wordpress.com/2016/01/11/against-softforks/

@harding
Copy link
Contributor Author

@harding harding commented Jan 20, 2016

New signatures should be added here: bitcoin-core/bitcoincore.org#53

I'm going to lock this issue now so nobody accidentally posts here.

@bitcoin-dot-org bitcoin-dot-org locked and limited conversation to collaborators Jan 20, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

You can’t perform that action at this time.