⚠️ Important Disclaimer
KeyAuth is an experimental implementation.
It is not canonical.
It is not authoritative.
It does not represent the protocol itself.
You are paying for infrastructure and support,
not for legitimacy or trust.
What KeyAuth Provides
KeyAuth provides hosted infrastructure for:
- Bitcoin signature authentication
- LNURL-Auth integration
- Nostr-based login (NIP-07)
- OAuth2 / OIDC compatibility
- Proof-of-Funds verification (PSBTs)
This service exists for teams that want to experiment
without running their own infrastructure.
What KeyAuth Does NOT Provide
KeyAuth does not:
- Define identity (users control their keys)
- Assign trust (reputation is derived, not assigned)
- Control reputation (system observes, doesn't judge)
- Prevent exit (always possible)
- Represent canonical deployment (one of many possible implementations)
Pricing Philosophy
Payment does not imply endorsement.
Payment does not imply authority.
Payment does not imply correctness.
Forking and self-hosting are always valid alternatives.
Current Pricing (Beta)
All tiers are FREE during beta.
When we exit beta (2025?), pricing below will apply.
We'll give 60 days notice before charging.
Free
$0/month • 1,000 active users
Bitcoin signature auth, basic time-locks, community support
Developer
$29/month • 10,000 active users
Email support (48h), early access features, priority bug fixes
Professional
$99/month • 100,000 active users
Priority support, custom covenants, direct feedback to roadmap
No "Enterprise" tier yet.
The system is not ready for mission-critical applications.
What Users Pay For
Users pay for:
- Hosted infrastructure (servers, monitoring, backups)
- Uptime and maintenance (best-effort, no SLA during beta)
- Integration support (email, documentation)
- Operational convenience (not running your own nodes)
What Users Do NOT Pay For
Users do not pay for:
- Identity legitimacy (cryptography provides this)
- Trust guarantees (trust is earned through behavior)
- Protocol authority (no one has this)
- Exclusive access (open source, forkable)
- Long-term control (exit always possible)
Explicit Red Line
Any monetization that requires:
- Lock-in (preventing users from leaving)
- Hidden constraints (undisclosed limitations)
- Asymmetry of exit (different rules for different users)
- Claims of canonical authority (KeyAuth is one implementation among many)
...violates the principles of HODLXXI and should be considered non-compliant.
Acceptable Revenue Sources
KeyAuth may generate revenue from:
- Infrastructure fees (hosting, API usage)
- Integration work (custom deployments)
- Consulting (system design advice)
- Research sponsorships (grant-funded work)
- Educational content (courses, workshops)
All revenue sources must preserve user agency and exit rights.