Add missing Clarity3 functions #1692
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
There are some other changes/additions needed for Clarity 3 / epoch 3:
|
|
i also think there is a way to automate this (i.e. in the open docs pr workflow), it'll just take a little massaging of the output. |
|
obycode
reviewed
Jan 22, 2025
Co-authored-by: Brice <[email protected]>
|
unrelated to this PR - but i think we can automate this process easier than i originally thought. i have some ideas i'll take a a look at it soon. |
|
obycode
reviewed
Jan 22, 2025
reference/functions.md
Outdated
| @@ -1311,7 +1313,7 @@ Introduced in: **Clarity 3** | |||
| The `get-stacks-block-info?` function fetches data for a block of the given *Stacks* block height. The value and type returned are determined by the specified `StacksBlockInfoPropertyName`. If the provided `stacks-block-height` does not correspond to an existing block prior to the current block, the function returns `none`. The currently available property names are as follows: | |||
|
|
|||
| - `id-header-hash`: This property returns a `(buff 32)` value containing the _index block hash_ of a Stacks block. This hash is globally unique, and is derived from the block hash and the history of accepted PoX operations. This is also the block hash value you would pass into `(at-block)`. | |||
| - `header-hash`: This property returns a `(buff 32)` value containing the header hash of a Stacks block, given a Stacks chain height. **WARNING** this hash is not guaranteed to be globally unique, since the same Stacks block can be mined in different PoX forks. If you need global uniqueness, you should use `id-header-hash`. | |||
| - `header-hash`: This property returns a `(buff 32)` value containing the header hash of a Stacks block, given a Stacks chain height. | |||
There was a problem hiding this comment.
I think this one is okay to leave. There is one that should be removed in stacks-block-height.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ref: https://github.com/stacks-network/stacks-core/actions/runs/12835755981
this adds the missing clarity3 functions from the stacks-core broken workflow.