Protocols
KittenSwap swaps on Hyperliquid, decoded
rotki turns your KittenSwap activity on Hyperliquid into readable swap events, validating each pool against the KittenSwap factory so only genuine KittenSwap trades get tagged.
Supported features
- KittenSwap swaps on Hyperliquid decoded as paired spend/receive trades rather than two loose token transfers.
- Pools are verified against the KittenSwap factory on first sight, so a look-alike pool emitting the same event is not mislabelled as KittenSwap.
- New pools are picked up automatically - there is no fixed pool list to wait on between releases.
Limitations
- Only swaps are decoded. Providing liquidity to KittenSwap is not decoded as a KittenSwap-counterparty event and no KittenSwap LP balance is queried.
- Verifying a pool requires an on-chain call to the factory the first time rotki sees it, so it depends on your Hyperliquid RPC endpoint being reachable.
Setup
- 1In rotki, open Blockchain Balances → Hyperliquid → Add address.
- 2Open History and let the transaction sync run. KittenSwap swaps are decoded automatically.
Frequently asked questions
Do I need to add new KittenSwap pools manually?
No. rotki checks unknown pools against the KittenSwap factory the first time it sees them, so pools created after the release still decode correctly.
Are my KittenSwap LP positions valued?
Not currently. The integration covers swaps; liquidity provision is not decoded as a KittenSwap event, and LP token movements appear as ordinary transfers.
Where do the Hyperliquid queries go?
rotki runs locally and talks directly to the Hyperliquid RPC endpoint you configure - the public default, a third-party provider, or your own node. Nothing passes through a rotki-operated server.