You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 6, 2023. It is now read-only.
We really should be using CRDT based replicating message spools for high availability within our mixnet messaging systems. To that end, @leif has written a draft "dspool" specification document which is not specific to mixnets at all but surely applicable. This draft documents needs cleanups and clarifications added.
For full mixnet integration this project may require the addition of other specification documents. An example is the specification of all the cryptographic primitives being used to implement the dspool protocol et cetera.
The text was updated successfully, but these errors were encountered:
Please fill in and correct the missing and ambiguous sections of the dspool specification document which I have labeled with 'XXX'. Replace run-on sentences with proper english paragraphs containing multiple sentences. Also please avoid using generic labels such as:
this replica
that replica
Instead I suggest using more distinct labels to disambiguate.
branch is dspool.0
We really should be using CRDT based replicating message spools for high availability within our mixnet messaging systems. To that end, @leif has written a draft "dspool" specification document which is not specific to mixnets at all but surely applicable. This draft documents needs cleanups and clarifications added.
For full mixnet integration this project may require the addition of other specification documents. An example is the specification of all the cryptographic primitives being used to implement the dspool protocol et cetera.
The text was updated successfully, but these errors were encountered: