ACTIGEN 2.0

One Engine · Multiple Solutions

Proof-of-work verified — no third party sees this login

New organisation? Register — tenant provisioned instantly

Human verification

sha-256 · leading zero bits

Rather than asking you to read distorted text — which the OCR engine in this product would read better than you can — your browser spends a moment of CPU on a puzzle only the server can set. It costs you once. It costs someone trying stolen passwords every attempt, and more each time they fail.

Difficulty0/ bits

Set by the server, and raised automatically after recent failed attempts.

Attempts by zero bits found
0
1
2
3
4
5
6
7
8
9
10
11

Log scale — each bucket holds roughly half the one before it. The amber bar is the target.

Attempts

Hash rate

Elapsed

One message for every failure

A wrong address and a wrong password answer identically, so this form cannot be used to discover who holds an account.

Constant work

An unknown address is still checked against a decoy hash, so how long the answer takes reveals nothing.

Lockout with backoff

Five failures locks the account, doubling each time — capped, so nobody can lock you out indefinitely.

Session cookie

HttpOnly and SameSite: page scripts cannot read it and another site cannot spend it.

Demo accounts — one per RBAC tier

These fill the address only. The shared password is set per deployment (ACTIGEN_DEMO_PASSWORD) — ask whoever gave you this link.