Comparing changes
Open a pull request
- 18 commits
- 6 files changed
- 5 contributors
Commits on Dec 6, 2024
-
Feat: locking l2 upgrade (DON'T MERGE) (#542)
### Description Updates Locking Contracts to handle upcoming block.time change Mainly changes the roundTimestamp() to have a forked implementation that uses different values to calculate week no for the blocks before and after l2 transition. Week numbers that return from roundTimestamp before and after should be continues and consistent. ### Other changes No ### Tested Unit and fork tests ### Related issues - Fixes #538 --------- Co-authored-by: philbow61 <philip.raetsch@gmail.com>
Commits on Dec 16, 2024
-
Feat/update storage layout action (#565)
### Description Storage layout check GH action is failing because of the issue described here: Rubilmax/foundry-storage-check#178 This PR updates the action to the latest release that includes a fix for this issue ### Other changes Uses official foundry toolchain and newer versions of checkout and setup-node actions ### Tested https://github.com/mento-protocol/mento-core/actions/runs/12201703113
Commits on Jan 29, 2025
-
Fix locking upgrade fork test (#574)
### Description Locking Upgrade fork tests were failing because: 1. Locking proxy admin is owned by the multisig now 2. A subtle issue in how we handle timetraveling causing problems with brokenLine internals because we fork the current block's state, roll back to Nov 7 roll forward 3 weeks and make calculations for the month December. Which causes brokenLine.update to try updating the line for a past time if you run the test after December. (kudos to @philbow61) This PR fixes the tests by setting up the fork test correctly and moving 30 weeks into future before starting tests ### Other changes _calculateBlocksTillNextWeek uses values from the contract now
Commits on Feb 5, 2025
-
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.
Commits on Feb 7, 2025
-
Feat: Disable Initializer (#576)
### Description This PR addresses the implementation having an exposed and callable, however without any structural risk, initializer in future implementations of the Locking contract
Commits on Mar 4, 2025
-
test: update fork tests for cGHS (#577)
### Description This change updates the fork tests to include the newly created exchange for cUSD/cGHS ### Other changes None ### Tested Ran the fork tests locally
Commits on Mar 11, 2025
-
feat: add proxies for GBP, JPY, NGN and ZAR (#580)
### Description Add the StableTokenXXXProxy contract for GBP, JPY, NGN and ZAR --------- Co-authored-by: baroooo <baranseltekin@gmail.com>
Commits on Mar 12, 2025
-
Test l2 changes with announced blockno and deployed locking impl (#579)
### Description New locking implementation is deployed and currently used by the Locking proxy on the mainnet. Also Celo L2 transition block no is announced. This PR udpates the L2 fork tests to use the announced block number and calculated l2 starting point week and epoch shift. ### How to review Go through the fork tests, ensure the changes introduced make sense and tests still pass, confirm the l2 starting point week and epoch shift.(epoch shift assumes there won't be down time) ### Other changes Forge v1.0 breaking changes addressed ### Tested Fork tests
-
-
-
-
Commits on Apr 3, 2025
Commits on Apr 14, 2025
Commits on May 6, 2025
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v2.6.3...develop