Bitcoin Block Header Explained: 6 Fields & How It Works

A Bitcoin block contains much more than a list of transactions. At the beginning of every block is a compact 80-byte structure called the Bitcoin block header. It contains important information that connects the block to the previous block, commits to the transactions inside it, and provides the data that miners use for Proof of Work.

The block header contains six fields: version, previous block header hash, Merkle root, timestamp, nBits, and nonce. Each field has a specific role, and together they form the header that Bitcoin hashes to determine whether a block satisfies the network's Proof-of-Work requirement.

If you have already learned about the Bitcoin Merkle Root, this guide is the next step. Here, we will break down every field of the Bitcoin block header, explain how the fields work together, and show how the header connects transactions, previous blocks, and Bitcoin mining.

Bitcoin block header explained with its six fields

Key Takeaways

  • A Bitcoin block header is 80 bytes long.
  • It contains six fields: version, previous block hash, Merkle root, timestamp, nBits, and nonce.
  • The Merkle root represents the transactions committed to by the block header.
  • The previous block hash connects a block to the blockchain's existing chain.
  • Bitcoin hashes the block header as part of its Proof-of-Work process.
  • Miners can change fields such as the nonce while searching for a header hash that satisfies the required target.

What Is a Bitcoin Block Header?

A Bitcoin block header is the compact header section of a Bitcoin block that contains the information needed to identify the block's position in the blockchain and evaluate its Proof-of-Work. The header has a fixed size of 80 bytes.

The header contains six fields: version, previous block header hash, Merkle root, time, nBits, and nonce. These fields do not contain the complete transactions of the block. Instead, the header contains a compact set of values that commits the block to its transaction set and links it to the previous block.

One especially important field is the Merkle root. Bitcoin calculates this value from the transaction IDs included in the block and places the resulting 32-byte hash in the block header. You can see the complete process in our guide to how a Bitcoin Merkle root works.

When Bitcoin evaluates Proof of Work, the serialized block header is hashed using double SHA-256. The resulting hash is compared with the target represented by the header's nBits field. A valid block must satisfy the network's consensus requirements, including the Proof-of-Work target.

Simple flow:

Transactions → Merkle Root → Block Header → Double SHA-256 → Block Hash → Proof-of-Work Check

So, the block header can be thought of as a compact summary and cryptographic link for an entire Bitcoin block. The full block contains the transactions and other block data, while the header provides the core information used to link the block and evaluate its Proof of Work.

Why Does Bitcoin Need a Block Header?

A Bitcoin block can contain many transactions, so the network needs a compact way to represent important information about that block without placing the complete transaction data into the part that miners repeatedly hash. The block header provides this compact structure.

One important purpose of the header is to link the current block to the previous block. The header contains the hash of the previous block header. Because each block refers to its predecessor, changing information in an earlier block can affect the hashes of the blocks that follow it.

The header also contains the Merkle root, which commits the block to its transaction set. If a transaction changes in a way that changes its TXID, the corresponding Merkle root also changes, which changes the block header.

Another major purpose is Proof of Work. Bitcoin miners repeatedly hash candidate block headers and compare the resulting hash with the required target. The header therefore provides the data that miners use in the computational search for a valid block.

Why the header matters:

  • It links the block to the previous block.
  • It commits to the block's transactions through the Merkle root.
  • It contains the target representation used for Proof-of-Work evaluation.
  • It provides the data that miners repeatedly hash.

In simple terms, the block header acts as a compact cryptographic summary of important properties of a Bitcoin block. It does not replace the full block, but it gives the network and miners a standardized structure for linking blocks and checking Proof of Work.

The 6 Fields of a Bitcoin Block Header

A Bitcoin block header has a fixed size of 80 bytes. Those 80 bytes are divided into six fields, and each field has a specific role in identifying, linking, or validating the block.

Field Size Main Purpose
Version 4 bytes Indicates block-version information and can carry version-bit signaling.
Previous Block Header Hash 32 bytes Links the current block to the previous block.
Merkle Root 32 bytes Commits the header to the transactions represented by their TXIDs.
Time 4 bytes Contains the block's timestamp value.
nBits 4 bytes Stores the compact representation of the Proof-of-Work target.
Nonce 4 bytes Provides a value miners can vary while searching for a valid block header hash.
Bitcoin block header six fields and their byte sizes

