The following color coding scheme will be followed for messaging between partners and axelar team.

All emails will be sent with the following subject line:

CODE_<Colour>_ALERT_AXELARNET

The following colors will be used:

We strongly encourage partners to keep us updated on their email addresses and to utilize a system like PagerDuty to alert team members about urgent issues. You can do this by alerting on CODE_RED_ALERT_AXELARNET as the subject line.

Messaging Procedure

  1. Upon receipt of a notice, please respond immediately with the email subject as “ACK”. Most messages will include a response requirement. Please try to be as diligent as possible for this acknowledgment.
    1. Generally, we expect an acknowledgement right away, with a follow-up email if any upgrade or update actions are necessary.
  2. When replaying to the email for upgrades/updates, please include what environments you updated. You can list as N/A if you don’t run a particular environment.
    1. Examples
      1. TestNet Nodes.
      2. MainNet Validators.
  3. When replying to the email please include your Validator Moniker/Company Name. This helps us quickly track responses.
  4. It is vital to our operations that you respond to these emails in a timely manner. You can also reach us on your private group in the Axelar Discord. If you do not have one, please reach out to [email protected] and we will create one for you.

Verifying Message Integrity

<aside> ⚠️

Critical messages will be signed from the axelardev account on keybase.io. To verify the message, check for the attached file in the email.

</aside>

<aside> ⚠️

You can verify the message on the web app by going to keybase.io/verify, or you can verify in the terminal if you have the Keybase CLI installed.

</aside>

<aside> ℹ️

Our Keybase account is axelardev and the identity is confirmed against axelar.dev and axelar.network in addition to X (formerly Twitter).

</aside>