-
Notifications
You must be signed in to change notification settings - Fork 1
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
feat: stargate receiver #1
base: main
Are you sure you want to change the base?
Conversation
kuchmenko
commented
Jan 24, 2025
•
edited
Loading
edited
- Implement starage receive lzCompose contract
- Add multicalls handling
- Deployment docs + .env.example
Things to improve:
I will work on 3 |
can you rename folder |
Co-authored-by: Ferman <119309671+0xh3rman@users.noreply.github.com>
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.
Thanks for the efforts to continue improving, I left some more comments, the ReentrancyGuard
should be added back
* @notice A contract that handles multiple calls in a single transaction. | ||
* @dev Inspired by https://github.com/across-protocol/contracts/blob/master/contracts/handlers/MulticallHandler.sol | ||
*/ | ||
contract MulticallHandler { |
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.
across's handler has MulticallHandler
but i can't see it on here or GemStargateMulticallHandler
|
||
struct Instructions { | ||
// Added to handle | ||
address token; |
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.
can we handle this in composeMsg
? Instructions
is better to be as generic as possible
// call across | ||
|
||
// Rest from across |
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.
// call across | |
// Rest from across |
echo "✅ Deployment to $NETWORK_NAME completed." | ||
done | ||
|
||
echo "🎉 All non-zkSync deployments done!" |
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.
lol, why zkSync is so special, deploy/deploy-stargate.sh
and deploy/deploy-stargate-zksync.sh
should be more proper naming