Skip to content
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,20 @@ Mithril is an research project to provide [Stake-based Threshold Multisignatures

This repository aims at hosting the various artefacts produced as part of the _prototyping phase_: Documentation, PoCs and prototype code...

* Mithril Aggregator - the server runtime that creates certified blockchain snapshots using Mithril signatures.
* Mithril Signer - the signer runtime that participates to Mithril signatures.
* Mithril Client - a client runtime that checks and restores blockchain certified snapshots.
* Mithril Common - shared library
* Mithril Core - the Mithril cryptographic library

* [Documentation](./docs)
* [Wiki](https://github.com/input-output-hk/mithril/wiki)

## Build

In a shell with a Cargo toolkit in the PATH, just enter

`make`

It should build the whole project.

7 changes: 1 addition & 6 deletions docs/root/topologies/signer.md
Original file line number Diff line number Diff line change
@@ -1,11 +1,6 @@
# Signer

A Signer is a participant to a Mithril Multisignature. As such, a signer assesses that the signed message is the expected genuine content. In this case, the blockchain snapshot is

* the right one according to the shared snapshot signature
* contains the previous snapshot signature

When he has checked these 3 steps, the Signer computes his Mithril vertification key using the shared content (snapshot digest) and sends it to the Aggregator so it will be used in the multisignature process.
A Signer is a participant to a Mithril Multisignature. As such, a signer assesses that the signed message is the expected genuine content. To do so, the signer computes the digest from the inormation stored on a Cardano node and signs it with his secret key. This signed message with the stake the Signer wants to invest in the signature process is sent to the Aggregator. This way, the Aggegator can assess that the Signer is identified and has the same message. With the Signer Key and the stake information, the Aggregator generates a Verification Key that is used to identify the Signer in the Mithril internal process.
Copy link
Member

@jpraynaud jpraynaud May 20, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A Signer is a participant to a Mithril Multisignature. As such, a signer contributes to signing an expected genuine message. To do so, the signer computes the digest from the information stored on a Cardano node and signs it with his secret key. This signed message is sent to the Aggregator, along with the corresponding won lottery numbers. This way, the Aggregator can assess that the Signer is identified and has signed the same message.


## Topology

Expand Down