Qniwwwerss

1. We are not going to put all business data to open world. We use permissioned blockchain technology, which means that it will only be accessible to a very small circle of people. 2. I think waiting 1 millisecond more, but being sure that your data is protected is better than just having quick responses. It's all a matter of implementation, you can make even the fastest database the slowest by making one mistake in the code.

We can simply remove that identity from list, so it will not be able to read or write. I think we can also change permissions, to restrict reading/writing.

Yes, the most sensitive data will be stored in the blockchain.

What I am planning, is to make not with license, because You may not pay in time and lose all access, but to pay once, teach workers, support if needed, and then let go. Probably, I will think about it more in future, but for now either like this, or with only yearly subscription. Our solution still should solve access restrictions. If You are in the list of "valid" identities - You can read and write the data.

We can make a separation by departments also, however would You mind sharing what exactly is wrong with access restrictions?

Tough situation :D

In the way I see it, there will be x509 certificates representing each worker. Using that, we can define who can read, and who can write the data. Ideally, made it mostly automated. If you are not in the "list" of valid identities - Your request simply won't proceed. That's not enough to hack the password, you should hack the entire system, which makes task quite a lot harder (which I am also considering).