The field sizes add up to exactly 80 bytes. Together, these fields form the serialized block header that is hashed during Bitcoin's Proof-of-Work process.

Easy way to remember: The first three fields mainly connect and commit the block, while the final three provide time and Proof-of-Work-related information.

In the next sections, we will examine each field individually, starting with the version field.

What Is the Version Field?

The version field is the first field in a Bitcoin block header and occupies 4 bytes. It provides version information associated with the block and can also be used for signaling certain protocol changes through version bits.

The version value helps Bitcoin software interpret the block according to the rules that apply to that version. Over Bitcoin's history, the meaning and use of this field have evolved. In particular, version bits allow miners to signal readiness for certain consensus-rule changes without requiring the entire 32-bit field to represent a simple sequential version number.

This means the version field should not be thought of simply as a number that increases by one for every new block. Some of its bits can have specific signaling purposes, depending on the Bitcoin consensus mechanism and the relevant BIP.

Simple idea:

Version field → 4 bytes → block-version information + possible version-bit signaling

The version field is therefore one part of the data that gets included when Bitcoin calculates the block header hash. If the header changes, its resulting hash changes as well.

For beginners, the most important point is that the version field is part of the 80-byte block header and provides information that Bitcoin uses when interpreting and validating blocks.

What Is the Previous Block Hash?

The previous block hash is the second field in a Bitcoin block header and occupies 32 bytes. It contains the hash of the previous block's header and creates a cryptographic link between consecutive blocks.

When a new Bitcoin block is created, its header includes the hash of the header of the block that came before it. This means the current block does not stand independently; it references its predecessor as part of the blockchain's structure.

Simple chain:

Block A → Block B → Block C → Block D

Block B's header contains the hash of Block A's header, while Block C's header contains the hash of Block B's header.

This linking mechanism is important because a change to an earlier block can change that block's header hash. The next block would then contain a reference that no longer matches, breaking the expected chain of header hashes from that point onward.

The previous block hash is therefore one of the key fields that gives the Bitcoin blockchain its linked-block structure. It works together with the Merkle root and the other header fields to form the complete block header that Bitcoin hashes for Proof of Work.

It is important to note that this field contains the previous block's header hash, not the hash of the previous block's entire serialized contents.

What Is the Merkle Root?

The Merkle root is the third field in a Bitcoin block header and occupies 32 bytes. It is a single hash that represents the transaction hashes included in the block's Merkle tree.

Bitcoin starts with the TXIDs of the transactions in the block. These transaction hashes are combined in pairs using double SHA-256 hashing. The resulting hashes are combined again, and this process continues until only one hash remains. That final hash is the Merkle root.

The Merkle root allows the block header to contain a compact cryptographic commitment to the block's transaction set instead of placing every transaction hash directly into the header.

Simple flow:

Transaction TXIDs → Merkle Tree → Merkle Root → Block Header

If a transaction changes in a way that changes its TXID, the corresponding path through the Merkle tree changes and the resulting Merkle root changes as well. Because the Merkle root is part of the block header, changing it also changes the block header hash.

This is why the Merkle root is an important connection between the transactions inside a block and the block header used for Proof of Work. For a detailed explanation of how this tree is constructed, see our guide to Bitcoin Merkle roots.

Important: The Merkle root is not the same as a transaction's TXID and is not the same as the final Bitcoin block hash. It is one 32-byte field inside the block header.

What Is the Timestamp?

The timestamp, also called the time field, is the fourth field in a Bitcoin block header and occupies 4 bytes. It records the time value claimed by the miner when creating the block.

The timestamp is not simply a permanent record of the exact moment when the block was mined. Bitcoin's consensus rules place limits on what timestamp values are acceptable. In particular, a block's timestamp must be greater than the median time of the previous 11 blocks, while also being subject to a maximum future-time constraint based on network-adjusted time.

Because the timestamp is part of the block header, changing it changes the serialized header and therefore changes the resulting block hash. A miner can therefore use an acceptable timestamp as one of the header values while searching for a valid Proof-of-Work solution.

Simple idea:

Timestamp → 4-byte time field → part of block header → included in the Proof-of-Work hash

The timestamp also helps establish the chronological ordering of blocks and is used in Bitcoin's difficulty-adjustment mechanism. However, it should not be treated as a perfectly precise real-world clock showing the exact second a miner found the block.

