3 ms·
the hash is cryptographically signed by the server. So whatever state the database is, there must be a proof from the signed state up to the current one. Otherw
by jeroiraz 5y ago
the hash is cryptographically signed by the server. So whatever state the database is, there must be a proof from the signed state up to the current one. Otherwise, the client application should handle this situation with care, as the database may be compromised.
- layer8 5y agoThose signatures don’t prevent or expose or otherwise impede server-side rollbacks. They are thus immaterial to the question raised.
- jeroiraz 5y agois out of the scope of immudb to prevent rollbacks if someone gain access to the filesystem. But even if that happen, immudb sdks will detect such situation when requesting a proof