Dynamic Pricing: A New Era for Compute Value

Acurast Introduces Dynamic Pricing: A New Era For Compute Value

Compute pricing on decentralized networks has always been quite unclear. Most networks let each provider set their own rates manually, and in practice, nobody ever updates them. A flagship phone and a budget phone from five years ago end up charging the same rate, because the pricing has no connection to what the hardware can actually do.

 

Today, that changes for Acurast.

 

The Acurast community has voted through an on-chain governance referendum to introduce Dynamic Pricing. A new model where compute is priced automatically by the network, based on real, on-chain hardware benchmarks. No more manual rates. No more stale pricing. No more guesswork.

 

This is one of the most significant protocol upgrades since Mainnet launched in January.

 

Why We Updated the Old Model

In the previous system, each processor manager had to manually set pricing for their devices. A base fee per execution and a fee per millisecond of compute time. In theory, this allowed for flexible pricing. In practice, prices were set once and never updated. So even if there were many deployments, because developers spent so few tokens, the compute remained undervalued. The marketplace wasn’t really a marketplace at all. It was a static list of numbers that stopped reflecting real value the day they were posted.

 

For developers, this meant pricing had no reliable connection to compute quality. For operators, it meant better hardware didn’t translate into more deployments. And for the network as a whole, there was no real price discovery happening.

 

 

How Dynamic Pricing Works

The new system removes manual pricing entirely.

 

Instead, a processor’s price is now derived automatically from its contribution to the network’s benchmark rewards. The same on-chain data the protocol already tracks every epoch (roughly every 90 minutes).

 

In simple terms: the network measures what each device can actually do, and prices it accordingly. Stronger hardware, higher benchmark scores, higher price. Automatically. No configuration needed from the processor manager. A fairer system.

 

The formula

The price per execution is calculated using the processor’s benchmark reward contribution, divided by the epoch length and block time, then multiplied by the execution duration and a global price multiplier. If the result falls below a protocol-defined minimum, the minimum applies instead.

 

The governance multiplier

Both the global multiplier and the minimum price are governance parameters, meaning the community can adjust them over time without requiring a runtime upgrade. The plan is to eventually move the multiplier to a usage-based curve, so pricing naturally adjusts based on how much the network is actually being used.

 

Think of it like surge pricing, but governed by the community and driven by real network data.

 

What This Means for Developers

Developers still set a maximum budget per deployment. If a processor’s computed price exceeds that budget, the match is simply rejected. No surprises, no hidden costs.

 

What changes is that the prices developers see now actually mean something. They reflect real hardware capabilities, verified on-chain, updated every epoch. This is transparent pricing by design. Not a pricing page that gets updated quarterly. Not a negotiation. The network handles it.

 

What This Means for Operators

If you’ve invested in better hardware, that investment now directly translates into better pricing. The protocol recognizes your device’s contribution through its benchmark scores and prices your compute accordingly. You don’t need to configure anything. The network does the work.

 

This also means the marketplace becomes genuinely competitive. Operators with stronger, more reliable hardware naturally attract more deployments because their pricing reflects their capability.

 

The Burn Mechanism

Here’s where it gets interesting for the broader ACU economy.

 

Whenever a developer deploys something using Acurast compute, they pay a compute fee in $ACU. This fee is not paid directly to the processor, but is handled at the protocol level. In return, providers who contribute compute receive a weight multiplier, which increases their eligibility to receive rewards from the network inflation.

 

Similar to how tokens are consumed on Ethereum when executing a smart contract, tokens from the compute fees are consumed when the provided compute is put to use. These tokens are burnt and therefore removed from circulation permanently.

 

As network usage increases, more compute is executed and more fees are processed through this mechanism.

This creates a direct link between network usage and token supply. The more the network is used, the more deflationary pressure on ACU. And with 443,000+ deployments and growing, every single execution contributes to this system.

 

Better Incentives for Matchers

The upgrade also changes how matchers are incentivized. Matchers are the entities that propose matches between deployments and processors.

 

Previously, matchers were paid upfront when a match was proposed, regardless of whether the processor actually accepted the job. Now, matchers only get paid when a processor acknowledges the assignment.

 

This aligns the matcher’s incentive with match quality. A match that gets rejected earns the matcher nothing. The result: better matches, less spam, a healthier marketplace.

 

Decided by the Community

This wasn’t a decision made behind closed doors. Dynamic Pricing went through Acurast’s on-chain governance process. Proposed, debated, and voted on by ACU token holders.

 

That’s decentralization in practice. Not advisory polls. Not team announcements. Real protocol changes decided by the people who use and hold the token.

 

What Comes Next

Dynamic Pricing is live. But this is just a starting point that will be further developed over time.

 

The global price multiplier will eventually move to a curve based on actual network utilization, meaning pricing will naturally respond to supply and demand in real time. The community will continue to govern the parameters as the network evolves.

 

For developers: transparent, hardware-verified compute pricing. No configuration needed.

For operators: better hardware now means better pricing, automatically.

For the ACU economy: every execution burns tokens. More usage, more burn.

 

This is what a real compute marketplace looks like.