WTF Am I Signing? Docs
Learn how to install, configure, and integrate with the Chrome extension that translates crypto transactions into plain English.
How to Install
Get up and running in under a minute. Follow these steps to add WTF Am I Signing to your Chrome browser.
Open the Chrome Web Store
Navigate to the Chrome Web Store or click the "Add to Chrome" button on our homepage. The extension is listed under the "Productivity" category.
Click "Add to Chrome"
On the extension page, click the blue "Add to Chrome" button in the top right. A dialog will appear asking you to confirm the permissions.
Approve Permissions
The extension requires permission to read transaction data from dApp pages. It does NOT access your private keys, seed phrases, or wallet passwords. Click "Add Extension" to proceed.
Pin the Extension
Click the puzzle piece icon in Chrome's toolbar, then click the pin icon next to "WTF Am I Signing?" so it is always visible and accessible.
Connect to a dApp
Visit any dApp (Uniswap, OpenSea, Aave, etc.) and initiate a transaction. The extension will automatically intercept the signing request and display a plain English explanation with a risk score.
Review and Sign (or Reject)
Read the explanation and risk assessment. If the transaction looks safe, proceed to sign. If something looks off, reject it. The extension never blocks you from signing -- it only informs you.
You are all set
The extension works automatically in the background. No configuration needed. Every transaction you encounter will be analyzed before you sign it.
Supported Wallets
WTF Am I Signing works with any browser-based wallet that uses the standard Ethereum provider API (EIP-1193). Here are the wallets we have tested and fully support.
MetaMask
Full SupportBrowser extension and mobile. All EVM transaction types supported.
Rabby
Full SupportFull interception of all transaction and signature requests.
Coinbase Wallet
Full SupportBrowser extension supported. Mobile via WalletConnect coming soon.
Rainbow
Full SupportBrowser extension with complete transaction decoding.
Trust Wallet
Full SupportBrowser extension supported. All standard EVM interactions.
Phantom (EVM)
Full SupportEVM mode fully supported. Solana support coming in a future update.
Other wallets: Any wallet that injects a standard Ethereum provider (window.ethereum) should work out of the box. If your wallet is not listed and you encounter issues, open an issue on our GitHub repository.
Supported Chains
All major EVM-compatible chains are fully supported. Transaction decoding, risk scoring, and contract intelligence work across every chain listed below.
Ethereum
Chain ID: 1
Base
Chain ID: 8453
Arbitrum
Chain ID: 42161
Polygon
Chain ID: 137
Optimism
Chain ID: 10
Avalanche
Chain ID: 43114
BSC
Chain ID: 56
Solana Support Coming Soon
Solana transaction decoding is currently in development and will be available for Pro users in an upcoming release.
How Risk Scoring Works
Every transaction is analyzed and assigned one of three risk levels. The score is based on multiple factors including contract verification, age, transaction type, known threat patterns, and on-chain intelligence.
Scoring is additive. Multiple risk factors compound the score. A transaction with one CAUTION-level factor is flagged as CAUTION, but a transaction with three or more CAUTION-level factors may be escalated to DANGER. The scoring engine is continuously updated based on new threat intelligence.
API Documentation
Integrate WTF Am I Signing into your own application or service. The REST API provides programmatic access to transaction decoding, risk scoring, and contract intelligence.
Base URL
https://api.wtfamisigning.com/v1
Authentication
All API requests require an API key passed in the request header. You can generate an API key from your dashboard after signing up for a Pro account.
Submit a raw transaction for analysis. Returns a plain English explanation, risk score, and contract metadata.
Request Body
Response
Retrieve intelligence about a specific contract address, including verification status, age, risk flags, and known protocol association.
Example Request
Response
Submit multiple transactions for analysis in a single request. Useful for analyzing multicall or batched transactions. Maximum 10 transactions per request.
Request Body
Response
Rate Limits
Rate limit headers are included in every response: X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset.