GLIF Docs
V1 English
V1 English
  • 👋Welcome to GLIF
    • Intro
    • History of GLIF and Filecoin DeFi
  • Storage Provider Economics
    • Use Cases
    • Storage Provider Equity
    • Storage Provider Liquidation Value
    • Storage Provider Earnings
    • Borrowing Limits
    • Guarantors
    • Withdraw funds
    • Rates & Payments
    • Quotas
    • Rule Enforcement
  • Agents
    • Agents
    • Owner and Operator Keys
    • Credentials
    • Add/Remove Miners
    • 3 Agent States
    • Helpful CLI commands
  • Token holder economics
    • How it works
    • Understand Collateral
    • Rewards & iFIL
    • Exits
    • Audits
    • Risks
  • More about the protocol
    • Agent Police
    • Agent Data Oracle
    • Decentralization
Powered by GitBook
On this page
  1. More about the protocol

Agent Data Oracle

PreviousAgent PoliceNextDecentralization

Last updated 1 year ago

The FVM runtime does not provide much rich, contextual, or historical data about SPs. Even if it did, it would be gas intensive in a L1 smart contract environment to make accurate risk computations on-chain. The ADO is an off-chain data aggregator that allows the pools to receive any real-time and/or historical data on SPs securely and at a very low cost. Each pool can receive its own unique data from the ADO, allowing maximum flexibility.

When an Agent wants to take an action like borrowing funds from a pool, it must first make a request to the ADO to get a credential. The ADO makes its , and issues a signed credential to the Agent containing the latest snapshot of data concerning the associated Agent and all of its associated miner actors. The Agent then takes this credential to the pool it wants to borrow from, which the pool uses to make a decision about approving the action.

security checks
The ADO issues signed credentials, which the Agent Police validates