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

feat: implement functionality to make rpc call to other nodes. #7

Merged
merged 27 commits into from
Aug 30, 2024

Conversation

Zurcusa
Copy link
Collaborator

@Zurcusa Zurcusa commented Aug 27, 2024

  • What does this PR do?
    Implements functionality to make RPC calls to other nodes.
  • Why are these changes needed?
    So that Fruzhin fallbacks to rpc call when populating sync state if protocols fail.

Fixes LimeChain#494

Checklist:

  • I have read the contributing guidelines.
  • My PR title matches the Conventional Commits spec.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

ablax and others added 23 commits August 22, 2024 09:48
# Conflicts:
#	src/main/java/com/limechain/teavm/HttpRequest.java
# Conflicts:
#	src/main/java/com/limechain/chain/lightsyncstate/LightSyncState.java
#	src/main/java/com/limechain/client/LightClient.java
#	src/main/java/com/limechain/storage/DBConstants.java
#	src/main/java/com/limechain/sync/JustificationVerifier.java
#	src/main/java/com/limechain/sync/warpsync/WarpSyncMachine.java
#	src/main/java/com/limechain/sync/warpsync/action/RequestFragmentsAction.java
#	src/main/java/com/limechain/sync/warpsync/action/VerifyJustificationAction.java
#	src/main/java/com/limechain/teavm/HttpRequest.java
@Zurcusa Zurcusa merged commit 92481d9 into dev Aug 30, 2024
1 check passed
@Zurcusa Zurcusa deleted the 494-sync-state-rpc-calls branch August 30, 2024 12:56
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.

P2P communication: Set up communication with RPC calls as a standalone system
2 participants