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
  • Why is the amount of FIL available to borrow for my node so small given that I have more collateral available?
  • Why does the address I'm transferring money to show a different one in the hash?
  • Why does it show that the transfer was successful, but the chain shows the amount as 0, and my receiving account didn't receive the transfer?
  1. TROUBLESHOOTING
  2. FAQ
  3. FAQ for Storage Providers

Transaction Issue

PreviousAgentsNextTUTORIALS

Last updated 10 months ago

Why is the amount of FIL available to borrow for my node so small given that I have more collateral available?

The current quota system within the pool may limit your borrowing capacity. This quota increases once the GLIF team has established a point of contact with the agent. Initially, this mechanism ensured that the team could communicate important upgrades or information to Storage Providers (SPs). You can request a quota increase .

Why does the address I'm transferring money to show a different one in the hash?

The hash is a unique identifier for your transaction. The transaction involves several underlying smart contract function calls before it finally transfers the FIL to the provided address.

Why does it show that the transfer was successful, but the chain shows the amount as 0, and my receiving account didn't receive the transfer?

This can be confusing but is correct. The top-level transaction is from your agent owner to your agent. The FIL transfer is an internal transaction within the system.

here