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

fix: blockhash syncing v6 - 2 #732

Merged

Conversation

FedericoAmura
Copy link
Contributor

Description

This is just a backport of #727 for our v6 SDK

Added some safety measures when syncing blockhash. More specifically:

  • verify fetch response from block-indexer is successful to avoid using error responses with undefined blockhashes
  • use previous-to-last blockhash from public providers on fallback to avoid using a blockhash not yet propagated to nodes
  • use block timestamp instead of user one as that is the one that defines if blockhash is still valid

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

  • Added unit tests for LitCore
  • Local run of CI tests

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

…s. Verify lit block indexer response success. Use a previous block from public providers to avoid using one nodes haven't received yet
@FedericoAmura
Copy link
Contributor Author

Local CI:

- testExecuteJsSignAndCombineEcdsa - Passed (8049.60 ms)
- testUseEoaSessionSigsToExecuteJsSigning (Passed in 3852.94 ms)
- testUseEoaSessionSigsToPkpSign (Passed in 4073.71 ms)
- testUsePkpSessionSigsToExecuteJsSigning (Passed in 4831.74 ms)
- testUsePkpSessionSigsToPkpSign (Passed in 5738.41 ms)
- testUseValidLitActionCodeGeneratedSessionSigsToExecuteJsSigning (Passed in 4749.52 ms)
- testUseValidLitActionCodeGeneratedSessionSigsToPkpSign (Passed in 6131.01 ms)
- testDelegatingCapacityCreditsNFTToAnotherWalletToExecuteJs (Passed in 8567.49 ms)
- testEthAuthSigToEncryptDecryptString (Passed in 3451.97 ms)
- testExecuteJsBroadcastAndCollect (Passed in 5183.60 ms)
- testExecutJsDecryptAndCombine (Passed in 5146.14 ms)
- testExecuteJsSignAndCombineEcdsa (Passed in 8049.60 ms)

Test Report: 11 test(s) passed, 0 failed, 0 skipped.

@FedericoAmura FedericoAmura mentioned this pull request Dec 5, 2024
14 tasks
Copy link
Collaborator

@Ansonhkg Ansonhkg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks straightforward to me!

@FedericoAmura FedericoAmura merged commit 9e719cd into master-v6 Dec 6, 2024
2 checks passed
@FedericoAmura FedericoAmura deleted the feature/lit-4046-blockhash-sync-fixes-v6-2 branch December 6, 2024 18:58
@FedericoAmura FedericoAmura mentioned this pull request Dec 6, 2024
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.

2 participants