TradeGuild

How it works

Prove it once. Get followed. Stay invisible.

Three steps for a caller, one tap for a follower.

Paste your wallet

Your phone reads Base, Robinhood Chain and Ethereum directly and computes your record with a published method. Every trade, losers included.

Seal it on the phone

The address is hashed with a secret salt, every transaction is pinned in a Merkle root, and the record gets a fingerprint. Only numbers and hashes leave the device.

Get followed

Followers see your multiple, win rate and calls. When you trade, their in-app wallet mirrors it through Matcha's routing. Nobody can copy your wallet, because nobody has it.

Feed

A tape of calls you can check, not screenshots you have to trust.

Every call is logged with the market cap when it was made, the target, and how it closed. Tap one and your phone re-hashes the caller's sealed record and checks the verifier's signature.

Sealed record

A multiple, a win rate and every position, computed from the chain and frozen by hash. Change one trade and the seal breaks.

Live calls

Entry level, target, result. Closed calls stay on the tape forever, including the ones that went to zero.

Mirror with one tap

Pick an allocation. Each trade is sized as your allocation times the share of capital the caller used, capped per trade, signed on your phone.

Self-custodial

Your USDC sits in a wallet whose key never leaves your Keychain. Export it any time. TradeGuild never holds funds.

The seal

What gets published, and what never does.

Published: the numbers and three hashes. Never: the address, the salt, or the transaction list. Those stay in the caller's Keychain, and the caller can hand them to an auditor of their choosing to reopen the seal.

Honest limit: on-device sealing proves the record has not been changed and can be reopened on demand. It does not by itself prove the caller pointed the app at a wallet they trade. A zero-knowledge proof of the computation removes that, and it is the next milestone rather than a claim.

Wallet commitment · sha256(address:salt)

b45a9fbc73422ed29f250a662d3529575469d839ca179dfc3d5be1eb7f4b7f63

Merkle root · 472 transactions

ddfa66750207de8a83145ecf3d7fbc88265582b30f0eee7f16a8301df8901ff5

Record fingerprint · sha256(published bytes)

19787f5bb387bb811c121c91f6c47b409eef92636c8299380e5db3e572aa1a9d

✓ Checks out · verified on this device · signature valid

Live example: the first sealed caller, @MemeIndexer.

Questions

Straight answers.

Why not just publish the wallet?

Because a public wallet is copy-traded within minutes and the trader gets nothing. Sealing gives followers accountability and gives the caller a reason to be followed here.

Does TradeGuild ever see my address?

No. The record is computed and sealed on your phone. The server refuses any payload containing an address. We cannot store what we never receive.

How do mirrors execute?

Quotes come from the 0x Swap API, the engine behind matcha.xyz. The transaction is signed on your phone and sent to Base. Mirrors run while the app is open and on background refresh.

Is this financial advice?

No. It is a tool for following people who chose to show their record. Memecoins routinely go to zero. Size like it.

Can a bad caller fake a record?

They can point the app at a wallet that is not theirs. Followers can see that, ask for an audit, and leave. The record itself cannot be edited after sealing. Zero-knowledge proof of ownership is what closes this fully.

Which chains?

Records read Base, Robinhood Chain and Ethereum. Mirrors execute on Base today. Robinhood Chain is quoted and next.

Copy sealed callers,
not wallets.