Repository navigation
Conversation
Signed-off-by: Shane Jaroch <chown_tee@proton.me>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
One of the four pillars helping clarify my MSCs -- Complement (also the MSC doc, library code, and homeserver impls).
A lot of small details are undecided, such as the algo name being
lthash16-v1or perhaps ratherlthash16:blake3:v1. The DST and algo name randomize the hash outputs, so no stable wire format exists until naming details are settled.The test suite is currently (10/02/26) basic. It sets a low bar for the plumbing the MSC requires. More coming soon (redactions, soft-fails, C2S api). Some tests may require state DAGs, state hashes, and set reconciliation all become companion MSCs.
In a nutshell, this allows instant state equality checks (both locally with your own database, and over the network). The incremental hashing paradigm may have more general future use (i.e., commutatively hashing CBOR fields -- things beyond and unrelated to state, per se).
The tests will fail on Synapse. Only my Congruent and Sithnapse forks support it today. The tests may even fail to compile (running on my fork doesn't mean running on
upstream/main; could be some import/syntax glitches lurking).Pull Request Checklist
not explicitly signed off yet (as of 10/2/26), due to lack of finalized wire format