How signing differs from login
1
Server loads the latest block hash
2
Server builds a block-bound challenge
3
Browser calls the authenticator and signs
4
Server records the signature as a block attestation
Signed challenge
challenge = SHA512( random_hash + block_hash + block_number + timestamp + rp_id )
Why this matters
Login
Proves the user is present now.
Sign
Proves the user is present and that the ledger state is current.
Result
The signature becomes part of the next block’s trusted attestation.
Sign a Block & Earn Tokens
Already registered? Sign a block directly — no login session needed.
Not registered yet? Register above to create your device-based account and start earning tokens.