Dear æternity crypto community,

It has been both exciting and stressful weeks since the æternity campaign ended. A lot of work has been done to make æternity a reality and the best is yet to come.

Scaling an organization is tricky. Most startups fail because of this reason. It is easy to coordinate when you have 5 people on the team, but a group-size above 10 easily becomes chaotic. By all means, æternity has been very efficient in handling operations so far. Scaling these operations and restructuring the team has been quite difficult during the past weeks. On a good note, the tech team is growing well and once we have thoroughly tested the new setup, we will announce the new hires.

Many of you have been approaching me directly, and yes, I have not been able to follow up on everything. I would like to apologize for this. If you have any important questions or comments, please reach out to someone from the æternity team, they are doing a great job of following up with you.

Unlike most of the other Ethereum ERC20 token campaigns, we chose to collect not just ETH but also BTC. Fundamentally, this makes the process more simple, but at the same time the aftermath becomes more complex.

During the campaign following issues have appeared:

Phase 1 Issues

In the morning of the official phase 1 launch, we were doing some last checks with testing addresses on wallet.aeternity.com, while this domain was kept secret. Unfortunately, one of our webdevs linked from the banner on the website to wallet.aeternity.com and several people sent to these test addresses.

People who sent to these test addresses will receive the correct amount of AE tokens, covered by æternity’s 17% pre-allocation.

Phase 2 Issues

We experienced some technical issues with the campaign wallet. There was a caching issue causing a confusion for people who chose BTC. Luckily no BTC was lost.

The price API (CryptoCompare.com), which was used to calculate the CHF amount, delivered for one day 0 (zero) CHF for ETH and BTC contributions. We needed to re-implement the back-end during phase 2, which also caused a lot of confusion. Read more about this issue at our blog.

Because of the issues we had far more work then expected. Big thanks goes to the support team.