Important: Bitcoin's block timestamp is a consensus-constrained value, not an independently verified timestamp from a trusted central clock.

What Is nBits and the Difficulty Target?

The nBits field is the fifth field in a Bitcoin block header and occupies 4 bytes. It stores a compact representation of the Proof-of-Work target that the block's hash must satisfy.

The target is a numerical threshold used when Bitcoin checks Proof of Work. A candidate block is valid only when its resulting block hash meets the required target condition. In simplified terms, the hash must be numerically less than or equal to the target.

Bitcoin does not store the full target as a 32-byte number in the block header. Instead, the header contains the compact nBits representation. Bitcoin software can decode this compact value to obtain the target used for that block.

Simple relationship:

nBits → compact target representation → Proof-of-Work target → block hash is checked against the target

The target also determines how difficult it is to find a valid block. A lower target means fewer possible hash results satisfy the requirement, making the Proof-of-Work search more difficult. A higher target makes the requirement less restrictive.

Bitcoin adjusts the target periodically so that blocks continue to be produced at approximately the intended rate over time. The exact adjustment rules are part of Bitcoin's consensus rules.

Because nBits is part of the block header, it is also included in the data that is hashed during Proof of Work. Changing nBits changes the block header and therefore changes the resulting block hash.

Important: nBits is not the same thing as the target itself. It is a compact representation of the target stored in the block header.

What Is the Nonce?

The nonce is the sixth and final field in a Bitcoin block header. It occupies 4 bytes and provides miners with a value they can change while searching for a block header hash that satisfies the required Proof-of-Work target.

Mining involves repeatedly hashing candidate block headers. Because even a small change in the header produces a different hash, a miner can change the nonce and calculate another candidate hash. The miner continues this process until it finds a header hash that meets the target represented by the block's nBits field.

Basic mining loop:

Change nonce → Hash block header → Compare hash with target → Try again if it fails

The nonce is a 32-bit value, so it provides a finite range of possible values. Modern Bitcoin mining can require miners to search far beyond the available nonce values. When that happens, miners can modify other parts of a candidate block, such as the coinbase transaction, which changes the Merkle root and therefore creates a new set of possible block headers to search.

This is why the nonce should not be thought of as a special number that makes a block valid by itself. It is simply one of the values miners can vary while searching for a valid Proof-of-Work solution.

Important: Finding a valid nonce is not about discovering a predetermined secret number. Miners search through possible header values until the resulting hash satisfies the network's target.

How Bitcoin Block Header Hashing Works

Once the six fields are assembled, they form the complete 80-byte Bitcoin block header. Bitcoin then applies the SHA-256 hash function twice to the serialized header. The resulting 256-bit value is commonly called the block hash.

During Proof of Work, miners repeatedly create and hash candidate block headers. They can change the nonce and, when necessary, other parts of the candidate block that ultimately affect the header. Each change produces a different header hash.

Basic process:

6 Header Fields → 80-Byte Block Header → Double SHA-256 → Candidate Block Hash → Compare With Target

The resulting hash is then evaluated against the Proof-of-Work target represented by nBits. If the hash satisfies the required target, the candidate block has a valid Proof-of-Work result. If it does not, the miner changes a value and tries another candidate.

This process is different from calculating a Merkle root. The Merkle root is calculated from the transaction hashes and then placed into the block header. The block hash, on the other hand, is calculated from the complete block header after all six fields are assembled.

Value Calculated From
Merkle Root Transaction hashes arranged through the Merkle tree
Block Hash The complete serialized 80-byte block header
Bitcoin block header hashing and Proof-of-Work process

Therefore, the block header creates the connection between the block's transaction commitment and Bitcoin's Proof-of-Work mechanism: the Merkle root becomes part of the header, and the entire header is then hashed.

Block Header vs Full Bitcoin Block

A Bitcoin block header and a full Bitcoin block are related, but they are not the same thing. The header is a compact 80-byte structure, while the complete block contains the header along with the transactions included in that block.

Feature Block Header Full Bitcoin Block
Size Fixed at 80 bytes Larger and variable
Contains Six header fields Header plus block transactions
Transactions included directly? No Yes
Merkle root Stored as a 32-byte field Transactions are represented by the root in the header
Proof of Work Header is the data hashed for Proof of Work Contains the header and transaction data

