Implementation of Algoburner

[wxivd]

Token burning affect the total supply of given tokens such as Yieldly, Choice, HDL.

Accounting for that in the portfolio view would facilitate the purpose of providing accurate information of ASA held in Wallet

What technical difficulties are there for implementation of such information

[ipaleka]

We don't have a system for presenting events, that would be the first one, is that worth it?

We can add an additional item of circulating supply to the left, but then that event should be presented only indirectly, by a lower value after it happens.

[wxivd]

We don't have a system for presenting events, that would be the first one, is that worth it?

That's open for discussion. I do not see it as a priority for now.

Initial thoughts were about deducting the amount of Assets sent to the burner account wallet from the total supply. This could be presented as burnt or permanently locked. A downside to this is the amount of manual work and presuming the burner wallet is kept the same for each ASA.

The assumption did not hold true. Each burning is set to new wallet as is shown in Yieldly (1 & 2)

We can add an additional item of circulating supply to the left, but then that event should be presented only indirectly, by a lower value after it happens.

How can is be presented indirectly? Something down the line of presenting ASA-list in distinct page similar to Tinyman ASA List (with handpicked asset details)

[ipaleka]

How can is be presented indirectly?

I mean, just by showing circulating supply value. So if you looked before and then if you look after burning, those two values will differ.

Algorand doesn't have an actual burning mechanism implemented, so projects are using some pseudo-burning mechanism, IIRC when you send an amount to those escrows like Yieldly did in that example, then the circulating supply value decreases.