Badges v1.1 Update

This proposal requests uploading the v1.1.0 version the Badges Hub contract. The logics for migrating the contract state can be found at: here.

This update includes two changes:

1. Separate data fee rates for metadata and claim keys

Background: Since Stargaze chain uses zero gas price, the Badges contract decides to charge a "data fee" to discourage spamming attacks. The fee is charged when creating a new badge and when adding claim keys to an existing badge, the amount being proportional to the storage space taken by the new data. Currently, the fee rate is set to 200,000 ustars per byte of data.

The problem: At the current fee rate, the cost for adding claim keys is quite high. It takes ~140 STARS or ~US$7 to add 10 keys. To host an event of 200 people would thus require ~US$140 just to upload the claim keys, which is unbearable for many badge creators. On the other hand, it is reasonable that keys have a lower fee rate than metadata, as whereas metadata are to be kept on chain forever, claim keys are deleted once used.

This update introduces separate fee rates for metadata and keys. Specifically, metadata fee rate will still be 200,000 ustars per byte, while for keys the rate is reduced to 10,000 ustars per byte.

2. Extend the claim deadline for badge #3

Badge #3 was supposed to be distributed at the Cosmoverse event. However, due to delays in shipping, the claim QR codes were not delivered to the recipients on time. This update extends the claim period of this badge to the end of this year (Decenber 31, 23:59:59 UTC) while the QR codes are to be distributed over email.

Wasm code info

The source code can be find at this repository. The binaries are compiled at commit dc485bd using workspace-optimizer v0.12.9. Specifically, the following command is used:

docker run --rm -v "$(pwd)":/code \
  --mount type=volume,source="$(basename "$(pwd)")_cache",target=/code/target \
  --mount type=volume,source=registry_cache,target=/usr/local/cargo/registry \
  cosmwasm/workspace-optimizer:v0.12.9

This results in the following SHA256 checksums:

fb7fd78933b989f1800e2c031fe443571302dc51558a1757d7d5e07da14fcd43  badge_hub.wasm
495d59c2de119fb2b9502714609ed904f4c0f0e5b7b66bb813f12a387e50c86b  badge_nft.wasm

Voters are encouraged to independently validate that the binary code proposed on-chain matches the Rust source code. The following command may be helpful:

starsd q gov proposal $id --output json \
| jq -r '.content.wasm_byte_code' \
| base64 -d \
| gzip -dc \
| sha256sum

where $id is the id of this proposal.