HyperEVM system transactions have different hashes depending on where you look(d4mr.com)
d4mr.com
HyperEVM system transactions have different hashes depending on where you look
https://d4mr.com/posts/hyperevm-phantom-hash/
https://d4mr.com/posts/hyperevm-phantom-hash/
Turns out: Hyperliquid publishes block data to S3, and system transactions don't have hashes. nanoreth (which explorers use) has to recompute them, but uses a different encoding convention. they stuff the system address into the signature field as a "pseudo transaction."
Neither is wrong exactly, but if you're building tooling you need to know which convention your data source uses.