# v1.1.1 — release notes

aeva-1's software upgrade `v1.1.1`, from `v1.1.0-locks`. No new module and no
store change.

## aeUSD's ERC-20

* aeUSD on aeva-1 is the USDG bridged from Robinhood Chain over the route
  `usdg-rh` (bank denom
  `hyperlane/0x726f757465725f61707000000000000000000000000000020000000000000001`,
  6 decimals). The upgrade gives it its ERC-20 at
  **`0x6F3D4d9994457e11cf88d5577A0b5ac457B2d78B`**: a precompile over the bank
  coin. `balanceOf` and `totalSupply` are the bank's, `transfer` moves the
  bank coin (nothing is wrapped or converted), and name, symbol and decimals
  come from the coin's metadata (aeUSD, aeUSD, 6).
* The native `aeusd`, the testnet's stand-in, has no supply on aeva-1. Its
  metadata and its ERC-20 at `0x5aB37c022D0ce153F1C1949a88a93A8DC3E546D7` are
  renamed **"aeUSD (legacy)"** (name and symbol), so wallets no longer show two
  aeUSD tokens. Its denom units and its pair are unchanged. Where `aeusd`
  circulates (the testnet) it is left as it is.
* Nothing else in the state changes.

## Rehearsed

On a copy of aeva-1's state (height 136 353, after the v1.1.0 upgrade, its
five validators): the expedited proposal with this release's plan info
passed, every node stopped at the plan height and applied `v1.1.1` on
restart, and blocks continued. After it, the bridged aeUSD's pair was at
`0x6F3D…d78B` and its ERC-20 read aeUSD, aeUSD, 6, with `totalSupply` equal to
the bank supply; the native `aeusd` and its ERC-20 read "aeUSD (legacy)";
every balance, delegation and validator was unchanged. An ERC-20 transfer
signed as an EVM transaction moved the bank coin one for one, supply
unchanged, and a bank send of the same coin still worked.

## Built

Reproducible from the tag with the module cache at a fixed path
(`PROVENANCE.md`): the binaries name no build machine's directories.