-
Notifications
You must be signed in to change notification settings - Fork 32
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
Dummy issue to test new sim request workflow params #84
Comments
Simulation run has completed successfuly. |
Simulation run has failed. Please contact the research team for assistance. |
Simulation run has completed successfuly. |
Simulation run has failed. Please contact the research team for assistance. |
2 similar comments
Simulation run has failed. Please contact the research team for assistance. |
Simulation run has failed. Please contact the research team for assistance. |
Simulation run has completed successfuly. |
Simulation run has failed. Please contact the research team for assistance. |
3 similar comments
Simulation run has failed. Please contact the research team for assistance. |
Simulation run has failed. Please contact the research team for assistance. |
Simulation run has failed. Please contact the research team for assistance. |
Simulation run has completed successfuly. |
Instructions:
In the issue description, put any explanation or context above the "Settings" heading, and the parameters for the simulation below it. This sample issue description follow the required format (hopefully this isn't too "meta"!).
Allowed parameters:
address
(required): the pool addresschain
(optional): Name of the chain or layer 2.Supported values are: "mainnet", "arbitrum", "optimism", "fantom", "avalanche", "matic", "xdai".
Defaults to "mainnet".
A
(optional): specified list of A params to simulate, given as a comma-separated list of valuesDefault will use a large range of values.
fee
(optional): specified list of fee values to simulate, given as a comma-separated list of valuesvol_mult
(optional): Modes for limiting trade volume.1: limits trade volumes proportionally to market volume for each pair
2: limits trade volumes equally across pairs
3: mode 2 for trades with meta-pool asset, mode 1 for basepool-only trades
Defaults to 1.
test
(optional): Uses small set of test parameters. Likely you don't want this. Defaults to "false".Caution: #168 means we can't use
vol_mult
as described above[SETTINGS]
address = 0xbebc44782c7db0a1a60cb6fe97d0b483032ff1c7
chain = mainnet
A = 500,600
fee = 500000
The text was updated successfully, but these errors were encountered: