ghostchain/ghost-telemetry-backend
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

issue with network genesis hash after re-deployment, thanks to f4ts0

Browse Source 
Signed-off-by: Uncle Stinky <uncle.stinky@ghostchain.io>
This commit is contained in:
Uncle Stinky 2024-12-15 18:16:36 +03:00
parent 51e78f29e7
commit ae56c4baf9
Signed by: st1nky
GPG Key ID: 016064BD97603B40
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
telemetry-core/src/state/chain.rs
View File

@ -68,7 +68,7 @@ pub struct RemoveNodeResult {
/// number of nodes to connect.
static FIRST_PARTY_NETWORKS: Lazy<HashSet<BlockHash>> = Lazy::new(|| {
let genesis_hash_strs = &[
"0xce321292c998085ec1c5f5fab1add59fc163a28a5762fa49080215ce6bc040c7", // Casper v0.0.2
"0x7657c8c868863dea692178d462fe9018ac8f1e16f51be31eea8f29274d85525b", // Casper v0.0.2
];
genesis_hash_strs

2
telemetry-core/src/state/state.rs
View File

@ -278,7 +278,7 @@ mod test {
}
fn get_valid_genesis() -> BlockHash {
BlockHash::from_str("0xce321292c998085ec1c5f5fab1add59fc163a28a5762fa49080215ce6bc040c7")
BlockHash::from_str("0x7657c8c868863dea692178d462fe9018ac8f1e16f51be31eea8f29274d85525b")
.expect("Should be good genesis")
}