Toknix was built from the ground up for developer privacy, resilience against credential stuffing attacks, and zero-liability data architecture.
Security Philosophy
Traditional SaaS platforms collect email addresses, company names, billing addresses, and credit card numbers. In the event of a vendor breach, this metadata links developer identities to project usage and IP addresses.
Toknix eliminates this entire surface area:
- No Email Collection: No user emails exist in Toknix databases. Phishing against Toknix user credentials is mathematically impossible.
- No Passwords: We do not store hashed passwords. Credential stuffing from third-party database leaks cannot compromise a Toknix account.
- No KYC or Card Numbers: All billing occurs via on-chain cryptocurrency transactions. No credit card records or billing names are stored.
10-Digit Numerical PIN
When an account is created, Toknix generates a 10-digit numerical PIN (e.g., 7419205832) offering 10 billion possible combinations.
Brute-force protection:
- Logins are rate-limited to 5 failed attempts per minute per IP address, with exponential backoff and CAPTCHA challenge requirements after consecutive failures.
- PINs are verified against cryptographic hashes in PostgreSQL with constant-time equality comparisons.
Defense-in-Depth with Subkeys
Never embed your primary master API key in client-side code, external CI/CD runners, or unverified community coding extensions.
Instead, use Subkeys:
- Assign hard budget caps (e.g., $10 maximum spend).
- Restrict specific models if necessary.
- Revoke instantly when a team member leaves or a repository is archived.
Incident Response Playbook
If you accidentally commit an API key to a public GitHub repository:
- Immediately open the Toknix dashboard on toknix.in.
- Navigate to API Keys and click Revoke next to the compromised key.
- Generate a fresh key and inject it into your local environment or secrets vault.
- Check
GET /v1/usageto inspect token transactions executed during the window of exposure.