-
Notifications
You must be signed in to change notification settings - Fork 0
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/verifier #19
Merged
Merged
Feat/verifier #19
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Added logic to mark nodes as fraudulent only after 5 failed verifications. - Reset failure count upon successful verification.
- Added Pow struct to handle PoW operations. - Implemented PerformPoW method to find a nonce that satisfies the difficulty using multiple CPUs. - Implemented VerifyPoW method to verify the PoW by checking the hash and nonce. - Moved PoW-related methods from verifier.go to a new file pow.go.
- Added `RequestPoWFromPeers` method in `Pow` to request PoW from a list of peers using multiple workers. - Updated `Verifier` to filter logs by qualified peers in `processUsageReports`. - Refactored `saveAndSendSignedUsages` to use multiple workers for sending signed usages. - Added `Clear` method in `Pow` to clear requests and qualified peers. - Added unit tests for `performPoW` and `verifyPoW` methods in `pow_test.go`.
- Added a new channel `signatureResponseChan` to the `Service` struct for handling SignatureResponse messages sequentially. - Modified the `onSignatureReceive` function to send the SignatureResponse to the `signatureResponseChan`. - Added a new function `handleSignatureResponses` to process the SignatureResponse messages from the channel sequentially. - Updated the `Start` and `Stop` methods to handle the new channel.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request includes several significant changes to the
subnet-node
project, focusing on logging improvements, configuration updates, and refactoring of theAccountService
andAppService
components. The most important changes are summarized below:Logging Improvements:
github.com/ipfs/go-log/v2
and set all loggers toLevelDebug
when the debug flag is enabled incmd/subnet/main.go
. [1] [2]Configuration Updates:
DefaultSubnetAppStoreAddr
,DefaultSubnetProviderAddr
, and addedDefaultSubnetVerifier
inconfig/default_config.go
.Refactoring
AccountService
:crypto/rand
and addedsigner
package incore/account/service.go
. [1] [2]subnetProvierUptime
related fields and methods fromAccountService
. [1] [2] [3] [4] [5]Sign
method and added a newSignTypedData
method for signing typed data.Refactoring
AppService
:UpdateAppConfig
,GetApps
, andRunApp
methods to use newatypes
package incore/apps
. [1] [2] [3] [4]core/apps
. [1] [2] [3] [4]These changes enhance the project's logging capabilities, update default configurations, and improve the structure and functionality of
AccountService
andAppService
components.