The problem Marriaged solves

Verifying sensitive personal attributes—such as marital status or identity—remains a critical privacy challenge. Existing systems force users to disclose private documents to centralized authorities, exposing them to risks of data breaches, identity theft, and invasive surveillance. The cumbersome, manual processes create friction and limit user autonomy.
Our solution
Built on the zkPassport SDK and advanced zero-knowledge proofs, our project enables secure, privacy-preserving, and trustless verification of marital status without revealing any underlying personal information. Users cryptographically prove facts like “I am legally single” or “I am married” while maintaining full control over their data.
This capability not only allows couples to enter into marriages seamlessly but also empowers individuals to prove their marital status across borders without repetitive document submissions. This simplifies access to spousal benefits, tax advantages, and legal rights in different countries—dramatically easing bureaucratic burdens.
Why it matters

• Removes reliance on centralized verifiers, reducing points of failure and censorship.
• Protects users from oversharing and identity theft through cryptographic privacy guarantees.
• Streamlines traditionally slow and complex bureaucratic procedures into seamless, automated digital workflows.
• Enables legally recognized marriages verified in a privacy-preserving way.
• Facilitates cross-border recognition of marital status, easing access to benefits and rights worldwide.

Use cases

• Privacy-first proof of eligibility for marriage or civil partnership.
• Seamless digital marriage registration with zk-backed verification.
• Internationally recognized marital status verification for benefits and legal processes.
• Age gating and access control without revealing exact birthdates.
• Decentralized identity verification for services requiring confidential status proofs.

Our solution is a game-changer in digital identity, empowering users with privacy and security, and setting new standards for trust in the decentralized era.

Challenges we ran into

While building our project using the zkPassport SDK, we ran into a few challenges. In the testing environment, all user IDs were identical, which required us to add extra conditions to differentiate users. In a real-world scenario, this wouldn’t be an issue, as each ID would be unique. Additionally, we initially had trouble connecting to the zkPassport SDK, but were able to resolve it by referencing the official example, which helped us structure the integration correctly.