This week the lead developer of Bitcoin ABC, Amaury Séchet, engaged in a Reddit Ask-Me-Anything (AMA) discussion about the future of Bitcoin Cash (BCH), and the protocol’s future scaling.
An AMA With Amaury Séchet – Lead Developer of Bitcoin ABC
This summer Amaury Séchet (otherwise known as ‘deadalnix’), the lead developer of the Bitcoin ABC client, revealed the team’s intentions at The Future of Bitcoin event to hard fork the Bitcoin network on August 1. Since then Bitcoin Cash has been thriving, and Séchet recently explained his vision for the future of the BCH chain and the ABC client. Many other BCH supporters and developers were involved in the conversation with Séchet including Yours network founder Ryan X Charles, Openbazaar’s Chris Pacia, Bitcoin Classic’s lead developer Thomas Zander and others.
A Configurable Block Size and Finding the Right Fee Structure for Bitcoin Cash
Participants asked Séchet questions concerning the current roadmap for bitcoin cash; such as future block sizes, BCH and BTC compatibility, and protocols like layer two solutions. For instance, the developer of the Electron Cash wallet, Jonald Fyookball asked the ABC developer what he thinks about “algorithm-based block size” solutions. Séchet explains the BCH block size can be configurable using the protocol in the ABC client.”
“I like these proposals,” explains Séchet. “Right now the block size is configurable in ABC, but I would like to have a way to determine this configuration automatically in the future.”
Yours network developer, Ryan X Charles, asks Séchet how the protocol can avoid ‘dust limits’ and fee management. “We [Yours developers] run into dust limits quite easily,” Charles explains regarding the software’s recent implementation of bitcoin cash.
“There is work to be done on fee management,” Séchet responds. “Finding the right fee structure will take time, if one exists at all.”
The next version of ABC will reserve a percentage of the block space for low fee transactions. This will improve over time.
“Because of the way the difficulty adjustment works on the Bitcoin chain, it makes it very unlikely that it would survive being a minority chain,” Séchet states in response to the question. As a result, it is unlikely that this chain will survive if Bitcoin Cash gets a lot of traction. As long as Bitcoin Cash is a minority chain, both chain will continue to live.”
Séchet also gives his opinion about layer one and layer two scaling solutions. The ABC developer reveals he’s not against layer two solutions but believes pushing every issue towards a layer two solution is unrealistic.
“I have nothing against layer 2 per se, but I think some important points have been ignored,” Séchet explains. “First layer 2 can only be as reliable as layer 1.”
When blocks become congested and layer 1 becomes unreliable, layer 2 does so as well. Second, layer 2 will have different characteristics than layer 1 and thinking we’ll push everything into layer 2 is not a realistic roadmap.
Learning from Past Mistakes
Séchet explains a whole lot more about how he envisions the future of bitcoin cash and the ABC client, including BCH anonymity – where he hopes the protocol’s lower fees will allow for cheaper tumbling processes. The ABC developer also gives further opinions about programmers like Gavin Andresen and Jeff Garzik not being “protective enough” to keep the original values of the Bitcoin project in the past.
“It [Bitcoin] ended up being hijacked. We need to learn from this mistake and not reproduce it,” Séchet states.
Maxwell Claims Bitcoin ABC Developer Séchet Plagiarized Bitcoin Core Code
However, there is no shortage of drama around the Bitcoin Cash code base. In a recent Github post, Gregory Maxwell claimed the Bcash developer plagiarized a piece of code. He said that Amaury Séchet (deadalnix) copied the migration to the per-txout UTXO database from the Bitcoin Core project, and did not credit the original authors with it. Instead, he used his name and copied everything verbatim down to the “grammatical oddities,” according to Greg Maxwell.
Do Séchet’s Actions Infringe on a Licensing Agreement?
Furthermore, Maxwell claims Séchet’s actions infringe on an open source licensing agreement and constitute a copyright infringement. He said, “Beyond being fraudulent and sleazy behavior, this action is a violation of the very minimal requirements of the MIT license.”
There is controversy over Maxwell’s position, though. Some commentators believe there is no infringement on the commit, because there is information on the source code within it. Séchet further said the code was “backported” and is “mentioned in the series of commits.”
The schnorr code is backported from https://github.com/deadalnix/schnorr/blob/master/schnorr.d
The per txout db is backported from core and it is mentioned in the series of commits.
Is He Fixing it Faster? Multiple Copyright Violations by Séchet
Maxwell continued his accusations, saying Séchet is also claiming he fixed the issue quicker than Blockstream. Maxwell also mentioned Séchet was been accused of copyright violations before. This is not a first offense. He said, “Amaury SECHET has a well known history of these copyright violating false attribution events. To give a few other examples. I also understand that he is advocating in your private issue tracker to remove all attribution to Bitcoin Core in the codebase from your repository.”
The community has responded to Maxwell’s accusations with dramatic flare. Some users are attacking Maxwell and Blockstream for focusing on trivial issues instead of updating Bitcoin Core. One user, sandakersmann, said, “So you guys are prioritizing this instead of releasing a new version of Bitcoin Core that is not vulnerable? Fits the pattern of backward priorities from you blockstreamers.”
Other users defend Maxwell and Core, saying people like sandakersmann were shifting the goalposts of the original post. They were trying to create a diversion from the serious issue of fraud and copyright infringement. User thijstriemstra responded to sandakersmann:
This has nothing to do with the fact you’re copy/pasting code and stripping out author. This is not done in any opensource project and you’re trying to divert attention away from it. It’s this project that creates unneccessary annoyance and extra work for the maintainers of bitcoin core.
Maxwell Asks Séchet to Discontinue Violating Copyright
Maxwell finished his blog post by asking Séchet to discontinue violating their copyright. He also wants him to correct his repository and credit the actual authors. At press time, Séchet had not responded to the request, other than to say the original code was “backported.”
What do you think about Séchet’s statements, the recent AMA and the accusations brought forward by Core developer Greg Maxwell? Let us know what you think in the comments below.
With additional reporting by Sterlin Lujan.
Images via Shutterstock, Linkedin, and Bitcoin ABC.