# Statemint/e Swap Discussion

**URL:** <https://forum.polkadot.network/t/statemint-e-swap-discussion/1498>\
**Category:** Tech Talk\
**Created:** [December 19, 2022, 11:47am UTC](https://forum.polkadot.network/t/statemint-e-swap-discussion/1498 "2022-12-19T11:47:47Z")\
**Posts on this page:** 1\
**Showing post:** 22

<div class="post-metadata">

**Author:** ![0mm-mark](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.polkadot.network/0mm-mark/32/850_2.png) [@0mm-mark](https://forum.polkadot.network/u/0mm-mark)\
**Post date:** [January 26, 2023, 5:26am UTC](https://forum.polkadot.network/t/statemint-e-swap-discussion/1498/22 "2023-01-26T05:26:02Z")

</div>

I believe the following discussion is relevant. In particular, if you object to the Statemine/Statemint DEX proposal, I’d be interested in whether my governance “blue-sky” suggestion would be attractive to you:

> [@Protecting your Parachain/Parathread against Expropriation](https://forum.polkadot.network/t/expropriation-safeguards/1831/2):
>
> I’ll kick off with my 2c Are there any enforceable governance safeguards against Polkadot expropriating your Parachain/Parathread idea? I don’t know with any certainty. The Statemine/Statemint DEX discussion strongly suggests there isn’t, or it is not generally known. Are such on-chain governance safeguards feasible in the current governance code? I’m not that familiar with the code. What should such a safeguard look like? The governance should have a hard/irrevocable bar on Polkadot ever …

---

_[View the full topic](https://forum.polkadot.network/t/statemint-e-swap-discussion/1498)._
