Your company on ENS

How a company name such as acme.taz0r.eth holds who may approve.

Each company has an ENS name under taz0r.eth, for example acme.taz0r.eth, with its own ENSv2 registry on Ethereum. That registry records who holds which role. Whitechain reads it by cryptographic proof, so no Tazor server decides who may approve.

Roles

• Approver can approve payments for the company.
• Admin manages the team: adds payees, grants temporary access, removes people.
• Agent is software that can pay within a 30-day cap.

How a role change reaches Whitechain

1. An admin changes the role on the company's ENS registry on Ethereum.
2. Whitechain learns the new Ethereum block about a minute later through its L1Block contract.
3. Someone submits a storage proof to the RoleCache on Whitechain, which checks it against Ethereum and caches the role.

In our measurement, an automatic sync took 84 s from the ENS change to the cached role. A sync proof costs about 0.96M gas and only runs when roles change, never on the payment path.

Who runs the sync

• On demand. When you open Company and someone is out of sync, the page asks the relayer to sync them, and shows the transaction when it lands. You can also choose Sync now in a person's panel.
• A daily sweep. The relayer also checks its watched company registries once a day.
• Anyone. The proof is checked on-chain, so any account can submit it. No Tazor server has to be running for roles to reach Whitechain.

If the relayer reports that Whitechain hasn't seen the ENS change yet, the page waits about a minute and tries once more. If role sync isn't enabled for your company's registry, the page says so and the manual route still works.

Why the cache can lag

A role removed on ENS still applies on Whitechain until the next sync. To stop someone immediately, use Removing a person, which takes effect on Whitechain directly.