[moralestapia]

I love the idea but I think you (author) need a lot of time/support polishing this. You need a team probably.

Also,

>Superfast proof generation time of around 1000 proofs per second per core.

Does this limit in any way things like read/write perfomance or usability in general?

[jjirsa]

> You need a team probably

The cardinal rule of database development:

http://www.dbms2.com/2013/03/18/dbms-development-marklogic-h...

[moralestapia]

Yup, I do not mean to discourage the authors.

I truly like the project and I have a few things in mind that could make use of it already. (Heck, one of them is pretty much Graviton + a front end).

But I cannot just jump into it as there's some real money involved and no one wants to experiment with that.

I see a bright future for Graviton, once it becomes tested and stable in production environments.

[jopari]

I'm sure the devs would be interested in hearing about your use cases, should you open an issue on the repo, or got in touch via https://dero.io/#contacts-section

(I'm not on the team, just interested in the project.)

[ysleepy]

The proof is just the nodes in the path of the merkle tree to the root. (or all sibling nodes of the path to the root).

So proof "generation" is just fetching the nodes and sending them to the client.

[jopari]

I asked the devs, and apparently "proof generation won't affect general read/write performance". But I guess this is the kind of thing where benchmarks might be useful, and there don't seem to be any public yet.