r/bitcoinxt • u/DevonGulshan • Nov 24 '15
r/bitcoinxt • u/Rabbit_row • Jan 13 '16
Maxwell does not care about transaction fees because he made tens of millions shorting during the 2008 subprime mortgage crisis. We need Bitcoin for the 99% not the 1%!
r/bitcoinxt • u/transistorblister • Dec 07 '15
Gregory Maxwell spends 2 minutes explaining his position on Youtube
r/bitcoinxt • u/DanielWilc • Dec 03 '15
Why Peter Rs Fee Market Wont Work
Hi guys, I have some differing views and wanted to discuss them here. Please don't down-vote this into oblivion, as that is itself a form of censorship that will prevent discussion.
At the first Scaling Bitcoin conference Peter R presented his ideas on why a fee market would exist without a block size limit. You can see his presentation here: https://www.youtube.com/watch?v=ad0Pjj_ms2k.
He is wrong and I will explain why.
Peter says that a non-zero supply curve exists because increasing block size increases cost to miners due to higher orphan rate. I have also heard a variation of this argument with increasing block size being constrained by hardware resources, internet bandwidth etc.
Theoretically these arguments are correct, practically they are not.
The effect of block size on these costs is almost negligible.
The supply curve is not exactly flat but very close to it. It is practically (if not theoretically) flat and at zero. In reality a fee market will not form.
As an example, we have a supply and demand curve for oxygen but there is no real market for it because its impractical for something so cheap with such a flat and low curve. Yes, Oxygen does have a supply curve because humans are capable of increasing its supply at an increasing cost.
When curves meet at extremes the market breaks down.
No block size limit would simply result in huge blocks and a much more centralised node network, that can be easier influenced by governments.
But lets ignore all of the above for a second.
Peter also says we need at least 2 mining pools, for a market to form based on the orphan rate cost. Of course you hardly have much of a market with 2 pools, or 5-10 pools. That is what we have now. You can not have a real efficient market for orphan rates with only a few participants at one end.
Furthermore, orphan rate is a result of block propagation and can be decreased by moving pools closer together geographically. That is obviously very negative if we are trying to prevent mining centralisation.
To quote Gregory Maxwell:
"How could you have written at such length and complexity but ignoring the simple expident miners have of simply centeralizing their operation around larger pools to lower their costs– an activity they previously performed, in practice, not just theory (which was walked back by handing them more efficient relay mechenisms) and which is simple, easy, and which reduces those marginal costs to 0 at the limit (e.g. all miners served off a particular host) — after I specifically called you out on this previously? Doubly so when your analysis gives provides a framework for analyizing the profitibility of moving from one point on that income tradeoff graph to another (e.g. the lost income from failing to centeralize)…."
You might ask, why can a fee market form with fixed block-size supply then? After-all we still have only a small number of pools? The reason is, that in Peter’s model the cost variable is due to the differing orphan rate between pools. That is not true for fixed block size. There is no variable for the supply curve. Thats why the supply curve is a straight vertical line.
Finally Peter refers to the block size limit as some ‘artificial centrally controlled limit’.
He does raise a good and important point here. In the situation of a fee-market based on limited block size, what would be the mechanism for changing the block-size limit and who would have control? The solutions from Peter R or others did not satisfy me personally. It is a valid question though. Are we to have a hard-fork each time we decide the fees are getting too high or low? Do we implement code to allow a semi-centralised authority to decide? These do not seem like good solutions.
To say it is a centrally controlled limit is wrong however. To change the limit needs the consensus of the network i.e. nodes. Core developers have some limited ability to influence people, but ultimately they can not force through any change by themselves, they need the networks tacit agreement. Nobody and everybody controls the limit. Its control is decentralised (and therefore hard to change).
Finally there is nothing exceptionally artificial about the limit. Bitcoin itself is artificial, the 21 million limit is also an arbitrary artificial limit. Humans set the parameters of Bitcoin, its supply and its block size limit. The problem and difference is the 21 million limit does not have to change. Block size limit might have to, how will that be decided?
http://danielwilczynski.com/2015/11/30/why-peter-rs-fee-market-wont-work/
r/bitcoinxt • u/piratacoins • Jan 06 '16
Blockstream is a SCAM and the core devs have been bought!
Just wanted to point that out. I know it's obvious to probably everyone here, but it should be much more well known throughout the bitcoin community.
If you think about it, any figureheads can be bought or otherwise compromised. So they should thank us for ignoring them. Let's scale this coin up!
r/bitcoinxt • u/BrokenStream • Dec 02 '15
Bitcoin needs people who invent _SOLUTIONS_ not just cry about problems. Gavin hints at an answer: Eject Maxwell from Core.
np.reddit.comr/bitcoinxt • u/ccaorr • Dec 19 '15
Bitcoin without Blockstream? More likely than you think. BIP-202 gets landslide support in Bitcoin Core!
r/bitcoinxt • u/41256d • Dec 14 '15
Isn't it possible to use the Sherman Act and "United States versus Microsoft" as a precedent and sue Blockstream and their investors for the vaporware?
Section 2 of the Sherman Act provides specific terms against "Attempted Monopolization"...
Attempted Monopolization
Section 2 also proscribes "attempt[s] to monopolize." Establishing attempted monopolization requires proof "(1) that the defendant has engaged in predatory or anticompetitive conduct with (2) a specific intent to monopolize and (3) a dangerous probability of achieving monopoly power."(9) It is "not necessary to show that success rewarded [the] attempt to monopolize;"(10) rather, "when that intent and the consequent dangerous probability exist, this statute, like many others and like the common law in some cases, directs itself against the dangerous probability as well as against the completed result."(11)
Attempted monopolization requires (1) anticompetitive conduct, (2) a specific intent to monopolize, and (3) a dangerous probability of achieving monopoly power.
By i) hiring all non-aligned-to-Satoshi's-principles "core" developers ii) pivoting Bitcoin's payment model, iii) censoring dissent in the highest discussion forums, and iv) the widespread promise of vaporware, it seems that a federal case can be built against blockstream for attempted monopolization of bitcoin payments through their channels.
...moreover, in USA vs. Microsoft, the Justice Dept. went precisely against the use of "vaporware" as a deterrence tactic:
IANAL. I have just been thinking that this sad outcome should not be discarded outright; and that we (investors and businesses invested in Satoshi's payment vision) may want to keep this discussion on the table. Since Blockstream's investors and developers only understand money, perhaps that's where we as btc investors should hold them to account. I would certainly pledge something like $50,000usd to help bring up the case.
5500+ unconfirmed transactions as of this writing.
r/bitcoinxt • u/Spartan_174849 • Sep 28 '15
Why wasn't BIP101 demonstrated to work yet?
Why is it hard to get about 50 people running BIP101coin from dif 0 and test it with various loads of automated transactions?
I'm sure a lot of people would change their minds about xt/big blocks if it was demonstrated to work.
r/bitcoinxt • u/distradaklutz • Oct 06 '15
/r/bitcoin censored: "Gregory Maxwell is one of the poisonous "people" Jeff Garzik is talking about. How could we cleanse BitCoin of his influence?"
r/bitcoinxt • u/aminok • Aug 29 '15
The anti-Blockstream reductionism here is not good for Bitcoin.
Blockstream is developing the most promising technologies in the Bitcoin space right now, and is doing it all open source. Their primary work is in developing infrastructure for Bitcoin, that anyone else can freely use. These are extensions that hold the potential to revolutionize Bitcoin.
Please don't let 10 day old throwaway accounts polarize this debate with their Blockstream vs Mike Hearn reductionism. They're probably playing both sides against each other. Be critical.
r/bitcoinxt • u/Methylfenidaat • Aug 19 '15
Blacklist in BitcoinXT is a big NO.
So, I did switch one node already but I'm going to revert that turn. I'm serious in favor for bigger blocks, but I can not accept a blacklist in the source code.
r/bitcoinxt • u/arruah • Aug 28 '15
We have lost the majority miners. Now KNC. They choose BIP100. I propose to raise hashnest.com power.
r/bitcoinxt • u/ThePiachu • Aug 02 '16
Contentious Bitcoin fork WILL create a split
r/bitcoinxt • u/thetimpotter • Nov 04 '15
I forked XT and removed the block size limit.
r/bitcoinxt • u/BIP-101 • Dec 29 '15
@Gavin: Why not propose a new compromise BIP?
I think it has become clear that many stakeholders (for whatever reasons) are opposed to BIP 101, especially miners (see here).
How about you propose a new BIP which is essentially the same as BIP 101 only with different parameters (so little and only trivial code changes)?
For example: 2 MB now, double every 2 years but only for 8 years. This gives:
2016: 2 MB
2018: 4 MB
2020: 8 MB
2022: 16 MB
2024: 32 MB
I think since many support 2-4-8 this could get widespread consensus.
Yes, this is a compromise and a slippery slope, however it is better than the current divide and would show a sign of good will. Once people realize that block size is not as big of an issue and hard forks are ok to do, in 8 years it will be very simple to increase further or even abolish the block size limit.
Also, do not forget that together with Segregated Witness, the actual block sizes are larger.
Paging /u/gavinandresen
r/bitcoinxt • u/nullc • Feb 01 '16
Current Bitcoin XT contains a network splitting bug. Rather than behaving responsibly, the maintainers of BitcoinXT are smearing the developers of Bitcoin Core (whom had nothing to do with their bug).
Recently XT integrated a change to how it fetches blocks to make "creative use" of the filteredblock functionality to send blocks using less space which they are calling "thinblocks".
This was originally proposed and implemented by Pieter Wuille in ~late 2012 but the idea was not pursued because it was slow, inefficient, and complex to get right. More recently Mike Hearn attempted a new implementation.
The way it is intended to work in XT is that when a block shows up, it is fetched with the BIP37 filtered block functionality using a match-everything filter. This causes it to send a list of all transactions and the transactions themselves, but-- hopefully-- skip the transactions that had already been sent, thus saving bandwidth.
Because of how the Bitcoin protocol works, once a transaction is in a block it cannot reliably be by itself fetched from a peer. The Bitcoin protocol provides no random access to the blockchain (as this would require resource intensive additional indexes). This is why BIP37 has any functionality to send transactions themselves at all. I say "not reliably" because there is a limited memory for recently advertised transactions which still can be fetched.
Bitcoin XT has mempool space management that makes it forget unconfirmed transactions. This interacts fatally with the thinblocks behavior, since peers will remember that a peer previously knew about transactions that peer has since forgotten (due to eviction) and never send them; causing block reconstruction to fail.
Unable to receive the block, a mining XT node would be forced to go and create a ledger fork.
In Bitcoin Core 0.12 we switched the datastructure that remembers what has already been received from or sent to other peers to a probabilistic one in order to have a longer memory but use less space. Because there could be false positives, we removed the already sent filtering from the filteredblock as it is imperative for existing SPV wallets to not withhold transactions there (as otherwise they'll never learn from them there), and required by the BIP37 specification not withhold.
A side effect of this is that it cures the above described network splitting bug-- but it also kills all of the space savings. For reasons unclear to me, XT cherry-picked this change out of core and included it in their thinblocks patch. This is very surprising to me because the change was very clearly described. They then merged that thinblocks patch-- even though it would have no space savings when speaking to another copy of itself, which indicates that they merged it without even enough tests to show it helped.
Today they began posting claiming that Core 'sabotaged' their project; which caused me to look at what they were actually doing in order to defend my reputation. After a quick review of their approach I realized that their design was fundamentally flawed and would fork the network, and was actually protected by the code they took from core that they were complaining about. They responded that they'd "noticed" that sometimes it didn't get all the transactions it needed and were working on making it fetch them-- apparently unaware that they cannot reliably fetch them (they can only fetch ones that had been 'recently' offered).
Avoiding problems like this takes an incredible amount of review and testing even by the most experienced developers. If the testing isn't even enough to detect that two copies of the same node don't even get any space savings, it surely isn't going to detect a network splitting effect that only happens due to mempool eviction... or god knows whatever other bugs lurk inside.
To me, going on the attack against Bitcoin Core for the regular maintenance of it's own software, while paying little attention do the deficient testing that failed to notice that the functionality didn't function is a really significant and objective warning sign that XT's developers do not currently have the resources or disposition required to maintain safe Bitcoin node software. The critical result of that inadequate testing was a failure to discover network forking bug. Implicitly depending on review from contributors to another project which they attack and slander is not a realistic and professional development practice.
r/bitcoinxt • u/ProHashing • Dec 11 '15
Nakamoto is the only person who can save bitcoin
r/bitcoinxt • u/fastpanther • Jun 30 '17
Rare Silver Plated Bitcoin Coin Collectible
r/bitcoinxt • u/BitcoinXPostBot • Sep 01 '15
Crunchbase investigation reveals BIP-101 supporters are nearly all linked to the same VC's.
r/bitcoinxt • u/eragmus • Dec 19 '15
BIP 109: Efficient block relay format & Mempool 'soft' consensus ("A backwards-compatible block relay system to scale to 100 TPS w/ current tech. Minimizes miner & p2p network consensus lag, with: miner tx commitments & use of lower difficulty blocks, i.e. soft blocks / weak blocks / near blocks.")
r/bitcoinxt • u/fustookman • Nov 06 '15
It's time to fight Blockstream and Adam Back
Just like Ghash.io were hostile, now it's Blockstream and Adam Back.
bitcoin must remain free and decentralized.
Blockstream is anti bitcoin.
Edit: My proposal is to do exactly what we did to Ghash.IO:
Shout out loud in the social networks that bitcoin is about to be stolen.
r/bitcoinxt • u/seweso • Nov 19 '15