add updated configurations for new chains#18
Merged
CluEleSsUK merged 42 commits intomasterfrom Jul 2, 2025
Merged
Conversation
Contributor
|
@CluEleSsUK All the tests should be good now. |
Contributor
Author
|
gonna merge despite failures and some test skipping.
|
This file contains hidden or 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
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.
All checks now pass.
The
DCIPHER_PUBLIC_KEYhas been switched over to the new one which is used on all chains that support user billing.The integration tests for the chains that do not support user billing yet, have been commented out temporarily.
Function
calculateRequestPriceNativehas been added to help users estimate how much their request will cost based on the callbackGasLimit and the current chain gas price (used by the RPC provider by default when not specified). This function is also used in therequestRandomnesslogic.calculateRequestPriceNativereturns a better estimate compared to callingRandomnessSender.estimateRequestPriceNative(uint32 _callbackGasLimit, uint256 _requestGasPriceWei))and passing in a hardcoded network gas price which could be lower than the current network gas price and will give the user a lower estimate compared tocalculateRequestPriceNativeand in some cases could lead to afee too lowrevert message fromBlocklockSender. @CluEleSsUK