Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc(releases): axelard v1.2.1 #543

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
41 changes: 41 additions & 0 deletions releases/axelard/2025-02-v1.2.0.md
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

file name should use v1.2.1

Original file line number Diff line number Diff line change
@@ -0,0 +1,41 @@
# axelard v1.2.1

| | **Owner** |
|-----------|------------|
| **Created By** | @haiyizxx <[email protected]> |
| **Deployment** | @RiceAndMeet <[email protected]> |

| **Network** | **Deployment Status** | **Date** |
|-------------|----------------------|----------|
| **Devnet Amplifier** | Deployed | 2025-02-07 |
| **Stagenet** | Deployed | 2025-02-07 |
| **Testnet** | - | TBD |
| **Mainnet** | - | TBD |

[Release](https://github.com/axelarnetwork/axelar-core/releases/tag/v1.2.1)

## Background

Changes in the release:

1. Burn transaction fees from circulation.
2. Security patches to wasmd and CometBFT.

## Deployment

- wasmvm lib has been updated from `v1.3.1` to `v1.5.8`, make sure update the dependency if you are using the axelard binary.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- wasmvm lib has been updated from `v1.3.1` to `v1.5.8`, make sure update the dependency if you are using the axelard binary.
- wasmvm lib has been updated from `v1.3.1` to `v1.5.8`, make sure to update the dependency if you are using the `axelard` binary.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add a link to the wasmvm lib?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also mention that if you're using the community scripts, you'll need to update


### Devnet Amplifier / Stagenet

### Testnet / Mainnet
Comment on lines +28 to +30
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
### Devnet Amplifier / Stagenet
### Testnet / Mainnet
- Stop the node once the upgrade height is reached. [Show upgrade height log]
- Restart the node with the `axelard v1.2.1` and `wasmvm v1.5.8`.


## Checklist

The following checks should be performed after the rollout

- [ ] Verify that nodes are producing new blocks after the upgrade.
- [ ] Check the denomination of burned fees in `burned-uaxl` on-chain using:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also mention the event and how to check on axelarscan for completeness

```bash
axelard q bank balances axelar1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqecnww6
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
axelard q bank balances axelar1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqecnww6
axelard q bank total --denom burned-uaxl
# OR
axelard q bank balances axelar1qqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqecnww6 --denom burned-uaxl

```

Loading