Skip to content

Conversation

@nvtaveras
Copy link

@nvtaveras nvtaveras commented Jan 17, 2026

Finding: https://cantina.0dns.co/594

This PR in combination with mento-protocol/mento-core#682 disable liquidations in the event the L2 sequencer is down or had a very recent recovery.

The idea is that if the sequencer were to go down, non-technical users have a higher risk of facing liquidation, since they wouldn't be able to easily add more collateral to their troves if needed. By disabling liquidations/giving a grace period to act in such a scenario, we make the playing field more fair for everyone.

See https://docs.chain.link/data-feeds/l2-sequencer-feeds#overview for more context

Other changes

  • Added a setter for the OracleAdapter in the priceFeed contract, which should've been there

bowd added a commit to mento-protocol/mento-core that referenced this pull request Jan 18, 2026
### Description

This adds an external function to the OracleAdapter to be able to check
the status of a chainlink sequencer uptime data feed. We will use this
in the bold repo to ensure that liquidations can only happen when the
sequencer has been up for at least a certain grace period.

See https://docs.chain.link/data-feeds/l2-sequencer-feeds for more
context

I decided to leave the ability of setting the l2SequencerUptimeFeed to
address(0), in case we ever want to disable this check for any reason.

Related PR in the bold repo:
mento-protocol/bold#33

### Tested

Added some basic unit tests. Will add integration tests once the bold
repo PR is merged
@nvtaveras nvtaveras merged commit c3041c3 into feat/mento-v3 Jan 18, 2026
7 checks passed
@nvtaveras nvtaveras deleted the fix/l2SequencerUptime branch January 18, 2026 21:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants