<p>It's not that you need a hash that is lower than the target - that's trivial as you pointed out. Rather you need to have a block whose block header must hash to a hash that is lower than the target. That is much harder to do because to find it either requires SHA256d to not have preimage resistance (i.e. given a hash, you can find the data used to produce that hash) or via brute force. Proof of Work works via the latter.</p>

CC BY-SA 3.0
2018-03-14T03:54:33.867Z
2018-03-14T03:54:33.867Z
Ava Chow
<p>So if in order to verify a block you just need a hash lower than the block in the hash, then why do you need to do a bunch of calculations rather than just using 0000000000000000000000000000000000000000000000000000000000000000000000000000001 every time?</p>

<transaction-verification>
If in order to verify a block your hash just has to be lower than the hash in the block, then why won't 00000000000000000000000000001 work every time?
user180969
# If in order to verify a block your hash just has to be lower than the hash in the block, then why won't 00000000000000000000000000001 work every time?

(Asked by: username_0 on 2018-03-14)

So if in order to verify a block you just need a hash lower than the block in the hash, then why do you need to do a bunch of calculations rather than just using 0000000000000000000000000000000000000000000000000000000000000000000000000000001 every time?

**Tags:** transaction-verification


---

## 1 answers

### Answer by username_1 on 2018-03-14. Score: 2 | Accepted answer

It's not that you need a hash that is lower than the target - that's trivial as you pointed out. Rather you need to have a block whose block header must hash to a hash that is lower than the target. That is much harder to do because to find it either requires SHA256d to not have preimage resistance (i.e. given a hash, you can find the data used to produce that hash) or via brute force. Proof of Work works via the latter.


---

