Tags: mento-protocol/mento-core
Tags
Release v2.6.3 (#581) ### Description New release after adding the new StableTokenXXX proxy contracts so that we can use them in mento-deployment #580 It seems like I messed up the release when I did v2.6.2 since the diff shows some commits that should have been merged as part of #578. Actual diff should only be 0ca0676 --------- Co-authored-by: baroooo <baranseltekin@gmail.com> Co-authored-by: philbow61 <philip.raetsch@gmail.com> Co-authored-by: Ryan Noble <ryanjnoble@gmail.com> Co-authored-by: Bayological <6872903+bayological@users.noreply.github.com>
Fix: Relocking min amount bypass (#575) ### Description [Hats issue #10](hats-finance#10) identified that in the event of relocking a completed lock, there was no minimum check that was present in a standard lock, this was given the assumption that relocking would only occur on non expired locks.
feat: GoodDollar (#522) 7704a9b chore: reserve storage gap in new contracts 040b7fe GoodDollar Fork Tests (#530) 2ee14b4 Feat(454): Exchange provider tests (#529) 578747c test: add BancorExchangeProvider pricing tests (#532) fcd3d02 feat: improve tests around the expansion controller (#533) d3a31fa Streamline comments and errors (#528) ec64f0a fix: ☦ pray to the lords of echidna 13d3a98 fix: add back forge install to the CI step c236009 fix: echidna tests c50a198 feat: add Broker liquidity check (#523) 914ba7d Address Slither Issues in GoodDollar/Bancor Contracts (#526) 8bcf3fd Feat/change gdollar modifiers (#524) 379a511 feat: make validate() internal bcbd9aa chore: added "yarn todo" task to log out open todos in the code 0631c60 refactor: renamed SafeERC20 to SafeERC20MintableBurnable 2800297 feat: simplified SafeERC20 e858391 feat: extend open zeppelin's IERC20 instead of duplicating it 196f6be chore: fixed linter and compiler warnings 096efe2 test: fix fork integration test e5308d9 feat: add GoodDollar contracts + tests 3135626 feat: update Broker + TradingLimits to 0.8 and make G$ changes
Revert "feat: remove maxTimestampSpread and only rely on expiry" (#504) This reverts commit ac1c540. ### Description Brings back the maxTimestampSpread setting. A visual explanation here: <img width="918" alt="image" src="https://github.com/user-attachments/assets/02dfaadb-f029-4f38-8bd5-965644b4a4b5"> We need it because CELO/USD has a heartbeat of 24hr and PHP/USD 5minutes, therefore we could be in a situation where the spread between reports is quite large, and if we rely only on max timestamp spread we could be reporting with stale data. The rule of thumb is: - Set `maxTimestampSpread` by considering the largest heartbeat frequency. - Set `tokenExpiry` in SortedOracles by considering the shortest heartbeat frequency. ### Other changes N/A ### Tested Yup ### Related issues N/A ### Backwards compatibility N/A ### Documentation N/A --------- Co-authored-by: chapati <philip.paetz@me.com> Co-authored-by: philbow61 <80156619+philbow61@users.noreply.github.com>
feat: update proposal threshold (#431) ### Description While going through governance config, we decided it will be better to start with a higher proposal threshold to prevent spam and decided 10_000 veMENTO would be a good start. There is another PR that updates the threshold in post deployment checks: mento-protocol/mento-deployment#183 Fork tests will be fixed once we have a new deployment. ### Other changes No ### Tested Updated some tests with larger lock amounts to pass the new threshold ### Related issues - Fixes #430
PreviousNext