From 8fef8d6dc66260f1b8744ab9afaf54c85cdaf7f7 Mon Sep 17 00:00:00 2001 From: Valentyn Faychuk Date: Mon, 23 Dec 2024 00:25:39 +0200 Subject: [PATCH] documentation update --- README.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/README.md b/README.md index d3aa52a..5ba382a 100644 --- a/README.md +++ b/README.md @@ -39,3 +39,18 @@ The node homepage source is also [here](./src/HOMEPAGE.md). ## Contributing to the challenge Don't forget to run `cargo clippy` and `cargo fmt` before submitting a PR. + +## Known issues + +1. If you create a new node as a root and it will create the private key and save it + to the disk, it will remain sealed and when the node will try to connect to the + rest of the network, it will still use the private key from the disk for minting. +2. If you run the hacker challenge on the Out Of Life processors you may have a + privilege to run certain attacks, for instance check (this + article)[https://x.com/PratyushRT/status/1828183761055330373]. +3. The challenge is compiled using the HW mode, not HYPER so it may not work on + the cloud providers (needs more testing). +4. The performance and stability of the challenge is not at its theoretical peak as + the challenge was done mostly as a poc and was not meant to be infinitely scalable + or very performant. +