Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Para-object: Path to Polkadot #157

Closed
jplatts12 opened this issue Nov 12, 2019 · 2 comments
Closed

Para-object: Path to Polkadot #157

jplatts12 opened this issue Nov 12, 2019 · 2 comments
Assignees
Labels
K3 - Parachains Parachain information. P2 - Sometime Soon Update that isn't urgent or needed immediately. T0 - Enhancement Content needs to be updated.

Comments

@jplatts12
Copy link

We need a list of possible migration paths and some examples from the real world of how this is being done.

Some teams we are speaking have a liquid ERC-20 token, which is listed and available for trading on exchanges. They want to migrate to be a Parachain with their own on-chain currency. They were concerned about the specifics of transitioning from one to the other with minimal community and liquidity costs.

One of the best things we can do is a lock/burn contract on Ethereum, which can then be used to bootstrap claims on the Parachain

  • One implementation detail, do they plan to support multiple imports of the contract? Or is it like "you either move your tokens by this date or else you don't get them"?
  • Binance did their migration using a deadline.
  • The lock/burn approach is being used by some of these teams because it is the common trend when migrating tokens between chains. This how we are doing it for Polkadot too. The DOT token has a placeholder as an ERC20 on Ethereum and it will be migrated to Polkadot on launch.

Having an example side chain of this would also be cool to link from the Wiki. Shawn from Parity might be able to ideate on this more or even code something up if Tech Ed can coordinate with them that would begreat.

@Swader
Copy link
Contributor

Swader commented Nov 14, 2019

IMO it's a bit of a hard sell parachains as the go-to strategy aren't all that viable for a large number of projects (and we want as many as possible to move!). In reality few even well established ERC20-powered projects in Eth (regardless of the volumes of liquidity they have) will be able or willing to afford a slot. IMO we should be demoing migration paths that focus more on parathreads or better yet migration to a de-facto tokenchain that we spin up in one of the reserved slots, rather than try and sell the dedicated chain story to each and every project which, ultimately, has the exact same thing under the hood (a simple ERC20 token). My 2 mDOT.

@lsaether lsaether self-assigned this Nov 14, 2019
@lsaether lsaether added the P2 - Sometime Soon Update that isn't urgent or needed immediately. label Mar 19, 2020
@salmad3 salmad3 added the T0 - Enhancement Content needs to be updated. label Aug 9, 2021
@salmad3 salmad3 added the K3 - Parachains Parachain information. label Sep 13, 2021
@salmad3 salmad3 changed the title Migration Paths for Existing Tokens Para-object: Path to Polkadot Sep 14, 2021
@salmad3
Copy link
Contributor

salmad3 commented Sep 14, 2021

We have content that briefly points to some of the items mentioned in the original issue, although the comments Bruno left seems like the most viable approach.

This is similar to the conflict I felt with: #286

We can focus on the smart contract platforms that have secured a slot on Kusama.

  • Moonriver
  • Shiden

Others examples in the ecosystem:

  • Edgeware
  • Acala’s upcoming DeFi Smart Contract Platform

Then, bridge parachains and parathreads

salmad3 added a commit that referenced this issue Sep 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
K3 - Parachains Parachain information. P2 - Sometime Soon Update that isn't urgent or needed immediately. T0 - Enhancement Content needs to be updated.
Projects
None yet
Development

No branches or pull requests

5 participants