Skip to content

fix admonitions and update footer discord #3492

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
roynakakawa merged 1 commit into from
Aug 24, 2026
+3 −3
Merged

fix admonitions and update footer discord #3492

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion docs/website/docusaurus.config.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -310,7 +310,7 @@ const config = {
title: "Community",
items: [
{
label: "Discord (#ask-mithril)",
label: "Discord (#general-mithril)",
href: "https://discord.gg/5kaErDKDRq",
},
{
Expand Down
4 changes: 2 additions & 2 deletions ...versioned_docs/version-maintained/mithril/advanced/mithril-protocol/protocol.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ The protocol has three phases:
2. **Initialization phase** during which Mithril nodes generate and exchange keys
3. **Operations phase** during which nodes sign and aggregate signatures of messages to produce certificates.

:::note Note
:::note[Note]

Note that all three phases require a set of parties (`P` in the paper) to be fixed. During the protocol establishment phase
three important parameters are generated:
Expand Down Expand Up @@ -118,7 +118,7 @@ a quorum of `k` valid signatures must be submitted.

- Each certificate `τ` can be verified as valid for some message, using the known setup parameters to verify the certificate’s proof and then verifying the aggregate signatures and verification keys.

:::note Note
:::note[Note]

Note that if the individual signatures are broadcast to all parties, then each party can independently produce the certificates. In particular, the party that performs aggregation is not required to have any specific knowledge, nor it is assumed to be honest. This means that _any_ third party that has access to the individual signatures can perform the signature aggregation.

Expand Down
Loading