Florian JacobWouldn't it be nice if your #Matrix homeserver could garbage-collect all this ancient room history and just keep a small cryptographic proof that everything was alright?
Our newest paper, “Proof-Carrying CRDTs allow Succinct Non-Interactive Byzantine Update Validation” https://dl.acm.org/doi/10.1145/3721473.3722142.
Byzantine-fault tolerant #CRDT ("Conflict-Free Replicated Data Types") are the scientific basis for Matrix, and in this work, CRDTs are combined first-time with non-interactive cryptographic proofs, as they are known from the zero-knowledge field. At the example of Matrix, we evaluate whether that combination is futile. There is still a lot of research to be done to make this a reality in Matrix, but the results were better than we expected:
While making every event carry a proof of authorization is not practical yet, one could add a proof to more seldom things like room upgrades. The article is freely available as Open Acces under CC-BY, and our implementation is licensed MIT. https://github.com/kit-dsn/proof-carrying-crdts
Our newest paper, “Proof-Carrying CRDTs allow Succinct Non-Interactive Byzantine Update Validation” https://dl.acm.org/doi/10.1145/3721473.3722142.
Byzantine-fault tolerant #CRDT ("Conflict-Free Replicated Data Types") are the scientific basis for Matrix, and in this work, CRDTs are combined first-time with non-interactive cryptographic proofs, as they are known from the zero-knowledge field. At the example of Matrix, we evaluate whether that combination is futile. There is still a lot of research to be done to make this a reality in Matrix, but the results were better than we expected:
While making every event carry a proof of authorization is not practical yet, one could add a proof to more seldom things like room upgrades. The article is freely available as Open Acces under CC-BY, and our implementation is licensed MIT. https://github.com/kit-dsn/proof-carrying-crdts