feat(ccq-server): enforce rate limits based on staking #4632
Conversation
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
aapclark
commented
Jan 6, 2026
- (ccq-server): query ccq staking contract and look up rate limits in ipfs tranche Rate limiting is enforced by the CCQ server before requests reach the guardian. Guardians trust that requests on the gossip network have already been validated. This aligns with the CCQ whitepaper: "The CCQ query server does request validation and responds with an error if it detects a bad request." - (ccq-server): support raw and eip191 signed messages - (ccq-server): remove unused permissions file - (ccq-server): add config values for contract address and ipfs host - (ccq-server): add X-Signature-Format header (values: "eip191" or default raw) - (ci): add ipfs provider with staking tranches - (ci): add queries staking contract deployment and pool creation - (js-query): switches to newer version of viem from web3 - (js-query): add integration tests for staking-based rate limits - (js-query): add integration tests for raw and eip191 signed messages Co-authored-by: web3ashlee <[email protected]>
removes duplicate call introduced by rebase
fix: configure notary once in node test removes duplicate call introduced by rebase chore(ccq): update ccq metrics chore(querystaking): update querystaking metrics chore(query): update context handling in memorystore fix(js-query): pass uint8Array buffer to BinaryReader fix(query): use common.ReadSafe
eth-node is built locally or in CI and is not a hosted docker image
fix delegation test
aapclark
force-pushed
the
ccq-server-staking-rate-limits
branch
from
cabf87e to
81ac7e8
Compare
- switch to improved format for rate limit payload - update querystaking and ipfs modules to retrieve and parse simplified payload - update CI setup scripts and tests fix(ccq-server): handle decayRate in queryType - the addition of `decayRate` in the staking contract `queryType` field makes it cumbersome to lookup a pool. Instead, the server will use a list of staking pool addresses rather than querying the factory contract. - add config option `stakingPoolAddresses` so that query-server can identify staking contracts without having to iterate through multiple possible decay rates - make config flag `ccqFactoryAddress` optional - update CI script to generate full queryType - update tests with new query type addresses
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Rate limiting is enforced by the CCQ server before requests reach the guardian. Guardians trust that requests on the gossip network have already been validated. This aligns with the CCQ whitepaper: "The CCQ query server does request validation and responds with an error if it detects a bad request."
(ccq-server): support raw and eip191 signed messages
(ccq-server): remove unused permissions file
(ccq-server): add config values for contract address and ipfs host
(ccq-server): add X-Signature-Format header (values: "eip191" or default raw)
(ci): add ipfs provider with staking tranches
(ci): add queries staking contract deployment and pool creation
(js-query): switches to newer version of viem from web3
(js-query): add integration tests for staking-based rate limits
(js-query): add integration tests for raw and eip191 signed messages