-
Notifications
You must be signed in to change notification settings - Fork 216
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
Fork dependent Chain spec #2197
Conversation
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
outdated.. RIP |
This is an attempt at making chain specs fork dependent that is more structural than #2194 but still incomplete. This PR:
chan.SpecData
structure and replaces it withspec.Common
struct, where it can access chainIDs and forksGet
prefix tochain.Spec
interface to avoid conflicts with attributesBlockBodyKZGOffset
to avoid import cycles amongchainSpec
andconsensus-types
modulescommon.ChainSpec
type instantiation and usesspec.Chain
instead.chain-spec
module and just usesconfig\spec