Fees

[NewJerry]

Hello community. I'm hoping I might be able to get some answers, insight or explanation of some kind of something that is happening to me. I've tried a couple places to get some more information but so far no one has been able to provide any infor or meaningfuil way of mitigating this. It would really be appreciated to have more information.

In the settings I give:
"paytxfee" : 0.00000000,
"relayfee" : 0.00010000,

Currently using the fee estimation within the dash system it tells me my estimated network fee will be: 0.05235602...

This one is horrible:
9904e6026ab83dcc4bf48f0ab8131d9d6353974ae069cec396b775837d6016e7
4 inputs, 0.155xx sent, 0.1 Dash network fee.


The rest of these seem to be between 0.01 and 0.04 per transaction.

79003750d5f838c467b17334bada1862d44174791c8a54dd75e423228fd41502
74a5e84cb3ed8b7509bd7b765e985c3d531fc42e4b278cd9cc5dc8643a1b0d8f
4b0768236d4866ff22d11691cb4fee7e3c892fb3a349801d8b8e1bff2037ab9b
1fee226c807bd4ba71d05449764b240a856f5816baa5683a1e84332a9ddd913a
561a73fd3c35e6ac0c22ee7ed6b2f7ef9f8720571add1f0aec994a9b1352f2d3
5125dfae8f19210a5b21a821209a7d1dc6498043e4c1e57331f4791c9d25e002
ecad3eae46d38d40d70d79c6aeb9fb328fb14f1cf5ebc4cee8a5325e537215b3
5bdda7cfce0c67bc5b093405b18386e39e868ac2ce3aacaeaaadeff7240f12fc
38cf100e44ee11cf326558751e79e321e363a3f7bcabe7c67a7169246fbf2459
e4c4994e2d9ac28c3978981f0d8cd34233e3c2c05130fa1498b1ee1d9f75ca33

Thanks a lot.

 

[UdjinM6]

Ok, I'm not 100% sure but I went through the whole algo again and again and there must be no errors besides... that it just doesn't work. The algo in btc 0.10 (which we forked 0.12 from) ramps up fee for "low priority" txes (i.e. small inputs and/or low confirmations) even if there is enough empty space in the block. And what's worse it keep doing so based on previous fees again and again and again. Basically there is no "negative loop" if there is small number of txes for small networks like ours i.e. there is not enough people sending high priority (old enough or high value) txes. So it's kind of ok for anti-spam protection on large scale but not in our case.

Using "paytxfee=0.00010000" should do the trick.