blob: 7bfc86263a72be857267582bea666e5014e26e4a (plain
We got a tip from Grgoire[m] to take a look at
because the FAQ and overall use-case sounded Sigsum related.
Below is a brief summary after navigating their documentation for ~15m.
* Some of their standpoints are similar to Sigsum. For example, they are
pointing out that CT is complex and that the use of Ed25519 is good. 
* Their security goals cannot be satisified by a transparency log. See the
definition of "append-only" and "availability".  They use a backend
called Chronicle  to create a Blakechain . It looks a bit like a
blockchain. Events are chained linearly. It is unclear how consensus or
gossip is solved, but not PoW/PoS/etc.
* The gist of their use-case is to sign messages with different
types of actions.  If these actions become public, good things can
happen. There are applications to WordPress and the PHP world.  A
claimant model + Sigsum can probably be used if the threat model is changed
to work with transparency logs.