Select
Choose a claim: loan repayment, completed contracts, deadlines met, verification status or an activity threshold.
MASK lets users prove reputation, activity and past behavior without exposing balances, addresses, counterparties or the full wallet behind the proof.
Onchain identity often asks users to reveal far more than the application actually needs. MASK separates the fact being proven from the private data used to prove it.
A full wallet becomes the reputation profile.
Balances, addresses, transaction patterns and counterparties can all become visible even when an app only needs one simple answer.
Only the verified fact is shared.
Users choose the claim they want to prove. MASK generates a proof while the underlying wallet data stays private.
MASK turns private history into reusable, selective proofs.
Choose a claim: loan repayment, completed contracts, deadlines met, verification status or an activity threshold.
The proof engine evaluates the relevant private history without publishing the raw wallet data.
The receiving app checks whether the proof is valid and whether the requested condition was satisfied.
Only the result leaves the private layer — enough to establish trust without revealing everything else.
MASK is designed as a private reputation layer that can move with the user instead of being trapped inside one app.
Use repayment proofs as a trust signal without publishing a complete financial history.
Show a record of completed work and reliable deadlines while keeping client and payment details private.
Prove membership, contribution or activity requirements without revealing unrelated wallet data.
Share portable reputation signals for OTC, P2P and marketplace interactions.
Apps can request only the proof they need instead of asking users to expose their whole wallet.
Reusable proofs can provide structured trust signals for autonomous onchain agents.
MASK separates what an application needs to know from everything it does not.
MASK is a private onchain reputation layer that lets users prove specific facts about their history without revealing their balances, addresses or complete wallet activity.
Examples include loan repayment, completed contracts, meeting deadlines, passing verification, and reaching a required transaction or activity threshold.
No. The concept is based on selective, claim-based reputation: prove the fact needed for a specific context rather than reducing the user to one opaque score.
The app receives the proof result needed for the requested claim. The sensitive underlying wallet data is not part of the shared credential.