Credential Readiness & Selective Disclosure
How YAMORI holds selective-disclosure credentials and how midnight-credential-gate
gates access on them. This is an independent implementation of credential readiness —
not an official Midnight “Passport” product, integration, or endorsement.
It is explicit about what runs today and what still needs real issuer infrastructure.
The Flow That Works Today
1. Wallet
YAMORI stores credentials locally, signs presentations with BIP44 ed25519, requires biometric/password confirmation per proof.
2. Proof
Wallet creates a selective-disclosure presentation bound to a verifier challenge. Only the predicate (yes/no) is disclosed by default.
3. Verifier
Any DApp or service checks dual signatures, challenge freshness, and predicate satisfaction. Works off-chain today.
4. Contract Gate
midnight-credential-gate Compact module lets any DApp enforce credential checks on chain. Library shipped.
What Is Real vs Future
require_credential(subject, claim), on-chain expiry via blockTimeLt (Compact 0.17)
Honest disclaimers
We make no claim of official Midnight Passport integration or endorsement.
- "Passport" is a direction the Midnight ecosystem is moving toward; this is an independent implementation compatible with that direction.
- Backend today is signed selective disclosure, not zero-knowledge predicates.
- No production issuer integration yet — only a development issuer for testing.
- The Compact contracts have not undergone external security audit.