IdeaWell

Project ideas from Hacker News discussions.

Are we self-sovereign PKI yet?

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

1. Usability challenges foreveryday users

"I'm lxgr17@key, yeah, don't ask about the first 16..." – lxgr

2. Desire for flexible, revocable identities instead of immutable keys

"This is impractical and the opposite of what we want. It's a required ID to use the internet, monitored by governments, tracked by corporations, and forever unchanging." – irq‑1

3. The proposal mirrors existing key‑transparency and blockchain naming schemes

"The entire premise of this article is wrong!" – NoahZuniga

🚀 Project Ideas

Generating project ideas…

Memorable Key Fingerprint Service(MemeFinger)

Summary

  • Generates human‑readable, vanity fingerprints (short strings or emoji combos) for cryptographic public keys, eliminating the need to recall 40‑plus character hashes.
  • Provides a decentralized lookup service so users can share memorable identifiers (e.g., alice✴️27) that map to their actual keys.

Details

Key Value
Target Audience Privacy‑focused users, Signal/Keybase participants, developers integrating crypto identities
Core Feature Vanity fingerprint generation + decentralized resolution via IPFS + ENS‑style smart contracts
Tech Stack Rust backend, IPFS, Solidity/Ethereum L2 contracts, React frontend
Difficulty Medium
Monetization Revenue-ready: Freemium with paid vanity generation (starting at $0.01 per attempt)

Notes

  • HN commenters would love it (“I’d love a way to say ‘my key is alice’ instead of a 40‑character hash” – irq‑1).
  • Sparks discussion on usability of crypto identities and potential for broader adoption in messaging apps.

Dynamic Contact‑Sync Identity System

Summary

  • Enables users to create new cryptographic IDs on‑the‑fly and automatically pushes the updated key to all contacts, eliminating manual re‑registration.
  • Solves tracking/required‑ID fatigue by introducing flux and churn in a user‑controlled way.

Details

Key Value
Target Audience Users seeking non‑static identifiers, secure messaging communities, contact‑centric crypto apps
Core Feature Contact book that broadcasts key changes to all contacts via push notifications and updates signing metadata automatically
Tech Stack Firebase Realtime Database, Web Crypto API, React Native mobile app, Node.js sync server
Difficulty High
Monetization Revenue-ready: Subscription $5/mo for premium sync & unlimited contacts

Notes- Addresses “flux and churn” desires highlighted by irq‑1 (“What we need is a system that allows people to easily create new IDs…”).

  • Potential for integration with existing messengers (Signal, Matrix) and for secure verification via transparency proofs.

Decentralized Name‑to‑Key Registry (KeyNS)

Summary

  • Provides a DAO‑governed marketplace for registering short, human‑readable names that map to cryptographic public keys, with anti‑squat mechanisms and time‑limited auctions.
  • Mirrors ENS concepts but focuses on key identity rather than domain names, reducing reliance on a single authority.

Details

Key Value
Target Audience Crypto developers, identity‑centric dApps, users wanting readable identifiers for keys
Core Feature On‑chain name registration → public key mapping, auction‑based squat protection, resolve via DNS/IPFS
Tech Stack Ethereum L2 (Optimism), Solidity smart contracts, IPFS, ENS‑compatible resolver UI
Difficulty High
Monetization Revenue-ready: Pay‑per‑registration fee (e.g., 0.01 ETH) + DAO treasury share

Notes

  • Echoes concerns about squatting (“Won’t this mean that squatters will keep buying the top‑alexa domains?” – captn3m0) and offers a concrete remedy.
  • Generates rich discussion around decentralized governance, cost models, and compatibility with existing naming systems.

Read Later