# LIP-9: Add an explicit log for the stETH burn events

**URL:** <https://research.lido.fi/t/lip-9-add-an-explicit-log-for-the-steth-burn-events/1609>\
**Category:** The LIP - Lido Improvement Proposal - Process\
**Created:** [January 24, 2022, 2:15pm UTC](https://research.lido.fi/t/lip-9-add-an-explicit-log-for-the-steth-burn-events/1609 "2022-01-24T14:15:29Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![arwer13](https://dub1.discourse-cdn.com/flex013/user_avatar/research.lido.fi/arwer13/32/798_2.png) [@arwer13](https://research.lido.fi/u/arwer13)\
**Post date:** [January 24, 2022, 2:15pm UTC](https://research.lido.fi/t/lip-9-add-an-explicit-log-for-the-steth-burn-events/1609/1 "2022-01-24T14:15:29Z")

</div>

# Motivation

Burning of the `stETH` underlying shares is one of the on-chain effects causing `stETH` token rebase. We’d like to have all token rebases logged. It’s a good thing to have in general. In particular, it would allow not to miss a rebase for the off-chain interactive UIs and to sync on-chain storage change with 3rd-party off-chain indexers and monitoring.

# Solution

We propose to include `StETHBurnt` event into the `StETH` contract and emit the proposed event on every `burnShares` invocation. The event must include information about the caller account, burnt shares amount and the corresponding amount of tokens burnt. It would allow to complete off-chain logs and hold a new invariant for Lido: every `stETH` token rebase must be covered with the some explicitly emitted event.

# Specification

Further details and code example are provided on the [LIP](https://github.com/lidofinance/lido-improvement-proposals/blob/develop/LIPS/lip-9.md) GitHub repo.

# References

- [stETH token contract](https://docs.lido.fi/contracts/lido)
- [use case of shares burning to apply coverage](https://research.lido.fi/t/lip-6-in-protocol-coverage-proposal/1468)
- [example implementation for the proposal](https://github.com/lidofinance/lido-dao/pull/373)