For example, imagine a Bitcoin block containing hundreds or thousands of transactions. The block header does not contain those transactions themselves. Instead, the header contains the Merkle root, which provides a compact commitment to the transaction hashes.

The full block is therefore the larger data structure that carries the actual transactions, while the header provides the compact information needed to link the block to the chain and perform the Proof-of-Work check.

Think of it this way:

Full Block = Block Header + Transactions

The header summarizes important block information; it does not contain the complete transaction list.

This distinction becomes particularly useful when learning about lightweight Bitcoin verification methods, where a system may work with block headers and Merkle proofs without downloading every transaction in every block.

How the Block Header Connects to Mining

Bitcoin mining is closely connected to the block header because miners search for a block header whose hash satisfies the network's current Proof-of-Work target.

A miner first creates a candidate block containing transactions. From those transactions, Bitcoin derives the Merkle root. The miner then assembles the block header using the version, previous block header hash, Merkle root, timestamp, nBits, and nonce.

The miner hashes this header using double SHA-256. If the resulting hash does not satisfy the target, the miner changes a value and hashes another candidate header. The nonce is one obvious value to vary, but miners can also modify other parts of the candidate block when necessary.

Mining flow:

Candidate Transactions → Merkle Root → Block Header → Double SHA-256 → Compare With Target → Valid or Try Again

Because the block header contains the previous block hash, Merkle root, and Proof-of-Work-related fields, changing important parts of a candidate block changes the header and therefore changes the hash being tested.

The nonce has a 32-bit range, so modern mining hardware can exhaust the available nonce values very quickly. When that happens, miners can modify other suitable parts of the candidate block, such as the coinbase transaction. This changes the transaction set represented by the Merkle root and gives the miner a new collection of header values to search.

When a miner eventually finds a header hash that satisfies the required target and the complete block also satisfies Bitcoin's consensus rules, the block can be broadcast to the network for validation.

Important: Mining is not simply a search for a particular nonce. It is a search for a valid block header whose resulting hash satisfies the current Proof-of-Work target.

How the Block Header Connects to Mining

The Bitcoin block header is at the center of the Proof-of-Work mining process. Miners construct a candidate block, create its block header, and repeatedly hash that header while searching for a hash that satisfies the network's current target.

A miner first selects transactions for the candidate block and creates the block's coinbase transaction. The transactions determine the Merkle root, which then becomes part of the block header. The miner also has values such as the timestamp, version, nBits, and nonce available as part of the header.

Mining connection:

Transactions → Merkle Root → Block Header → Double SHA-256 → Hash → Target Check

The nonce provides a 4-byte value that miners can change while searching for different header hashes. If the available nonce range is exhausted, miners can create a different candidate header by changing other suitable data. For example, changing data in the coinbase transaction changes its TXID, which changes the Merkle root and therefore produces a different block header.

Miners can also work with other header fields within the limits allowed by Bitcoin's consensus rules. This gives mining hardware a large search space of possible block headers rather than relying only on the 32-bit nonce.

For every candidate header, Bitcoin's Proof-of-Work calculation applies double SHA-256 to the serialized 80-byte header. The resulting hash is compared numerically with the target represented by nBits.

If the resulting hash satisfies the target and the complete block follows Bitcoin's other consensus rules, the block can be accepted by nodes as a valid Proof-of-Work block. If the hash does not satisfy the target, the miner continues searching with another candidate.

Important: Mining is not simply a process of repeatedly changing the nonce forever. Modern mining can also change other parts of a candidate block, such as coinbase data, creating a new Merkle root and a new set of possible block headers.

This explains why the block header is so important to Bitcoin mining: it combines the block's identity, its connection to the previous block, its transaction commitment, and its Proof-of-Work parameters into the data that miners repeatedly hash.

What Happens If a Bitcoin Block Header Changes?

A Bitcoin block header is protected by cryptographic hashing. If even a small part of the header changes, the resulting block hash changes as well.

For example, changing the nonce, timestamp, nBits, version, previous block hash, or Merkle root changes the serialized header. When Bitcoin applies double SHA-256 to the modified header, it produces a different hash.

This relationship is especially important for the previous block hash. Suppose a block's header is modified after it has been accepted. Its block hash would change. The next block contains the original block's header hash in its previous-block-hash field, so that reference would no longer match the modified block.

