[Feature]: Split Runtime and Node - Githubissues

frequency-chain / frequency

Frequency: A Polkadot Parachain

https://www.frequency.xyz

Apache License 2.0

48 stars 18 forks source link

[Feature]: Split Runtime and Node #2043

Open wilwade opened 1 week ago

wilwade commented 1 week ago

Feature Description

Details

It is now possible to separate out the repositories for the node vs the runtime code of the chain.

Goal

To have a clean separation between the node and the runtime

A/C (Repo Split Version)

(Note names are WIP)

Two repos, both with the history up to now
frequency-chain/runtimes (or should this still be the frequency repo?): Contains the Mainnet and Testnet runtimes
- Produces wasm and runtime related artifacts only
frequency-chain/node: Contains the custom node code for frequency
- Produces the Docker images and node binaries

Open Questions

How do we handle local development runtime builds? aka what does make start do in what repo?
Do we need to separate repos or just one repo with separate folders?
Testing e2e setup goes in which repo or both?
Where does api-augment live?

Related

Polkadot Runtimes: https://github.com/polkadot-fellows/runtimes/
Paseo Runtimes: https://github.com/paseo-network/runtimes/

Searched for Related Issues

[X] I have done a search for related issues and either found none, or noted them