Replies: 3 comments
|
Thanks for initiating this discussion. Adding int-to-buff function would be valuable to make handling BTC transaction data easier. |
0 replies
@jbencin also recently suggested adding new conversion functions as well. See https://github.com/clarity-lang/reference/issues/81 for example (note that repo is where we've been collecting ideas for Clarity upgrades). These conversions can definitely be included in the next Clarity version. |
0 replies
|
Relevant issue at clarity-lang/reference: https://github.com/clarity-lang/reference/issues/71 |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
As discussed during last weeks ClarityWG, the ability to 'read' a Bitcoin transaction is quite limited in Clarity. Currently, developers use the Bitcoin-Clarity-v5.clar contract to:
An idea was floated (though it's certainly been mentioned many times before) to create a new set of Clarity functions that specifically help read Bitcoin state. This discussion is meant as a starting point for that research.
I'm tagging all participants who were there during the CWG meeting and/or have mentioned the idea beforehand: @friedger @obycode @djordon @dylanft @MarvinJanssen
All reactions