Simple example:

Block A Header → Block A Hash → stored in Block B's Previous Block Hash field

If Block A Header changes → Block A Hash changes → Block B's reference no longer matches.

The same idea applies to the Merkle root. If a transaction changes in a way that changes its TXID, the affected Merkle-tree path and final Merkle root can change. Because the Merkle root is part of the block header, the block hash changes too.

This does not mean that every modification to transaction-related data necessarily changes the traditional TXID. For example, SegWit witness data is treated separately from the traditional TXID. Bitcoin therefore has specific rules for how transaction data and witness data are committed.

In simple terms, the block header creates a chain of cryptographic dependencies: the transaction set affects the Merkle root, the Merkle root is included in the header, the header determines the block hash, and the next block refers to that header hash.

Key point: Changing a block header changes its hash. Because later blocks reference previous block header hashes, modifying an earlier block can also invalidate the expected links to subsequent blocks.

A Simple Bitcoin Block Header Example

The easiest way to understand a Bitcoin block header is to look at its six fields together. The following is a fictional educational example. The values are intentionally illustrative and should not be treated as the header of a real Bitcoin block.

Header Field Illustrative Value What It Represents
Version Example value Block-version information and possible signaling bits
Previous Block Hash 32-byte hash Links this block to its predecessor
Merkle Root 32-byte hash Commits to the block's transaction hashes
Time Example timestamp Miner's block timestamp value
nBits Example compact value Compact representation of the Proof-of-Work target
Nonce Example 32-bit value One value miners can vary during the search

These six fields are serialized together to form the 80-byte block header. Bitcoin then applies double SHA-256 to this serialized header to obtain the candidate block hash.

Putting everything together:

Version + Previous Block Hash + Merkle Root + Time + nBits + Nonce

↓

80-Byte Block Header

↓

Double SHA-256

↓

Candidate Block Hash

This example also shows why the six fields should be understood together. The previous block hash connects the block to the chain, the Merkle root connects the header to its transactions, and the remaining fields provide information used when evaluating the block and its Proof of Work.

Note: The values above are placeholders for learning purposes. They are not copied from a real Bitcoin block and should not be interpreted as a real block header.

Block Header and the Blockchain Chain

The Bitcoin block header plays an important role in connecting individual blocks into a continuous blockchain. The key field responsible for this connection is the previous block header hash.

When a new block is created, its header contains the hash of the previous block's header. The next block then refers to the current block in the same way. This creates a chain of cryptographic references between consecutive blocks.

Simple blockchain link:

Block A Header → Block A Hash

↓

Block B Header → Previous Block Hash = Block A Header Hash

↓

Block C Header → Previous Block Hash = Block B Header Hash

This structure means that changing the header of an earlier block changes its hash. The following block would still contain the old hash in its previous-block-hash field, so the cryptographic link would no longer match.

The header also connects the blockchain to the transactions inside each block through the Merkle root. The previous block hash links one block to another, while the Merkle root links the header to the transaction set represented by the block.

Together, these relationships create an important chain of commitments: transactions → Merkle root → block header → block hash → next block's previous-block reference.

This is one reason the Bitcoin blockchain is not simply a chronological database of transactions. Each block contains cryptographic references that connect it to the block before it while also committing the header to the transactions represented by its Merkle root.

Key point: The previous block hash creates the link between consecutive block headers, while the Merkle root connects a block header to the transactions represented by that block.

Common Bitcoin Block Header Misconceptions

1. Is the block header the same as the full Bitcoin block?

No. The block header is only 80 bytes and contains six fields. A full Bitcoin block contains the header along with the transactions included in that block.

2. Does the block header contain all Bitcoin transactions?

No. The header does not contain the complete transaction data. Instead, it contains the Merkle root, which provides a compact cryptographic commitment to the transaction hashes represented by the block.

3. Is the Merkle root the same as the block hash?

No. The Merkle root is calculated from the transaction hashes and stored as one field in the header. The block hash is calculated by applying double SHA-256 to the complete serialized block header.

4. Is the nonce the only value miners can change?

No. The nonce is a 4-byte field that miners can vary, but miners can also modify other suitable parts of a candidate block. For example, changing coinbase transaction data can change the Merkle root and therefore create a different block header to search.

5. Does a higher nonce mean more mining power?

