Hi Pyth team,
We’re currently encountering a blocking issue with one of our contracts on HyperEVM, where the Pyth Entropy callback did not execute, leaving the game in a “Finalizing” state.
- Contract & Context
Game contract: 0xa91Efb3eC5b4b2a0Dabe07fB0CD268C91fa2640f
Entropy proxy: 0xfA25E653b44586dBbe27eE9d252192F0e4956683
Provider: 0x52DeaA1c84233F7bb8C8A45baeDE41091c616506
Sequence ID: 1345
Request tx: 0x7e384b7b568… at block 7261384
Round ID: 0
- On-Chain Observations
RequestedWithCallback(…, seq=1345, …) was emitted successfully
No RevealedWithCallback(…, seq=1345, …) exists for this sequence
getProviderInfo() shows feeManager was set after block 7261384; its balance is 0
Previous sequences (1343, 1344) were processed normally
- Diagnosis
Internal isFulfilled(1345) returns true, confirming fulfillment
Our entropyCallback() was never invoked
The game remains in a pending state due to the unresolved round
- Operational Impact
Round remains unresolvable via standard flow
Progression and user interactions are blocked until resolution
- Request for Support
Could you verify why the keeper didn’t trigger reveal(1345) after the feeManager update?
If this is a known issue, is there an admin-side remedy (manual trigger or override function) you recommend?
Alternatively, is there an on-chain method to gracefully handle stuck sequences like this?
We appreciate your assistance in identifying and resolving the root cause. Let us know if additional diagnostics or contract access are needed.
Best regards,