<p>We ensure that the Aggregator does not modify the data of the snapshots by verifying the signature. The Mithril team will soon release documentation where this type of information will be clearer.</p>
<p>But to answer your question, the snapshots will be signed by Mithril nodes, and distributed by the aggregators as you said. However, the role of the aggregator is only to serve as a distributor, and we don't need to trust that the data shared is correct. That's what the signature is for. A Mithril client downloads the certificate (which cannot be forged by the aggregator) and the snapshot. Then, it verifies that the snapshot is signed (and therefore validated) by the Mithril certificate. This guarantees that the snapshot received by the client is the one signed by the Mithril nodes, and has not been tampered by the Aggregator. If the signature validates, then the Mithril client can use that snapshot to spin the wallet/node.</p>
<p>[EDIT]: The Mithril project is finally public. You can find more information in the proof of concept documentation:</p>
<p><a href="https://mithril.network/doc/" rel="nofollow noreferrer">https://mithril.network/doc/</a></p>

CC BY-SA 4.0
2022-08-01T11:47:46.190Z
2022-08-30T06:44:42.730Z
2022-08-30T06:44:42.730Z
azinig
<p>Mithril is a mechanism for developing lightweight wallets by storing blockchain snapshots on Mithril Aggregator. We can authenticate these snapshots using Multi Signature. But after the snapshot is signed, it will be stored by Mithril Aggregator. How to ensure Mithril Aggregator does not modify the data of these snapshots?</p>

<wallet><stake-pool><multisig><signing-key-file><message-signing>
Can Mithril Aggregators change snapshot after signing?
# Can Mithril Aggregators change snapshot after signing?

(Asked by: username_0 on 2022-07-31)

Mithril is a mechanism for developing lightweight wallets by storing blockchain snapshots on Mithril Aggregator. We can authenticate these snapshots using Multi Signature. But after the snapshot is signed, it will be stored by Mithril Aggregator. How to ensure Mithril Aggregator does not modify the data of these snapshots?

**Tags:** wallet, stake-pool, multisig, signing-key-file, message-signing

---

## 1 answers

### Answer by username_1 on 2022-08-01. Score: 0

We ensure that the Aggregator does not modify the data of the snapshots by verifying the signature. The Mithril team will soon release documentation where this type of information will be clearer.

But to answer your question, the snapshots will be signed by Mithril nodes, and distributed by the aggregators as you said. However, the role of the aggregator is only to serve as a distributor, and we don't need to trust that the data shared is correct. That's what the signature is for. A Mithril client downloads the certificate (which cannot be forged by the aggregator) and the snapshot. Then, it verifies that the snapshot is signed (and therefore validated) by the Mithril certificate. This guarantees that the snapshot received by the client is the one signed by the Mithril nodes, and has not been tampered by the Aggregator. If the signature validates, then the Mithril client can use that snapshot to spin the wallet/node.

[EDIT]: The Mithril project is finally public. You can find more information in the proof of concept documentation:

<https://mithril.network/doc/>


---

