Proven skill, no address, no liquidation price.
1.1Proves
1.2Hides
1.3Signs
$UNDOX
Prove the record. Keep the address.
Undoxed reads a Hyperliquid account's public history inside an enclave and signs a certificate of the results. The address never leaves the attester.
Return, worst drawdown, months active, trade count and volume tier, computed from the account's fills, funding and account-value history on Hyperliquid's public info API. Figures are bucketed so they cannot be matched back to an address.
2.1Source
2.2Bucketed
2.3Tiered by
You sign a message for each address inside an enclave (Intel TDX or AWS Nitro). The enclave reads the public history, computes the stats and signs the certificate. Its code is open source, and remote attestation shows what it ran.
5.1Connect
Open the web app and add each Hyperliquid address you trade from.
5.2Sign
Sign to prove control of this address. The address is read inside the enclave and is never published. A signature that does not match the connected address gets no certificate.
5.3Read
The enclave pulls fills, funding and account-value history from Hyperliquid's public info API.
5.4Compute and sign
Stats are computed, bucketed and signed into a certificate bound to a fresh pseudonymous ID. The HyperEVM registry stores only its hash.
5.5Show and refresh
You get a public certificate page and a badge for your X bio. Refresh weekly, or the certificate lapses.
5.6Phase 2
zkTLS proofs of the API responses replace the enclave. Until then this is an enclave you trust, not a zero-knowledge proof.
Sleuth accounts post Hyperliquid whales' entries and liquidation prices as soon as an address is known. Traders with real records keep their addresses quiet, so followers are left with screenshots.
6.1What gets posted
6.2Recent cases
6.3What is missing
Every fill on Hyperliquid is already public, so the record can be proven. What is missing is a way to separate the proof from the address.
Prop firms and vault platforms check a certificate through the allocator API, only with the trader's consent, and pay per check. A record they can verify replaces the paid challenge as the first filter.
7.1Check
7.2Replaces
7
$UNDOX
$UNDOX starts as points. The product runs on fees without it, so the supply stays small.
| Ticker | $UNDOX |
|---|---|
| Type | Points that convert to a token with a fee share. Becomes the attester stake once attesters are independent. |
| Chain | Hyperliquid. Certificate registry on HyperEVM. |
| Points go to | Traders who certify and keep certificates fresh, and allocators who integrate the check. |
| Launch | Fair launch on HyperEVM, paired with HYPE, only once about 1,000 certificates are live (planned threshold, not a count). |
| Fees | Allocators pay per check, with the trader's consent. Check fees fund buybacks. |
| Phase 2 | Independent attesters stake $UNDOX and can be removed for proven misreporting. |
| Status | Not launched. No contract deployed. |
9.1Cherry-picking
Someone with many addresses could certify only the lucky one. Account age, trade count and the combined-address flag are on every certificate, and history-length rules have to stay strict.
9.2Enclave trust
One leaked address-to-certificate mapping would end the product, and enclaves have had side-channel attacks. Open code and remote attestation help. An independent audit is still needed and has not been done.
9.3Inference
Exact stats plus public data could narrow down an address. Stats are bucketed for that reason, so they say less.
9.4Prop firm incentives
Prop firms earn from challenge fees. They may not fast-track verified traders, which would leave only the status use.
9.5Willingness to pay
Status alone may not sustain the token. The token is the thinnest part of the design.
9.6Venue privacy
Hyperliquid or a rival venue could add native position privacy, such as hidden orders, and shrink the problem.