Deploying Clarity 3 contracts using platform.hiro.so fails

[314159265359879]

I understand this as the issue

• When a user deploys a contract with clarity 3 keywords in it
• they expect it to get deployed as a clarity 3 contract
• however the contract is deployed as a clarity 2 contract and then fails to deploy

From:
https://hiro-pbc.canny.io/hiro-platform/p/nakamoto-clarity-3

What is needed to support this on our end.

Does anyone have an example of a contract with clarity 3 keywords?

[linear]

LEA-1762 Deploying Clarity 3 contracts using platform.hiro.so fails

[markmhendrickson]

@leahjlou might you have some technical input here re: what's needed on our end given your involvement in this thread?

@314159265359879 this seems more like a bug than an enhancement per se (since we provide the expectation that Stacks contracts of all types can get deployed)?

[kyranjamie]

We need to upgrade to the latest version and accept a clarity version through our API. I can try taking this on as part of API work

[leahjlou]

I was thinking this issue was being tracked here but thinking through it now, I see that is slightly different task.

Please let me know if there's anything I can do to help out here.

[camerow]

@kyranjamie added this to the next cycle - unless you feel it deserves higher priority (or you @markmhendrickson)

[r0zar]

Looking forward to seeing a PR merged for this!

[314159265359879]

@camerow, can you link the related PR to this once it is public?

[314159265359879]

With the work needed for this, can this issue be addressed too?
#5931

Another developer was asking for it, it looks related to me. I think it makes sense to deploy contracts with the latest version of Clarity as a default?

The developer explained they need block-height to return the Stacks block height and with Clarity 2 that will return the tenure height instead.

[camerow]

@314159265359879 I think that makes sense, @kyranjamie is going to be working on this I believe in the coming days.