Skip to content
B3Pay homeB3Pay homeB3Pay

Get your protocol clear-signed

Wallets that support ERC-7730 show what a call does instead of raw calldata, once a descriptor for your contract is in a registry they read. We write that descriptor, test it against real transactions, submit it, and keep it current as your contracts change.
Start with your contractsHow a descriptor works

What you get

Section titled “What you get”

  1. Scope. We list the contracts and functions your users sign on each chain you are deployed to, including proxies and the implementations behind them.

  2. Descriptors. We write an ERC-7730 descriptor for each contract from its verified ABI: an intent for each function, and each value labeled and formatted, such as token amounts with their decimals, addresses and dates.

  3. Tests on real calldata. Every function gets a test built from a real transaction, and every descriptor passes the official linter’s schema and ABI checks before anyone else sees it.

  4. Submission. We open the pull request to the registry and answer its reviewers. You see each change before it goes out.

  5. Upkeep. When a proxy is upgraded or an ABI changes, a check in your CI flags the descriptors that no longer match, and we update them.

What we don’t claim

Section titled “What we don’t claim”
  • Being in the registry is not an audit. The registry’s maintainers screen submissions, and inclusion is not an endorsement.
  • Writing a descriptor does not attest it. An attestation is a reviewer’s signed claim about one exact descriptor, under ERC-8176, which is still a draft. We call a descriptor attested only when an attestation exists for its current content, and we link to it.
  • Wallets decide. Each wallet chooses which registries and which reviewers it trusts, so a descriptor that one wallet shows is not a promise about every wallet.

Sources, checked 30 October 2026: ethereum.org’s Clear Signing guide and ERC-8176. The details are in the docs.

Before we start

Section titled “Before we start”
  • The registry needs your contracts verified on Sourcify. If they are not, we help you verify them first.
  • We need public information only: chains, addresses, and the flows your users sign. Never send a private key, a seed phrase or any other secret.
  • We reply with a scope and a quote, based on how many contracts and functions you want covered.

Start

Section titled “Start”

Public addresses are all we need. Never send a private key, seed phrase or other secret, here or anywhere else.

© 2026 B3Pay. Code on GitHub.