Fluree DB – A scalable blockchain database

Blockchain alone doesn't prevent you from modifying data -- just rewrite the entire chain. As an example, Bitcoin only prevents this with proof of work, but only following accumulated difficulty prevents someone from thinking my privately-mined chain is true.

If you want to have integrity control, you can use digital signatures without blockchain.

If all you're trying to fix is making it hard to issue a DELETE statement, then make it easier to set permissions. Which isn't really hard in any mainstream database...

It seems like this is a log, which might work better, although existing RDBMS already have high performance versioning/change tracking.

If I look at the encrypted data before I delete the surrogate key and can see that this data is related to a person x. That’s an identifier. Even if I do delete that afterwards I can still connect that information because I’ve seen the data before. And even if you delete something there might be enough information left to still figure out who that person was and then under the law.

The right to be erased does mean that there shouldn’t be any traces of you ever been there in the first place and the law is pretty clear about it. It’s not the weaker term “deleted”. But I guess there has to a ruling in some court before we know how they interprete this law.

Can you see, at all, from the other perspective? Maybe I annoy the living daylights out of you, but can you also see how you come off as one of those cliche "hater HN commentors"?

If you had 3 worlds to choose from, one where people openly talk about their work which they give away for free to others, or a world where everybody tries to censor, silence, and hate on others for being passionate about their Open Source projects, or a world where, because everybody is so spiteful and nobody is supportive, that everybody is forced to make their software proprietary and charge for it. Which world would you want to be in?

VC funding is another indication/signal of the value I have created. And no, they don't want me to do some stupid "open core" crippleware (like some of my competitors do) or even convert the open source code from MIT/similar to a terrible AGPL/similar license. They want me to create such a core component of infrastructure that we become the defacto standard, like MySQL, Redhat, and others have become.

So no. You have no basis to hate what we are doing, except for your own frustration probably at hate others have given you. Don't pass that along, you are better than that.

So yes, her PhD is in psychology, and she's a visiting research scientist at Stanford's School of Education.

Meanwhile, I work on the computer science side, although am not an academic (although I interact with plenty of academics, MIT, Berkeley, Stanford, and some European schools). The tech talk I linked to explains how the algorithms work (CRDTs), you don't need to be an academic to understand how it works.

The system has been used on Navy warships, as well. If you'd like to talk to the Sergeant Major who deployed the system in production in the industry, shoot me an email and I'll happily connect you. :)

We're not writing our own cryptography, lol, we're using existing libraries based around OpenSSL using industry accepted and standardized algorithms and curves (ECDSA 256, AES 256, ECDH 256, PBKDF, etc.)

So yes, please email me the moment those get broken/cracked and we'll upgrade to whatever new standards are available.