HYPER EVM Callback issue

Entropy
1

:waving_hand: 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.

  1. Contract & Context

Game contract: 0xa91Efb3eC5b4b2a0Dabe07fB0CD268C91fa2640f

Entropy proxy: 0xfA25E653b44586dBbe27eE9d252192F0e4956683

Provider: 0x52DeaA1c84233F7bb8C8A45baeDE41091c616506

Sequence ID: 1345

Request tx: 0x7e384b7b568… at block 7261384

Round ID: 0

  1. 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

  1. 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

  1. Operational Impact

Round remains unresolvable via standard flow

Progression and user interactions are blocked until resolution

  1. 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,

2

Gm @hyper , thanks for reaching out. Let me look into why there wasn’t a successful callback. Usually in situations like this, your callback reverted due to insufficient gas or a revert in your code.

In the meantime, you can manually reveal and call your callback using this tool to get unstuck: https://entropy-debugger.pyth.network/

3

Yeah looks like the callback was called but the contract reverted during gas estimation, which likely means that your entropyCallback function reverted. There was no revert code unfortunately. Or we hit a transiently lagging RPC node, but this is unlikely since we retried the callback 11 times.

You can manually resolve your round using the tool I linked above.

1 Like
4

Hey man thanks for your reply; I get this error;

image
image1246×956 39.7 KB

page-1b3509168cc0663…smw6jPTwjq3VaQCoU:1 GET https://fortuna.dourolabs.app/v1/chains/hyperevm/revelations/1345?block_number=7261384 net::ERR_CERT_AUTHORITY_INVALID

L @ page-1b3509168cc0663…smw6jPTwjq3VaQCoU:1
R @ page-1b3509168cc0663…smw6jPTwjq3VaQCoU:1
await in R
(anonymous) @ page-1b3509168cc0663…smw6jPTwjq3VaQCoU:1
iX @ 42fc8f10-1a1111caf84…smw6jPTwjq3VaQCoU:1
(anonymous) @ 42fc8f10-1a1111caf84…smw6jPTwjq3VaQCoU:1
nS @ 42fc8f10-1a1111caf84…smw6jPTwjq3VaQCoU:1
i2 @ 42fc8f10-1a1111caf84…smw6jPTwjq3VaQCoU:1
s7 @ 42fc8f10-1a1111caf84…smw6jPTwjq3VaQCoU:1
s5 @ 42fc8f10-1a1111caf84…smw6jPTwjq3VaQCoU:1
6

Hm that’s strange, we aren’t able to reproduce the cert issue on our side. Could you please share the full request tx hash so we can debug further?