Allow burn to have a callback just like Send

[ferencdg]

it would be nice to have contracts (usually the owner) notified that certain tokens have been burned just like it is done with the Send message

[ueco-jb]

Is cw-plus right place for such request?
Could you share more details what you have in mind with Send message callback?

[ferencdg]

Is cw-plus right place for such request? Could you share more details what you have in mind with Send message callback?

sorry what I meant is your cw20 implementation
https://github.com/CosmWasm/cw-plus/blob/main/packages/cw20/README.md

the send allows calling back a contract:
Send{contract, amount, msg}

however the Burn doesn't
Burn{amount}

but contracts might want to be notified too that some users burnt some tokens (possibly a token managed by the contract that needs to be called)

[mr-rooftop]

yes that would be very useful!

[ethanfrey]

Currently, you could Send it to the contract, and that contract will do whatever action is expected, and then return another message to burn the tokens it just received.

Understood that is not the UX you want, but it will serve as a placeholder

[ethanfrey]

Also, Burn was designed as an analog to Transfer (which doesn't call a contract).
We would need a new name for this method. And I'm still not sure it would be that heavily used such that my workaround (above) wouldn't be sufficient

[ferencdg]

thanks, I was aware of this workaround, just hoped there will be a direct support if you think it is an unnecessary feature, then please close this ticket, thanks

…

On Tue, May 17, 2022 at 2:53 AM Ethan Frey ***@***.***> wrote: Also, Burn was designed as an analog to Transfer (which doesn't call a contract). We would need a new name for this method. And I'm still not sure it would be that heavily used such that my workaround (above) wouldn't be sufficient — Reply to this email directly, view it on GitHub <#717 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AEXFZQERMNONELB7JRMXTU3VKKRSVANCNFSM5VIDVAAQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>