documentation update
This commit is contained in:
parent
f256e5e44f
commit
8fef8d6dc6
15
README.md
15
README.md
@ -39,3 +39,18 @@ The node homepage source is also [here](./src/HOMEPAGE.md).
|
|||||||
## Contributing to the challenge
|
## Contributing to the challenge
|
||||||
|
|
||||||
Don't forget to run `cargo clippy` and `cargo fmt` before submitting a PR.
|
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.
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user