Releases: public-awesome/badges
v1.2.0
v1.1.0
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.
v1.0.0
v1.0.0-rc3
Fixed two bugs
- Previously if no fund is sent (i.e.
info.fundsis empty),stringify_fundswill generate an empty string. However, using empty strings as values of event attributes is not allowed. Now "no fund" is stringified to this string:[]. - When invoking
set_nfton the Hub contract, the Hub should automatically set the NFT as "ready".
v1.0.0-rc2
new instantiation logic for the nft contract
v1.0.0-rc1
adding schema, basically
v1.0.0-rc0
basically rewrote the whole thing for redeployment on Stargaze