How it works

The Transaction Checker API works by simulating the transaction or EIP-712 signature request in a sandboxed environment of the blockchain and analyzing these outcomes using machine learning and heuristic engines. By doing so, it can provide insight into the transaction or signature request including:

Tokens/NFTs/ETH being sent or received
Approval changes that grant/revoke permission to others to access the wallet's assets
State changes to smart contracts
If the transaction/signature request involves a scam contract or wallet

What we look for:

	Description
Approval changes	Check if there are any permissions to access the wallet's assets being granted or revoked.
Balance changes	Check for any NFTs/Tokens/ETH being sent or received.
Scammer counterparties	Check if any of the wallets or contracts involved in the transaction are known to be scammers.
Security vulnerabilities	Check any contract involved in the transaction for security vulnerabilities in the source code that could lead to attacks that might drain assets or otherwise allow unauthorized changes. See the Smart Contract Weakness (SWC) Registry for some examples.
Scam contract code	Check any contract involved in the transaction for code patterns or behaviors that are known to be used in scam contracts (i.e. honeypots).
Verified contract code	Check if any contract involved in the transaction has verified source code.
ERC compliance	Check if any contract involved in the transaction is compliant with any of the typical ERC standards for NFTs (ERC721, ERC1155) and cryptocurrencies (ERC20).
Domain impersonation	Check if the website that triggered the transaction appears to be impersonating a legitimate site (i.e. NFT project sites, marketplaces).
Unintentional burning	Check send tokens to their own contract in a way that would effectively burn them unintentionally.

Use cases

Wallets

Simulate and analyze transaction requests before presentng to the user in order to provide details on what will happen and protect them from potential scams.