GLIF Docs
V2 English
V2 English
  • Introduction
    • Quick Guide
    • GLIF Overview
    • Protocol Users
  • For Liquidity Providers
    • Benefits for token holders
    • GLIF Reward Mechanism - iFIL
    • Exit - Withdraw FIL
    • Asset Security
    • Risks
  • For Storage Providers
    • Benefits for Storage Providers
    • SP Liquidation Values
    • Borrowing Limits & DTL
    • Uses of Borrowed FIL
    • Liquidations
    • Borrowing Cost
    • Manage Miner Actors with Agents
    • Guarantor Model
  • Developer Resources
    • GLIF SDK
    • GLIF CLI
    • Deployed Contracts
  • TROUBLESHOOTING
    • FAQ
      • FAQ for Liquidity Providers
        • About GLIF
        • Deposit FIL
        • Withdraw FIL
        • Risk
        • Wallet Connection
        • GLIF Points
        • Miscellaneous
      • FAQ for Storage Providers
        • Borrow and Withdraw FIL
        • Key Financial Ratio
        • Payment
        • Liquidation
        • Agents
        • Transaction Issue
    • TUTORIALS
      • For Token Holders
        • Wallets
          • How to find your corresponding 0x/f410 wallet address
          • How to obtain a Ledger wallet as the intermediary wallet
          • How to obtain a burner wallet as the intermediary wallet
          • How to obtain a FilSnap wallet as the intermediary wallet
          • How to connect your wallet to Filecoin Mainnet
          • How to transfer FIL from a 0x address to an f1 address
          • How to create a multisig wallet on GLIF
        • Using the Pool
          • Deposit FIL into GLIF to earn rewards
          • How to deposit Filecoin from a hardware wallet with GLIF
          • How to deposit FIL to GLIF using multisig wallet
          • Withdraw FIL from GLIF
          • How to withdraw FIL from GLIF using a multisig wallet
        • Transfer FIL to/from exchanges
          • Transfer FIL between exchange and GLIF
          • Binance
            • Transfer FIL from Binance to GLIF
            • Transfer FIL from GLIF to Binance
          • MEXC
            • Transfer FIL from MEXC to GLIF
            • Transfer FIL from GLIF to MEXC
      • For Storage Providers
        • GLIF Agent Website Tutorial Part I— Preparation Setup
        • GLIF Agent Website Tutorial Part II — Create your Agent
        • GLIF Agent Website Tutorial Part III — Add Your Miner
        • How to withdraw FIL from the agent to an exchange at GLIF
      • How to Claim $GLF Airdrop
    • Glossary
    • Contact Us
  • Governance
    • Governance
    • Delegation
    • Proposals (GIPs)
    • Voting Process
Powered by GitBook
On this page
  • What are Agents
  • Deploy an Agent
  • Add Collateral to an Agent
  • Agent Ownership
  • Agent Owner and Operator Keys
  • Owner Key:
  • Operator Key:
  • Agent Police
  • Agent Data Oracle (ADO)
  1. For Storage Providers

Manage Miner Actors with Agents

Agents are unique FEVM smart contracts that Storage Providers use to borrow FIL from GLIF

PreviousBorrowing CostNextGuarantor Model

Last updated 10 months ago

What are Agents

Agents are smart contracts on the FEVM that allow Storage Providers (SPs) to collateralize Filecoin Miner Actors (miners) in order to borrow FIL from GLIF. Every Storage Provider deploys and owns their own Agent smart contract. Agents act as intermediaries between SPs and GLIF, allowing SPs to maintain ownership and control over their miner(s) while borrowing from GLIF.

Deploy an Agent

More detailed agent creation tutorials are coming soon!

Add Collateral to an Agent

Agents can borrow once they have collateral. You can add collateral simply by sending FIL to an Agent smart contract, or by pledging one or more Filecoin Miner Actors. In depth tutorials will be posted soon for adding collateral to Agents.

To pledge a Filecoin Miner Actor to a GLIF Agent smart contract, the Storage Provider must assign Ownership of their Filecoin Miner Actor to the address of their GLIF Agent smart contract.

The more mining power added to an Agent, the greater the Agent's liquidation value, which increases the total amount of FIL the Agent can borrow.

Agent Ownership

The Storage Provider that deploys an Agent is in complete and total control of the Agent. If the Storage Provider loses its Agent ownership keys, there is nothing the GLIF team can do to recover the Storage Providers assets.

It is extremely important that Storage Providers manage and backup their Agent keys in a secure and responsible way

Agent Owner and Operator Keys

The GLIF protocol utilizes two distinct keys for managing Agents smart contracts. Only the SP should have access to these keys, and it's important to keep them private and safe. Changes to these keys follow a secure two-step process that involves a proposal by the current holder and acceptance by the new holder.

Owner Key:

The owner key has executive privileges to move FIL in and out of the Agent. It allows actions such as borrowing, withdrawing funds, adding or removing Miner and changing the operator, typically controlled by Storage Provider management.

Operator Key:

The operator key enables operational functions like making payments, managing worker addresses, and moving funds to and from the Agent to any of its Miner.

Agent Police

The Agent Police is GLIF’s keeper contract that ensures each Agent stays within debt-to-liquidation (DTL) ratio when executing actions like borrowing or withdrawing FIL. If an Agent violates system rules, the Agent Police is responsible for processing Agent state transitions and liquidations.

Agent Data Oracle (ADO)

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.

Through GLIF

Through the GLIF

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 GLIF, which the pool uses to make a decision about approving the action.

website
CLI
security checks