Relying-party demo. The node only stores KEL key hashes. This page stores the
next password hash and checks the password the extension returns on sign-in.
Protocol
·
Password app
·
Mobile setup
This page origin (branch_peer)
—
checking…counter —
Local next password hash (RP)
—
Node KEL counter
—
Install the Yada Password extension
From the repo: cd clients/password-manager && ./scripts/build.sh extension
Open chrome://extensions (Chrome / Edge / Brave) and enable Developer mode.
Load unpacked and choose
clients/password-manager/apps/extension/dist.
Open the extension popup: set Node URL (Chrome will ask to allow that host), save the vault, Broadcast inception.
On this tab, popup → Allow this page (one-time), then use Register / Sign in below.
After every rebuild: Reload the extension, then hard-refresh this page so the content script updates.
Load the Yada Password extension and Broadcast inception once.
Click Register below. The extension writes a KEL branch; this page stores the next password hash.
Click Sign in & rotate below (or the same button in the extension). The backend verifies the current password and requires a signed ratchet advance — there is no password-only path.
Tip counter advances on every successful sign-in. Repeat to watch continuous rotation.
WebView handoff (no extension)
Enter the Yada username from your identity announcement. The node routes
a request to the Yada Password app over its WebSocket presence (no FCM).
Keep the app open / online on your home node, then Approve.
Enforced sign-in + rotation
Extension returns passwordHash + nextPasswordHash.
This page verifies locally.
Manual check (optional): paste password only hits verify without txn and must fail.