Outbound transfer of 48,200 USDC to an account first funded three hours earlier. Linking the transaction so others can compare it against the earlier reports on this log.
Not a verdict.A record.
Report suspicious wallet activity with proof attached. Evidence stacks publicly — nobody decides for you.
- Transaction hash required
- No scores, no verdicts
- Wallets can respond
We have read the reports on this log and will publish a signed breakdown this week.
Inbound funds arrived from an account that also appears in two other evidence logs. Linking the arrival transaction; the origin account is visible in the instruction data.
Outbound transfer to a newly funded account, followed by a split across 14 further accounts within nine minutes. Each hop is visible from the linked signature.
tx hash
MpmpV…A3nsv
corroborations
12
field that cannot be skipped
A transaction hash, attached to every report.
verdict labels, anywhere
Only reported, evidence, unverified, corroborated.
planned stake per report
Refunded on corroboration. Not live.
phases on the public roadmap
From example surface to live accountability.
The premise
Aclaimwithoutasourceisjustnoise.WitnessProtocolkeepsthetransactionattachedtoeveryreport,keepsthelanguageprecise,andleavestheconclusiontoyou.
How it works
Four steps from observation to public record.
Scroll through the lifecycle of a single report.
1Report with evidence
Attach a transaction hash and write only what the record can support. No source, no report.
Step 01 · file
Wallet
7gBX…9xQ2
Transaction hash · required
MpmpVxKama…7t9A3nsv
Note
Outbound transfer followed by a split across 14 accounts.
2Stake your signal
Filing commits 50 $WTNS in the planned live protocol. It shows you stand behind the evidence, and it is refunded when others corroborate it.
Step 02 · stake
50 $WTNS
Staked on filing. Refunded on corroboration.
Planned for the live protocol. This proof of concept does not move funds.
3Corroborate or slash
Other reporters can add agreement to the same evidence. Reports found to be made in bad faith can lose their stake. Planned, not live.
Step 03 · corroborate
12 corroborations
Agreement among reporters, nothing more.
4The wallet can respond
The wallet can post a signed response. It sits in the timeline at its real chronological position, never buried below the reports.
Step 04 · respond
The transfers on 18 April were treasury rebalancing. A signed breakdown follows this week.
22 APR 2026 · signed by wallet
Placed in true chronological order.
Anatomy of a card
Everything a report carries, and nothing it doesn’t.
Hover a row to see where it lives on the card.
Outbound transfer to a newly funded account, followed by a split across 14 further accounts within nine minutes. Each hop is visible from the linked signature.
18 APR 2026 · 14:32 UTC · by rptr_4f2a
Evidence, stacked
A public log, in the order it happened.
Reports and wallet responses share one timeline. A response sits exactly where it was posted, never buried at the bottom.
We have read the reports on this log. The transfers on 18 April were treasury rebalancing between wallets operated by the same team. We will publish a signed breakdown of the destination accounts this week.
Outbound transfer to a newly funded account, followed by a split across 14 further accounts within nine minutes. Each hop is visible from the linked signature.
Inbound funds arrived from an account that also appears in two other evidence logs. Linking the arrival transaction; the origin account is visible in the instruction data.
The most important thing on this site
Unverified means unverified.
Every card here carries the same label: community-reported, unverified. Nothing on Witness Protocol is a verdict, a score, or a conclusion. It is a public record of claims, each one pinned to a transaction you can inspect yourself.
A report is a claim
It records what someone observed in a linked transaction. It is not a finding.
Corroboration is agreement
A count of reporters who found the same evidence worth recording. It never turns into a label.
Verify independently
Every card links to the transaction. Open it, read it, and decide for yourself.
Principles
Six rules the whole interface is built around.
They are written into the design, the copy and the protocol itself.
Evidence first
A report without a linked transaction hash cannot be filed. The source travels with the claim, always.
Precise language
Reports describe what a transaction shows. They do not infer intent, assign labels, or declare outcomes.
Public by default
Every report, corroboration and response is visible to everyone, in order, with nothing quietly removed.
Skin in the game
In the planned live protocol, filing and corroborating both stake $WTNS, so careless reports have a cost.
Right of reply
The wallet can respond in its own voice. Responses sit inline in the timeline, never in a footnote.
No scores
There is no risk rating and no ranking. Summaries are counts, framed neutrally: reports filed, reports corroborated.
Who it is for
Built for people who read the transaction.
Community observers
You noticed a pattern on-chain. File it with the transaction attached so the next person does not have to rediscover it.
Wallet owners
See every report that references your wallet, read the evidence, and respond in the open with a signed statement.
Researchers & readers
Follow the linked transactions, compare reports side by side, and judge the evidence on its own merits.
Questions
Plain answers to the obvious questions.
No. Witness Protocol is not a blocklist, a rating, or a score. It is a public log of reports, each with a linked transaction, shown in the order they were filed.
Ready when you are
Start with a transaction.
Look up the example wallet, or put your own evidence on record. Either way, the source stays attached.