curve-dao-contracts
curve-dao-contracts copied to clipboard
curvefi
Vyper contracts to be used by Curve DAO
https://github.com/curvefi/curve-dao-contracts/blob/3bee979b7b6293c9e7654ee7dfbf5cc9ff40ca58/contracts/ERC20CRV.vy#L112-L113 When the inflation rate drops to 0, _update_mining_parameters() will update the inflation rate to initial_rate. It happens in the 246th year. The inflation rate will repeat again and again.
I'm trying to deploy the contracts on a local forked network, and at some point of the process some of the contracts fail to deploy because they are missing some...
Wrong indexes of coins were used to determine the type of crypto pool. Fixed that and added a comment in head of the contract.
## What I did Added burner that unwraps WETH and sends ETH to receiver(Pool Proxy). ## Tests ```shell brownie test tests/fork/Burners/test_wrapped_burner.py --network mainnet-fork ```
``` WEEK: constant(uint256) = 7 * 86400 # all future times are rounded by week MAXTIME: constant(uint256) = 4 * **365** * 86400 # 4 years MULTIPLIER: constant(uint256) = 10...
when I'm running `brownie run voting/new_vote make_vote --network mainnet -I` this will get thrown inside the make_vote function. Are the ABIs not the correct ones or what could cause this...
when I run the new_vote.py script it throws cause it doesn't have an etherscan API key. The question is where to put that?
On LiquidityGaugeV5, the `add_reward` function [does not check that `_distributor` is not the zero address](https://github.com/curvefi/curve-dao-contracts/blob/1148abe970784e2ddfa17d9fb26bfd08b27a6918/contracts/gauges/LiquidityGaugeV5.vy#L672). This is important, because the gauge assumes reward tokens with a zero distributor are uninitialized...
# What I did Added script to change parameters for pools and factory pools. It simulates the vote and checks twice(separately and together) that all parameters will be set. Logs...
According to [the inflation contract](https://github.com/curvefi/curve-dao-contracts/blob/master/contracts/ERC20CRV.vy), the issuance schedule on the `README` is incorrect. I ran the code myself and found the table below to be the correct representation of yearly...
