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

[WIP] Yet Another Parachain #6089

Draft
wants to merge 2 commits into
base: stable2409
Choose a base branch
from
Draft

[WIP] Yet Another Parachain #6089

wants to merge 2 commits into from

Conversation

s0me0ne-unkn0wn
Copy link
Contributor

This PR adds yet another testing parachain (YAP) with the following features:

  • It parses its own chainspec name to learn to which relay chain it belongs and what parachain ID it should use (examples being yap-rococo-local-100 or yap-kusama-live-2089);
  • Its genesis state contains 16000 pre-funded account pairs derived from seeds //Sender/<n> and //Receiver/<n> where n ∈ [0, 15999]. Regular well-known testing accounts are also available;
  • It contains balances and sudo pallets (the latter is bound to the Alice account) and is missing the XCM functionality;
  • It has CheckNonce and CheckGenesis signed extensions disabled.

};
use yet_another_parachain_runtime::AuraId;

const NUM_ACCOUNT_PAIRS: usize = 16000;
Copy link
Member

@eskimor eskimor Oct 30, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would 12k suffice? (Given our current PoV size limitations, might be beneficial for the community spamming chains.)

@s0me0ne-unkn0wn s0me0ne-unkn0wn changed the base branch from master to stable2409 November 11, 2024 14:50
Copy link

This pull request is amending an existing release. Please proceed with extreme caution,
as to not impact downstream teams that rely on the stability of it. Some things to consider:

  • Backports are only for 'patch' or 'minor' changes. No 'major' or other breaking change.
  • Should be a legit fix for some bug, not adding tons of new features.
  • Must either be already audited or not need an audit.
Emergency Bypass

If you really need to bypass this check: add validate: false to each crate
in the Prdoc where a breaking change is introduced. This will release a new major
version of that crate and all its reverse dependencies and basically break the release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants