-
Notifications
You must be signed in to change notification settings - Fork 3
[VEN-3338] Configure TreasuryConverter on BSC, Ethereum, Arbitrum #596
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
base: feat/VEN-3328
Are you sure you want to change the base?
Conversation
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.
addTokenConverter
and addOrUpdateDistributionConfigs
are missing.
Can you please include simulations for
|
vips/vip-536/bscmainnet.ts
Outdated
signature: "setConversionConfigs(address,address[],(uint256,uint8)[])", | ||
params: [ | ||
TREASURY_CONVERTER.bscmainnet.tokenIn, | ||
TREASURY_CONVERTER.bscmainnet.tokenOuts, |
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.
These must be the addresses of every underlying asset supported on BNB Chain, except the tokenIn and the assets we want to directly transfer to the destination contract
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 also need the bsctestnet commands and simulations
Description
Resolves VEN