Skip to content

Commit

Permalink
[XCM]: Remove NetworkIds for testnets (#108)
Browse files Browse the repository at this point in the history
Testnets are not stable and shouldn't be included in the XCM language.
They should be able to be specified with `NetworkId::ByGenesis`.
  • Loading branch information
franciscoaguirre authored Aug 5, 2024
1 parent 091d8d9 commit 094dcea
Showing 1 changed file with 61 additions and 0 deletions.
61 changes: 61 additions & 0 deletions text/0108-xcm-remove-testnet-ids.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,61 @@
# RFC-0108: Remove XCM testnet NetworkIds

| | |
| --------------- | ------------------------------------------------------------------------------------------- |
| **Start Date** | 23 July 2024 |
| **Description** | Remove the NetworkIds for testnets Westend and Rococo |
| **Authors** | |

## Summary

This RFC aims to remove the `NetworkId`s of `Westend` and `Rococo`, arguing that testnets shouldn't go in the language.

## Motivation

We've already seen the plans to phase out Rococo and Paseo has appeared.
Instead of constantly changing the testnets included in the language, we should favor specifying them via their genesis hash,
using `NetworkId::ByGenesis`.

## Stakeholders

- Runtime devs
- Wallets
- dApps

## Explanation

Remove `Westend` and `Rococo` from the included `NetworkId`s in the language.

## Drawbacks

This RFC will make it less convenient to specify a testnet, but not by a large amount.

## Testing, Security, and Privacy

None.

## Performance, Ergonomics, and Compatibility

### Performance

None.

### Ergonomics

It will very slightly reduce the ergonomics of testnet developers but improve the stability of the language.

### Compatibility

`NetworkId::Rococo` and `NetworkId::Westend` can just use `NetworkId::ByGenesis`, as can other testnets.

## Prior Art and References

A previous attempt to add `NetworkId::Paseo`: https://github.com/polkadot-fellows/xcm-format/pull/58.

## Unresolved Questions

None.

## Future Directions and Related Material

None.

0 comments on commit 094dcea

Please sign in to comment.