Introduce a consensus hash

[lgalabru]

Having ord publishing a consensus / root hash that would include:

• consensus hash of previous block
• for each blessed inscription reveal: inscription number + inscription inscription id + content hash
• for each blessed inscription transfer: inscription id + new outpoint + new offset

Introducing this kind of consensus hash would be very helpful for many actors in this ecosystem.
It would also help everyone understand that if it's not part of consensus (say, cursed inscriptions, or even better, inscription number), it is subject to change.

[raphjaph]

I can see this being helpful, we could publish the current block's hash on the /status page. We would just have to agree on the serialization and order of hashing.

[lgalabru]

@raphjaph we will be tackling this in ordhook and probably be using the following spec, feel free to leave some feedbacks :)

[casey]

The consensus hash should probably include bitcoin block hashes.