SilentTransfer
Private transfer infrastructure for public blockchains

Website · GitHub · X · Documentation · Main Repository · Protocol (sthood)

CA: 0x01f44ADdf4af1DB2d9016a4992FFef5163648c0a

SilentTransfer is privacy-oriented private transfer infrastructure for public EVM chains. It provides a professional console and API for private receive, private transfer, payment discovery, and settlement—without KYC in the product path.

On a public blockchain, a normal wallet-to-wallet send exposes the recipient’s primary address immediately. SilentTransfer routes value to a fresh one-time destination, then lets the intended recipient claim into their wallet. The result is stronger recipient privacy than a plain transfer—while remaining honest about limits: chain explorers still show public transactions, and privacy today is partial, not full anonymity or mixer-grade unlinkability.

The protocol asset is sthood (hard-capped at 1,000,000,000). Official contract address:

0x01f44ADdf4af1DB2d9016a4992FFef5163648c0a

Allocation policy targets a Virtual-style fair launch: community-majority supply with a small protocol share for operations—0% VC.

Public blockchains are transparent by design. That transparency is excellent for settlement and auditability—but brutal for ordinary private payments.

• No private receive path — A normal send lands on the recipient’s public address; anyone watching sees who got paid.
• No product-grade private transfer UX — Privacy research exists (stealth addresses, standards), but operators and users lack a clean console + API to use it day to day.
• No KYC-free product rail — Many “privacy” products force identity gates. SilentTransfer keeps KYC out of the product path.
• No honest status — The market is full of overclaims. We document what is private now vs what is still roadmap.
• No fair protocol asset model — Community-first supply with hard-capped sthood, not VC-dominated tokenomics.

Sender                         Recipient
   |                               |
   ▼                               ▼
Connect wallet              Connect wallet
   |                               |
   ▼                               ▼
Private send ──►  one-time address  ◄── scan / discover
                  (fresh EOA fund)
                       |
          ┌────────────┼────────────┐
          ▼            ▼            ▼
   On-chain fund   API announce   Claim path
   (public tx)     (routing +     (recipient
                    metadata)      sweeps)
                       |
                       ▼
              Funds on recipient wallet

1. Connect — Sender and recipient use a standard EVM wallet on the supported network.
2. Send — Sender initiates a private transfer; value goes to a new one-time address, not the recipient’s public wallet.
3. Announce — The app records payment context for the intended recipient (API-assisted discovery today).
4. Discover — Recipient scans / opens receive flow to see claimable payments.
5. Claim — Recipient claims; funds move from the one-time address to their wallet.
6. Settle — On-chain settlement as configured (testnet may simulate settlement until a full bundler/paymaster path is live).

Honesty note: Privacy is partial—better than plain A→B, not “untraceable.” See privacy status in the main repository.

SilentTransfer is a full-stack monorepo: web console, API, and Solidity contracts.

User layer — Next.js console for private send/receive, scanner, transactions, analytics, docs, and the sthood protocol page. SIWE-style session auth where enabled.

Core layer — FastAPI services for registrations, announcements, stats, health, and relay/scanner paths. PostgreSQL (or SQLite in light environments) for operational state.

Infrastructure layer — EVM smart contracts (Hardhat): registry / messenger-oriented surfaces, sthood token, paymaster scaffolding. Primary network today: Robinhood Chain Testnet (46630). Not affiliated with Robinhood Markets, Inc.

Tech stack: Next.js · TypeScript · Tailwind · wagmi/viem · FastAPI · PostgreSQL · Solidity · Hardhat · ethers.

Fees currently 0%; a small sponsored-claim fee is planned for protocol operations. Details: silenttransfer.com/silent.

The main codebase is open for inspection and contribution. Developers can run the stack locally, deploy contracts to testnet, and integrate against the public API patterns documented in-app.

To get started:

• Clone the main repository
• Follow the installation guide in the root README
• Run API + web locally (Node 20+, Python 3.11+)
• Read docs/PRIVACY_STATUS.md before making privacy claims in forks or integrations
• Review SECURITY.md for reporting practices

Live (testnet console) — Private send / receive flow with real on-chain funding to one-time addresses · claim path · scanner · transactions · analytics · docs · sthood tokenomics page · honest partial-privacy labeling.

Building — Stronger client-held claim keys · deeper ERC-5564 / ERC-6538 alignment · batch 1→many private send · paymaster / gasless claim UX · privacy score backed by real signals · SDK polish.

Future — Mainnet settlement with full operator hardening · multi-chain · optional stronger unlinkability layers where product and compliance allow · audits and production checklist completion.

• Website: https://silenttransfer.com
• Documentation: https://silenttransfer.com/docs
• Protocol (sthood): https://silenttransfer.com/silent
• sthood CA: 0x01f44ADdf4af1DB2d9016a4992FFef5163648c0a
• Main Repository: https://github.com/SilentTransfer/silenttransfer
• Organization: https://github.com/SilentTransfer

© 2026 SilentTransfer · Protocol asset sthood