Configurable client propagation parameters

[hackfisher]

Refer another api bitcoin_settrxfee.

_chain_db->set_priority_fee( amount );

[vikramrajkumar]

We probably want a separate command like: wallet_delegate_set_min_priority_fee

[nathanielhourt]

So what exactly is the issue here? We need a new API call to set the minimum fee for transactions my delegate(s) will include in their blocks?

[vikramrajkumar]

Progress: https://github.com/BitShares/bitshares_toolkit/commit/d17ac54b894621e752f2a093d9514beadcd44bae

[drltc]

Does @nathanhourt describe this issue accurately? Please specify what the two fees are.

[vikramrajkumar]

The default fee to construct new transactions with can already be set with wallet_set_transaction_fee.

We should have another command that lets users set the minimum transaction fee that they require to propagate the transaction. This is currently set to 0.1 XTS and users are not able to change it.

[drltc]

Instead of having a minimum prop fee set by each peer, we should have each delegate publish a TITAN profile field called min_prop_fee describing the smallest tx fee that delegate is willing to include in a block. Then peers set peer_min_prop_fee = min(m, 0.1 XTS) where m is the ~~minimum~~ median value of the delegates' min_prop_fee fields (or zero if no delegates currently publish that field).

The main motivation for this design is:

• Allow clients to predict the effect of raising or lowering transaction fees
• Transparently publish changes to the network's propagation behavior
• Allow delegates to collectively control fees in a decentralized manner without requiring hardforking or requiring delegates to coordinate to all make a change at the same time

I think @bytemaster proposed something very similar to this on the forum some time ago.

[drltc]

Edit above: Replace "minimum" with "median"