general/hacker-challenge
4
0
Fork 1
Code Issues Pull Requests Packages Projects Releases Wiki Activity

switch to correct solana RPCs

Browse Source
This commit is contained in:
Valentyn Faychuk 2024-12-23 18:44:39 +02:00
parent 8fef8d6dc6
commit 00e0db312b
Signed by: valy
GPG Key ID: F1AB995E20FEADC5
2 changed files with 9 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@ -43,14 +43,16 @@ Don't forget to run `cargo clippy` and `cargo fmt` before submitting a PR.
## Known issues ## Known issues
1. If you create a new node as a root and it will create the private key and save it 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 to the disk, it will remain sealed and when the node will restart and try to join
rest of the network, it will still use the private key from the disk for minting. 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 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 privilege to run certain attacks, for instance check (this
article)[https://x.com/PratyushRT/status/1828183761055330373]. article)[https://x.com/PratyushRT/status/1828183761055330373].
3. The challenge is compiled using the HW mode, not HYPER so it may not work on 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 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 the challenge was done mostly as a poc and was not meant to be infinitely scalable
or very performant. 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.

3
src/solana.rs
View File

@ -15,7 +15,10 @@ use spl_token::{
}; };
use tokio::time::{sleep, Duration}; use tokio::time::{sleep, Duration};
#[cfg(feature = "test")]
const RPC_URL: &str = "https://api.devnet.solana.com"; 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 { pub struct SolClient {
client: RpcClient, client: RpcClient,