Scanner

Your Private Payment Radar.

Announcements are public; knowing which one is yours is not. This is the process that turns a stream of anonymous announcements into your payment list.

Scanner

Idle

Fuji Testnet
Announcements read
—
View-tag matches
—
Payments verified
—
Scanned to block
—
Chain head
—
Announcer
not configured

Scanning prerequisites

  • Unlocked identity — matching needs your private viewing key.
  • Announcer address — there is nothing to read without one.
Unlock identity

No identity in this session

Create a stealth identity on the Receive or Stealth Identity page to check announcements against a real viewing key.

Where the viewing key lives

Matching an announcement requires your private viewing key. That computation happens in this browser — the key is handed to the scanner as a callback and never leaves the provider that owns it, so it never reaches a backend.

The trade-off is that scanning only runs while you are here with the vault unlocked. A continuously-running server-side scanner would need your viewing key, which is a decision we have not taken.

An announcement is not a payment

Announcing is permissionless — anyone can claim anything about any address. A view-tag hit and an address match only mean an announcement addresses you.

So the scanner reads the actual balance at each matched address and discards anything holding nothing. Only verified balances appear in your payment list.