nodeSolidServer / nodeSolidServer/node-solid-server
HTTP Schnorr Signature Authentication
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.8k
- Forks
- 308
- PR merge metrics
- No merged PRs in 30d
Description
Motivation
Millions of users already have cryptographic keys. This proposal lets them authenticate to Solid pods instantly - no account creation, no passwords, no redirect flows.
📸 Login page with Schnorr SSO:
🎥 See it in action: https://youtube.com/watch?v=wlADHzVNcvM
What is it?
- HTTP Schnorr Auth - Authentication using BIP-340 Schnorr signatures
- did:nostr - A self-certifying DID method (one compatible identity format)
Users authenticate with browser extensions - one click, no passwords.
4-Phase Roadmap
| Phase | Description | Status |
|---|---|---|
| Phase 1 | DID identities in ACLs + Schnorr signature verification | ✅ Complete |
| Phase 2 | SSO "Sign in with Schnorr" button on login page | ✅ Complete |
| Phase 3 | Linked identities (WebID ↔ DID) | Planned |
| Phase 4 | Global DID resolver integration | Planned |
Specifications
- http-schnorr-auth v0.0.1 - HTTP authentication spec
- did:nostr v0.0.10 - Compatible DID method
Test Suite
10 test vectors: https://github.com/nostrcg/http-schnorr-auth/tree/gh-pages/test-vectors
Related Work
Working implementations exist for CSS, Pivot, and JSS. This represents 2 years of development and testing.
Phase Issues
- Phase 1+2: To be submitted and linked to this issue
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the linked http-schnorr-auth and did:nostr specifications and their test vectors first. The issue names no repository files or concrete acceptance test; clarify whether the intended work is Phase 3 linked identities or Phase 4 resolver integration, and define completion criteria with maintainers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- authentication, backend-api-design, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100