LIVE · SDK 0.1.4

Docs · Case study

CASE STUDY · DIAMOND HANDS CARRY · TESTNET

Diamond Hands Carry

Diamond Hands runs a BTC carry vault with a short perp leg on Hyperliquid. The vault books its funding by measuring it on-chain. PerpBrain checks every one of those entries against Hyperliquid's own funding record and publishes a receipt anyone can re-run.

TESTNET data. These are reconciliation results, not returns. Risk disclosure.

Why it matters

A carry vault lives or dies on its funding books. If the vault credits more funding than the venue paid, someone is owed money that isn't there. If it credits less, users are short-changed. The vault can't mark its own homework, so an outside check is worth having, and it is cheapest to build while the vault is still on testnet.

How the check works

PerpBrain only reads public data. It holds no Diamond Hands keys and sees nothing beyond what is on-chain and on the venue.

Results

CheckPeriod (Asia/Qatar)Result
Hourly windows, booked vs venue3 Nov 02:10 to 16 Nov 10:00293 of 293 match, largest difference 0.000000 USDC
Daily totals, booked vs venue2 Oct to 8 NovRunning total matches to the micro-USDC at every day end from 28 Oct, when hourly booking began
Split identity (liquidity share + fee + to loans = measured)2 Oct to 16 NovHolds on all 415 entries
Funding anomalies flagged by the vault2 Oct to 16 NovNone

What the check found

The books are clean. Two things stood out, and both are about the keeper rather than the accounting. After the first test trades on 2 Oct, the vault went 26 days without a funding entry, until 28 Oct. There was a 12-hour pause on 8 Nov too. Each time, the next entry booked the whole gap in one go, and that single entry matched the venue exactly. No funding went missing, but an hourly check like this is how a stalled keeper gets spotted the same day.

Hyperliquid keeps hourly funding rows for about a week and rolls older rows into daily totals, so earlier history is checked day by day. Updated 16 Nov 2026.

Check it yourself

Allocators and auditors can follow the step-by-step guide: Independent verification of Diamond Hands Carry's Hyperliquid activity (PDF). To have an agent run the same check, give it perpbrain.com/verify-dh.md. Download the receipt and its inputs (the hourly record), or the daily running totals. Drop both files into perpbrain.com/verify, or run:

pip install "perpbrain-read>=0.1.3"
python -c "import json;from perpbrain_read.sim.funding_recon import verify_recon_receipt as v;print(v(json.load(open('receipt.json')),open('inputs.json','rb').read()))"

Vault on HyperEVM testnet (chain 998): 0x5310AE7e24835cC6f7740db18ebbF9f3aB422554.

Verify with your AI agent

TESTNET

Paste this into your own agent. It will follow the published instructions and check the vault's Hyperliquid activity without trusting Diamond Hands or Perp Brain.

Independently verify the Diamond Hands Carry vault's Hyperliquid activity, without trusting Diamond Hands or Perp Brain. Read and follow https://perpbrain.com/verify-dh.md exactly. It lists every file, API call and command you need. Run every check yourself, then report: the receipt verification result (VERIFIED or MISMATCH), whether the vault's booked funding matches what Hyperliquid paid over the receipt window, whether the vault's on-chain records match the receipt, and any step you couldn't complete or any difference you found.

What comes next

A fresh receipt every week, so the hourly record never rolls up. Then per-loan allocation checks and an owed-versus-held solvency check, both before mainnet.