-
Notifications
You must be signed in to change notification settings - Fork 39
Closed
Labels
Description
What happened
Is it safe to use same private key in two or more algorithms?
I'm not sure, but I know to solve a system of equations that has two equations is definitely easier than solving one equation.
-
BLST
Lines 532 to 534 in fd220ad
fn get_my_hex_privkey(&self) -> Vec<u8> { hex_decode(&self.config.privkey.as_string_trim0x()).unwrap() }
Lines 538 to 540 in fd220ad
let hex_privkey = self.get_my_hex_privkey(); let bls_priv_key = BlsPrivateKey::try_from(hex_privkey.as_ref()) .map_err(MainError::Crypto) Ref: BLST
-
Secp256k1 (Two different Version)
axon/core/network/src/config.rs
Line 117 in fd220ad
.secio_keypair(&config.privkey.as_string_trim0x())
Lines 608 to 612 in fd220ad
let hex_privkey = self.get_my_hex_privkey(); let node_info = NodeInfo { chain_id: self.genesis.block.header.chain_id, self_address: self.get_my_address(hex_privkey.clone()), self_pub_key: self.get_my_pubkey(hex_privkey).to_bytes(),
Lines 518 to 521 in fd220ad
fn get_my_pubkey(&self, hex_privkey: Vec<u8>) -> Secp256k1PublicKey { let my_privkey = Secp256k1PrivateKey::try_from(hex_privkey.as_ref()) .map_err(MainError::Crypto) .unwrap();
Lines 5909 to 5910 in fd220ad
name = "secp256k1" version = "0.22.2"
Lines 5918 to 5919 in fd220ad
name = "secp256k1" version = "0.24.3" Ref:
- tentacle-secio/secp256k1 (Same as CKB used)
- ophelia-secp256k1/secp256k1
Reactions are currently unavailable