Selective Disclosure
Selective disclosure verification
Public verification surfaces for committed balance-threshold disclosure without exposing private witnesses or over-claiming compliance.
Disclosure
Verification
Privacy
Wallets
Explorers
Public-safe does not mean unrestricted. Public mode, privacy mode, safe mode, read-only mode, quotas, deployment profile, and gateway policy can still mask or deny behavior.
Public Verification RPCs
Selective disclosure verification is public-safe when callers submit public proof material and never expose private witnesses.
| Method | Category | Public profile behavior | Notes |
|---|
talero_getDisclosureInputs | DiagnosticsSafe | Public-safe diagnostic summary; safe mode and quotas still apply. | privacy |
talero_getDisclosureMembershipProof | DiagnosticsSafe | Public-safe diagnostic summary; safe mode and quotas still apply. | privacy |
talero_verifyDisclosure | DiagnosticsSafe | Public-safe diagnostic summary; safe mode and quotas still apply. | privacy |
W1.1 and W1.2.6 Style Boundary
W1.1-style flows are committed-witness balance-threshold checks. W1.2.6-style flows add a clearer membership proof path for consumers that need to distinguish a committed proof from state membership evidence.
Explorers and wallets should label verified disclosures by claim type, verifier result, source surface, and redaction posture. They should not display raw private data or imply a broader audit conclusion.
Explicit Non-Claims
- Selective disclosure is not proof of reserve.
- It is not KYC and is not an AML/CFT solution by itself.
- It is not a public balance reveal.
- The public node does not provide a public prover.
- Raw balance, private witness, blinding, nonce, salt, and private keys must not be exposed.
Example
talero_verifyDisclosure
{
"jsonrpc": "2.0",
"id": 1,
"method": "talero_verifyDisclosure",
"params": [
{
"claim": "balance_gte",
"proof": "0x..."
}
]
}