Blockflow Docs
Console
Console
  • Welcome to BlockFlow!
    • 👋Introduction
    • 🪄The Difference
    • ✊Our motivation
  • Overview
    • 💡What we do
    • 📪Databases
    • 🚄Instances
    • ✈️APIs
    • ㊙️Secret Manager
  • Guides
    • 📪Creating a Database
      • 🖊️Working with Managed Database
    • 🚄Creating an Instance
      • 🖊️Defining Actions in Blockflow Instances
    • ✈️Creating an API
      • 🖊️How to write API logics
      • 🖊️How to get API Key
      • 🖊️Calling APIs on Blockflow
      • 🖊️How to Test APIs
    • ㊙️Storing Secrets
  • Use Cases
    • Lido Finance
      • Databases
        • LidoSubmission
        • LidoTransfer
        • SharesBurn
        • LidoApproval
        • CurrentFee
        • LidoConfig
        • LidoTotals
        • LidoStats
        • LidoHolder
        • LidoShares
        • LidoOracleConfig
        • LidoOracleReport
        • LidoOracleCompleted
        • LidoOracleMember
        • LidoNodeOperatorFees
        • LidoNodeOperatorsShares
        • LidoBeaconReport
        • LidoOracleExpectedEpoch
        • LidoTotalReward
      • Contracts
        • Lido
        • Lido Legacy Oracle
  • Pricing
    • Blockflow Pricing Structure
Powered by GitBook
On this page
  1. Use Cases
  2. Lido Finance
  3. Databases

LidoApproval

This table keeps track of approval events, where an account owner grants permission to another address (spender) to spend a certain amount of the owner's tokens (e.g., Lido shares).

Schema

Data Fields
Description

id

The amount of tokens held by the account before the rebase.

owner

The address of the account that approved the spending.

spender

The address that was approved to spend the owner's tokens.

value

The amount of tokens (e.g., Lido shares) that the spender is allowed to spend.

PreviousSharesBurnNextCurrentFee