SIP-033: Clarity 4: high-demand new builtins #218
Conversation
Without a `with-stacking`, the body may not stack the STX of the `asset-owner`.
Allowances are now passed in as an argument to the expression, similar to the way `let` works.
Using `u0` for an error code might be confusing, so start at `u1`.
|
We all agreed offline that SIP would be assigned to number: |
…st SIP_TEMPLATE We are creating a SIP_TEMPLATE.md for all SIP authors to follow so sections ordering and stylistically can be consistent. I added Governance CAB to the Consideration to get their CAB sign off as well.
|
Thank you for adding secp256r1 support to SIP-033. This allows Stacks developers to build applications with native passkey integration, unlocking use cases like 2FA for VCs in multisig setups, embedded mints on X with Touch ID purchases, and instant wallet creation with Face ID in seconds. All secured by the user's device secure enclave without third parties. |
Update sip-clarity4.md - stylistic and ordering editing to match late…
|
@obycode now that sip number is assigned, can you rename the folder to |
Done ✅ |
obycode
force-pushed
the
feat/clarity-4
branch
from
530be02 to
ab1c9e0
Compare
obycode
force-pushed
the
feat/clarity-4
branch
from
ab1c9e0 to
d7b0517
Compare
whoabuddy
changed the title
|
I'm looking for examples of |
11 participants
The Clarity smart contract language powers decentralized applications across a
wide range of domains. Over years of real-world use, developers have encountered
several pain points when interacting with other, sometimes untrusted, contracts.
Securely calling unknown contracts unlocks powerful use cases, but demands
careful safeguards.
This SIP addresses common feedback and requests from builders in the ecosystem.
It proposes new Clarity features to make it easier for developers to write
secure and composable smart contracts. Specifically, it proposes:
enables on-chain contract code validation, for example allowing contract A to
validate that contract B follows a specific template and is therefore safe to
interact with. This is especially useful for enabling bridges and
marketplaces to safely and trustlessly support a dynamic set of assets.
to protect its assets. These allow a contract to safely call arbitrary
external contracts (e.g. passed in as traits) while ensuring that if the
executed code moves assets beyond those specified, the changes will be rolled
back.
string-asciivalues. This function will enable developers to easily convert values like
bools andprincipals into their ASCII string representations,facilitating the generation of string-based messages for interacting with
cross-chain protocols.
Note
Additional feature added 👇
keyword will allow developers to easily access the timestamp of the block
currently being processed, enabling time-based logic and features in their
smart contracts. This is especially important for DeFi applications.