BLADE ACCOUNT CARD
BAC · File Credential System · v1.0.0
CHECKING

BAC cannot reach its database.

Bind your Cloudflare D1 database to the Pages project with the exact variable name DB, then redeploy. BAC creates its schema automatically.

Initialize BAC.

Create the first administrator. After initialization, issue that administrator a .bac credential file before signing out.

Present your BAC.

Your encrypted credential file is the possession factor. Its private key is decrypted locally and used only to sign a one-time challenge.

Select BAC Credential

The .bac file and its password are never uploaded. BAC sends only the credential ID and cryptographic signature needed for authentication.

Control Center

People
—
Active BAC files
—
Audit events
—

BAC v2 credential model

Each issued .bac file contains identity metadata plus an AES-256-GCM encrypted ECDSA P-256 private key. D1 stores the public key and lifecycle state. Copying the file alone is insufficient without its file password, and the server can revoke the credential at any time.

Add person

PersonUsernameRoleStatusActions
Important: BAC does not keep a recoverable copy of an issued private key. If a .bac file is lost, revoke it and issue a replacement.
CredentialOwnerTypeStatusExpiresAction
TimeActionTarget

Database backup

Export BAC server records as a JSON backup. Private keys are never included because they exist only inside user-owned .bac files.

Recovery model

Keep database backups and credential-file backups separately. Restoring D1 records cannot recreate a lost .bac private key.

Blade Account Card v1.0.0 · File-based cryptographic identity system