In D15100#338969, @Fabien wrote:

why not use an explicit burn ? https://github.com/badger-cash/slp-self-mint-protocol/blob/master/token-type1-burn.md

..TIL

For now, main idea is to deprecate the complicated tx building functions / tests in Cashtab and replace them with simpler ones that clearly maintain the same functionality. I would like to add explicit OP_RETURN script generators, like those in the badger fork of Cashtab, and lose the slp-mdm library -- then, why not explicit burn?

But I think this should happen after the transaction functions are cleaned up.

In D15100#339016, @bytesofman wrote:

In D15100#338969, @Fabien wrote:

why not use an explicit burn ? https://github.com/badger-cash/slp-self-mint-protocol/blob/master/token-type1-burn.md

..TIL

For now, main idea is to deprecate the complicated tx building functions / tests in Cashtab and replace them with simpler ones that clearly maintain the same functionality. I would like to add explicit OP_RETURN script generators, like those in the badger fork of Cashtab, and lose the slp-mdm library -- then, why not explicit burn?

But I think this should happen after the transaction functions are cleaned up.

OK as a transition step but slp-mdm really is 328 lines of code including some code redundant with existing code in our repo. It can be removed easily by implementing our own set of functions. Also slp-mdm last version is 0.0.7 and it's already 3 years old, so unlikely to be maintained (even if it's simple enough that it should not require a lot of maintenance)

This revision is now accepted and ready to land.Jan 8 2024, 09:55

rebase

Harbormaster completed remote builds in B26217: Diff 43993.Jan 9 2024, 16:23

Closed by commit rABCe4e6f0954be9: [Cashtab] Add function to generate burn targetOutputs (authored by bytesofman). · Explain WhyJan 10 2024, 14:00

This revision was automatically updated to reflect the committed changes.

bytesofman added a commit: rABCe4e6f0954be9: [Cashtab] Add function to generate burn targetOutputs.