> ## Documentation Index > Fetch the complete documentation index at: https://docs.txshield.xyz/llms.txt > Use this file to discover all available pages before exploring further. # The Scam Was Already Written > Why showing users where their funds go — before they go there — is the most important shift in crypto security since auditing was invented. ## The problem with auditing is that it looks backwards. A smart contract audit is a report about what a contract *was* when someone read it. By the time a retail user encounters a token on a DEX, that audit — if it even exists — is already in the past. The contract may have been modified. The ownership may have transferred. A time-locked function may have activated. The tax that was 0% at audit time may now be 99%. None of that shows up in the audit. The audit is a photograph. You are making a financial decision in the present. *** ## The blockchain doesn't have an undo button. This is the fact that every other security tool in crypto quietly ignores. When a user clicks confirm, the transaction is final. There is no dispute resolution. There is no fraud department. There is no 48-hour reversal window. The moment that transaction is signed and broadcast, the outcome is locked. Every scam contract in existence is built on this single truth. Rug pulls, honeypots, approval drains, permit abusers — they all rely on the same thing: **the user confirms before they understand what they confirmed.** The scam doesn't happen when you get drained. It happens when you click approve. *** ## Competitors told you whether a contract was dangerous. ## TxShield shows you what actually happens to your money. This is the distinction that matters. Existing tools in this space — and they do good work — operate as **classifiers**. They take a contract address and return a verdict. Safe. Risky. Honeypot. The verdict is correct or it isn't. But a verdict doesn't answer the question a user is actually asking. A user APE-ing into a new token is not asking *"is this contract theoretically dangerous?"* They are asking: **"If I send this transaction right now, what happens to my funds?"** Those are different questions. TxShield is built to answer the second one. *** ## What simulation actually means. When TxShield simulates a transaction, it does not guess. It does not pattern-match against known scam signatures. It does not check a database of flagged contracts. It **runs the transaction** — against the real contract, against the real chain state, at the current block — and observes the outcome before you've signed anything. It sees: * How much of your funds arrive at the destination vs. how much is taken as tax * Whether your approved allowance gets routed to a third-party address you never interacted with * Whether a `permit()` signature you're being asked to sign grants someone else control over your wallet * Whether the contract behaves differently 24 hours from now than it does at this exact moment The result is not a verdict. It is a **preview**. You see the future of your transaction before you confirm it. *** ## Security is not a premium feature. The crypto industry has quietly accepted a two-tier system. Sophisticated users — developers, DeFi power users, people who know how to read Etherscan — have always been able to inspect a contract before interacting with it. They can decode calldata. They can read a token's transfer function. They know what an approval actually grants. Everyone else clicks confirm and hopes. This is not a knowledge gap. This is a tooling gap. Retail users are not less intelligent than developers. They are less equipped. And the entire scam ecosystem in crypto is built to exploit exactly that gap. TxShield's position is simple: > **Every person who owns crypto — regardless of how much, > regardless of their technical background — has the right to > know what a transaction does before they sign it.** Security is not an advanced feature. It is infrastructure. It belongs at the point of transaction, not in a report that most users will never read. *** ## Where TxShield fits in the stack. TxShield is not a wallet. It is not an exchange. It is not an audit firm. It is the security layer that sits **at the moment of transaction** — wherever that moment happens. That means: **DEX aggregators** surface TxShield simulation results before a swap is confirmed. The user sees a breakdown of where their funds go, not just a price quote. **Wallets** run TxShield checks on every approval and permit signature before presenting the confirmation screen. The user knows what they're signing. **Token screeners** embed TxShield verdicts alongside price charts so users evaluating a new token see risk data at the same moment they see market data. **Protocols** integrate TxShield's API to protect their users from interacting with malicious contracts in the first place. The goal is that no matter where in the Web3 stack a user encounters a transaction — on a DEX, in a wallet, on a launchpad, in a game — TxShield has already run before they confirm. *** ## The shift we are making. Auditing asked: *"Is this contract dangerous?"* TxShield asks: *"What happens to your money if you interact with this contract right now?"* The first question protects protocols. The second question protects people. We are not replacing auditing. Audits are necessary. We are filling the gap that auditing was never designed to fill — the gap between a developer publishing a contract and a user sending funds into it. That gap is where every retail loss in crypto happens. That gap is where TxShield lives. *** The technical pipeline — Phantom Contracts, eth\_call, stateOverride, and why no transaction ever touches the chain. Add TxShield risk signals directly to your platform UI.