this is a nice articulation of why prover networks should have a metered execution like evm

building new things // prev: protocol eng @ https://recall.network

avichalp

The same can also happen for tripartite MPC markets (buyer - garbler, seller - executor, validator - verifier): a verifier of execution cannot disambiguate a slow executor, a poor connection between garbler and executor, or a faulty executor, without having an explicit cap (either in circuit size or time, or both)

We have a continuation model, where there's an explicit upper bound. It avoids the "trusted arbitrator" issue

BDFL of Quilibrium, ex-Farcaster, ex-Coinbase, always opinionated, never hydrated

/quilibrium

Wrapped QUIL

They don't! But they do bound the maximum allotted work per interval

how does continuations prevent never ending loops?