Litchi Pi

The problem is that `echo "'$1'"` creates an execution line like this: ``` env CC_x86_64-unknown-linux-gnu= CXX_x86_64-unknown-linux-gnu= CC_x86_64-unknown-linux-gnu= CXX_x86_64-unknown-linux-gnu= DEP_GDK-3_INCLUDE= 'DEP_GDK-3_BACKENDS='\''broadway' wayland 'x11'\''' DEP__INCLUDE= /cargo build --release --target x86_64-unknown-linux-gnu --no-default-features --message-format...

My bad the problem is not the function you created, it's because it requires `dep_keys_sanitized="$(echo ''${depKeys[@]})"` in `mkcrate-utils.sh`

Yes it only causes a problem on `nixos-unstable`, but I thought the `unstable` branch was synced with nixpkgs `unstable` Well I let you merge it / delay it however you...

@kolloch If you think it's a good first issue, I am willing to try to solve it Are you able point out what is going wrong here, and what is...

@AurelienFT If you have a list on the issue board for security issues, this one could go into it. If you don't have this list, consider making one, that'd be...

If we start a labnet without keeping the ledger, just a normal one without any operations on the branch `test_bootstrap_big`, the bootstrap process will work but the hashes of `final_state`...

I figured out why the `final state` hash are different when the node generates a brand new ledger, it works now. However, it's still different when a ledger is generated...

~~The hash mismatch occurs when launching a labnet on `main` with crafted ledger. After I tried with smaller keys / values in datastore (length 9000), it still does it, so...

That's actually what I already do - A while ago I started a node normally, and copied the storage into a local folder `A`. - To craft a new ledger,...

@Leo-Besancon My bad, I made a mistake while writing the message, when using smaller datastore key + value, the hashes DOES MATCH, so it seams that's it's linked to the...