Purser
Purser Shield

Three agents attacked, every agent protected.

Every wallet fights alone. On Purser, an attack the firewall blocks is refused at once by the account that caught it. Once 3 independent accounts with a payment history report the same attacker, every account refuses it.

Attackers on the list
0
Reported by 3 or more accounts
Injected instructions
0
Sentences fingerprinted
Stopped by the Shield
0
Payments on other accounts
Accounts protected
0
Every Purser account, by default
  1. 01

    One firewall catches an attack

    An agent reads a page with a hidden instruction, or is asked to pay a wallet that forwards everything away. Its firewall simulates the payment and refuses it before anything is signed.

  2. 02

    The attacker goes on the list

    The attacker's side of that attack is recorded in the same second: the address, the contract behind it and a fingerprint of the injected sentence. The account that caught it refuses it from then on.

  3. 03

    Three reports, every account

    Once 3 independent accounts with a payment history report the same attacker, it goes on the shared list. Every account's firewall then checks the payee, every recipient and every spender against it before it signs.

Only the attacker is shared

  • Attacker addresses: planted payees, forwarding wallets and hostile spenders
  • The contract a forwarding wallet hands control to
  • A one-way fingerprint of each injected sentence, with addresses and amounts masked
  • How many accounts an attack was aimed at, as a number

Never shared

  • Balances, amounts or what an agent paid for
  • Owners, agents or which accounts were attacked
  • The text the agent read
  • Anything about payments that went through

Your call, per account

Block, the default. A payment that touches anything on the list is refused before it is signed.

Warn and wait for me. The payment is held, nothing moves, and you release or reject it from the dashboard.

An address you put on your own list is never stopped for you; you get a warning instead. Scheduled payouts never wait: a flagged payee is not paid again, and the owner is told at once.

Set it in the dashboard

Is an address on the list?

The list, live

Nothing on the list yet

When 3 Purser independent accounts with a payment history have caught the same attacker, its address and a fingerprint of the injected instruction appear here, with how many accounts it was aimed at.