Question about the fees for non-replicated outcalls

Developers
1

Hi, I noticed that the canister HTTP outcall feature has introduced a new option: enable non-replicated outcalls

This feature allows a single node in the subnet to send HTTP outcalls externally — a very useful capability, as it means we no longer need an off-chain idempotent proxy.

However, I’ve observed that the cycle fee for non-replicated requests appears to be the same as for replicated requests. Why is that? Shouldn’t it cost less when only one node in the subnet issues the request?

1 Like
2

Hi, great question.

The cycle fee is the same because both non-replicated and fully-replicated calls consume a similar amount of block space, and block space is the most expensive part of an outcall.

That being said, we’re planning to propose bigger changes to this feature, which we’ll share on the forum soon. The final price of outcalls is one of the main things we are reviewing.

1 Like