You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a regular Balancer Pool, token weights, swap fees, cap etc. can be inferred by calling correspondent view functions in their smart contract or by checking Balancer UI, since they are set once and can't change.
Into a readable sequence of events with method names and parameters.
This would allow us also to know in detail which methods where used to add / remove liquidity from pools (Balancer has different methods where you know either the exact amount of pool share tokens you want in/out and give limits for tokens in/out of the pool, or viceversa)
Example json output for other actions we are using:
For a regular Balancer Pool, token weights, swap fees, cap etc. can be inferred by calling correspondent view functions in their smart contract or by checking Balancer UI, since they are set once and can't change.
However, for Configurable Rights Pool like the one used by PERP protocol for liquidity bootstrapping, token weights were changed periodically.
In other cases, tokens can be dynamically added and removed, swap fees can change, and cap limits.
In order to have a reproducible set of actions, we need a script that either
Into a readable sequence of events with method names and parameters.
This would allow us also to know in detail which methods where used to add / remove liquidity from pools (Balancer has different methods where you know either the exact amount of pool share tokens you want in/out and give limits for tokens in/out of the pool, or viceversa)
Example json output for other actions we are using:
The text was updated successfully, but these errors were encountered: