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

SharesBurn

This table stores data related to the burning of Lido shares, potentially during a rebase event. It includes the account address, the token amounts before and after the rebase, and the number of shares burned.

Schema

Data Fields
Description

id

A unique identifier for the share burn event.

account

A unique identifier for the share burn event.

post_rebase_token_amount

A unique identifier for the share burn event.

pre_rebase_token_amount

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

shares_amount

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

PreviousLidoTransferNextLidoApproval