# Merger Between Osmosis and Umee

**URL:** <https://forum.osmosis.zone/t/merger-between-osmosis-and-umee/780>\
**Category:** Ecosystem\
**Created:** [December 3, 2023, 7:03pm UTC](https://forum.osmosis.zone/t/merger-between-osmosis-and-umee/780 "2023-12-03T19:03:28Z")\
**Posts on this page:** 6\
**Page:** 3

<div class="post-metadata">

**Author:** ![The\_Person](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.osmosis.zone/the_person/32/987_2.png) [@The\_Person](https://forum.osmosis.zone/u/The_Person)\
**Post date:** [December 30, 2023, 4:44pm UTC](https://forum.osmosis.zone/t/merger-between-osmosis-and-umee/780/42 "2023-12-30T16:44:56Z")

</div>

I’d like to discuss the possible migration strategies more. is it a significant amount of maintenance time for both teams? how often. ect

is it possible to do option one in the short term so the product is usable within the app and then work toward a maintenance-free option?

---

<div class="post-metadata">

**Author:** ![robert](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.osmosis.zone/robert/32/774_2.png) [@robert](https://forum.osmosis.zone/u/robert)\
**Post date:** [December 31, 2023, 3:56pm UTC](https://forum.osmosis.zone/t/merger-between-osmosis-and-umee/780/43 "2023-12-31T15:56:25Z")

</div>

There is always a maintenance and series of improvements.

We were also discussing an option to merge the Go code, and do the new stuff in cosmwasm layer. If we will do the Go code merge, then I think we will discuss improvements and new features case by case.

---

<div class="post-metadata">

**Author:** ![LeonoorsCryptoman](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.osmosis.zone/leonoorscryptoman/32/208_2.png) [@LeonoorsCryptoman](https://forum.osmosis.zone/u/LeonoorsCryptoman)\
**Post date:** [January 1, 2024, 7:30pm UTC](https://forum.osmosis.zone/t/merger-between-osmosis-and-umee/780/44 "2024-01-01T19:30:18Z")

</div>

I can imagine, but merging the code in the first place moves the work done further away from the harmonisation I think?

Or do I have to see it more like UMEE being a module?

---

<div class="post-metadata">

**Author:** ![Rahul\_Patel](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.osmosis.zone/rahul_patel/32/2020_2.png) [@Rahul\_Patel](https://forum.osmosis.zone/u/Rahul_Patel)\
**Post date:** [March 23, 2024, 2:27pm UTC](https://forum.osmosis.zone/t/merger-between-osmosis-and-umee/780/45 "2024-03-23T14:27:44Z")

</div>

@robert hey i heard osmosis was no longer interested in merging with umee. any updates on what happened?

---

<div class="post-metadata">

**Author:** ![robert](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.osmosis.zone/robert/32/774_2.png) [@robert](https://forum.osmosis.zone/u/robert)\
**Post date:** [March 23, 2024, 5:38pm UTC](https://forum.osmosis.zone/t/merger-between-osmosis-and-umee/780/46 "2024-03-23T17:38:47Z")

</div>

Actually, we are working on a new product that will bind Osmosis DEX with the UX Chain leverage protocol.  
Stay tuned for more announcements next weeks.

---

<div class="post-metadata">

**Author:** ![RSCriss](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.osmosis.zone/rscriss/32/757_2.png) [@RSCriss](https://forum.osmosis.zone/u/RSCriss)\
**Post date:** [April 26, 2024, 7:18pm UTC](https://forum.osmosis.zone/t/merger-between-osmosis-and-umee/780/47 "2024-04-26T19:18:57Z")

</div>

Merger Update blogpost:

> **[UX & Osmosis Merger Update: Exploring Paths for the Future of DeFi - UX...](https://www.ux.xyz/blog/ux-osmosis-merger)**
>
> We are sharing an exciting progress update on the UX and Osmosis merger discussions. We're looking at a range of options that will benefit both communities, from mesh security to a hybrid approach. Read more about what's ahead...

[Previous page](https://forum.osmosis.zone/t/merger-between-osmosis-and-umee/780.md?page=2)