5 ms·
several solutions may be possible. Simplest would be to delete payloads associated to entries. While the actual data won't be there, it will still be possible t
by jeroiraz 5y ago
several solutions may be possible.
Simplest would be to delete payloads associated to entries. While the actual data won't be there, it will still be possible to build cryptographic proofs.
Then it's possible to prune by physical deleting entire transaction data, which may or not affect proof generation. However, tampering will still be subject to detection.
- jcims 5y agoAre records atomically immutable or is there a set concept such that the lack of mutation can be verified over a set of records?
- jeroiraz 5y agoevery change is made by appending a new transaction. immutability is intrinsic to transaction processing, it can not be disabled. Once a transaction (it may include several entries) is committed, the database state change accordingly and no change into already committed transaction may be done without clients being able to notice it. Note for this to be ensured, clients of immudb should keep track of the latest verified state. official sdks handle this for end-applications