From 9bb062f29bd4b911cefa066f786bc9020d120d6a Mon Sep 17 00:00:00 2001 From: Sarah Jamie Lewis Date: Thu, 19 Jul 2018 12:59:26 -0700 Subject: [PATCH] fix --- content/metadata-resistant-consensus.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/metadata-resistant-consensus.md b/content/metadata-resistant-consensus.md index a4c4a64b..fc2bcd71 100644 --- a/content/metadata-resistant-consensus.md +++ b/content/metadata-resistant-consensus.md @@ -4,7 +4,7 @@ title = "Metadata Resistant Consensus" tags = ["metadata-resistance", "briar"] +++ -How do group participants in a decentralized, metadata resistant, asynchronous environment come to a consensus on transcript consistency? This is a [https://code.briarproject.org/briar/briar/wikis/Fundamental-Problems](fundamental problem) when designing such systems and one that we need to solve in order to advance the discipline and build usable tools that people can rely on. +How do group participants in a decentralized, metadata resistant, asynchronous environment come to a consensus on transcript consistency? This is a [fundamental problem](https://code.briarproject.org/briar/briar/wikis/Fundamental-Problems) when designing such systems and one that we need to solve in order to advance the discipline and build usable tools that people can rely on. Cwtch presents a partial solution to the problem through the introduction of a concept called "Untrusted Infrastructure". All participants in a group transcript relay their messages through Cwtch Server, the metadata resistant properties of the system mean that, the server gains no information on which to manipulate the transcript *in a targeted fashion* and as such peers can have some assurance that the transcript they ultimately see reflects reality.