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

[RFC] Add Paseo NetworkId #58

Closed
wants to merge 1 commit into from
Closed

[RFC] Add Paseo NetworkId #58

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
40 changes: 40 additions & 0 deletions proposals/0000-paseo-network-id.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,40 @@
---
Title: Add Paseo NetworkId
Number: 0
Status: Draft
Version: 5
Authors:
- Francisco Aguirre
Created: 2024-05-23
Impact: Low
Requires:
Replaces:
---

## Summary

This RFC proposes adding the Paseo testnet as a `NetworkId`, for easier identification.

## Motivation

While the Paseo testnet can be addressed using `NetworkId::ByGenesis`, the importance in the Polkadot ecosystem merits
their own `NetworkId`, just as `Rococo`.

## Specification

The `NetworkId` enum is getting a new variant, `Paseo`.

The relevant paragraph in the spec will be changed to reflect this.

## Security considerations

None.

## Impact

The impact of this proposal is low.
XCMs referencing Paseo via `ByGenesis` can just change to use the `Paseo` specific `NetworkId`.

## Alternatives

Not add the specific `NetworkId` and just leave it as `ByGenesis`.