Disclaimer: These reviews are done as is from what is on display in the master branch of the repo’s made available. This review is not a comment on the overall project, scope, or success thereof. This was done as an educational review by me and any comments in the article are simply my opinion. It should not be used as any comment or advice on the project as a whole.
Review Date: 17/03/2018
==EDIT 19/03/2018 Stuart Farmer (CEO of Lamden) posted a comment below and reached out (very passionate guy), his full comments are below the article but I will extract the key points here;
“ This code is in the middle of a refactor with the basic-demo branch being complete, and is launched here: https://testnet.lamden.io/” Me: So the summary here is that the code I reviewed wasn’t the actual updated and completed code, there is another branch that instead has their code (basic-demo branch), I will have a look at the different branches and update accordingly
“ In terms of Seneca, your understanding is completely flawed. Seneca is a restricted AST module so that you can produce smart contracts using the standard Python APIs.” Me: Will have a look again and update accordingly
“ What you see on Clove is our public repo, so you actually aren’t seeing much of anything there as most of it is private.” Me: So you can ignore the comments below on Clove
“ Admittedly, Flora and Saffron are on ice” Me: So again, you can ignore the comments below on Flora and Saffron.
I have omitted the juicer bits of his comment, you can see he is really passionate about his code and his project, so do read the full comment he made on the article below
==
We start off with a lot of repositories, 20 to be in fact, one thing I noticed is that these repositories are very seldom worked though. Their activity seems minimal, but let’s continue
There are 5 pinned repositories, Cilantro, Clove, Saffron, Flora, and Seneca. Let’s have a look at each
I started looking at Seneca, this is their Smart Contract (actually database) implementation. This is less of a smart contract and more just extended database functionality
And turns out it’s less of an implementation than a pure wrapper around mysql. Other than this single wrapper there is nothing to see in Seneca. So let’s move on to Flora.
After some investigation, Flora is a distributed smart contract package manager for Ethereum that is just sharded over Cassandra.
Nothing has been implemented yet, there are a few basic wrappers for existing software like sqlite, IPFS, or cassandra, but there is nothing here right now. So moving on to Saffron.
Saffron is a private blockchain, so looks like we might have something here.
Interesting, that’s an Ethereum genesis block
And now we now why, because it is just Ethereum. Very little other code here other than a sqlite wrapper that stores solidy contracts in raw form. So done with Saffron, let’s look at Clove
That’s 50% of the entire code, there is nothing here. Done with Clove, let’s go to Cillantro
Some basic code, very blockchain 101 kind of stuff, it just has a zmq listener and then consumes transactions off of the queue and saves in a merkle.
Masternode not really doing anything yet. Nothing else to see here, so done with Cillantro as well.
Conclusion: These are very inactive code bases and it’s very blockchain 101 type of code. The implementations currently provided as well are just wrappers on existing technology so it isn’t offering anything new to the user. There is also a reason why most of these offerings haven’t been implemented and that’s because they aren’t decentralized.
There is nothing to see here or to review really, they are far away from having anything real world available and I don’t see any aspect in which they compete with the current existing players in the market.