Chainstack's Node Credential Rotation Requires Old Keys to Be Disabled

Chainstack customers completing node credential rotation need to move their applications to replacement credentials and then deactivate the old ones. Generating new credentials alone does not complete the process.

During the switch, both sets of credentials remain active. Once customers deactivate the old credentials, requests that use them are rejected. Chainstack’s rotation process does not change a multichain authentication token.

The guidance adds a practical step to Chainstack’s earlier credential-rotation coverage. The company has asked customers to rotate node credentials, change passwords, regenerate platform API keys if used and watch for phishing. Customer-facing services continued operating, and customer nodes, the console and API were not modified.