-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🆙 Chore: packages & node update #43
base: main
Are you sure you want to change the base?
Conversation
- node version to 20+ - moved yarn to pnpm - updated docker file to build and test setup service with pnpm - lb-tests ci update to `docker compose` - docker compose change expose port for anvil with platform force to amd64 - cleanup light bridge service from based as it's been prepared in reg and parellel
- Added mapping variable for percentExitFee `{sourceChainId} => {percentExitFee}` - Added variable to record the collectedFee. - Event to capture the PercentExitFee or change - Function to calculate the amountAfterFee deduction with input as amount and sourceChainId. - update disburseAsset fn to use the calculateAmountAfterFee and fee deducted to keep record. - function to set PercentExitFee corresponding to sourceChainId only owner can set it.
Nice! Seems like there is just a public node not working rn. Do the tests run locally for you if you define the RPC environment variables with some Tenderly private nodes? @sk-enya |
Can you please help me with tenderly L2 url, I am unable to find that! for sure it will start working as soon as our L2 sepolia will be back. |
if Boba Sepolia is down @boyuan-chen or @jyoti-enya might be better to help with that as you suggested in our chat. :-) |
…ub.com-enya:bobanetwork/light-bridge into feat/lb-update-exit-fee-with-record-collection
…record-collection Feat: ExitFee in percentage logic move to contract.
…chore/packages-node-update
Before we merge this:
Huge change. And also, do we plan to re-audit the contract? Or what's the thought process here. |
Yes, please. I don't think we need another round of the audit. The changes are very minor. The core logic of sending funds doesn't change. |
blockNumber | ||
) | ||
const events = | ||
await teleportationService._getAssetReceivedEventsViaQueryFilter( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah that's why the tests might be going through here. We just don't test the graphutils package in combination with the lightbridge anymore.
Could you check if tests still pass if replaced with the subgraph as this is what's being used in prod?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should get this fixed as tests are failing through recent graph-utils changes. @sk-enya
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
left a comment and would be great to test this on testnet first.
Sure, will review and update comments. yeah make sense to first validate on testnet! |
Closes: #41
Change
test:unit
test:e2e
docker compose
docker compose