You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
For catamaranswaps, I want to verify that a bitcoin tx was mined using clarity-bitcoin-lib-v5. However, clarinet returns the same block header hash for all blocks (get-burn-chain-info? header-hash u100). It is not clear what the block looks like that is used to create the hash.
Describe the solution you'd like
Simple solution: provide docs describing the mocked(?) block used to generate the hash.
Advanced solution: add section to Clarinet.toml that allows to define a bitcoin block that is used to generate the hash.
Describe alternatives you've considered
Only test for failure of on-chain verificaion
Is your feature request related to a problem? Please describe.
For catamaranswaps, I want to verify that a bitcoin tx was mined using clarity-bitcoin-lib-v5. However, clarinet returns the same block header hash for all blocks
(get-burn-chain-info? header-hash u100)
. It is not clear what the block looks like that is used to create the hash.Describe the solution you'd like
Simple solution: provide docs describing the mocked(?) block used to generate the hash.
Advanced solution: add section to Clarinet.toml that allows to define a bitcoin block that is used to generate the hash.
Describe alternatives you've considered
Only test for failure of on-chain verificaion
Additional context
https://github.com/friedger/clarity-catamaranswaps/pull/6/files#diff-a89b2fb3bfe4fbbcc904e8a68ec9ad8724076cfe10d8c7ddfbae1fe66bcf4879R175
The text was updated successfully, but these errors were encountered: