秋田预测市场 · Discord 审计

Treasurio 整合 Hyperliquid 时针对现货映射和价格精度的确认

2026-07-15 · Hyperliquid · 3 条相关讨论

Tom Bombadil 2026-07-15 00:51:59

Hi Hyperliquid team, We're the team behind Treasurio (treasurio.xyz). We're building a workspace for traders: instead of juggling ten separate tabs, you can lay out your positions, charts, order book, and data feeds side by side on a single infinite canvas. In short, think "Notion for trading" rather than "yet another analytics terminal." We recently integrated Hyperliquid futures into this canvas: live prices, order book, funding rates, liquidity, slippage, and fee data now run as widgets alongside the trader's other tools. The integration went smoothly, and we appreciate the documentation. We'd like to confirm our approach with you on two points: 1. Spot coverage. We resolve spot symbol mapping via spotMeta and are aware of the frontend remappings (e.g. BTC/USDC maps to UBTC/USDC). However, when we reviewed the fixed list of ~29 coins we track on our platform, we found that only 4 of them have an actual counterpart on Hyperliquid spot. Since we couldn't offer our users a meaningful experience with that coverage, we've decided to postpone the spot integration for now. If there's a more comprehensive spot market reference we may have missed, we'd appreciate it if you could point us to it, and we'd be happy to revisit our decision. 2. Price precision. We understand the 5 significant figures rule and the MAX_DECIMALS minus szDecimals constraint. Currently, we display prices exactly as returned by the API, without any additional rounding or formatting on our side. Is relying directly on the precision returned by the API the right approach, or are there other considerations we should keep in mind on the display side? We'd appreciate your confirmation. More broadly, we'd love to stay in touch as we continue improving our Hyperliquid support. If there's a developer channel or point of contact for integrators, we'd be grateful if you could point us in the right direction. Thanks, The Treasurio Team treasurio.xyz

Hi Hyperliquid team, We're the team behind Treasurio (treasurio.xyz). We're building a workspace for traders: instead of juggling ten separate tabs, you can lay out your positions, charts, order book, and data feeds side by side on a single infinite canvas. In short, think "Notion for trading" rather than "yet another analytics terminal." We recently integrated Hyperliquid futures into this canvas: live prices, order book, funding rates, liquidity, slippage, and fee data now run as widgets alongside the trader's other tools. The integration went smoothly, and we appreciate the documentation. We'd like to confirm our approach with you on two points: 1. Spot coverage. We resolve spot symbol mapping via spotMeta and are aware of the frontend remappings (e.g. BTC/USDC maps to UBTC/USDC). However, when we reviewed the fixed list of ~29 coins we track on our platform, we found that only 4 of them have an actual counterpart on Hyperliquid spot. Since we couldn't offer our users a meaningful experience with that coverage, we've decided to postpone the spot integration for now. If there's a more comprehensive spot market reference we may have missed, we'd appreciate it if you could point us to it, and we'd be happy to revisit our decision. 2. Price precision. We understand the 5 significant figures rule and the MAX_DECIMALS minus szDecimals constraint. Currently, we display prices exactly as returned by the API, without any additional rounding or formatting on our side. Is relying directly on the precision returned by the API the right approach, or are there other considerations we should keep in mind on the display side? We'd appreciate your confirmation. More broadly, we'd love to stay in touch as we continue improving our Hyperliquid support. If there's a developer channel or point of contact for integrators, we'd be grateful if you could point us in the right direction. Thanks, The Treasurio Team treasurio.xyz

routinedisrupted 2026-07-15 00:53:46

answer for 1. is covered in the docs. Should call spotMeta to find out how different assets are encoded * For Spot, coin should be PURR/USDC for PURR, and @{index} e.g. @1 for all other spot tokens where index is the index of the spot pair in the universe field of the spotMeta response. For example, the spot index for HYPE on mainnet is @107 because the token index of HYPE is 150 and the spot pair @107 has tokens [150, 0]* https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/info-endpoint

answer for 1. is covered in the docs. Should call spotMeta to find out how different assets are encoded * For Spot, coin should be PURR/USDC for PURR, and @{index} e.g. @1 for all other spot tokens where index is the index of the spot pair in the universe field of the spotMeta response. For example, the spot index for HYPE on mainnet is @107 because the token index of HYPE is 150 and the spot pair @107 has tokens [150, 0]* https://hyperliquid.gitbook.io/hyperliquid-docs/for-developers/api/info-endpoint

Tom Bombadil 2026-07-15 01:01:49

Thank you so much!

Thank you so much!