Bitcoin RIPEMD160 purpose

Bitcoin RIPEMD160 purpose

Bitcoin uses RIPEMD160 on top of SHA256. Is its sole purpose to make public key address shorter or does it strengthen security in any way?

https://ift.tt/2vO6nzD

Comments

  1. Mystery boxFebruary 13, 2022 at 3:06 AM

    This blog very is impressive; I am inspired how continuously you describe this topic. After reading your post, thanks for taking the time to discuss this,

    If you ssearching for a legit financial service .Check it out. Link below.
    legit paypal transfer dark web
    dark web financial services .
    Unclaimed Mystery Box
    I feel happy about it and I love learning more about this topic...

    ReplyDelete

Post a Comment

Popular posts from this blog

New z-enemy 1.26 Nvidia GPU Miner With Improved Performance

Image
New z-enemy 1.26 Nvidia GPU Miner With Improved Performance The latest z-enemy 1.26 Nvidia GPU miner comes with additional performance boost in a number of the supported crypto algorithms as well as improved stability. We should note that the latest version also marks the removal of support for the Renesis algorithm, apparently due to the project introducing this algorithm getting abandoned. The new version adds up to +5-7% for X16r and X16s, +7% for Bitcore, few percent for other algorithms such as X17, C11, Aergo … on GTX 10×0 cards. The Hex algorithm gets +10% for GTX 10×0 cards and +2% for RTX 20×0 GPUs as a hashrate boost. The latest z-enemy version 1.26 is available for CUDA 9.1, 9.2 and 10.0 for 64-bit Windows versions as well as CUDA 9.0, CUDA 9.1, CUDA 9.2 and CUDA 10 binaries for Linux (HiveOS, PiMP OS, EthOS & Ubuntu). Make sure that you have the respective recent video driver version installed for the CUDA version you want to use – 388+ for 9.1, 397+ for 9.2 and 411+ ...
Read more

New coin daemon crashes ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=8)

New coin daemon crashes ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=0, nPos=8) Hi so I generated the genesis block using std::unique_ptr<CChainParams> CreateChainParams(const std::string& chain) { if (chain == CBaseChainParams::MAIN) return std::unique_ptr<CChainParams>(new CMainParams()); else if (chain == CBaseChainParams::TESTNET) return std::unique_ptr<CChainParams>(new CTestNetParams()); else if (chain == CBaseChainParams::REGTEST) return std::unique_ptr<CChainParams>(new CRegTestParams()); throw std::runtime_error(strprintf("%s: Unknown chain %s.", __func__, chain)); } void SelectParams(const std::string& network) { SelectBaseParams(network); globalChainParams = CreateChainParams(network); } void UpdateVersionBitsParameters(Consensus::DeploymentPos d, int64_t nStartTime, int64_t nTimeout) { globalChainParams->UpdateVersionBitsParameters(d, nStartTime, nTimeout); } void MineGenesisBlock(CBl...
Read more

How do I calculate the witness commitment hash for a given block?

How do I calculate the witness commitment hash for a given block? From my understanding, every SegWit enabled block has an added output script which is used as a place to store the "Witness commitment" specified in BIP 141 . One issue I've stumbled upon was calculating the commitment hash value only given the raw block/transaction data. For example, I've chosen Block #542213 as it only has 4 total transactions (including the coinbase generation) Coinbase witness commitment script: OP_RETURN OP_PUSHDATA(36) [aa21a9ed4a657fcaa2149342376247e2e283a55a6b92dcc35d4d89e4ac7b74488cb63be2] BIP141 states that the pushed data can be broken down to the following: 0xaa21a9ed - Commitment header (seemingly random) 0x4a657fcaa2149342376247e2e283a55a6b92dcc35d4d89e4ac7b74488cb63be2 - SHA256(SHA256(witness root hash|witness reserved value)) The documentation mentions that the witness root hash can be derived similarly to the merkle root in a block header, where each wtxid act...
Read more