allbridge-core: track bridge contracts instead of liquidity pools - #506
Open
YaroslavNekryach wants to merge 1 commit into
Open
allbridge-core: track bridge contracts instead of liquidity pools#506YaroslavNekryach wants to merge 1 commit into
YaroslavNekryach wants to merge 1 commit into
Conversation
Allbridge Core wound down its liquidity pools; volume is now read from the TokensSent-style events of the bridge contracts (CCTP v1/v2, OFT, xReserve) on Ethereum, Arbitrum, Avalanche, Base, Polygon, Optimism, Unichain and Tron. Withdrawals are counted for CCTP v2 only, where the Allbridge contract triggers the mint. The analytics API helper for Solana/Sui/Stellar pool events is removed with the pools.
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
1 participant
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.
Summary
Read Allbridge Core (https://core.allbridge.io/, https://x.com/Allbridge_io) bridge volume from the bridge contracts instead of the retired liquidity pools, and drop the pool-based analytics helper.
Why
Allbridge Core wound down its liquidity pools; the adapter indexed their
SwappedToVUsd/SwappedFromVUsdevents, which no longer happen, and fetched Solana, Sui and Stellar pool events from an analytics API that is being decommissioned. All remaining routes are burn-and-mint transfers through partner protocols (Circle CCTP v1/v2, LayerZero OFT, Circle xReserve), executed from Allbridge bridge contracts on the source chain.Changes
TokensSent(CCTP v1 and v2 bridges),OftTokensSent(OFT bridge) andXReserveTokensSent(xReserve bridge) events of the Allbridge contracts on the source chain. Addresses: https://api.core.allbridge.io/token-info.ReceivedMessageIdevent and takes recipient and net amount from Circle'sMintAndWithdrawevent in the same receipt. Other routes are delivered by the partner protocol directly to the recipient without an Allbridge contract, so they are counted on the source chain only.analyticsApi.ts;bridgeNetworkData.tsis updated accordingly.Testing
npm run test allbridge-core 6000: OFT deposits found on Ethereum and Tron, values pass the type checks.0x7f9c3364b0af71fce97162f994ad6d86c84b31c81a6b44483047b13ff9e15d09→ 99.886014 USDC to0xA8b19905a9BFB77Ce0C0EeCD95A5c5cF904Da845.tsc --noEmitis clean for the adapter.Related PRs