Security & settings
Live health of everything a payment depends on, the relayer this device uses, recent removals, and the controls for a lost device.
Trust model
What each party can and can’t do with your payments.
- WhiteBITCan Decides who is a verified person (WB Soul), and can remove that verification; that person then can’t approve.Can’t Move company funds or approve a payment.
- TetherCan Freeze USDT held at any address, including a company account.Can’t Approve or redirect a payment.
- Whitechain’s proposer and GuardianCan Delay or pause withdrawals from Whitechain back to Ethereum.Can’t Stop a payment sent through Ethereum: it arrives as an Ethereum deposit, which Whitechain must include.
- Whoever controls taz0r.eth’s contentCan Serve a different version of this app.Can’t Make you sign something else: your device rebuilds each payment and checks it with the contract before you sign. The build is reproducible, so anyone can compare its content ID with the published one.
- Tazor’s relayerCan Refuse or delay sending a payment; it is optional.Can’t Change what you signed. Anyone can send the same signed payment, and it also goes through Ethereum.
- Sandbox demo keysCan Play the other parties in the Autopilot (testnet only, held by the relayer, for the sandbox company only).Can’t Act for any real company.
What still works if Tazor disappears
- Your company’s USDT stays in its own account on Whitechain. There is no owner key and no upgrade key over it, and an admin can move it out through the time-locked exit.
- Who may approve stays on the company’s ENS name on Ethereum.
- A signed payment can still be delivered through Ethereum with the standalone page (fallback.html, one file you can keep) or the forward script, without Tazor’s site or servers.
- A backup key (an ordinary wallet you add on Approver setup) still approves from any other copy of Tazor. Passkeys are tied to this website’s address, so keep a backup key.
- Invoices live inside their payment links, not on a Tazor server.
Open the standalone payment page · Security model · Censorship resistance
System health
Checking from this device…
| Service | Status | Detail |
|---|---|---|
If our servers go down
A signed payment doesn't need Tazor: anyone can submit it, and if the relayer or the sequencer stops it, it can be sent through Ethereum and still lands on Whitechain. How the fallback works
Relayer
Optional. "Copy calldata" and "Send via Ethereum" work without one; a relayer only saves you sending the transaction yourself.
Using: none (default for this build)
Contracts
The contracts this build talks to on Whitechain Sepolia (chain 1874) and Ethereum Sepolia. Full addresses are on the Contracts docs page.
- PaymentModule v1
- 0xe19d…540Aexplorer
- MandateModule v1
- 0xB6f4…aC32explorer
- RevocationList v1
- 0x407a…311eexplorer
- ApproverAccountFactory
- 0xf15c…3D8eexplorer
- TazorAccountFactory
- 0xe6ef…b4A2explorer
- RoleCache
- 0x8AC4…8BDeexplorer
- WB Soul (simulated mirror)
- 0x9822…0928explorer
- PaymentModuleV2
- 0x9066…36f3explorer
- MandateModuleV2
- 0x24b6…220Fexplorer
- RevocationListV2
- 0x4AD5…2f5aexplorer
- EnsGate (Sepolia)
- 0x3fDF…6c2aexplorer
- EnsGate v2 (Sepolia)
- 0xF7EB…B656explorer
Recent revocations
Removed approvers for , and removals made from this device.
Lost device
Only if this device is lost or compromised. This can't be undone.
Freeze this device
If this phone is lost or compromised, revoke its approver for a company. It takes effect on Whitechain immediately and cannot be undone; an admin has to add a new approver account.