RFC-000-002: MultiVariable Fee Control Proposal

I like the idea of algorithmically based fees.

As for the variables considered by the algorithm:

  • Asset being bridged :+1:
  • Direction (burn/mint) :+1:
  • Size of transaction :-1: (I am concerned this could be gamed)
  • Chain :-1: (I do not see the value since we already consider the asset being bridged)

I suggest replacing “Size of transaction” with something based on overall volume for the specific asset. Something like what @loong described in Fee increase one day maybe?

I imagine the algorithm would include constants. Darknodes should be able to vote on adjusting any constants that are part of the algorithm.

1 Like