From 0db70efa553e2dc37ff672ca4062bdbe592ab450 Mon Sep 17 00:00:00 2001
From: Hugo Trentesaux <hugo@trentesaux.fr>
Date: Mon, 13 Mar 2023 18:43:05 +0100
Subject: [PATCH] wip smooth

---
 docs/dev/launch-a-live-network.md | 18 +-----------------
 docs/dev/release-new-runtime.md   |  2 +-
 2 files changed, 2 insertions(+), 18 deletions(-)

diff --git a/docs/dev/launch-a-live-network.md b/docs/dev/launch-a-live-network.md
index a92ffbcd2..cc87050d8 100644
--- a/docs/dev/launch-a-live-network.md
+++ b/docs/dev/launch-a-live-network.md
@@ -15,8 +15,7 @@ When launching a new network, you're likely to use a new runtime. See how to [re
 
 ### Inject runtime in chainspec
 
-FIXME order?
-Once you updated your session keys, inject the runtime code built with srtool inside the raw chainspec file.
+ÄžDev runtime is automatically embeded in the raw chainspec with the `include_bytes!` macro. An other way to inject the runtime is to use "inject-runtime-code" xtask:
 
 ```bash
 cargo xtask inject-runtime-code --runtime runtime/gdev/target/srtool/release/wbuild/gdev-runtime/gdev_runtime.compact.compressed.wasm --raw-spec resources/gdev-raw.json 
@@ -26,8 +25,6 @@ cargo xtask inject-runtime-code --runtime runtime/gdev/target/srtool/release/wbu
 
 ### Choose the currency type
 
-Ensure that the currency type you want has the requirements (TODO explain).
-
 For now, only `gdev` is supported.
 
 In the commands that will be indicated afterwards, you will have to replace `CURRENCY` by the
@@ -109,15 +106,6 @@ The following steps should be completed once you are satisfied with the new live
 
 You should rotate session keys for more secured keys produced on the server (the one you used before are still in your develop machine bash history and clipboard).
 
-TODO explain how with polkadotjs + vpn (?)
-
-Then update the raw chainspec file with your new session keys. (FIXME is this right?)
-
-### Embed the raw chainspec in the binary
-
-TODO embed the raw chain spec in the binary with include_bytes! macro
-
-
 ### Publish image
 
 With these new session keys in the chainspec and the runtime build with srtool, you can release the new runtime again with: 
@@ -129,7 +117,3 @@ cargo xtask release-runtime 400
 ### Tell the other smith
 
 Once you completed all these steps, the other smith can pull the docker image with a genesis containing your bootnode with the correct session keys. They can base their `docker-compose.yml` on the `duniter-validator` template.
-
----
-
-TODO rusty-hook pb?
\ No newline at end of file
diff --git a/docs/dev/release-new-runtime.md b/docs/dev/release-new-runtime.md
index b2a0b4b93..43920e1c5 100644
--- a/docs/dev/release-new-runtime.md
+++ b/docs/dev/release-new-runtime.md
@@ -4,7 +4,7 @@ Here you will learn how to release a new runtime using `gitlab ci` and `cargo xt
 
 ## Runtime tag and spec version
 
-When launching a new network, you're likely to use a new runtime for the genesis. Our runtime tags use `xxyy` version numbers where `x` corresponds to major change and `y` hotfix.
+Our runtime tags use `xxyy` version numbers where `x` corresponds to major change and `y` hotfix.
 
 1. Make sure to move any issue or merge request assigned to the choosen milestone `runtime-xxyy` to the next one. This prevents from forgetting unfinished work.
 1. Check that the [CI on release/runtime-XX00](https://git.duniter.org/nodes/rust/duniter-v2s/-/pipelines?scope=all&page=1&ref=runtime-400) (runtime major release branch) is passing. This is necessary to build the docker images.
-- 
GitLab