Add POST /v2/verify/{chainId}/{address} endpoint
#2040
Merged
+2,232
−421
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
Adds a central mapping for error codes to messages, such that they can be reused in server.
Needed for the corresponding API response field
manuelwedler
force-pushed
the
apiv2-verify-endpoint
branch
from
5d820d5 to
adc3ead
Compare
|
Some explanations:
|
marcocastignoli
approved these changes
Mar 31, 2025
services/server/src/server/services/storageServices/SourcifyDatabaseService.ts
Show resolved
Hide resolved
services/server/src/server/services/workers/verificationWorker.ts
Outdated
Show resolved
Hide resolved
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.
Closes #1910
As specified in https://sourcify.stoplight.io/docs/sourcify-apiv2/h55xvo5bsu9qz-verify-contract-standard-json
Includes the needed verification worker which is implemented with the Piscina library.
See commit messages for details.
We should still do some testing on the worker configuration (number of threads, ...) and some benchmarking after this.