Fix dead docs link in README.md #14
Open
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
…t of providers respond, but they don't agree with each other (#6229)
The idea is to remove chainType and chainId from all manifests are replace them with networkId which combines both, and will be passed up to low-level functions of our code PR got pretty massive so it was split into smaller ones, this one adds new field - networkId, updates chain-configs package and does a few small, cosmetic changes
- Removed low quality sources
https://docs.google.com/spreadsheets/d/1ianku2-603Lx35X_nLfHUcpb2nZDkjM2-RBMrIiOQ_k/edit?usp=sharing DO NOT MERGE before deployment on 11.06.
…6263) - RPCs for hyperevm have troubles with agree on the same results, they return latest value even when you specify block number in request - due to that we have a lot of missing feeds from hyperevm because we cannot find two or more the same results from the same block - solution from this PR tries to find the result closest to other ones and from the newest block
1. Add iteration timeout 2. Add some diagnostic info which might be helpful when our monitoring will hang again (assuming that point 1 will work..)
Co-authored-by: jakkorzeniewski <[email protected]>
Fixes the case, when every split iteration sends same ping healtcheck, so we don't know, if one of these is broken.
Extract contracts creation to separate methods in fetchers and override those methods in tests to use mock contracts. Most of the time, we can get rid of the mock provider after such a change. In some tests, we call getBalance directly on the provider. In such cases, we create a mock provider and add it to the sage of chains object.
I reviewed the tokens in main and primary - in most cases I removed the "bitfinex-usd" source, because it deviated significantly from the other sources and the price changed very rarely
- yes, token from bnb we deploy on base <img width="528" alt="image" src="https://github.com/user-attachments/assets/9195a63f-5859-42d0-abd5-8e0822fd586c" />
Sources taken from main.json
# Will be fixed later!
- wrong token was fetch in the fetcher, it should be USDT if we calculate value for USDC and other way around, handled that by adding overrides in `StablesRatioFetcher` - turned out that we don't support fetching multiple tokens with the same name from single fetcher using the same token under the hood, e.g. USDC and USDC_V2 is using USDC for cex fetchers - handled that case by storing multiple symbol per id, in cex fetcher we already had cache so it needed only support for multiple values per single id
CEX: - BNB: `["bingx-usdt", "bingx-usdc"]` - TRX: `["bingx-usdt", "bitmart-usdt", "kraken-usd", "mexc-usdt"]` - stETH: `["bybit-usdt", "okx-usdt"]` - TON: `["binance-usdt"]` - USD1: `[ "binance-usdt", "mexc-usdt", "lbank-usdt", "gate-usdt"]` DEX: - USDX: `["curve-bnb-susdx_bnb_fundamental", "pancake-swap-bnb-susdx_bnb_fundamental-500"]` - BIO: `["uniswap-v3-base-weth-3000"]`
- mostly breaks dependency cycles - no logic changes - adds a linter for checking cyclic dependencies
requirements: https://redstone-team.atlassian.net/browse/RDS-3904?focusedCommentId=15639&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel&sourceType=mention#comment-15639 gist to mimic custom price extraction: https://gist.github.com/MirthFutures/a59b3c47c6ccdb22184e5659aa2021bc
They werent really testing anything and we have better tests.
- Allow snoozing specific log monitoring alarm (ex. "price-out-of-hard-limit") - Allow snoozing log monitoring for specific data service (nodes only) - more granular snoozing
Move dev to prod
- a lot of changes are only formatting because our script started to change the order of keys in object
New fallback relayer operates as a lambda running on schedule. Right now it only runs in **multi-feed** mode. We should have 1 lambda per-chain. The following logic is executed in parallel for each dataFeedId for a given chain: 1. Fetch relevant data packages 2. Check update triggers (as per relayer manifest) 3. If any of the update triggers is satisfied, schedule the retry after `RETRY_OFFSET_MS` Retry logic: Repeat steps 1,2. If the deviation is still present, send a transaction on chain (updateDataFeedsValues on the contract). There's some extra effort to try and batch multiple transactions together if possible with minimal delay.
- stHYPE_LP_FUNDAMENTAL is a token we have already integrated, but due to issues with multicall, we had to remove it - now we want to restore it and see if we can have it stable on dev for some time
…lackhole (#6907) - kittenswap is velodrome clone so need to move and thanks to that could remove one method from class - remove unnecessary modifiers in blackhole class --------- Co-authored-by: robal <[email protected]>
Co-authored-by: Wojciech Rybakiewicz <[email protected]>
It previously linked to a /smart-contract-devs/ namespace in your docs which no longer exists
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
21 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.
It previously linked to a /smart-contract-devs/ namespace in your docs which no longer exists