Social
ETC participants are most active on discord.
Join ETC on Discord
A talented developer referred to as Dexaran funded and formed the Ethereum Commonwealth, the third Ethereum Classic (ETC) development team. Dexaran has been accused of being the DAO attacker. Here are Dexaran’s answers to some questions:
I prefer to stay a pseudonymous person, thus, I can only tell [you] that I live in Russia. I could say that my main direction is “information security and cryptography”. I came into [the] crypto space seeking [the] opportunity to protect myself from the influence of “uncontrollable centralized authorities” (such as Russian government) and the opportunity to resist censorship since this is [extremely] relevant in my country.
I have two main reasons to be here, in [the] ETC community[:]
The first and the most important one is my ideology. Each blockchain project consists of two core parts: a protocol and a history of transactions. Ethereum is a good protocol but Ethereum’s history of transactions was violated by TheDAO hardfork. Ethereum C[l]assic is exactly the same protocol but [with] a clean history of transactions. I’m not against hardforks and I’m not against Ethereum. I am against a violation of someone’s rights after they were given. TheDAO hardfork was exactly the result of [the] “the influence of centralized authorities” which I do not support. As the result, I’m in [the] C[l]assic camp. I can not say that [the] Ethereum Foundation was wrong. I will say that we think different[ly]. Let people who believe in [the] Ethereum Foundation join Ethereum and people who believe in decentralization and censorship resistance join C[l]assic.
The second reason is that I had some ideas of how to improve Ethereum. I thought that it [would] be easier to realize [these] ideas for ETC, but now I see that I was wrong. I was told[,] “Go propose [a] new token standard on Ethereum and if they decide that it is a good idea then we will follow” when I came with a proposal to fix a bug in [the] ERC20 token standard[,] which [has] caused millions of dollars [of] loss already. [The] ETC community is smaller[,] but it is much more conservative[,] and it is harder to achieve an agreement about new features compared to Ethereum.
Some might consider my views radical enough. I’d like to remain anonymous for now, but I think that someday I will deanonymize myself.
There was a slight discrepancy between my vision of what should be done and what the existing teams were offering.
The main one is financial transparency. I believe that it is one of the most important issues for any organization especially in [the] crypto space. We are the only Ethereum C[l]assic development team that [adheres] to a policy of [complete] financial transparency.
There was a proposal to establish a treasury for Ethereum Classic. It could solve [the] problems of financial transparency and [the] lack of [a] governance system. Unfortunately, it was rejected.
The second reason to create a separate team was that none of the existing teams [were] working on solving already-existing problems. Both [of] our teams are working on moving forwards but no one tends to learn from Ethereum’s mistakes and solve any of the already-existing problems or prevent the emergence of Ethereum’s problems. Someone had to solve [the] existing problems, for example [the] loss of money due to [the] token standard flaw or [the] lack of [a] browser extension for accessing Ethereum (C[l]assic) enabled distributed applications. There was MetaMask for Ethereum, but there was no analog that supports the [Classic] chain. MetaMask is a key point for most [dapps] that require user interaction with them. For example[,] you [cannot] create a fully decentralized exchange and let someone use it without MetaMask. That’s why I decided to work in this direction. There are still many problems that have to be solved yet.
The main goal is to develop solutions [for] those problems of the ETC network that no one is willing to solve.
Currently, the most important problems of ETC are:
Address-to-address messaging seems to be the most relevant for me because no one else is working in this direction. It is a great problem of the whole Ethereum ecosystem. I’m planning to create a global smart-contract based messaging service which will allow you to contact [the] owner of any address directly. This will liquidate [the] problem of “I sent my ETC to some ETH address and I don’t know who owns it and how to contact him”.
There are four developers in [the] Ethereum Commonwealth currently. Me and Yohan Graterol are public. The other two are private. Their [G]ithub profiles are available [in the] Ethereum Commonwealth financial report and their contributions are available [in the] Ethereum Commonwealth projects commit history. I don’t know their real names.
It is difficult to manage a large team of developers. As a result, I decided that we will work as a small group, [each] working on a separate task. I’m coordinating everything through our separate Ethereum Commonwealth [G]ithub organization. We communicate through Discord or e-mails. Each task requiremen[t is] described at the corresponding issue [in the] Ethereum Commonwealth Roadmap repository. It serves as [an analog] of [the] ECIPs repository for [the] Ethereum Commonwealth.
Unfortunately, I have not raised enough funding to hire a professional manager to form a separate group to work on more tasks simultaneously.
Ethereum Commonwealth is now open for contributions. Ideally, I see it as a “local treasury” where everyone can define a task and anyone else can propose a solution and receive payment from [the] ETC [Commonwealth] fund if the solution [is] accepted.
We have a decision making process based on token voting. This utilizes blockchain advantages to resolve conflicts of [interest] transparently.
these accusations?
I can only say that I never hacked TheDAO. If I were [T]heDAO hacker then why do I need an ICO to fund my own team?
You can contact me by clicking any of these icons:
I would like to thank IOHK (Input Output Hong Kong) for funding this effort.
This work is licensed under the Creative Commons Attribution ShareAlike 4.0 International License.