Bridges of LI.FI across chains, the contract is LiFiDiamond_v2

[lequangphu]

Thank you for contributing to Spellbook 🪄

Please open the PR in draft and mark as ready when you want to request a review.

Description:

Extract bridge data from event LiFiDiamond_v2_evt_LiFiTransferStarted on each chain, then union across chains.

---

quick links for more information:

• README.md
• spellbook docs
• CONTRIBUTING.md

[jeff-dude]

before we dig into the failing test, i think we need to redesign this pipeline a bit.

• flip your materialization strategy approach -- i.e. materialize each chain incrementally, then have the crosschain be a view on top
• looks like the code is the same per chain -- in this case, i'd use a dbt macro for the logic and call the macro for each chain while passing in the blockchain parameter to differentiate. there are tons of examples in spellbook to use as reference, one to search could be the uniswap models in dex subproject (but plenty others too!)
• when joining from decoded to base table to get additional columns, lets use this shared macro. an example to call the macro is here
• when using the if is incremental logic, let's use the latest macro approach like here rather than hardcode last 7 days
• for incremental chain models, i would expect config to contain all of this
• looks like you removed the surrogate key logic, i'd put that back in and use as unique key. then update the schema yml to run unique test on this column, not the combination of columns that make up the surrogate key

let's leave it at that for now, and revisit once all this in place 🙏

[lequangphu]

before we dig into the failing test, i think we need to redesign this pipeline a bit.

• flip your materialization strategy approach -- i.e. materialize each chain incrementally, then have the crosschain be a view on top
• looks like the code is the same per chain -- in this case, i'd use a dbt macro for the logic and call the macro for each chain while passing in the blockchain parameter to differentiate. there are tons of examples in spellbook to use as reference, one to search could be the uniswap models in dex subproject (but plenty others too!)
• when joining from decoded to base table to get additional columns, lets use this shared macro. an example to call the macro is here
• when using the if is incremental logic, let's use the latest macro approach like here rather than hardcode last 7 days
• for incremental chain models, i would expect config to contain all of this
• looks like you removed the surrogate key logic, i'd put that back in and use as unique key. then update the schema yml to run unique test on this column, not the combination of columns that make up the surrogate key

let's leave it at that for now, and revisit once all this in place 🙏

thanks, i will update the pr based on your recommendation.