$JLP is a gem! $JLP — I tested JLP/USDC limit orders on Jupiter and found a useful UX issue.

After submitting a limit sell, the interface returned “Order status is unknown” and could not immediately confirm whether the order was placed. The order later executed successfully. I also noticed that the order marker temporarily disappeared from the chart and later reappeared.

Suggestion: make the order status in “My Orders” the single authoritative status, and clearly distinguish Pending / Confirmed / Executed / Failed. A persistent sync indicator on the chart would also help.

This would reduce the risk of users submitting duplicate orders when the UI is still synchronizing.

$PYTH SDK onboarding gap: the official hermes-client README still teaches the keyless setup that now returns 401.

What I tried (4 Oct 2026): copied the Quickstart from pyth-crosschain apps/hermes/client/js/README.md — new HermesClient("https://hermes.pyth.network", {}) — and also hit the REST endpoint directly:

curl -i "https://hermes.pyth.network/v2/updates/price/latest?ids[]=0xef0d8b6f...b56d"

-> HTTP 401, body "unauthorized".

The docs banner explains it (Hermes requires an API key since the Aug 26, 2026 Pyth Core upgrade), but the README's Quickstart (line 26), the example-runner command, and the "Pyth offers a free public endpoint at hermes.pyth.network" line (line 93) never mention auth. The SDK already supports keys: HermesClientConfig has accessToken, sent as Authorization: Bearer (and as ACCESS_TOKEN for SSE/WebSocket) in hermes-client@3.1.0.

Suggestion: update the Quickstart to new HermesClient(endpoint, { accessToken: process.env.PYTH_API_KEY }), add the key-signup link beside it, and fix the "free public endpoint" sentence + example command. Right now a builder copying the README hits a 401 that looks like an outage.

Question: should SDK users switch the base URL to the upgraded pyth.dourolabs.app/hermes, or does hermes.pyth.network stay valid once a key is set?

$PYTH Answering @wolfur's question below with a test. I build small Python market dashboards, so today I tried both paths for a free once-a-day price.

1. Hermes: /v2/price_feeds still answers without a key, but /v2/updates/price/latest returns 401 with a plain-text "unauthorized", as described.

2. On-chain push feed: I read the sponsored SOL/USD account (7UVimf…jLiE) straight from the public Solana RPC with a short standard-library Python script: one getAccountInfo call, then decode the PriceUpdateV2 layout. No key, no SDK. Result: SOL/USD 119.80 USD ± 0.01.

What I noticed: the price was already 26 s old when I read it, so the sponsored feed doesn't refresh every slot. Fine for a daily script, not for a perp.

Suggestion: the 401 body could say "API key required" and link the sponsored push-feed accounts per chain with a minimal read example. That one link would have saved me the detour.

Question for the team: which Solana feeds are guaranteed to stay sponsored, and what update cadence or deviation threshold do they follow?