No, BIP100 is directly against both BIP101 and XT.
No, it is primarily against the small blockians. The 1MBers will be forked away by BIP100 and/or BIP101.
JStolfi explained it very well:
No, because BIP100 starts at 1MB and can stay at 1MB.
BIP101 starts higher so BIP100 would not accept BIP101 blocks.
Garzik himself said he will prefer BIP101 against the 1MB 'solution' of the small blockers.
I said I'd prefer pepsimax to coffee.
So what?
He will not only prefer it, he will support it, and so will the majority of his followers.
That has nothing to do with BIP100
Edit: BIP100 starts at 1MB - that is the BIP.
It can grow if the required consensus in the BIP is met for growth, but it starts at 1MB and will stay 1MB after the 'time' passes when XT fails to reach consensus.
Protocol changes proposed:
1. Hard fork to remove 1MB block size limit.
2. Simultaneously, add a new soft fork limit of 2MB.3. Schedule the hard fork on testnet for September 1, 2015.
4. Schedule the hard fork on bitcoin main chain for December 11, 2015.
5. Default miner block size becomes 1MB (easily changeable by miner at any time, as today).
6. Changing the 2MB limit is accomplished in a manner similar to BIP 34, a oneway lockin upgrade with a 12,000 block (3 month) threshold.
Well I'm reading the BIP itself and it doesn't say that, unless you have a verified update?
jgarzik stated on his twitter account ...
https://twitter.com/jgarzik/status/610494283334860800... that the draft BIP100 v0.8.1 in June, was:
http://gtf.org/garzik/bitcoin/BIP100-blocksizechangeproposal.pdfBIP100 says:
1. Hard fork, to
2. Remove static
1MB block size limit.
3. Simultaneously, add a new floating block size limit, set to
1MB.
4. The historical 32MB limit remains.
5. Schedule the hard fork on testnet for September 1, 2015.
6. Schedule the hard fork on bitcoin main chain for January 11, 2016.
7. Changing the
1MB limit is accomplished in a manner similar to BIP 34, a oneway lockin upgrade with a 12,000 block (3 month) threshold by 90% of the blocks.
8. Limit increase or decrease may not exceed 2x in any one step.
9. Miners vote by encoding ‘BV’+BlockSizeRequestValue into coinbase scriptSig, e.g. “/BV8000000/” to vote for 8M. Votes are evaluated by dropping bottom 20% and top 20%, and then the most common floor (minimum) is chosen.
Which isn't what you posted.
P.S. 2MB would not affect the fact that BIP100 will not support BIP101