ConsentKy: A Playful Experiment in Multi-User Consent With Pubky Ring

ConsentKy was one of the more playful projects from our internal hackathon in Lugano, but beneath the humor is a clear demonstration of how Pubky’s identity tools can support simple, verifiable agreements between multiple users. The app uses Pubky Ring to collect consent from two people and then stores a signed, timestamped record of that agreement on each user’s Homeserver.

The concept is intentionally lighthearted, but the pattern it showcases is very real and broadly useful in decentralized identity workflows.

[embed]

Core Idea: Mutual Consent With Cryptographic Proof

The flow is straightforward. Two users scan a Pubky Ring QR code, each approves the action, and once both have agreed, the app writes the result to their Homeservers. No accounts, no central service, no shared backend. Each user walks away with their own independently stored proof.

This makes ConsentKy a small example of how Pubky enables multi-party authorization without introducing trust in anything except the participants’ keys.

How ConsentKy Works

The interaction consists of just a few steps:

• User A opens ConsentKy • User B scans the Pubky Ring QR code to authorize • Both users click Agree • ConsentKy writes a signed and timestamped “agreement” to each Homeserver via the Pubky SDK

Because the record is stored on both sides, each user maintains their own copy of the agreement. If the app vanished tomorrow, the data would still live with the identities that created it.

Why It Matters for Pubky

ConsentKy highlights a practical capability of the Pubky stack:

• Pubky Ring handles short-lived sessions and per-action authorization • Pubky SDK writes create cryptographically anchored records tied to a user’s keys • Homeservers give each participant their own authoritative copy of shared actions

This is the foundation for more serious use cases: approvals, shared ownership, multi-user workflows, or any scenario where two or more people need to authorize something together without relying on a central application to hold the record.

ConsentKy takes that pattern and wraps it in humor, but the underlying flow is genuine and technically grounded.

Github repo: https://github.com/jacobo-synonym/hackathon-2025/tree/main/consentky