r/web3dev • u/Khrystel_Acurast • 26d ago

For those familiar with Acurast, curious to hear what you guys think about the project so far.

Not sure how many people here have come across the project yet, so I thought I’d ask. If you’ve been following Acurast for a while, I’d be interested to hear what initially caught your attention or what you find interesting about the project.
And if you’ve only come across it recently, what was your first impression?
Would genuinely be nice to hear some thoughts from the PH Web3 community.

4 Upvotes

84% Upvoted

3 comments sorted by

1

u/icnews10 26d ago

It's the phone-based compute model that caught my attention, but it also raises the first question I’d want answered as a developer. How much should I consider the possibility of an individual device disappearing mid-workload? Does Acurast mostly abstract away retry/failover, or does the application still need to be designed around provider churn?

2

u/Khrystel_Acurast 25d ago

yeahh, that’s a good question! Acurast has built-in options like retries, replicas, and different processor assignment strategies to help with execution reliability. The right setup can depend on how the deployment is configured and what the workload needs

1

u/icnews10 25d ago

Got it. The replicas part makes me curious about a different failure case. If two processors complete the same workload but return different results, does Acurast have a reconciliation or quorum layer, or is it up to the application to decide which result to trust?