Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support FDG #9

Merged
merged 7 commits into from
Aug 20, 2024
Merged

Support FDG #9

merged 7 commits into from
Aug 20, 2024

Conversation

boyuan-chen
Copy link
Contributor

@boyuan-chen boyuan-chen commented Aug 8, 2024

Now we can fully rely on our subgraphs.

We have two functions:

  • getLatestFDGSubmittedBlock(chainId) -> It returns the l2 block number of latest FDG game that has been resolved. Any l2 withdrawal transaction before this block number can submit the proof.
    If something goes wrong, it return 0.
  • getRootClaimOfFDGSubmission(chainId, blockNumber) -> It returns
{ status: 'success', id: FDG_ADDRESS, rootClaim, l2BlockNumber, index }

given a l2 block number.

If the game has been created or resolved, it returns

{ status: 'error', error:' 'No submission found for the given block number' }

For any other problems, it returns

{ status: 'error', error:' 'Unknown error' }

These issues have been fixed
I am worried about the RPC endpoint.
I am talking with Tenderly to see if there is a way to use their RPC endpoint in our gateway.

@boyuan-chen boyuan-chen requested review from wsdt and sk-enya August 8, 2024 16:54
@wsdt
Copy link
Contributor

wsdt commented Aug 8, 2024

++ on the RPC

@sk-enya
Copy link
Contributor

sk-enya commented Aug 20, 2024

Changes tested with gateway locally all looks good so merging PR!

@sk-enya sk-enya merged commit 7d137ed into wsdt/graph-outsource Aug 20, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants