Codes are decoupled from transaction intent
SMS, email, and static OTP codes can be relayed through phishing proxies without proving which amount, recipient, or action the user actually confirmed.
The trust layer for every transaction. Trustlith binds user approval of sensitive actions—sign-ins, payouts, account changes, and administrative workflows—to device-bound asymmetric keys, deterministic canonical payloads, and authoritative server verification on Cloudflare Workers and D1.
THE PROBLEM
Authentication is not just logging in. Modern SaaS and financial applications need verifiable proof that the right person, on an enrolled device, approved a specific action—not a relayed six-digit code.
SMS, email, and static OTP codes can be relayed through phishing proxies without proving which amount, recipient, or action the user actually confirmed.
Key rotation, additional-device enrollment, and account recovery fail dangerously when mobile clients delete keys prematurely or skip authoritative server reconciliation after an uncertain network outcome.
Many developer portals blur browser sessions with runtime verification secrets. Trustlith keeps developer onboarding strictly separated from the authoritative Cloudflare Worker and D1 security ledger.
ARCHITECTURE
Every Trustlith ceremony reconstructs deterministic canonical proof bytes server-side, verifies device signatures against scoped credentials, and records append-oriented audit chains.
Creates a short-lived, single-use scoped challenge over server-authenticated API calls—never trusting browser approval flags.
Validates tenant/application/user scope, persists the challenge in Cloudflare D1, and reconstructs canonical signing bytes deterministically.
Displays exact action context, requires explicit local user presence or biometric confirmation, and signs with the device-bound P-256 key.
Verifies the signature, commits an atomic compare-and-set terminal decision, and appends tamper-evident audit facts before returning the result.
ACTIVE, SUSPENDED, LOST, REVOKED, REPLACED).trustlith-portal) with a dedicated Portal Identity D1 database—completely separate from Trustlith runtime D1 tables./api/auth/*.DEVELOPMENT STATUS
Trustlith is built in audited, security-first phases. Below is our verified current engineering state and what comes next.
DEVELOPER PORTAL
Sign in with an existing developer passkey to access the authenticated multi-tenant organization workspace. Public registration opens once controlled verification is enabled.