Search results
21 lut 2021 · From what I understand, a cryptocurrency mine needs to store a copy of the entire blockchain in order to be able verify transactions, which is why most wallet owners are not miners. The more centralized a decentralized consensus is, the more likely it is that its participants will 'defect' and screw over other participants, as in 51% attacks.
30 wrz 2020 · Since only you should be able to spend your bitcoins, each wallet is protected by a special cryptographic method that uses a unique pair of distinct but connected keys: a private and a public key. If a message is encrypted with a specific public key, only the owner of the paired private key can decrypt and read the message. The reverse is also ...
20 sty 2018 · Blockchain systems in their conventional form are based on. preimage and collision resistance of the employed hash functions for most functions, including transaction IDs, block IDs, and the Proof-of-Work (PoW) scheme in mining. hardness of DLP/ECDLP for security of transaction signatures and user addresses (so that private keys can not be found)
2. Someone else will probably explain but you can’t do it without compromising those properties, unless you extend “16 characters” to include a bunch of non-Latin characters. If you can compromise security just truncate it, but if you need to preserve security there’s no way to compress a hash efficiently, since it’s effectively ...
1 sie 2022 · But private keys are generally only seen by your own wallet, and so every wallet can decide on a different way to present or store a private key. E.g. I think the popular electrum wallet will only let you see your seed words, and won't even show you a hex representation of your private key.
16 gru 2021 · HTLC transaction and the snark proof of a proper secret hashed seems relevant. H is the Rescue hash function. Each w_i is a 4-tuple of field elements. These are private inputs, known only to the prover. p is the public output of the hash (which also consists of 4 field elements).
6 sie 2023 · Hash the action. Sign the hash with private key to create a signature. Post the {action, signature} to the server. Server side. Verify the action using the signature and public key. Perform the transfer between wallets (if valid) I'm pretty sure that this is correct.
18 cze 2017 · 53. From a cryptographic standpoint it is OK to expose a public key in the sense of revealing its value. The most basic assumption in cryptography involving public/private key pairs is that the value of a public key is public; hence its name. It is extremely important that an adversary can not alter a public key.
14 cze 2022 · The HKDF paper provides as good a summary as any:. A Key derivation function (KDF) is a basic and essential component of cryptographic systems: Its goal is to take a source of initial keying material, usually containing some good amount of randomness, but not distributed uniformly or for which an attacker has some partial knowledge, and derive from it one or more cryptographically strong ...
17 maj 2018 · 2. I am generating ECC private keys. however I noticed that since ECC private key is just a BigInteger. e.g. spec256k1 says private key is anywhere between [0~2^256-1]. my question is, if everyone is using Random(32) to generate a 32bytes private key, there is not likely but still possible situation that 2 people could generate the same private ...
