Event-Driven Updates
Osito Protocol uses an event-driven approach for state updates, which is fundamentally different from protocols that rely on regular, scheduled updates or oracle-driven mechanisms.
Key Principle
The protocol state is updated only when users interact with it - no global scheduled updates are needed.
Just-In-Time Data Fetching
On-Demand Calculations
Fresh pool values are fetched at the exact moment they're needed for decision-making. This approach ensures that:
- All calculations use the current state of liquidity pools, not stale data
- Decisions about borrowing limits are always made with the most up-to-date information
- No scheduled background processes or "keepers" are required to maintain protocol state
Real-Time Risk Assessment
The protocol re-queries pool data at each critical operation:
- When a user deposits collateral
- When a user withdraws collateral
- When a user borrows BERA
- When a user repays borrowed BERA
This ensures lending limits always reflect current market conditions without relying on price oracles.
Benefits of the Approach
No Oracle Dependency
By calculating values on-demand using real-time liquidity data, the protocol completely eliminates oracle dependencies and the associated risks.
Simplicity
The system avoids complex mechanisms for updating state outside of user interactions, reducing attack surface and potential failure modes.
Up-to-Date Risk Assessment
Every user action is evaluated against the current state of the blockchain, ensuring risk calculations are never based on outdated information.
No "Keeper" Requirements
The protocol doesn't require external parties to perform maintenance operations to keep it functioning properly.