Uh oh!
There was an error while loading. Please reload this page.
chore: update RILT chain spec and boot nodes - #633
Conversation
ntn-x2
commented
May 29, 2024
@Ad96el can you pick this up now and update accordingly? I think it's also a nice exercise to get familiar with the new structure. |
In order to get the chain spec, I did:
Genesis state
|
ntn-x2
left a comment
There was a problem hiding this comment.
I don't think we need a new module. The peregrine-new generator generates a chainspec that is supposed to be changed locally, as long as the runtime stays the same. So we don't need a rilt-new nor the rilt module, but simply generate a new chainspec, make any changes locally, generate the raw spec, and paste that into the file tree to be used as rilt.
ntn-x2
left a comment
There was a problem hiding this comment.
If the chainspec is the one currently running, let's merge this 🚀
ntn-x2
commented
Jul 17, 2024
Integration tests will be fixed in a separate PR. |
## fixes KILTProtocol/ticket#3400
RILT is booted from scratch, resulting in a different genesis
state/wasm. To add more nodes later on, we need to update the chain's
specifications.
The chain spec is generated by calling: `docker run kiltprotocol/kilt-node:1.13.0 build-spec --chain=rilt-new
--raw > nodes/parachain/res/rilt.json`
The deprecated bootnodes are also updated.
fixes KILTProtocol/ticket#3400
RILT is booted from scratch, resulting in a different genesis state/wasm. To add more nodes later on, we need to update the chain's specifications.
The chain spec is generated by calling:
docker run kiltprotocol/kilt-node:1.13.0 build-spec --chain=rilt-new --raw > nodes/parachain/res/rilt.jsonThe deprecated bootnodes are also updated.