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

[SPIKE] Bridge SORA Mainnet <-> SORA Parachain #33

Closed
Tieumsan opened this issue Jun 28, 2022 · 1 comment
Closed

[SPIKE] Bridge SORA Mainnet <-> SORA Parachain #33

Tieumsan opened this issue Jun 28, 2022 · 1 comment
Assignees
Labels
spike Further information is requested or research is required

Comments

@Tieumsan
Copy link
Contributor

Tieumsan commented Jun 28, 2022

What do other projects use ?

Common solution - Parity bridge ?

Update doc: https://soramitsu.atlassian.net/wiki/spaces/PLS/pages/2213347329/Substrate+-+Relay-chain+bridge

Update with sora network—sora kusama parachain bridge

parity bridge commons pallet

Study: https://github.com/paritytech/parity-bridges-common

Investigate what networks use this

3 cases:

  • asset created on the sora network, move it back and forth to the kusama parachain
  • asset created on the sora kusama parachain and move it back and forth to the sora network
  • asset created on another network and moved to the sora kusama parachain via xcm and move it back and forth to the sora network (highest priority)
@Tieumsan Tieumsan added the spike Further information is requested or research is required label Jun 30, 2022
@N1ghtStorm
Copy link
Contributor

@Tieumsan Tieumsan changed the title [SPIKE] Bridge SORA <-> Kusama Parachain [SPIKE] Bridge SORA Mainnet <-> SORA Parachain Aug 1, 2022
@bgodlin bgodlin transferred this issue from sora-xor/sora2-network Sep 9, 2022
@bgodlin bgodlin added this to the Interoperability with Kusama milestone Sep 18, 2022
@Tieumsan Tieumsan closed this as completed Oct 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spike Further information is requested or research is required
Development

No branches or pull requests

3 participants