# Mergeable Tokens on Algorand

**URL:** <https://forum.algorand.co/t/mergeable-tokens-on-algorand/2864>\
**Category:** Uncategorized\
**Tags:** teal\
**Created:** [March 23, 2021, 12:13pm UTC](https://forum.algorand.co/t/mergeable-tokens-on-algorand/2864 "2021-03-23T12:13:33Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![Supirogurafu](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.algorand.co/supirogurafu/32/1001_2.png) [@Supirogurafu](https://forum.algorand.co/u/Supirogurafu)\
**Post date:** [March 23, 2021, 8:53pm UTC](https://forum.algorand.co/t/mergeable-tokens-on-algorand/2864/9 "2021-03-23T20:53:23Z")

</div>

Yes, you’re describing my intention correctly, @ryanRfox. Abstracting from the very helpful [tutorial on Assets and Custom Transfer Logic](https://developer.algorand.org/solutions/assets-and-custom-transfer-logic/) I would assume the contract would need to be the manager address so that the two input assets would be destroyed and the output asset would be generated. Presumably in that contract I could write the “risk” parameter to global/local state.

---

_[View the full topic](https://forum.algorand.co/t/mergeable-tokens-on-algorand/2864)._