chore: rework finalized/inBlock with BlockHashRune

[harrysolovay]

Given that we have inBlockHash/finalizedHash and inBlockEvents/finalizedEvents, there's a chance that finalized alone for describing block would be confusing.

[tjjfvi]

I think instead we should rename them back to .finalized() and use .finalized().hash instead of .finalizedHash()

[harrysolovay]

Is there a path that would better-position devs to avoid an accidental extra network call (using the hash to retrieve the block)? Thoughts on finalized producing a new BlockHashRune, which would have a block method on it? (same for inBlock).

[tjjfvi]

.finalized().hash wouldn't produce an extra network call because runes are lazy

[harrysolovay]

Yes, but let's consider cases where devs just want to await finalization.

await chain
  .extrinsic(Balances.transfer({
    value: 12345n,
    dest: billy.address,
  }))
  .signed(signature({ sender: alexa }))
  .sent()
  .finalized()
  .run()

It's easy to forget the .hash.

[tjjfvi]

Fair enough – then yeah, a BlockHashRune makes sense