4,157 questions
4,370 answers
5,718 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.