Appeal to help reveal manually this sequence numbers

Entropy
1

hi am opening a ticket about an entropy service

i want you to help me manually the this sequence for your entropy provider on abstract chain
965986,1
966009,2
966029,3
966040,4

sequence and bet id so my contract can call back and relsease reserved eth

i made a mistake when deploy and testnet that eth got stuck on contract waiting for reveal

2

Hey, you can try our Entropy Explorer https://entropy-explorer.pyth.network/, we have various filters that you can search via. You could check the sequence number yourself.

I hope this is what you were looking for.

3

is it possible for you to help manually settle this sequence pls

i noticed on this scan

https://entropy-explorer.pyth.network/?pageSize=100&chain=abstract&page=89

none of the sequence i am looking for are there
965986
966009
966029
966040

that means they where skipped was wondering if the team can help me settle it manually from their end

u can check for yourself
page 89 of abstract

in the image i attached you will notice 965986 is missing was skippped
same with 966009 and the rest 2

image
image1889Ă—579 104 KB

4

Gm @marv , it looks like you may have specified a different provider for those requests? Currently we run the only provider (0x52DeaA1c84233F7bb8C8A45baeDE41091c616506) and it would have picked up these sequence numbers, but I don’t see it in our logs. If you used a different provider, unfortunately we can’t unbrick those requests.

5

this is the one i used

entropy address
0x5a4a369F4db5df2054994AF031b7b23949b98c0e

provider
**0x52DeaA1c84233F7bb8C8A45baeDE41091c616506

you can cheeck here

thats one transaction **

image
image1571Ă—212 13.8 KB

6

no help still yet ….

7

Apologies for the delay @marv . I’m investigating how we can help unbrick you. Please give me a few hours and i’ll get back to you with my findings.

1 Like
8

@marv Alright I did some digging – based on the tx you provided, it looks like your contract called request and not requestWithCallback. This is an old flow and is incapable of executing a callback.

You can still obtain the final random number if it helps you:

  1. Call the revelation API with the sequence number to get the provider revelation
  2. Since you didn’t originally register a callback in the request (due to the usage of request and not requestWithCallback ,) there’s no way for us to call your callback with the result.
  3. However, you can have your contract call reveal with the original user random number and the provider revelation to get the final random number.

We will update our Solidity files to emphasize that request does not provide a callback, and that it’s recommended to call requestV2 on IEntropyV2 instead.

I know it’s not the resolution you hoped for, but hopefully this helps. Thanks!

3 Likes
9

return error code 400 chain not supported

when i queried supported chain

returned this
[ “sanko-testnet”, “blast-testnet”, “b3-testnet”, “kaia-testnet”, “berachain-bepolia”, “sonic-blaze-testnet”, “base-sepolia”, “story-testnet”, “apechain-testnet”, “arbitrum-sepolia”, “monad-testnet”, “zetachain-testnet”, “optimism-sepolia”, “abstract-testnet”, “soneium-minato-testnet”, “hyperevm-testnet”, “sei-evm-testnet”, “tabi-testnet”, “unichain-sepolia”, “etherlink-testnet” ]

All testnet on abstract mainnet

image
image1890Ă—785 33.5 KB

10

Ah sorry I linked you the testnet provider. This will work for mainnets: Swagger UI

11

image
image1828Ă—872 34.9 KB
for some reasons same things lol

i quired supported chain

[ “arbitrum”, “sei-evm”, “optimism”, “sonic”, “berachain”, “abstract”, “apechain”, “b3”, “unichain”, “base”, “sanko”, “story”, “etherlink”, “blast”, “zetachain”, “kaia”, “soneium”, “hyperevm” ]

abstract is there but same thing

13

@marv The chain_id is of type string, so pass in abstract , it will work fine.

I tried for your sequence. Attaching success snippet below.

image
image2532Ă—1716 245 KB
you can check out the chains that are supported from chains API, use the same format for the chain as given in the output.

14

hey gm okay i got it

but the transaction is failing cause my contract requires entropy provider to be the one using the entropy call back

image
image559Ă—192 9.6 KB

15

@marv Could you please elaborate what are you trying in this transaction.

I hope the call to revelation API worked for you.

16

@marv Yeah unfortunately a callback is only possible when the original request was done via requestWithCallback or requestV2. In that flow, Entropy will call your callback with the random number.

The flow you’re following works differently – your contract can call reveal to get the final random number with the provider revelation, not the other way around.

17

damn it
well its over from here
thanks for your help tejas and nidhi

1 Like