Platus FAQ: Private Ethereum Payments

What is Platus?

Platus is a private account layer for Ethereum. It represents private value as encrypted notes and uses zero-knowledge proofs to verify that transactions are valid without revealing their private details.

How does Platus protect payment privacy?

The chain records commitments, nullifiers, and encrypted ciphertexts rather than a plaintext payment history. A proof establishes that an Action follows the protocol rules while the note owner, amount, asset, and recipient remain private. See Notes & Commitments and Post-quantum Note Encryption.

What are stealth addresses used for?

Stealth addresses allow a recipient to receive through fresh, unlinkable addresses derived from their account material. They reduce the repeated-address patterns that make public payment histories easy to cluster. See Stealth Addresses.

Why does Platus use passkeys?

Passkeys use origin-bound WebAuthn credentials protected by a device authenticator. Platus derives account material locally from the passkey workflow, making private-account access closer to a normal sign-in flow than a seed-phrase workflow. See Passkey Architecture.

Can private value interact with on-chain applications?

Platus uses per-application AppAccounts to let shielded value drive an on-chain action. The result can be re-shielded into the private pool after execution. See App Account.

What does post-quantum note encryption mean here?

Platus combines BabyJubJub ECDH with ML-KEM-768 when encrypting note data. The hybrid design avoids relying only on the classical key-agreement component for note confidentiality. See Post-quantum Note Encryption.

Where can I read the full security model?

Start with the Security Model, then review the System Overview and the individual circuit and contract pages for implementation detail.