Brice

Let's get any failing tests working again in this branch.

~~Since this add-on is for minor changes to Clarity, let's also add removal of `index-of` and `element-at`, forcing the use of the variants ending in `?`. What do you think?~~...

> very good question - @obycode any insight here? Copying the responses from Slack here: friedger: The block hash is the stacks block hash. The consensus hash from tenure? Aaron:...

At today's WG sync, we discussed the value in minimizing changes to the function as `get-block-info?` instead of removing it and adding `get-stacks-block-info?`, with the goal of minimizing unnecessary changes...

There was some more discussion about this and there seems to be a preference to not add new functions, but instead just add a new property to `get-block-info?` for the...

Just had another chat about this, and I think we came full circle back around to your original proposal 😅.

Do you think calling `(get-stacks-block-info? time u1234)` where `1234` is a pre-epoch 3.0 block should return the burnchain time or should it return `none`? I think my preference is to...

I think we may also need to add a new function `(get-tenure-for-block? block-height)` which returns an `(optional uint)` which is the tenure height of the specified block if `block-height

Based on discussion from today's call, I will change the implementation of `get-tenure-info?` to take in a burn block height as its parameter. `tenure-height` can be a new additional property.

Another change here... `get-tenure-info?` will take a Stacks block height as its parameter. Implemented in stacks-network/stacks-core#4846