-
-
Founder Room locked before private credential verification.
-
Qualifying credential confirmed while the underlying data remains private.
-
Nonqualifying credential returns only an eligibility failure.
Inspiration
People are often asked to reveal far more information than necessary to prove that they qualify for access. A wallet connection can expose balances, collectibles, transaction history, and other activity when the application may only need one simple answer.
One Home Private Passport was inspired by the idea that access should not require surrendering privacy.
What it does
One Home Private Passport allows a person to privately prove that they possess a qualifying credential.
The application reveals only one public result:
Eligibility verified: Yes or No
It does not need to publicly reveal the underlying credential, exact token balance, complete wallet contents, transaction history, or personal identity.
When eligibility is confirmed, the private Founder Room changes from locked to unlocked.
How we are building it
The project is being created during the July 17–19, 2026 Midnight Hackathon in a new public repository.
We are using Midnight and Compact to create the private credential-verification logic. A simple web interface presents the locked room, starts the private verification process, receives the eligibility result, and unlocks the room when the proof succeeds.
Challenges
Our main challenge is turning a complex privacy and blockchain process into an experience that feels simple to someone who may know nothing about wallets, zero-knowledge technology, or Web3.
We are intentionally limiting the project to one clear verification flow so that privacy remains the focus.
Accomplishments
We developed a focused real-world use case for selective disclosure:
- Prove possession of a qualifying credential
- Keep the underlying information private
- Reveal only an eligible or not eligible result
- Use that result to control access to a private digital room
What we learned
Privacy technology is most useful when users do not need to understand every technical detail behind it. The public experience should clearly explain what is being proven, what remains private, and what information the application receives.
What's next
Future versions could support multiple private rooms, different credential requirements, community memberships, event access, age or location requirements, and other forms of selective disclosure without exposing unnecessary personal information.
Built With
- compact
- github
- midnight
