From 2488d7f4febf1a8c61e84847cef5604ef7043c08 Mon Sep 17 00:00:00 2001 From: "dhub-sync[bot]" <145223974+dhub-sync[bot]@users.noreply.github.com> Date: Sun, 23 Jun 2024 18:27:34 +0000 Subject: [PATCH] Changes from dhub --- docs/learn/frequently-asked-questions.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/docs/learn/frequently-asked-questions.md b/docs/learn/frequently-asked-questions.md index c31548b..51f00e8 100644 --- a/docs/learn/frequently-asked-questions.md +++ b/docs/learn/frequently-asked-questions.md @@ -14,12 +14,11 @@ Zano leverages the proven and time-tested cryptographic primitives that were fir Our implementation boils down to: -\ -\- **d/v-CLSAG** **Ring Signatures** that hide the sender. +- **d/v-CLSAG** **Ring Signatures** that hide the sender. -\- **Stealth addresses** that hide the receiver and asset type being transacted. +- **Stealth addresses** that hide the receiver and asset type being transacted. -\- **RingCT** which hides amounts/balances, even when staking thanks to **Zarcanum.** +- **RingCT** which hides amounts/balances, even when staking thanks to **Zarcanum.** This makes sure that **by default,** transaction data being stored on the blockchain is **only** accessible by parties who authorized the transactions, none of it is ever publicly published.