Notifications
What the interface tells you, when, and why every alert corresponds to something you can actually do about it.
Notifications come from the interface, not from the protocol. The contracts emit events; a front end reads them and tells you. That distinction matters: no notification is a condition of anything, and the protocol works identically for someone who never receives one.
Alerts about your position
| Trigger | Who is told | When |
|---|---|---|
| A confirmed on-chain fall starts the persistence clock on your branch | Affected positions | Real time, before anything can execute |
Your ratio is within 10 points of the liquidation threshold at the current pLiq | Affected positions | Real time |
| Your position comes within 5% of the front of the redemption queue | Borrower | Real time |
| Your chosen rate has fallen below the current tier floor | Borrower | Weekly |
The first two are the ones that can precede a liquidation. In DEGRADED you get the persistence window and the longer confirmation delay between the moment a fall becomes visible on-chain and the moment anyone can act on it.
Every one of these alerts is paired with an action: a single button that computes the exact repayment or deposit needed to clear the threshold, with a margin above it, and executes it in one transaction. Repaying and depositing read no price, so the button works in every regime.
Rules R-15.3, R-15.1.6, R-15.1.7
Alerts about your branch
Sent to every position on the branch, in real time:
- Mint freeze entered or left — the branch's aggregate ratio has fallen under 175%, or bad debt is outstanding.
- Oracle paused for a corporate action.
- Feed stale for more than an hour.
- Circuit condition open.
- Token contract upgrade freeze.
- Interest clock paused or resumed.
- Branch shutdown.
None of these blocks repayment or collateral deposit. Several of them block borrowing, and the notification says which.
Rules R-15.3, R-6.8.1, R-4.3.9, R-5.5.5
Alerts about the protocol
Sent to everyone:
- The Closer key freezing something, and the end of that freeze.
- A branch shutdown, and Sunset.
- The key being renounced, or expiring at day 365.
- A dormant branch activating.
- A debt ceiling step being reached, or permanently locked by a bad-debt event.
The key's every use emits an event and appears on a dedicated page showing its address, its countdown, the freezes in force, the cumulative budget it has consumed per branch, and how many liquidation freezes remain out of three.
Rules R-12.1.6, R-15.1.13, R-15.3
Alerts for depositors
Daily, when a threshold is crossed:
- PSM reserve below 5% of supply.
- Total Stability Pool deposits below 30% of fyUSD supply — which also automatically redirects the treasury share back into the pools until the ratio recovers to 40%.
- Measured market depth decaying because nobody has sampled it for 48 hours.
Rules R-15.3, R-10.4, R-5.4.2
What you will never receive
- A notification urging you to borrow more, or to increase leverage.
- A countdown that exists to create urgency rather than to describe a real deadline.
- A promotion, a referral prompt, a limited-time offer, or a scarcity claim.
Rule R-15.4.2
Do not rely on them
Risk
Notifications are a convenience provided by a front end that the protocol does not depend on and that nobody is contractually obliged to keep running. The reference interface is operated by third parties. If it disappears, your position continues exactly as before, liquidation continues to work, and you continue to be able to repay by calling the contract directly — but nobody will tell you when to.
Set your own monitoring if the position matters to you. The events are public and any watcher can read them.
Rules R-12.6.1, R-15 preamble
Reading the state yourself
Every alert corresponds to a view function you can call without a front end: canActivate() on a dormant branch, debtCeiling() and getEntireDebt() for remaining capacity, getDebt(user) for your exact payoff amount, the oracle adapter's PriceView for the branch's regime, confidence and three prices, and the Closer's expiry timestamp. The ABI reference lists them.
Last reviewed: 2026-09-07 · Spec v0.4
Corporate actions
Splits, dividends, mergers and delistings — what the protocol does automatically, what it deliberately does not do, and the one case that can cost you.
Using Fyber from the Robinhood Wallet
The protocol lives on Robinhood Chain and is designed for a phone. What you need, what you do not need, and what depends on a third party.