Connector API key

warning

The Connector API does not have authorization enabled, but it will be required on Tuesday, February 25 at 9am EST / 3pm CET.

This is not expected to cause any disruption, as Treasury will always passes authorization to it's requests to connector API.

As long as your Treasury instance is configured to use an API key normally, no disruption is expected. You can validate this is the case by checking the health endpoint (http://127.0.0.1:8777/healthy?verbose) on the connector node (node running with --connector). If you see a message like:

could not use oracle API: Unauthenticated: Neither access token nor API key passed

Then you do not have a working API key configured. Please see how to setup an API key and add it to your connecting node.

Update

We discovered a small edge case where the API key was not getting configured as expected by 'connecting' treasury nodes. We are fixing this in 25.2.7, and the following workaround will resolve the issue in the meantime.

Update your $TREASURY_HOME/treasury.toml file to have a meaningless override, like so:

[connector]
#  ...
# Useless override: can remove after Treasury is on `25.2.7`
[connector.chains.btc]
a = 1

Only needs to be done on any connector node (nodes using the --connector flag).