NUTS Platform Docs
2.0.0
2.0.0
  • Introduction
  • Opportunity
    • Multiple Classes of Financial Instruments
      • Financial Instruments Supported
    • Reducing Barriers to Entry
    • Customization and Compatibility
  • Architecture Overview
    • Design Principles
    • Domain Model
    • Access Control
  • Implementation
    • Escrow
      • Common Functionalities
      • Instrument Escrow
      • Issuance Escrow
      • Deposit Escrow
    • Instrument Manager
    • Instrument Registry
    • Common Oracles
      • Timer Oracle
      • Price Oracle
    • Protobuf Solidity Generator
    • Interactions
      • Interaction - Instrument Management
      • Interaction - Issuance Creation
      • Interaction - Issuance Engagement
      • Interaction - Token Deposit
  • Platform Upgrade
  • API Reference
  • FSP Guidebook
    • Principles
    • Use Cases
      • Loan Instrument
      • Lockup Instrument
      • PIPE Instrument
      • ESOP Instrument
  • Appendix
    • FAQ
    • Glossary
Powered by GitBook
On this page

Was this helpful?

  1. Implementation
  2. Common Oracles

Timer Oracle

Instrument Manager aims at providing standardized Oracle services to Instruments. The Timer Oracle service is the first Oracle service introduced.

Issuance state changes are mostly triggered by participant actions. For example, collateral deposits from borrower makes borrow tokens available to borrowers. Sometimes issuance state changes are also driven by time. For example, if there is no collateral deposited within some period, the issuance should be delinquent. Therefore, an Oracle is needed to provide timing information to issuance.

Currently Instrument supports two times of scheduled events:

  • Events that are scheduled to happen after some timestamp

  • Events that are scheduled to happen after specific block

In order to scheduled these events, issuances emit events that contains information including timing(timestamp or block), event name and event payload. A Timer Oracle notifies issuance once the scheduled time has passed.

Note that one scheduled event might be notifies multiple times. Therefore, it's up to the Instrument to make sure that the same event is not processed multiple times.

PreviousCommon OraclesNextPrice Oracle

Last updated 5 years ago

Was this helpful?