Key Aliases

Key Aliases

When baking with TezBake, the baker automatically injects your default baker key. If you use additional keys — such as a separate consensus key or a DAL companion key — you need to register them as key aliases so the baker knows about them.

There are two approaches:

Method Behavior Use when…
additional_key_aliases Adds keys on top of the default baker key You want to keep the default baker key and add extra keys
key_aliases Replaces the default key list entirely You need full control over which keys are injected

This is the simplest and safest approach. Your default baker key continues to be injected automatically, and the aliases you specify are added alongside it.

Add aliases

tezbake node modify --set configuration.additional_key_aliases '["bb1_consensus","bb1_dal"]'

View current aliases

tezbake node show configuration.additional_key_aliases

Remove a specific alias

tezbake node modify --remove configuration.additional_key_aliases '"bb1_dal"'

Clear all additional aliases

tezbake node modify --unset configuration.additional_key_aliases

After any change, apply the updated configuration:

tezbake upgrade

If your install uses different lifecycle commands, confirm the current command with tezbake --help.

Advanced: key_aliases

Use key_aliases when you need complete control over which keys the baker uses.

⚠️ WARNING: When you set key_aliases, the default baker key is NOT automatically included. You must add it explicitly if you still want it injected.

Set key aliases (replaces defaults)

tezbake node modify --set configuration.key_aliases '["bb1_consensus","bb1_dal"]'

Add a single alias

tezbake node modify --add configuration.key_aliases '"bb2_dal"'

Remove a single alias

tezbake node modify --remove configuration.key_aliases '"bb2_dal"'

View current aliases

tezbake node show configuration.key_aliases

Clear and return to default behavior

tezbake node modify --unset configuration.key_aliases

After any change, apply the updated configuration:

tezbake upgrade

If your install uses different lifecycle commands, confirm the current command with tezbake --help.

Which Should I Use?

Scenario Method
Adding a consensus key alongside your baker additional_key_aliases
Adding a DAL companion key alongside your baker additional_key_aliases
Running multiple keys and need full control key_aliases
Simple single-key baking setup Neither — TezBake handles it automatically

Rule of thumb: If you want the baker to keep working as normal and just need to add a key, use additional_key_aliases. Only use key_aliases if you have a specific reason to override the default key injection behavior.

Migration from additional_key_aliases.list

⚠️ DEPRECATED: The file-based method (/bake-buddy/node/additional_key_aliases.list) is deprecated. Migrate to the CLI-based configuration described above.

If you currently have an additional_key_aliases.list file:

  1. Note the aliases in your file
  2. Set them via CLI: 
    tezbake node modify --set configuration.additional_key_aliases '["alias1","alias2"]'
  3. Delete the old file: 
    rm /bake-buddy/node/additional_key_aliases.list
  4. Apply the updated configuration: 
    tezbake upgrade

Common Examples

Consensus key + DAL companion

Use this when your separate consensus key was imported as consensus:

tezbake node modify --set configuration.additional_key_aliases '["consensus","companion"]'

Default baker consensus key + DAL companion

If your consensus key is imported under the default baker alias, you only need to add the companion:

tezbake node modify --set configuration.additional_key_aliases '["companion"]'

If you previously had baker + consensus + companion and your tz4 key is now active, follow the TezSign later cleanup section.

Verify everything is set

tezbake node show configuration.key_aliases
tezbake node show configuration.additional_key_aliases
tezbake info --dal

If configuration.key_aliases is set, it replaces the default baker key list. Most setups should leave it unset or null and use additional_key_aliases instead. If the baker log says a tz4 consensus key “has not been provided to the baker,” the tz4 signing alias set is incomplete or key_aliases is overriding the default baker alias.