Questions people ask

No. We only answer a question. Nothing is sent, signed or moved. The trade we run is a simulation.

No. It means we found nothing that should stop you at the moment we looked. A token can still fall in price, and things can change after the check. We give risk information, not financial advice.

We found real risks and we list them: for example, the owner can still print new tokens, or the pool is small. Most platforms warn the user or cap the size of the trade.

You get "unknown" and you aren't charged. We would sooner say we don't know than guess.

Keep it, and run us beside it for a few weeks. The traps that take the most money on Base today sit in a part of the newest Uniswap pools that the common free checkers don't read. A pilot shows you, on your own traffic, what they pass and we catch.

Often, yes. Scammers make wallets with the same first and last characters as one you have paid, then plant them in your history with fake USDC or USDT transfers, hoping your next payment goes to the copy. Our address check blocks a wallet whose only history is planted like that, and names the real address it imitates. It can't know which address you meant to pay, so always check every character of a new one.

No. Being new is not a reason to block. A new token with a real pool, locked liquidity and no dangerous owner powers can get an allow, and in our tests it does.

A token check answers in about a second. A wallet check takes about a fifth of a second.

Base and Ethereum today.

The address that was checked, the size of the trade if you send it, our answer, when, and which key asked. Nothing about your users. Our own records hold no IP addresses. A caller without a key is counted by address for one minute, to stop abuse, and our hosting provider's request logs keep the address a request came from for about a week, as any web service's do. The whole of it is in the privacy note.

Yes. Every answer is signed and carries the exact block and time it was true.

Tell us: by email, or straight from your code (one request with the answer's id and what you expected). We reproduce it the same day, and a confirmed mistake becomes a permanent test.

Yes. Every token we answer about is looked at again an hour, a day and a week later, so we know how often an "allow" went wrong without waiting for someone to tell us.

No. We screen against the US sanctions list as one of our checks. That is a useful floor, not a compliance programme.