Private Key Guide

How to use private keys in the Living Constitution

๐Ÿ” Generating Your Key

When you visit the registration page, you can generate a new cryptographically secure private key using the browser's crypto API. This key is your unique identity on the platform.

  • Keys are 32 bytes (256 bits) of randomness
  • Converted to base64 for human-readable display
  • Your public identity is derived via SHA-256 hash

๐Ÿ’พ Saving Your Key

Once generated, you MUST save your private key immediately. There is no recovery mechanism.

  • Write it down on paper
  • Store in a password manager
  • Save to an encrypted file
  • Never share it except when registering
Warning: Losing your key means losing your account permanently.

๐Ÿ”‘ How It Works

The system uses ed25519-style key derivation for simplicity:

  1. Generate 32 random bytes
  2. Encode as base64url (no padding)
  3. Your public key = SHA-256(private_key_bytes)[:20] base64url-encoded
  4. Authentication: derive public key from submitted private key and compare

๐ŸŒ No Emails, No Passwords

Traditional authentication (email + password) is replaced with:

  • One-time key generation
  • Public key derivation (server never sees private key)
  • Session cookies signed with HMAC-SHA256
  • All state stored in your browser session

๐Ÿ”„ Logging In

To log in, simply paste your private key. The system derives your public key and matches it against your registered account. No password, no 2FA needed - just your key.

๐Ÿ›ก๏ธ Why a key is more private and secure than email + password

A key is not โ€œa password with a different nameโ€. It changes what the server ever holds about you, and what a breach can actually take.

  Email + password OAuth (Google, GitHub, โ€ฆ) Private key (this site)
What the server stores Your email address and a password hash A provider user id, an email, an access token A public key derived from your private key
What a breach exposes Emails and password hashes โ€” crackable offline, then reused everywhere Account tokens that can be replayed against you Only public keys. Nothing that can be logged in with
Third parties None, but the server is the single point of failure The provider sees every login; it can lock you out at any time Nobody in between โ€” no provider, no tracking, no profile
Reuse across sites Usually yes, and that is exactly the danger Scoped to one provider Never โ€” the key is unique to this constitution
Phishing Easy: fake login pages steal the password Harder but the provider can be impersonated Possible, but the key cannot be handed to a third party
Identity data Ties you to an email address, a phone number, a carrier Ties you to a full social profile Only the display name you choose
Censorship / portability Account is owned by the server operator Account is owned by the provider You hold the key; the constitution is the record
The honest trade-off: with a key there is no โ€œforgot passwordโ€. If you lose the key, the account is gone โ€” that is the price of the server never being able to reset, read or recover it.

๐Ÿงญ Practical advice

  • Store the key in a password manager, an encrypted file, or on paper โ€” not in a chat or a screenshot.
  • Use a different key per community if you want your identities to stay separate.
  • Never paste your key into a form you did not open yourself. This site asks for it only on the register and login pages.
  • Signing out on a shared device is not enough โ€” clear the site data too.