63%

Github

NO

Product readyness

mainnet

Team

N/A

Docs

YES

Audit

YES

Available support

6 channels

Ecosystem

N/A

Last update

N/A
OPENESS

Project Description

Silensio is a privacy-first protocol on Ethereum designed to keep your onchain activity will be more private. SilenMixer : you can swap without a trace. SilenWallet: protects your assets without exposure. SilenPay : enables anonymous payments. SilenMesh : keeps your dApp interactions private. All built for one purpose: full control over your privacy.

Infrastructure links

Team members

N/A

Product launch day

2025-07-17T17:00:00.000Z

Opensource

No

Funding

TECHNOLOGY

Technology type

N/A

Encryption

Zero-Knowledge Proofs (zk-SNARKs), stealth addresses, and end-to-end encryption for onchain messaging. All components are fully onchain and Ethereum-compatible, with no centralized servers or offchain dependencies

License

N/A

Whitepaper

YES

Version

Live on mainnet

Features

N/A

Client diversability

N/A
PRIVACY

Peer to Peer (P2P)

N/A

Know Your Customer (KYC)

NO

Decentralized storage

NO

Default privacy

YES

Revealed recipient

N/A

Revealed sender

N/A

Revealed amount

N/A

Reversability

N/A

Connected Txs

N/A

Data masking

N/A

Tx history

N/A

Privacy Policy

NO

Collected data

Silensio collects no personal data

Data usage

Silensio doesn’t collect or store any user information — so there's nothing to use.

Frontend anonymity

N/A

Compliance

NO

Sign-in requirements

[ "wallet" ]

Identity integrations

N/A
SECURITY

Asset custody

Upgradability

NO – undefined

Social dependency

Silensio is currently governed by a core team using a multisig wallet for key operations and contract management. In the future, governance will gradually transition to a DAO structure, allowing the community to vote on upgrades, fees, and ecosystem decisions using the $SILEN token.

Third-party dependency

YES

Technical dependency

Silensio is built fully onchain and doesn’t store user data, so there’s nothing to leak. A shutdown or exploit would require a critical smart contract vulnerability or compromise of the multisig wallet managing upgrades. We don’t use centralized servers, and there are no admin backdoors.

Audits


ManifestoHow to get involvedGrants / Support UsEventsArticlesTalksPrivacy ExplorerPrivacy use-cases database

All rights not reserved, Creative commons 2024 - Web3Privacy z.s.
Developed by