May 11, 2026

Capitalizations Index – B ∞/21M

What is Hashing & Digital Signature in The Blockchain?

What is hashing & digital signature in the blockchain?

What is Hashing & Digital Signature in The Blockchain?

What is hashing & digital signature in the blockchain?What is Hashing & Digital Signature in The Blockchain? https://blockgeeks.com/

Today, we’re going to be talking about the word blockchain and breaking it down to understand what does it mean when someone says, “Blockchain.”

What is hashing? Hashing refers to the concept of taking an arbitrary amount of input data, applying some algorithm to it, and generating a fixed-size output data called the hash. The input can be any number of bits that could represent a single character, an MP3 file, an entire novel, a spreadsheet of your banking history, or even the entire Internet. The point is that the input can be infinitely big. The hashing algorithm [00:01:00] can be chosen depending on your needs and there are many publicly available hashing algorithms. The point is that the algorithm takes the infinite input of bits, applies some calculations to them, and outputs a finite number of bits. For example, 256 bits.

What can this hash be used for? A common usage for hashes today is to fingerprint files, also known as check zones. This means that a hash is used to verify that a file has not been [00:01:30] tampered with or modified in any way not intended by the author. If WikiLeaks, for example, publishes a set of files along with their MD5 hashes, whoever downloads those files can verify that they are actually from WikiLeaks by calculating the MD5 hash of the downloaded files, and if the hash doesn’t match what was published by WikiLeaks, then you know that the file has been modified in some way.

How does the blockchain make use of hashes? [00:02:00] Hashes are used in blockchains to represent the current state of the world. The input is the entire state of the blockchain, meaning all the transactions that have taken place so far and the resulting output hash represents the current state of the blockchain. The hash is used to agree between all parties that the world state is one in the same, but how are these hashes actually calculated?

The first hash is calculated for the first block [00:02:30] or the Genesis block using the transactions inside that block. The sequence of initial transactions is used to calculate a block hash for the Genesis block. For every new block that is generated afterwords, the previous block’s hash is also used, as well as its own transactions, as input to determine its block hash. This is how a chain of blocks is formed, each new block hash pointing to the block hash that came before it.

This system of hashing guarantees that no transaction in the history can be tampered with because if any single part of the transaction changes, so does the hash of the block to which it belongs, and any following blocks’ hashes as a result. It would be fairly easy to catch any tampering as a result because you can just compare the hashes. This is cool because everyone on the blockchain only needs to agree on 256 bits to represent the potentially infinite state of the blockchain. The Ethereum blockchain is currently tens of gigabytes, but the current state of the blockchain, as of this recording, is this hexadecimal hash representing 256 bits.

What about digital signatures? Digital signatures, like real signatures, are a way to prove that somebody is who they say they are, except that we use cryptography or math, which is more secure than handwritten signatures that can be [00:04:00] easily forged. A digital signature is a way to prove that a message originates from a specific person and no one else, like a hacker.

Digital signatures are used today all over the Internet. Whenever you visit a website over ACTPS, you are using SSL, which uses digital signatures to establish trust between you and the server. This means that when you visit Facebook.com, your browser can check the digital signature that came with the web page to verify that it indeed originated from Facebook and not some hacker.

In asymmetric encryption systems, users generate something called a key pair, which is a public key and a private key using some known algorithm. The public key and private key are associated with each other through some mathematical relationship. The public key is meant to be distributed publicly to serve as an address to receive messages from other users, like an IP address or home address. The private key is meant to be kept secret and is used to digitally sign messages sent to other users. The signature is included with the message so that the recipient can verify using the sender’s public key. This way, the recipient can be sure that only the sender could have sent this message. Generating a key pair is analogous to creating an account on the blockchain, but without having to actually register anywhere. Pretty cool. Also, every transaction that is executed on the blockchain is digitally signed by the sender using their private key. This signature ensures that only the owner of the account can move money out of the account.

Previous Article

Mainstream Media Coverage of Bitcoin Goes up as Price Falls: Survey

Next Article

Consultant Service Intern

You might be interested in …

_mg_7089

_MG_7089

_MG_7089The Peace Plus One – World Sustainability Project www.WorldSustainability.Org is interested in the opportunities afforded to young people in the new economy of Caring Currency. The currency of the 99%. The concept of Caring Currency […]

BIP91: The SegWit Activation "Kludge" That Should Keep Bitcoin Whole

BIP91: The SegWit Activation "Kludge" That Should Keep Bitcoin Whole

