Appendix

This appendix provides additional technical context and learning resources to better understand the architecture, principles, and cryptographic foundations behind Silensio. Whether you're a developer, auditor, researcher, or community contributor, this section is designed to give you clarity and confidence when interacting with Silensio’s stack.

Key Zero-Knowledge Concepts

Understanding how Silensio works begins with understanding the fundamentals of zero-knowledge cryptography. Here are the core concepts we build on:

  • Zero-Knowledge Proof (ZKP) A method to prove something is true without revealing any additional information beyond the truth of the statement itself. Enables privacy-preserving verification in public systems.

  • zk-SNARKs (Succinct Non-Interactive Argument of Knowledge) A compact, efficient proof system requiring a trusted setup, widely used for private transactions and credential verification.

  • zk-STARKs (Scalable Transparent Argument of Knowledge) A more scalable proof system that does not require a trusted setup and is post-quantum secure, useful for massive computation verification.

  • Plonk A universal zk-SNARK that allows proving many types of circuits using a single trusted setup. It balances performance, scalability, and developer usability.

  • Halo2 A recursive SNARK developed by the Electric Coin Company (Zcash). Useful for creating layered or nested proofs, particularly in zkRollups and cross-layer systems.

  • Circom A domain-specific language for writing zk circuits. Circom enables developers to express logic in zero-knowledge form, powering modules like SilenMixer and zkCredentials.

  • zkLogin A method of logging in or verifying access using traditional Web2 accounts (like Google or Twitter) while preserving privacy via zero-knowledge proofs.

  • Verifiable Credentials (VCs) Digital credentials that can be cryptographically verified without revealing private data. VCs allow anonymous proof of facts like age, membership, or qualifications.

References & Technical Resources

Silensio is built on the shoulders of brilliant cryptographers, engineers, and open-source communities. Below are resources that inspired and supported our development:

These references are excellent entry points for contributors who want to audit, extend, or build with Silensio's underlying technology.

Performance & Gas Benchmarks

Silensio continuously evaluates gas efficiency, proof size, and on-chain cost for zk operations. The following benchmarks are based on internal testing using Groth16 and Plonk (subject to network conditions):

Operation
Proof System
Estimated Gas Usage

SilenMixer Deposit

Groth16

290k – 330k gas

SilenMixer Withdrawal

Groth16

370k – 420k gas

zkCredential Verification

Plonk

150k – 200k gas

SilenDex Swap Execution

Halo2

450k – 600k gas

zkLogin Identity Proof

Plonk

180k – 230k gas

Optimization efforts include proof batching, circuit compression, and off-chain proof generation with on-chain verification.

Architecture Diagrams & Flow Maps

Silensio’s architecture is designed to be modular, composable, and zk-native. The following visual diagrams are available for review and download:

  • Silensio Ecosystem Overview Illustrates how SilenWallet, SilenPay, SilenMixer, SilenDex, SilenMesh, and SilenFile interact with each other.

  • Private Payment Flow Shows how zkPayment transactions are routed via relayers, from wallet to merchant.

  • zkCredential Issuance & Verification Details the process of issuing verifiable credentials and using zkProofs to confirm access or roles without identity exposure.

  • Encrypted File Upload & Access (SilenFile) Visualizes encryption on upload, IPFS storage, zk access gate, and decryption upon proof.

  • DAO Treasury Workflow with Privacy Demonstrates how a DAO might manage funds, distribute payroll, and vote anonymously using Silensio tools.

To request SVG/PNG diagrams or contribute to visualization design, please visit the /assets directory or contact the Silensio design core team.

Silensio is committed to transparency—of design, not identity. We believe everyone should be able to verify how privacy works, even when they can’t see the data itself.

If you’re a builder, researcher, or auditor, this appendix is your starting point.

Keep learning. Keep verifying. Keep building—silently.

PreviousConclusion

Last updated