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.

Sign up for GitHub

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

Jump to bottom

[P<>K bridge] Kusama Fellowship replaced by the Polkadot Fellowship acting over the bridge #484

Open
4 tasks
Tracked by #490
acatangiu opened this issue Oct 15, 2024 · 0 comments
Open
4 tasks
Tracked by #490

[P<>K bridge] Kusama Fellowship replaced by the Polkadot Fellowship acting over the bridge #484

acatangiu opened this issue Oct 15, 2024 · 0 comments

Comments

@acatangiu
Copy link
Contributor

Description

We want to retire the Kusama Technical Fellowship and have its functions fulfilled by the Polkadot Technical Fellowship acting over the bridge.

Progress
@pandres95 pandres95 mentioned this issue Oct 20, 2024
Merged
12 tasks
fellowship-merge-bot bot pushed a commit that referenced this issue Dec 12, 2024
@pandres95 @clangenb
@claravanstaden @Ank4n @seadanda @bkontur
Update to SDK stable2409-1 (#490)
7b096c1 
Closes #457 
Closes #469

Updating the runtimes to SDK version `stable2409-1`. CHANGELOG mentions
all relevant changes for UI and Walletbuilders.

## Checklist

- [x] Update SDK to `stable2409`
- [x] Update configuration for relay chains.
- [x] Update configuration for system parachains.
- [x] Update configuration for emulated chains.
- [x] Update configuration for Encointer (see _Help wanted_).
- [x] Update CHANGELOG.
- [x] Update SDK to `stable2409-1`

## Dependencies

This PR depends on certain PRs to be merged before it can properly work.

- [x] #472

## Impacts

The success of this PR impacts directly on the feasibility of executing
certain issues, or closing certain PRs.

- [ ] #455
- [ ] #476
- [ ] #480
- [ ] #484

## Help wanted

Initially, I request the help of:

- @franciscoaguirre to help me correcting the potential conflicts that
may arise when foreign assets change to `XCMv4`.
- @acatangiu to help me setting up the Bridge Hubs, as well as adding
the respective transition layer (a.k.a. preparing the migrations from
fixed `Lanes` to `LegacyLane`-based lanes storage).
- @clangenb to help me upgrading Encointer.
- @Szegoo to check the parameters that changed in Coretime.

---------

Co-authored-by: clangenb <[email protected]>
Co-authored-by: Clara van Staden <[email protected]>
Co-authored-by: Ankan <[email protected]>
Co-authored-by: Dónal Murray <[email protected]>
Co-authored-by: Branislav Kontur <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@acatangiu