Thanks. I'll push an update today that falls back to a fee estimation method that doesn't suffer from this problem.