CronCat Tasks

The CronCat tasks contract is commonly-used since it involves task creation and removal. It also contains several helpful methods like determining a task hash before creation. This has an interplay with the CronCat manager contract, which stores the funds for every task. The manager contract will be in charge of some task-related methods dealing with funds such as refilling a task balance, so it might continue.

See https://docs.cron.cat/docs/contracts-tasks for more info.

Store WASM Code

Contract uploaded:

Source code: https://github.com/CronCats/cw-croncat/tree/main/contracts/croncat-tasks

Compile Instructions

CronCat consists of several smart contracts, utilizing cargo workspaces. Look in the project root for a

that contains several helper utilities.

To compile the canonical way:

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:0.12.13

The above will take a while. \ud83d\ude3c

This results in the following checksum:

8f95ef9d61226a5797507b2eeb670c623d93e6a118824f5858a78a4149e40cc9

Verify on-chain contract

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

Verify locally

sha256sum artifacts/croncat_tasks.wasm

Hakuna matata.