# Consensus

**URL:** https://discourse.ironfish.network/c/protocol-proposals/consensus/11.md

[Latest](https://discourse.ironfish.network/latest.md) · [Categories](https://discourse.ironfish.network/categories.md) · [Tags](https://discourse.ironfish.network/tags.md)

---

## [About the Consensus category](https://discourse.ironfish.network/t/about-the-consensus-category/17)

<div class="topic-metadata">

**Author:** [@elena](https://discourse.ironfish.network/u/elena)\
**Replies:** 0

</div>

For discussions to anything related to consensus parameters of Iron Fish. Examples of these are: discussing changing block time target, difficulty calculations, confirmation time, and so on.

---

## [Swap Nonce and Graffiti Header Positions](https://discourse.ironfish.network/t/swap-nonce-and-graffiti-header-positions/93)

<div class="topic-metadata">

**Author:** [@danielfish](https://discourse.ironfish.network/u/danielfish)\
**Replies:** 1\
**Last updated:** [February 15, 2024, 12:58am UTC](https://discourse.ironfish.network/t/swap-nonce-and-graffiti-header-positions/93 "2024-02-15T00:58:29Z")

</div>

Background Currently most mining software uses the graffiti field as a nonce when mining Iron Fish blocks. The block header is serialized as follows before being passed to the blake3 hashing algorithm. writeBigU64BE(hea…

---

## [Longer Difficulty Adjustment Period](https://discourse.ironfish.network/t/longer-difficulty-adjustment-period/90)

<div class="topic-metadata">

**Author:** [@danielfish](https://discourse.ironfish.network/u/danielfish)\
**Replies:** 1\
**Last updated:** [February 9, 2024, 9:28pm UTC](https://discourse.ironfish.network/t/longer-difficulty-adjustment-period/90 "2024-02-09T21:28:06Z")

</div>

Background Currently, when mining, a block’s difficulty can only be adjusted for 99 buckets, or 16.5 minutes. This results in a maximum adjustment per block of around 5% (4.834%). (You can play with the numbers in this f…

---

## [Re-org Limits and Checkpoints](https://discourse.ironfish.network/t/re-org-limits-and-checkpoints/91)

<div class="topic-metadata">

**Author:** [@danielfish](https://discourse.ironfish.network/u/danielfish)\
**Replies:** 3\
**Last updated:** [February 7, 2024, 12:00am UTC](https://discourse.ironfish.network/t/re-org-limits-and-checkpoints/91 "2024-02-07T00:00:58Z")

</div>

Background A re-org limit in this proposal means an agreed upon number of blocks after which nodes will not switch over to a new chain. For example, if the re-org limit is 10 blocks and a node reaches block 100, that nod…

---

## [\[Proposal\] Restrict block from having timestamp earlier than previous block](https://discourse.ironfish.network/t/proposal-restrict-block-from-having-timestamp-earlier-than-previous-block/50)

<div class="topic-metadata">

**Author:** [@yajun](https://discourse.ironfish.network/u/yajun)\
**Replies:** 7\
**Last updated:** [July 20, 2023, 12:45am UTC](https://discourse.ironfish.network/t/proposal-restrict-block-from-having-timestamp-earlier-than-previous-block/50 "2023-07-20T00:45:51Z")

</div>

TLDR It’s a known vulnerability that Iron Fish allow blocks with timestamps that are earlier than timestamps from previous block. Miners are incentivized to exploit it by manipulating the block timestamps to consistently…