jwinterm
fb3c547d93
- api/website.rs: sign-in-with-wallet (dapp connect). challenge bound to origin + short TTL; verify is single-use (remove-before-verify, race-safe), expiry- checked, signature via Result<(),AppError> verifiers (no oracle), resolves an EXISTING user by the proven key's pubkey_hash (never mints identity), mints a Platform::Web session. - api/users.rs: username set/get + by-username lookup (JWT-gated, 409 on taken, constant-shape lookup); per-asset key registration bound to the JWT user (no spoofable user_id) + public key-directory reads. - api/nip05.rs: /.well-known/nostr.json directory (username -> nostr_pubkey). - Wired into api/mod.rs; website+users nested at /api/v1, nip05 at root; all paths/schemas registered (openapi.json now 17 endpoints). - main.rs: periodic GC of expired web challenges (bounds the in-memory store). Adversarially reviewed (register_key authz + website identity-binding both hold; no critical/high). 69 tests green. Deferred LOW: per-IP rate-limit on the website routes lands with the router-assembly unit.
smirk-backend-core
Open, self-hostable backend for the Smirk non-custodial, multi-chain wallet. It provides the chain-access and identity surface a Smirk wallet needs — authentication, per-chain wallet access (Bitcoin, Litecoin, Monero, Wownero, Grin), the Grin slatepack relay, and Nostr-based identity — so anyone can run their own backend and a Smirk wallet can connect to it.
Status: early, under active development. Interfaces and the database schema may change before the first tagged release. Not yet recommended for production self-hosting.
What it is
- Non-custodial. The server never holds spend keys or seeds. It brokers access to blockchain data and relays wallet-to-wallet messages.
- Open core, feature-flagged. Every feature ships in this codebase and is
toggled per deployment; the wallet reads
GET /api/v1/capabilitiesand adapts to what a given backend offers. - Identity via "Sign in with Smirk". Authentication uses a seed-derived Nostr key (NIP-98); the server stores only public keys.
- Privacy first. No PII is required to use it; operator and user privacy are explicit design goals.
Architecture
Rust + Axum, PostgreSQL via sqlx. The public HTTP contract is generated from the handlers with utoipa (OpenAPI), which in turn drives the wallet's generated TypeScript client — one source of truth, checked for drift in CI.
Quickstart
cp .env.example .env # then fill in DATABASE_URL, JWT_SECRET, node URLs
cargo run # starts the API server
A full self-hosting guide (node requirements, reverse proxy, Tor admin onion,
backups) will live in docs/ as it stabilises.
Security
Please report vulnerabilities privately — see SECURITY.md. Do not open public issues for security reports.
License
To be finalized (MIT vs AGPL-3.0-or-later). Until a LICENSE file is added,
all rights are reserved.