As of 2024-05-14 a change has been implemented to enforce access token expiry. If you see higher numbers of HTTP 401 responses, please check tokens that may have expired. For more details, including how to mitigate disruption, please check our docs guide on Expired Access Tokens. If you have a support contract, you may open a support ticket for additional assistance.
Resolves #1628 (closed). There are a couple minor earmarks for missed BCH parameters in config/defaults.yaml that did not cause issue in practice. This also folds in a change to use the max fee over last 10 blocks for LTC/DOGE to reduce fee noise a bit.