4,164 questions
4,377 answers
5,729 comments
Thanks, I think you found a bug here in the paytxfee runtime parameter. We'll aim to fix this in the next maintenance release. In the meantime please use the settxfee API command instead.