Technical documentation for the SATO protocol.
This documentation covers the protocol architecture, bonding-curve monetary design, reserve model, research notes, security interpretation, and listing information for scanners, wallets, explorers, and token information platforms.
| Component | Address / Role |
|---|---|
| SATO ERC-20 | 0x829f4B62EEBE12Af653b4dD4fFc480966F7d7f09 |
| SatoHook | 0x0000f07d2B5F1Ddf3244b8780F972f306EFd2888 |
| SatoSwapRouter | 0x06A645079cd4F3Bb38FfaD47f92180B8041145E3 |
| Uniswap v4 PoolManager | 0x000000000004444c5dc75cB358380D2e3dE08A90 |
- Security Overview
- Threat Model
- Trust Model
- Security Guarantees
- False Positive Analysis
- Scanner Compatibility
- Public Review Checklist
For a complete technical understanding of SATO, start with:
For listing submissions, wallet metadata, scanner review, or explorer context, use:
After that, review the research and security sections for deeper economic, formal, and scanner-related analysis.
Builders who want to study or independently reimplement the protocol should read Forking and Independent Implementations before copying any source. Public verification and source availability do not, by themselves, establish an open-source license.
SATO uses a bonding-curve issuance model rather than a standard fixed-supply ERC-20 launch.
Minting and burning are expected protocol behavior and are routed through the verified SatoHook contract. The verified SatoSwapRouter is an execution router for direct curve buy and sell calls; it does not control issuance, reserve custody, or curve pricing.
This documentation is not a security audit. Users and reviewers should independently verify deployed contracts, source code, on-chain state, market liquidity, and transaction behavior.