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
12 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
3 reactions

cqb pfp
cqb
@cqb
I love reading about new VM architectures. makes me wonder if there will eventually be a standard set of instructions with modular extensions in a similar spirit as riscv but for distributed execution, maybe with different flavours of word sizes
1 reply
0 recast
1 reaction

looking4ward 🎩 pfp
looking4ward 🎩
@looking4ward.eth
523 $DEGEN
0 reply
0 recast
0 reaction