-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Add "Capacity increases" page with initial signatures #1165
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
Conversation
ACK statement |
ACK Statement. |
ACK statement |
2 similar comments
ACK statement |
ACK statement |
Note if you want your name added to the list, use "ACK statement" |
ACK statement |
ACK statement, this is duly needed. |
ACK statement |
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. |
9492cc1
to
942f98d
Compare
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. |
942f98d
to
6a1d260
Compare
ACK statement |
1 similar comment
ACK statement |
re-ACK statemenet |
re-ACK statement |
[skip ci]
re-ACK statement |
1 similar comment
re-ACK statement |
re-ACK |
ACK statement |
re-ACK statement |
ACK statement |
ACK statement |
UnACK statement -- Marshall Long of FinalHash |
ACK statement |
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. |
ACK statement (Infrequent contributor to Bitcoin Core, contributor to Mastercoin/Omni -- this ACK is on behalf of myself.) |
ACK statement |
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. |
Not contributor but I like segwit and other ideas seem reasonable to me too. Keep up good work and thank you! |
ACK statement |
2 similar comments
ACK statement |
ACK statement |
ACK statement on behalf of Bitcoinpaygate |
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.) |
ACK statement on behalf of Blocktrail |
NBitcoin will be updated as soon as segwit is merged, so .NET bitcoin software will be able to enjoy it very quickly. |
ACK statement |
ACK statement on behalf bitbank Inc. Writing up Japanese translation right now. |
ACK Statement, by ZhangLian.info |
ACK statement |
ACK statement on behalf bw.com. |
ACK statement |
I'm keeping an open mind so have declined to sign on to statements as much could occur in the near future. |
-----BEGIN PGP SIGNED MESSAGE----- ACK statement re: Gregory Maxwell's "Capacity increases for the Bitcoin system" -----BEGIN PGP SIGNATURE----- iQGrBAEBCACVBQJWhb49XhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw |
ACK statement |
-----BEGIN PGP SIGNED MESSAGE----- ACK statement https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-December/011865.html iQEcBAEBCAAGBQJWkYSyAAoJEDzYwH8LXOFOWXMH+waxYK2U/teWOMOH4dPrh2ED |
ACK statement PS. not a contributor, just a Bitcoin user. Developing some product related to Bitcoin. |
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/ |
New signatures should be added here: bitcoin-core/bitcoincore.org#53 I'm going to lock this issue now so nobody accidentally posts here. |
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.