B.BlockAxis⌕ Search
Menu

Public key

A value that permits signature verification without revealing the private key.

A concrete example

A verifier checks a signature over a message using the matching public key.

In context

Hashing is not encryption. Encryption conceals a message until it is decrypted; a hash helps check integrity. Matching a fingerprint establishes consistency with particular data, not that the underlying statement is true. Hashing a false invoice does not make it genuine.

The related mechanism, visually

SEE THE CONNECTIONS
Know what a hash or signature can establishFour connected ideas
  1. 01Message + context
  2. 02Private-key signature
  3. 03Public-key verification
  4. 04Authorization, not truth

Read these as connected concepts, not necessarily consecutive steps.

Read the explanation

A private key is used to produce signatures; the corresponding public key lets others verify them. Verification binds a signature to a particular message. The message must also specify its intended context, such as the network and contract: otherwise an authorization may be accepted somewhere it was not intended. Replay protection is an application rule, often involving a nonce; readable formatting alone does not provide it. A wallet can request a transfer, a contract call or a structured message. Read that request, not just the description on the website.

Explore the full explanation

Blockchain

Hashes, keys and signatures

A cryptographic hash maps data to a fixed-length fingerprint.

Beginner6 min reading + workshop ↗

← Back to the glossary

Sources and references

References for the mechanisms described. Numerical examples are hypothetical unless stated otherwise. Check the applicable version, network and jurisdiction.

References reviewed on 21 September 2026. All sources →