AERGO Code Review: Customizable Enterprise Blockchains

Share this article

We had a good look at this one about a month ago, figured it would be worth sharing the AERGO code review around a little and seeing what you guys thought too. Comments are open.

Suddenly everyone talking about the enterprise, that’s not a bad thing, adoption can be top-down or bottom-up and we’ve seen a lot of projects that seem to be middle-out (sorry) with no real plan for how they intend to scale their user base. Interested to see where this one goes.

So what is Aergo saying?

“AERGO is a 4th generation — enterprise ready — blockchain protocol combined with an IT platform that uses advanced technologies.”

That’s inspiring… what do they mean?

So a private chain?

But why? SQL is a query language, meant to be used to interrogate data. This is not a computational language (or scripting language). I would understand SQL for the DLT, but SQL for smart contracts?

Starting with consensus.

Consensus service, with a blockfactory. Looks interesting, let’s dig deeper.

dPoS :’(

Still very skeleton code. A lot of skeleton code, but still a skeleton.

dPoS is straight forward, check current validator set and compare with block. Moving on.

Protobuff.

All the usual blockchain 101 team are here, account, proto, rpc, state (key/value pair), p2p.

Not seeing the SQL, or the “blockchain 4.0” part.

AERGO Code Review Conclusion:

They are keeping close to their roadmap, everything they promised is there. Code is fine, nothing wow, just another blockchain 0.5 for now. Guess September and December will be key.

A lot of code for a pre-ICO company, a lot more substance than I’m used to for where they are in their life cycle. Nothing wow yet, but good so far. I’ll check in on them again in September and December.

Our full AERGO ICO Review is here.

Or chat about it in our Telegram group.

Disclaimer: Crypto Briefing code reviews are performed by auditing what is on display in the master branch of the repo’s made available. This was performed as an educational review and any comments in the article are the opinion of the writer. It is normal for code to change rapidly, hence we timestamp our code reviews so that they present a snapshot at a moment in time. Information contained herein should not be used as any comment or advice on the project as a whole.

Vite Code Review Timestamp: August 3rd 2018

Share this article