When you rent computing power on Acurast, a quote over your budget means no match.
A task that runs once every minute executes 1,440 times a day. The cost per run may look small, but over several weeks, it adds up—and needs to be carefully calculated.
@Acurast’s deployment pricing includes a specific constraint. Developers can set a budget for each execution, and if a node’s quote exceeds the limit, that match is rejected. For tasks with multiple executions, the total execution cost for the entire schedule must also stay within the total budget locked in beforehand.
Node quotes are calculated automatically by the protocol. The device’s on-chain benchmark contribution and the task’s specified execution duration are factored into the calculation, along with a uniform price coefficient and a minimum price. Anyone using the compute can check how the price was determined.
I like that budget limits are built into the matching rules. For scheduled scripts and long-running automation, you should decide how much you’re willing to spend on compute before deployment.
With this mechanism, setting the budget too low could mean you can’t find a suitable node. You can decide before deployment how much extra you’re willing to pay for performance. This controls Acurast compute costs; fees for external paid APIs called by your task need to be managed separately.
To learn about Acurast and take part in official tasks, use my referral code: jescfm
A task that runs once every minute executes 1,440 times a day. The cost per run may look small, but over several weeks, it adds up—and needs to be carefully calculated.
@Acurast’s deployment pricing includes a specific constraint. Developers can set a budget for each execution, and if a node’s quote exceeds the limit, that match is rejected. For tasks with multiple executions, the total execution cost for the entire schedule must also stay within the total budget locked in beforehand.
Node quotes are calculated automatically by the protocol. The device’s on-chain benchmark contribution and the task’s specified execution duration are factored into the calculation, along with a uniform price coefficient and a minimum price. Anyone using the compute can check how the price was determined.
I like that budget limits are built into the matching rules. For scheduled scripts and long-running automation, you should decide how much you’re willing to spend on compute before deployment.
With this mechanism, setting the budget too low could mean you can’t find a suitable node. You can decide before deployment how much extra you’re willing to pay for performance. This controls Acurast compute costs; fees for external paid APIs called by your task need to be managed separately.
To learn about Acurast and take part in official tasks, use my referral code: jescfm
