Yaugourt.hl@Yaugourt
Yesterday I posted about HIP4 being the first HIP to use HyperEVM.
Full research → liquidterminal.xyz/hip4/home
HIP4 has no official documentation. No verified source. No ABI. So we reverse-engineered the contract from bytecode and calldata on testnet.
What we mapped:
→ Full reconstructed ABI (selectors, signatures, access control)
→ Every event (DepositReceived, Claimed, ContestCreated, ContestFinalized, MerkleRootPublished)
→ All revert strings mined from bytecode
→ Storage layout (owner, mappings, initialization flags)
→ Complete contest lifecycle: createContest
→ deposit
→ publishMerkleRoot
→ claim
→ sweepUnclaimed
→ Bridge architecture L1↔EVM (asset index formula, outcome token mapping)
→ Real decoded testnet transactions
→ JS + Python code examples
Some findings:
- Pre-deployed at genesis, not a standard deployment
- renounceOwnership always reverts, admin is permanent by design
- Merkle-based claims, 0.9% platform fee on reward pool
- Three market types: custom, priceBinary, recurring
liquidterminal.xyz/hip4/home
Testnet only.
This is v1, early test from the team, raw design, and some things might be off. Nothing is final.
If you spot errors or have insights, feedback is very much appreciated.
Hyperliquid.