Wallet safety · browser private

Understand the approval before you sign it.

Answer six boundaries from the wallet prompt and official project records. Nothing is uploaded, no wallet connects, and this page never asks for an address, seed phrase or private key.

Six-boundary check

Review the request locally.

Use the wallet's decoded prompt, the project's official documentation and a block explorer. “Unknown” always stops the review.

1. Is this explicitly a token approval or spending-cap request?Do not assume every signature or transaction is an approval.
2. Is the amount limited to what this action needs?Unlimited or unexpectedly broad access fails this boundary.
3. Does the spender contract match an official source?Names and logos are not contract-address evidence.
4. Does the wallet's network match the intended action?Approvals are chain-specific; verify the selected network.
5. Did you independently verify the dapp domain?A bookmark or official documentation is stronger than an unsolicited link.
6. Is this permission required right now?Reject dormant, unexpected or unrelated approvals.

Primary safety paths

Verify or revoke through a known route.

These independent sources explain what approvals are and how an existing allowance can be reviewed or revoked. Leaving Bremo may involve a wallet transaction and network fee.

What this checker cannot prove

A passed checklist does not prove a contract, dapp, wallet, transaction or person is safe. It does not simulate calldata, inspect current chain state, detect compromised frontends or replace independent technical review. Reject any prompt that changes after your review.

Checking the BREMO contract itself?

Use the separate exact-address verifier. It compares locally and does not establish price, liquidity, security or return.

Open contract verifier →