Intents
/intents100
Discussions about intent-centric infrastructure and applications
cross-posting this here, figured may be interesting.
solver-based multi-chain balance unification
solver-based multi-chain balance unification
I found the definition of an intent here super elegant.
An intent describes the output, whereas a transaction defines the input.
Cheers to all the intent enjoyooors!
https://www.youtube.com/watch?v=seETIrzlU70
An intent describes the output, whereas a transaction defines the input.
Cheers to all the intent enjoyooors!
https://www.youtube.com/watch?v=seETIrzlU70
essentials team built out two pieces recently, declarative execution environment (essentialvm) & constraint driven language (pint)
pint contracts are composed of a persistent storage block & a series of predicates which constrain how state transitions happen. state access is made explicit in predicates, identifier (counter) may constrain existing state, identifier w single-quote suffix (counter') may constrain next state.
vm itself is a 64 bit stack machine w two execution stages, one for loading storage variables into a tx buffer, the other for constraining values in the tx buffer. isa is minimal, w a handful of logical, arithmetic, elliptic curve, sha, storage, and control flow ops
note that state is not explicitly assigned to a single value, state is arbitrarily provided by solvers, predicates only constrain the bounds of what solvers submit
obligatory counter attached:
pint contracts are composed of a persistent storage block & a series of predicates which constrain how state transitions happen. state access is made explicit in predicates, identifier (counter) may constrain existing state, identifier w single-quote suffix (counter') may constrain next state.
vm itself is a 64 bit stack machine w two execution stages, one for loading storage variables into a tx buffer, the other for constraining values in the tx buffer. isa is minimal, w a handful of logical, arithmetic, elliptic curve, sha, storage, and control flow ops
note that state is not explicitly assigned to a single value, state is arbitrarily provided by solvers, predicates only constrain the bounds of what solvers submit
obligatory counter attached:
A few solid resources on intents:
https://blog.particle.network/intent-centric-design-repackaging-account-abstraction-or-evolving-it-further-2
https://www.paradigm.xyz/2023/06/intents
https://www.brink.trade/blog/powerful-intents-part-1
https://blog.essential.builders/a-slightly-more-formal-definition-of-intents
https://blog.particle.network/intent-centric-design-repackaging-account-abstraction-or-evolving-it-further-2
https://www.paradigm.xyz/2023/06/intents
https://www.brink.trade/blog/powerful-intents-part-1
https://blog.essential.builders/a-slightly-more-formal-definition-of-intents