No. The nonce is simply a value included in the block header. A higher nonce does not automatically mean a block required more work or that a miner had more computing power.

6. Is the timestamp the exact moment a block was mined?

Not necessarily. The block timestamp is a value supplied by the miner and must satisfy Bitcoin's consensus rules. It should not be treated as a perfectly precise record of the exact second when the block was found.

7. Is nBits the same as the difficulty target?

Not exactly. nBits is a compact representation of the Proof-of-Work target stored in the block header. Bitcoin software interprets this value to obtain the target used when checking the block hash.

8. Does changing one field always make a block invalid?

Changing a field changes the block header hash, but whether the resulting block is valid depends on the consensus rules and the new values. During mining, miners intentionally change certain header-related values while searching for a valid Proof-of-Work result.

Remember: The six header fields work together. The previous block hash links the chain, the Merkle root commits to transactions, and the remaining fields contribute to the information used when evaluating the block and its Proof of Work.

FAQ: Bitcoin Block Header

What is a Bitcoin block header?

A Bitcoin block header is an 80-byte structure containing six fields: version, previous block header hash, Merkle root, time, nBits, and nonce. The serialized header is hashed as part of Bitcoin's Proof-of-Work process.

How many fields are in a Bitcoin block header?

A Bitcoin block header contains six fields: version, previous block header hash, Merkle root, timestamp, nBits, and nonce.

What is the size of a Bitcoin block header?

The Bitcoin block header has a fixed size of 80 bytes.

What is the Merkle root in a block header?

The Merkle root is a 32-byte hash derived from the transaction hashes represented by the block's Merkle tree. It is stored as one of the six fields in the block header.

What is the previous block hash used for?

The previous block hash contains the hash of the previous block's header. It creates a cryptographic link between consecutive blocks in the blockchain.

What is nBits in a Bitcoin block header?

nBits is a 4-byte compact representation of the Proof-of-Work target. Bitcoin uses the decoded target when checking whether a block's hash satisfies the required Proof-of-Work condition.

What is the nonce used for in Bitcoin mining?

The nonce is a 4-byte field that miners can vary while searching for a block header hash that satisfies the current Proof-of-Work target.

Is the Bitcoin block header the same as the block hash?

No. The block header is the 80-byte data structure containing the six fields. The block hash is the result of applying double SHA-256 to the serialized block header.

Key Takeaways

  • A Bitcoin block header is 80 bytes and contains six fields.
  • The six fields are version, previous block header hash, Merkle root, time, nBits, and nonce.
  • The previous block hash creates the cryptographic link between consecutive blocks.
  • The Merkle root commits the header to the transaction hashes represented by the block.
  • nBits stores a compact representation of the Proof-of-Work target.
  • The nonce is one value miners can vary while searching for a valid header hash.
  • Bitcoin applies double SHA-256 to the serialized block header as part of its Proof-of-Work process.
  • The block header is not the same as the full Bitcoin block; the full block also contains its transaction data.
  • Changing the block header changes its resulting block hash, which is important for Bitcoin's chain of cryptographic links.

In one line: A Bitcoin block header is an 80-byte structure that links a block to its predecessor, commits it to its transactions, and provides the data used to evaluate its Proof of Work.

Final Takeaway

The Bitcoin block header is a small but essential part of every Bitcoin block. Its fixed 80-byte structure contains six fields that work together to connect blocks, represent the block's transaction commitment, and provide the data used for Proof of Work.

The easiest way to understand the whole concept is to remember the relationship between the fields: the previous block hash connects the current block to the blockchain, the Merkle root connects the header to the transactions represented by the block, and the version, time, nBits, and nonce provide additional header information used within Bitcoin's consensus and mining process.

Once these six fields are serialized, Bitcoin applies double SHA-256 to the 80-byte header to produce the block hash. Miners search through possible header values until they find a hash that satisfies the required Proof-of-Work target.

Understanding the block header therefore makes several Bitcoin concepts easier to connect: transactions, TXIDs, Merkle roots, block hashes, Proof of Work, mining, and the blockchain itself.

Disclaimer: This article is provided for educational and informational purposes only. It is not financial, investment, trading, or legal advice. Cryptocurrency technology involves risks and technical complexities, so readers should conduct their own research before making any financial decisions.

Post a Comment

0 Comments