Metadium Code Review: Identity Protocol
Share this article
Before I get into the Metadium code review this is interesting. It’s another’ Big Data is Evil’ yada yada thing but they actually express the problem well in one part of their website: “Scattered. Controlled. Vulnerable.” Those are three good reasons for them to exist.
I don’t want my data to be scattered to third parties, controlled by centralized authorities, or vulnerable to hackers. Tell me more!
But instead they go off into la-la land.
“Blockchain ecosystem that allows for the expansion of blockchain platform. Metadium aims to accomplish complete-digitalization of real world. Metadium solves the issue of on-line trust identity and formulates firm connections between identities.”
I don’t know what the above means.
“Powered by blockchain, Metadium offers; Enhanced Scalability, Game-Changing Expandability, Exceptional Performance”, aren’t those all the same thing?
These kinds of solutions always intrigue me, because they have a key chicken-egg problem. For integrators to adopt using them, they need a lot of users. For users to use it, they need a lot of integrators. And how much does the average user care about their data?
More importantly, why do these guys need their own blockchain? Just build this on Ethereum. Anyway, let’s jump over to the whitepaper.
That was quick, not a lot going on in there, although I did like the architecture diagrams (even if they again don’t need blockchain).
We have a demo, the token contract, and go-metadium which is a go-ethereum fork.
51 commits ahead of go-ethereum. 202 commits behind go-ethereum. Let’s see what they did in those 51 commits.
Started on Jun 27th.
Good git logs. Added a new type for metadium, in POA for now.
Changed block generation behavior (not bad actually)
Good knowledge of go-ethereum, mostly just devOps changes so far.
Increased blocks to 100MB and increased gas size. I guess this is the “Enchanced Scalability, Game-Changing Expandability, Exceptional Performance”
Governance contract so that admins can add/remove members.
Mostly devops stuff again.
And that’s all we have.
Metadium Code Review Conclusion:
I don’t know, the changes they have made to go-ethereum aren’t inherently bad, but is cloning geth and making some governance contract changes to PoA really the way to go? Wouldn’t a dapp on ethereum make more sense? Or if you have to, run it on POA.
Seems kinda pointless.
You can chat about Metadium 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.
Metadium Code Review Timestamp: August 25th 2018