From 00e0db312bb1c3afa5cf0a3e561e8247cefcb958 Mon Sep 17 00:00:00 2001 From: Valentyn Faychuk Date: Mon, 23 Dec 2024 18:44:39 +0200 Subject: [PATCH] switch to correct solana RPCs --- README.md | 10 ++++++---- src/solana.rs | 3 +++ 2 files changed, 9 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 5ba382a..4a2ae09 100644 --- a/README.md +++ b/README.md @@ -43,14 +43,16 @@ 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. + to the disk, it will remain sealed and when the node will restart and try to join + the rest of the network, it will still use the private key from the disk for + minting and sharing. 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). + some cloud providers, like Azure Intel SGX VMs (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. - +5. The challenge is not mutable once deployed, which means that it will remain + secure for as long as the community will not find a new vulnerability in SGX. diff --git a/src/solana.rs b/src/solana.rs index f62d775..b4d8b98 100644 --- a/src/solana.rs +++ b/src/solana.rs @@ -15,7 +15,10 @@ use spl_token::{ }; use tokio::time::{sleep, Duration}; +#[cfg(feature = "test")] const RPC_URL: &str = "https://api.devnet.solana.com"; +#[cfg(not(feature = "test"))] +const RPC_URL: &str = "https://api.mainnet-beta.solana.com"; pub struct SolClient { client: RpcClient,