@awemany: I know you looked very careful into the issue of
Satoshi's misattributed commits. When I read your synopsis, I was left with the impression that Greg claimed various commits made by
Satoshi Gavin and Sirius. However, Greg vehemently denies this. But his denial seems to be more of "yes I did this but I did it for a good reason" without actually admitting that he did in fact attribute the commits to his own account.
So my question: is it an indisputable fact that Greg attributed commits of
Satoshi's other people to his own account? (Leaving the rationale for why he might have done this and whether it was right or wrong out of it).
Yes, it is indisputable. Note that we are talking about commits
on github. Due to the nature of git, misattributing git commits would be a much more involved endeavor.
In the github issue report, he himself linked an IRC log admitting as much.
And for example,
here are time-stamped screenshots of the sirius-m and
gavinandresen commits that are mis-attributed. (Time stamps (SHA256 of png) can be verified
here)
A couple further notes:
- These github commit misattributions
had people confused, AFAIR even Mike Hearn
- He mis-attributed Gavin Andresen (His excuse is that he did so many accounts that that one slipped by, by mass-attributing to himself)
- He initially only fixed the issue half-assedly. I only found Gavin's commits after he fixed the sirius-m misattribution and this is all in my bug report linked above. (Curiously, there doesn't appear to be a way for Greg to mass-unattribute commits
) Also curious is that Greg asserts that he doesn't know how that happened - and again that is also in the bug report.
- He asserts that this issue has been reported to github.
If you ask for evidence on this, it is always answered by silence. I believe the explanation is that no such report with github exists, but I cannot prove that. Someone better connected to github might want to research this further.
[doublepost=1484380847,1484379834][/doublepost]Two further things:
1.)
@AdrianX : While looking through my old archives on the github issue to answer's
@Peter R 's question, I came across this
comment from you. I also came across
this comment from the Blockstream CEO (in the same thread,
1.5 years ago!), saying that it is reasonable to raise maxblocksize now (now as in 1.5 years ago) to
not do it at the last minute ...
Funny. Everything has been said a long time ago. As I said, I recently share these worries that you expressed there - more so since owning some hashpower.
2.) Several times in the past, it has been said by various Core supporters and people that 'no controversial changes to the Bitcoin Core code will be merged, only with consensus'. Given that RBF and everything surrounding it is contentious, I do really wonder still about the decision process for controversial
non-consensus code changes within Bitcoin Core.