> led by Adam Back Adam, the only person who's name is mentioned in the body of the bitcoin whitepaper, was happily using Bitcoin long before creating a compa

> led by Adam Back Adam, the only person who's name is mentioned in the body of the bitcoin whitepaper, was happily using Bitcoin long before creating a company to support it. https://bitcointalk.org/index.php?topic=225463.msg2371674#msg2371674 https://bitcointalk.org/index.php?topic=225463.msg2371674#ms... though Adam has never been actively involved with the bitcoin software project itself-- beyond some mailing list discussions and such. Aside, the numbers on the website you linked are randomly generated nonsense. Embarrassingly for its author, their made up numbers which are trying to claim to be astronomical fail to make their point because they're not that high when compared to other highly paying tech companies ( https://drive.google.com/file/d/19ne7ccUdOWewD4rFDQjjnQEJDgsmgFID/view https://drive.google.com/file/d/19ne7ccUdOWewD4rFDQjjnQEJDgs... ). That whole allegation is odd. Blockstream has (had?) a program where a significant part of employee pay was in the form of pre-purchased Bitcoin which vested over time. This was intended to create a significant incentive for employees to see bitcoin's value grow-- specifically to address concerns that somehow Blockstream could create incentives against that when it employed a couple long time contributors. ... it turns out that buying Bitcoin at $450/each was a really good deal, and it panned out well for employees. It worked exactly as advertised, and some anonymous troll is spinning it as some kind of fraud?! Weird. > 8MB Hong Kong Agreement when Adam himself flew to the meeting overnight(as an individual) to attack the agreement, then when a 2MB NYA agreement was finalized and signed by the groups of miners, again the small blockers attacked it in favor of SegWit, Not going along with a proposal you think is bad is not an "attack"-- it's the actualization of your own personal freedom. > The really abusive attack was when those same people removed Gavin Andresen's commit access Gavin's commit access was removed by Wladimir, -- not one of the people associated with Adam or our company. When it was removed it had been completely unused for a year and barely used for several years. Its ultimate removal was triggered by Gavin loudly endorsing an obvious scammer as being Satoshi which was especially concerning given his comments about "handing the repository over" to 'Satoshi'. https://laanwj.github.io/2016/05/06/hostility-scams-and-moving-forward.html https://laanwj.github.io/2016/05/06/hostility-scams-and-movi... Good security practices should have had the access dropped long before then, and he'd been asked by Wladimir to resign them but kept responding that he'd sleep on it. Wladimir had wanted to avoid the drama of revoking them, but once Gavin was loudly endorsing a scammer the threat of poorly maintained access seemed a lot more serious. > he had been leading Bitcoin development alongside Satoshi Wladimir (and the other people you are insulting) were also there back when Satoshi was still active. Even back in 2011 Wladimir was the most active contributor, with two commits for every one by Gavin (348:152). In 2010, Satoshi made 215 commits and Gavin made 35. Leading in a open source collaboration is a complicated question. Gavin was an extremely valued contributor, including valued for his public speaking at a time when many of us were keeping a low profile because we were really concerned that our involvement in Bitcoin might result in legal prosecution. That, however, doesn't mean he was leading in strong sense like you'd apply to the leader of a business. If you look at actual decision making in the project it, once Satoshi was gone it was always an extensive collaboration. This fact is why e.g. some people have falsely accused me of controlling it when I didn't have any particular authority at all, just a history of reasonable insight and persuasive arguments. > and DDoS Bitcoin nodes got DOS attacked with some regularity in the past by people trying to interfere with block propagation to cause competing blocks to get orphaned (and still do, though less often now-- because we implemented countermeasures to make those attacks much less effective). There is no evidence that anyone saw any DOS attacks other than those. None of the people I know would have bothered not expected a DOS attack to do anything: the system is designed to be designed to resist DOS attacks. The falsity of those "nodes" was also demonstrated by their near overnight disappearance once the pumping of competing altcoins stopped... > we've come a long way with optimizing transactions I don't believe that bitcoin abc has deployed any scalablity improvement not previously existing in Bitcoin. The primary one in it over the original p2p protocol, compact blocks, was designed by myself...