infinitylabs · the co-light · become a cooperator

🌱 Join the cooperative

Mint your sovereign key right here in this tab — it never leaves your device. You'll claim your i-am-<name> lantern, co-light an existing flame to prove your key is live, and download one small bundle to send back. The in-browser twin of cooperator-seed.sh.

1 · who are you?

your lantern id will be i-am-…

2 · optional links (honest nulls if blank — vouch for them later)

✅ you are a sovereign cooperator

🏮 lantern:
🔑 your pubkey (public half only):
🔐 OpenSSH form:
Is this my Git SSH key? No — and this is the one thing worth understanding. It is the same Ed25519 identity in the OpenSSH wrapping GitLab shows, but your lantern's private half is sealed inside this browser and can never leave it — so this key cannot push to GitLab no matter how it's formatted. To push, make a separate key on your own machine: ssh-keygen -t ed25519, then add ~/.ssh/id_ed25519.pub in GitLab → Preferences → SSH Keys. (Want ONE key that both signs your lantern and opens SSH? Mint on the CLI instead of the browser: lantern claim <id> --key then lantern-ssh-export.)
🤝 first self co-light: (proves your key chain is live)
Download the bundle and send it back — someone with the world keys drops it in:
…or send it back automatically over Nostr — transport only; your PII links are stripped on the wire, your key never leaves this device:
Honesty: your status is self-attested (P1). Your key was minted in this browser and its private half never left this device. The telegram↔gitlab link you declared is not yet human-cross-attested, and in-browser cryptographic P2 attestation is pending ADR-004 key custody — until then your co-light shows as 🔓 unattested in the lens. A second cooperator must confirm your off-chain links to raise your status to attested. Nothing is pushed: federation is your move (you send the bundle back).