WB Soul

WhiteBIT-verified identity: the real registry on Whitechain mainnet, and the labelled mirror on testnet.

Tazor only accepts approvals from people WhiteBIT has verified. That verification is WB Soul: an identity record on Whitechain mainnet that WhiteBIT links to a person's wallet addresses after KYC.

Real Soul and the testnet mirror

WB Soul exists only on Whitechain mainnet, at 0x…2000, with the IsVerified attribute held in the attribute registry at 0x…2002. Tazor runs on Whitechain Sepolia, where there is no WB Soul, so payments there check a mirror contract with the same interface that we fill ourselves.

Wherever a person appears, Tazor shows two lines: WB Soul (mainnet), read live from the real registry, and Testnet mirror, which is what the testnet payment contracts used. Only the first line says anything about WhiteBIT.

How a company admin gets a real Soul

1. Complete identity verification (KYC) with WhiteBIT.
2. WhiteBIT assigns your wallet address to your Soul on Whitechain mainnet and sets IsVerified.
3. Check your address below. Once it shows Verified, you pass the identity check that Tazor's payment contracts make for every approver.

As observed on chain, the address assignments (assignAddress, registerSoul) are sent by WhiteBIT's operator 0xb358…0ED9, so you don't send a mainnet transaction yourself. WhiteBIT doesn't publish this as a guarantee; it is simply what the registry's history shows.

What WhiteBIT can and can't do

• It can verify a person, and it can revoke that verification. A revoked person can no longer approve payments.
• It can't move company funds or approve a payment on anyone's behalf.

Check any address