defi

• KOVAN ENV
• Deploy StakingRewards for iETH as staking token and SNX as rewards (simplest one)
• Deploy Uniswap V2 sXAU/USDC UNI-V2 TESTNETS
• Deploy StakingRewards for sXAU/USDC exchange and SNX as rewards
• ping me and I'll configure RewardsDistribution for testing

Hi

I'm not sure if this is an issue or a user error, but when I attempt to get the token details using get_token() for the following contracts I get an error saying 'Invalid Token Address' -

1. 0x431ad2ff6a9c365805ebad47ee021148d6f7dbe0
2. 0x9f8F72aA9304c8B593d555F12eF6589cC3A579A2

I've tried with a heap of other tokens without issue, but these two seem to fail. I've also tried using Ve

Request from @poolpitako

setRewards() in BaseStrategy should be settable by gov.

Todo:

• add the changes.
• cherry-pick the changes on older version and tag a new version

to discuss:

Part 1:
debug=staking:

• to much output for a longer operating in production with debugmode staking, but without, we have too less infos for a minted block and cant monitor chainsplits or rollbacks.
  Proposal: Add following lines to normal Logmode without debug=staking
  **2021-05-05T17:19:45Z MakeStake: kernel found
  2021-05-05T17:19:45Z new proof-of-stake block found hash: 067c

It'd be nice if we could have access to Etherscan-like mapping of addr->name, instead of doing it manually/slowly ourselves https://github.com/flashbots/mev-inspect-rs/blob/master/src/addresses.rs#L112-L188. This could easily be done with the CSV crate, as shown here

Is your feature request related to a problem? Please describe.
Run yarn compile and you will see a LOT of yellow warning text show up. Some of these are very very minor, some can potentially come into a larger issue.

Describe the solution you'd like
Resolve all of these warnings by modifying the solidity code, or add rules to the compiler to dismiss them, such that we have no warn