Whitepaper v2.0 · Short Edition · September 2026
SaveSaveSaveSave
A Transparent Risk Tool for Everyone in Crypto
"Four chains. Four data sources. Four reasons for the name: save your funds, save your time, save your trust, save the regret."
1. What It Is
SaveSaveSaveSave checks a wallet or token against real security data and returns a plain verdict — PASS, CAUTION, FAIL, or INSUFFICIENT DATA — before you act, not after. Not financial advice, not a price prediction. A risk read, in seconds, built on evidence you can inspect rather than a score you have to trust.
2. The Name
Four repetitions, four real product pillars — not four copies of the same idea:
- Save your funds — honeypot, mint-authority, and sanctions/malicious-address detection before you sign.
- Save your time — one scan across four blockchain ecosystems, multiple independent data sources at once where available.
- Save your trust — every check names its source; a PASS is never presented as a guarantee.
- Save the regret — the newest checks exist to catch exposure a user would otherwise only discover after the money has already moved.
The wordmark above reflects this directly: four instances of the word, each weighted differently, the last resolving into the brand's accent color — a deliberate cascade, not a typo.
3. The Problem
It's rarely "the market crashed." More often, it's smaller and preventable: a token that turns out to be unsellable, built that way from the start. A wallet connected to a project without understanding what permission was just granted. Funds sent to an address that turns out, on public record, to be sanctioned — discovered only when an exchange freezes the deposit.
None of this requires bad luck. It requires the absence of one thing: a clear signal before the decision, not an explanation after. Price charts show what already happened. Institutional compliance platforms are often genuinely good, but sold through enterprise contracts — confirmed directly against how those vendors actually sell today, not assumed. There's very little built for the space in between.
4. What's Covered
| Ecosystem | Coverage |
|---|---|
| EVM — 14 chains | Ethereum, BNB Smart Chain, Polygon, Arbitrum, Optimism, Base, Avalanche, Fantom, zkSync Era, Linea, Scroll, Blast, Mantle, Gnosis. Full token and wallet screening. |
| Solana | Native security model — mint/freeze authority, metadata mutability, transfer hooks — plus liquidity data (pool count, TVL, LP-lock status) shown as context. Wallet screening included. |
| Sui | Token security only — the data provider doesn't yet return liquidity or holder data for Sui, so scope matches what's actually available. |
| TRON | Token security, verified to share EVM's data schema rather than assumed to. Address-format collision odds with Solana were calculated (~1 in 400 quadrillion), not waved away. |
Evaluated, not built: Aptos is named in the data provider's marketing material, but no verifiable technical endpoint could be confirmed — so it isn't claimed as supported. Address type is detected automatically across all four ecosystems; the four formats don't overlap by construction.
5. Wallet-Risk Intelligence, in Three Layers
Layer 1 — Malicious-address screening (EVM, Solana): sanctions, phishing, theft, money laundering, mixer exposure, dark-web and cybercrime association.
Layer 2 — The Chainalysis Sanctions Oracle: a free, on-chain smart contract, independently verified — contract address cross-checked directly on Etherscan, function selector computed and confirmed against the real deployed bytecode, not assumed. Live on 8 of its 9 deployed chains here. One honest limitation: an independent review found real gaps — over 90 days in one case — between a designation taking effect and the oracle reflecting it. Reported as a match against the oracle, not an unconditional real-time guarantee.
Layer 3 — Recent counterparty checking: a bounded, disclosed window of recent token transfers cross-checked against the same oracle. Not transaction history — that capability doesn't exist at the protocol level for any chain — and doesn't see native-asset transfers. One sanctioned counterparty moves the result to caution, not an automatic fail; that override stays reserved for the wallet's own address being directly designated.
6. Why It Can Be Trusted a Little More Than Most
Absence of evidence is never treated as evidence of safety — an incomplete check produces INSUFFICIENT DATA, not a quiet pass. One confirmed critical finding overrides everything else; accumulated weak signals can never outvote it. Every chain is evaluated on its own native security model, not a template forced across ecosystems. All of it is enforced by a 61-test automated regression suite, including tests written specifically to try to break the "weak evidence can't outvote strong evidence" rule.
7. What It Isn't
A clean result isn't a safety guarantee — it means nothing was found among what was actually checked. Addresses are pseudonymous, and interacting with a flagged one is not proof of wrongdoing. Coverage differs by chain, and the interface says which chain supports which check rather than pretending otherwise.
8. Glossary
- Wallet
- Holds the keys controlling your crypto; lets you send, receive, or interact with it.
- Private key
- A secret that proves ownership and moves funds. Never share it — not with SaveSaveSaveSave, not with anyone.
- Smart contract
- Self-executing code on a blockchain that defines how a token or app behaves.
- Honeypot
- A token built so it can be bought but not sold.
- Mint authority / mint function
- The ability to create new supply after launch. Not automatically dangerous — worth knowing regardless.
- Sanctions oracle
- A publicly callable smart contract that answers whether an address is currently sanctioned — free, on-chain, no account required.
- Counterparty
- An address that a wallet has directly transacted with. Exposure to a risky counterparty is not the same claim as the wallet itself being risky.
- Read-only access
- Permission to view, never to change, move, or spend.
9. Closing: The Promise
Most tools in this space ask for trust. This one is built to need less of it.
Verified, because a tool asking to be trusted has an obligation to earn it — every technical claim in this document was checked against a primary source before being written down. Constantly improving, because the risk landscape doesn't hold still, and neither should the tool built to read it.
This whitepaper is a living document. It will evolve as the product evolves.