该用户的聊天记录定位。
Hi <@859061718114238474> <@486268131560390657> feel free to use our Quicknode Hyperliquid Testnet Faucet faucet[dot]quicknode[dot]com And select Hyperliquid testnet
Hi <@859061718114238474> <@486268131560390657> feel free to use our Quicknode Hyperliquid Testnet Faucet faucet[dot]quicknode[dot]com And select Hyperliquid testnet
You get all the trades via WebSockets or gRPC (even faster than WebSockets) Dm me, and we can hook you up with a free trial
You get all the trades via WebSockets or gRPC (even faster than WebSockets) Dm me, and we can hook you up with a free trial
We don't break RTT out per-method yet so I can't give you a clean `eth_sendRawTransaction` number, but happy to set you up with a trial so you can benchmark our endpoint against your own node!
We don't break RTT out per-method yet so I can't give you a clean `eth_sendRawTransaction` number, but happy to set you up with a trial so you can benchmark our endpoint against your own node!
That 300-800ms is the submission RTT (the node accepting your tx into the mempool), not block finalization. Those are two separate clocks The spikes are almost certainly cold connections If you're opening a fresh TCP/TLS handshake per call, that alone can be 200-400ms. To fix use persistent connections (keep-alive/HTTP2) or a websocket, and pre-sign your txs ahead of time so you're not doing that work in the hot path Geography also matters more than people realize, all 24 HL validators are in AWS Tokyo (ap-northeast-1) If you're in EU/US, you're already 200ms+ behind someone colocated there, and a shared public endpoint adds more on top. A dedicated endpoint closer to Tokyo helps P.S. Also double-check you're on small blocks (default, ~1–2s) and set a real priority fee cause both affect inclusion speed independently of the broadcast latency
That 300-800ms is the submission RTT (the node accepting your tx into the mempool), not block finalization. Those are two separate clocks The spikes are almost certainly cold connections If you're opening a fresh TCP/TLS handshake per call, that alone can be 200-400ms. To fix use persistent connections (keep-alive/HTTP2) or a websocket, and pre-sign your txs ahead of time so you're not doing that work in the hot path Geography also matters more than people realize, all 24 HL validators are in AWS Tokyo (ap-northeast-1) If you're in EU/US, you're already 200ms+ behind someone colocated there, and a shared public endpoint adds more on top. A dedicated endpoint closer to Tokyo helps P.S. Also double-check you're on small blocks (default, ~1–2s) and set a real priority fee cause both affect inclusion speed independently of the broadcast latency
`openInterest` in `metaAndAssetCtxs` is one-sided. It's the total size of open positions on a single side, not the sum of longs + shorts.
`openInterest` in `metaAndAssetCtxs` is one-sided. It's the total size of open positions on a single side, not the sum of longs + shorts.
Hey <@410821483133141003> saw your msg in the <#1030196642508447785> channel Quicknode's HL gRPC endpoints might be worth a look for this real-time streams for trades, orders, liquidations without spinning up your own node. not free but probably cheaper than whatever's causing the pain rn
Hey <@410821483133141003> saw your msg in the <#1030196642508447785> channel Quicknode's HL gRPC endpoints might be worth a look for this real-time streams for trades, orders, liquidations without spinning up your own node. not free but probably cheaper than whatever's causing the pain rn
Hyperliquid