Crypto
Home›Crypto›Market Structure›Pyth misses oracle cutover, requires API keys for Herm…
Pyth misses oracle cutover, requires API keys for Hermes requests
Pyth warned that mismatched Hermes endpoints or on-chain contract settings can block oracle-driven price update transactions until developers update authentication and configuration.
Pyth Network missed its documented 16:00 UTC cutover deadline on Aug. 26, and added a new requirement for developers who call its Hermes price-delivery service directly: requests now need an API key, according to CryptoSlate.
While protocols that already integrate the oracle may not need to take direct action, Pyth documented that the old hermes.pyth.network address would redirect to an upgraded backend after the deadline, with authentication required. Developers can also use a new Hermes URL and pass the key as a bearer token or SDK access token, with the upgraded Hermes endpoint serving payloads intended for the upgraded Pyth Core contract.
The migration guide warns that changing the endpoint without updating the contract generation, or doing the reverse, can leave applications unable to verify price updates. In a pull-oracle design, either mismatch can stop the price-update transaction from completing until configuration is corrected.
On Sui, CryptoSlate said builders had to update both the client used to fetch price data and the on-chain Move package dependency, because integrations reference the Pyth package by object ID and the Pyth DAO could not automatically swap packages. As of a post-deadline check, there was no confirmed outage, stale-price event, loss of funds, or official confirmation that every redirect and migration completed cleanly, with attention focused on whether direct callers could authenticate and whether endpoint, SDK, and on-chain contract generation match.