bitcoin’s long-lasting scaling debate appeared to be heading toward a climax lately, with two proposals gaining significant traction. At one end of the fence there is Bitcoin Improvement Proposal 148 (BIP148), a user activated soft fork (UASF) originally proposed by the pseudonymous developer “shaolinfry.” On the other, there’s SegWit2x, an agreement forged between a significant number of bitcoin companies and miners.

The good news is that both of these proposals have a short-term solution in common: both plan to activate Segregated Witness (SegWit) this summer. The bad news is that the activation method of the two has differed, which could lead to a coin-split.

As of today, it seems this schism will be avoided — at least initially. The SegWit2x development team plans to implement BIP91, a proposal by Bitmain Warranty engineer James Hilliard that cleverly makes the two conflicting activation methods compatible.

Here’s how.

BIP141

The current implementation of Segregated Witness is defined by BIP141. This version is included in the latest Bitcoin Core releases, and is widely deployed on the bitcoin network. BIP141 is activated through the activation method defined by BIP9. This means that 95 percent of all blocks within a two-week period need to include a piece of data: “bit 1.” This indicates that a miner is ready for the upgrade. As such, SegWit would be activated if the vast majority of miners are ready for it.

Or that was the intention. So far, only some 30 percent of hash power is signaling support for the upgrade. There is a lot of speculation as to why this is the case, but it almost certainly has nothing to do with (a lack of) readiness.

That’s why other activation methods are increasingly being considered.

BIP148

BIP148 is a user activated soft fork (UASF), specifically designed to trigger BIP141.

On August 1st, anyone running bitcoin software that implemented BIP148 will start rejecting all blocks that do not include bit 1, the SegWit signalling data.

This means that if a mere majority of miners (by hash power) runs this software, they will reject all blocks from the minority of miners that does not. As a result, this majority of miners will always have the longest valid chain according to all bitcoin nodes on the network. Consequently, all deployed BIP141 nodes will see a chain that includes over 95 percent of bit 1 blocks, meaning SegWit would be activated on the network.

However, if BIP148 is not supported by a majority of miners (by hash power), bitcoin’s blockchain could split in two. In that case, there would effectively be two types of bitcoin, where one activated BIP148 and the other did not. This may resolve over time — or it may not.

SegWit2x

SegWit2x (also referred to as “SegWit2MB” or “the Silbert Accord”), is the scaling agreement reached by a numer of bitcoin companies and over 80 percent of miners (by hash power), drafted just before the Consensus 2017 conference.

For some time, the details surrounding SegWit2x were not very specific. As the name suggests, all that was really known was that SegWit was included in the agreement, and that it included a hard fork to double bitcoin’s “base block size” to two megabytes.

And, of course, SegWit was meant to be implemented using a different activation method. Like the original BIP141 proposal, SegWit2x was to be activated by miners through hash power. But where BIP141 requires 95 percent hash power support, SegWit2x would only require 80 percent. Moreover, SegWit2x readiness would be signaled using another piece of activation data: “bit 4” instead of “bit 1.”

This makes SegWit2x largely incompatible with BIP141, and especially with BIP148: Different nodes would be looking at different activation bits, meaning they could activate SegWit under different circumstances and at different times; and that would mess up SegWit-specific block relay policy between nodes, potentially fracturing the network.

BIP91

Now, it seems BIP91 has provided the solution.

BIP91 is a proposal by Bitmain Warranty (not to be confused with Bitmain) engineer James Hilliard which was specifically designed to prevent a coin-split by making SegWit2x and BIP148 compatible.

The proposal resembles BIP148 to some extent. Upon activation of BIP91, all BIP91 nodes will reject any blocks that do not signal support for SegWit through bit 1. As such, if a majority of miners (by hash power) run BIP91, the longest valid bitcoin chain will consist of SegWit-signaling blocks only, and all regular BIP141 SegWit nodes will activate the protocol upgrade.

Where BIP91 differs from BIP148 is that it doesn’t have a set activation date, but is instead triggered by hash power. BIP91 nodes will reject any non-SegWit signalling blocks if, and only if, 80 percent of blocks first indicate within two days that’s what they’ll do.

This indication is done with bit 4. As such, the Silbert Accord can technically be upheld — 80 percent hash power activation with bit 4 — while at the same time activating the existing SegWit proposal. And if this is done before August 1st, it’s also compatible with BIP148, since BIP148 nodes would reject non-bit 1 blocks just the same.

This proposal gives miners a little over six weeks to avoid a coin-split, under their own agreed-upon terms. With a SegWit2x launch date planned for July 21st, that should not be a problem… assuming that the miners actually follow through.

The post BIP91: The SegWit Activation "Kludge" That Should Keep Bitcoin Whole appeared first on Bitcoin Magazine.