Public chains are permanent ledgers
A direct A→B transfer is forever readable. Counterparties, amounts, and patterns sit on a public graph anyone can query.
Untraceable transfer · public chains
Private payouts that are harder to trace
SilentTransfer is private transfer infrastructure for public blockchains. Deposit into a vault, then pay any wallet—single or batch, any time. Recipients never open the site. Built to break the public A→B link.
Vault-based payouts Auto-receive for B Honest privacy limits
Testnet livesthood
Private vault flow
Deposit → vault balance → send single or batch. Wallet is the key.
DepositInto private vaultLive
SendOne or many walletsLive
ReceiveAuto — no claimLive
Built for untraceable-oriented private transfers
Private vaultBatch & single payoutNo recipient claimWallet as keyHonest docs
The problem
Public rails were never designed for private payments
Every direct transfer is a permanent public record. Privacy tools that force receivers through claim portals fail in the real world. SilentTransfer focuses on vault payouts that land in ordinary wallets—harder to map as a simple A→B payment.
Reused wallets build a history
Every payment from the same address deepens a profile. Private payouts need a different path than “send from main wallet.”
Claim UX kills privacy products
If the receiver must visit a site, paste codes, or set up special keys, adoption dies. SilentTransfer pays wallets directly from the vault.
Product
Everything you need to move value privately
A minimal console for vault deposit, private send, and batch payout—focused on breaking public payment graphs, not collecting identity.
Private vault
Deposit into a wallet-bound vault. Later send any amount—once or in pieces—to any address. Your connected wallet is the key. No note files to back up.
Break the public A→B link
Payouts leave the vault, not your everyday wallet. Recipients receive ETH directly—without a public one-to-one send from your known address.
Recipients never open the site
Batch or single send from the vault. Funds land in their wallet automatically. No claim step, no app install for the receiver.
Send when you choose
Deposit once. Withdraw later—different times, different amounts, one wallet or many. Timing is under your control.
Standards path (advanced)
Optional ERC-5564 / ERC-6538 stealth tooling and a shield pool remain available for power users. Docs mark what is live vs experimental.
Honest privacy docs
We document what is harder to trace today—and what still links on a public chain (amounts, timing, funding graph). No fake anonymity claims.
How it works
Three steps. Wallet is the key.
From deposit to payout in one continuous flow—designed so receivers never need the app.
Connect your wallet
Open the console and connect. Your wallet signs deposits and sends. That same wallet owns your vault balance—nothing else to store.
Deposit into the vault
Move ETH into your private vault on-chain. A small protocol fee may apply on deposit. Balance sits ready until you decide to pay out.
Send single or batch anytime
Pay one address or many. Recipients get funds in their wallet with no website visit. You control amounts and timing.
Roadmap
Live today. Building next. Honest later.
Private vault is live on testnet. Everything below is labeled Live, Next, or Later— intentions with clear status, not fake ship dates or overstated completion.
LiveNextLater
01
LivePrivate vault
Deposit into a wallet-bound vault. Single or batch send anytime. Recipients auto-receive—no claim site. Wallet is the key.
02
LiveHarder-to-trace payouts
Funds leave the vault contract, not a plain A→B send from your hot wallet. Split amounts and timing under your control.
03
LiveConsole, docs & $sthood
Minimal operations console, honest privacy docs, and sthood (1B hard cap, community-majority, 0% VC) on testnet.
04
NextStronger unlinkability
Delayed and fixed-size payout patterns, larger shared anonymity sets, and hygiene guidance against amount/timing correlation.
05
NextShield pool maturity
Testnet shield notes exist today. Production Groth16 path-hiding ships only when ceremony and product scope allow—not claimed complete.
06
NextPayroll & treasury scheduling
Recurring private batch payouts for operators and DAOs—same auto-receive model for every recipient line.
07
LaterMainnet + external audit
Production money path only after audit and hardened ops. Mainnet TVL is not claimed today.
08
LaterMulti-chain expansion
Additional networks after the primary vault path is stable and documented on the first production chain.
Protocol asset
$sthood — hard-capped. Community-majority.
Maximum supply of 1B. Community 90% · Protocol 10% · Venture capital 0% · separate team pool 0%. Community-first fair launch design.
Name / ticker
sthood
Zero VC · community-majority
Hard-capped supply
1B
1,000,000,000 max · mint above cap disabled
Contract
0x01f44A…648c0a
Set via environment after deployment
- Community90%
- Protocol10%
- VC / Team0%
Community90%
Protocol10%
VC + separate team pool: 0%
Launch: Launched on Pons launchpad: community-majority supply with a small protocol share for operations. No venture allocation and no separate team pool.
Hard cap: Maximum supply is 1B sthood. The contract does not permit minting above the cap.
Fees (current): 0% product fee on many paths; vault deposit may charge a protocol fee on-chain. Fees (planned): 0.5% on sponsored flows—for protocol operations and open-market sthood buybacks.
Product fees are currently 0%. A planned 0.5% fee on sponsored claims will fund protocol operations and open-market sthood buybacks—not venture distributions.
Scope: Exchange listings, market pricing, and live vesting contracts are outside current product claims.
Full $sthood overview
Security & trust
Privacy claims you can audit
We ship capabilities and limits with equal rigor. Harder to trace—not invisible to every analyst forever.
Testnet live · mainnet staged
Real vault deposit and send run on Robinhood Chain Testnet. Mainnet production money movement is staged and should not be assumed audited.
Documented threat model
Public metadata, amount fingerprinting, timing linkability, and vault interaction graphs—written down so operators know the real envelope.
What “untraceable” means here
Payouts leave a shared vault path rather than a plain A→B send; receivers need no app. We still disclose residual chain analysis risk. Users remain responsible for applicable law.
1
Primary flow: private vault
0
Claim steps for recipients
1B
sthood hard cap
0%
Venture allocation
FAQ
Straight answers
The questions people ask before they click Launch app—answered without spin.
Start with a private vault transfer
Connect a wallet, deposit on testnet, send single or batch. Limitations are documented. The path is real.