Aye

Setting onDemandBaseFee to 0.005 KSM

inWhitelisted Caller

2 years ago

Executed

This proposal sets the minimum fee for an order for a single block via the on-demand system to be 0.005 KSM. The reason for the change is to set a starting point that is high enough to deter spam but low enough that experimentation would not be cost-prohibitive.

If this minimum is found out to be too high after the on-demand system goes live, another proposal to lower the base fee should be proposed.

Note that the proposal has been submitted on the Whitelisted Caller track, meaning the Fellowship will be also voting shortly to whitelist the submission hash.

Comments (4)

2 years ago

Please correct me if my rationalization of this is misguided:

If I look up system.blockWeights I get:

  "maxBlock": {
    "refTime": 2000000000000,
    "proofSize": 18446744073709551615
  }

If I put these numbers in a utility.withWeight call like this call data: 0x1805000010746573740b00204aa9d10113ffffffffffffffff (I know this would fail, but for the sake of fee estimation), I get a fee of ~0.054 KSM.

Is this referendum suggesting that we decrease the cost of a block by a factor of 10 once on-demand goes live? I know you mention a follow-up to decrease but if my understanding is correct, shouldn't we start even higher?

2 years ago

@Adam_Clay_Steeber

The on-demand fee is on top of regular transaction fees.

Transaction fee pays for the weight of the transaction itself, the on-demand fee pays for the sharded validation of the para block.

2 years ago

I think this suggestion makes sense and protecting network from spam is important, but we definitely need to pay attention on possible side effects and influence of this change to prevent possible drawbacks, such as uncomfortable cost.

PleaseLogin to comment

Proposal Passed

Summary

Aye

Nay

Aye (177)0.0 DOT

Support0.0 DOT

Nay (2)0.0 DOT