Content pfp
Content
@
0 reply
0 recast
0 reaction

jtriley.eth pfp
jtriley.eth
@jtriley
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:
2 replies
3 recasts
10 reactions

androidsixteen pfp
androidsixteen
@androidsixteen.eth
do you think that they'll have success convincing Solidity developers to move to a new language and VM? I'm bearish on any "intents" play that doesn't leverage the existing stack
1 reply
0 recast
2 reactions

jtriley.eth pfp
jtriley.eth
@jtriley
i'm bearish solidity & evm i think devs that want to stay there will be just fine, in the same way java devs are still just fine. but ppl wanting to leverage smth more flexible that's built with the knowledge we have about blockchain execution environments that we didn't then will absolutely try out new vm's and dsl's imo
1 reply
0 recast
3 reactions

androidsixteen pfp
androidsixteen
@androidsixteen.eth
Don’t you feel there’s too much critical mass around the evm? I get that it has serious flaws, but nothing competes well with a first mover advantage like this I see JavaScript / TS as the better analogy. Garbage origins, slow maturation, but massively pervasive and sticky given tooling lock-in
1 reply
0 recast
2 reactions