CronCat Tasks
passed
Expected result
—
Turnout / Quorum
69.91% / 20.00%
Voting start 2023.06.23 at 17:06:48
Voting end 2023.06.26 at 17:06:48
99.99%
561 917 429 stars
Yes
0.00%
7 923 stars
No
0.00%
450 stars
Veto
0.01%
29 448 stars
Abstain
Details
Proposer
-
Total deposit
50 000 stars
Submit time
2023.06.22 at 22:06:46
Deposit end time
2023.07.06 at 22:07:46
Description
CronCat Tasks\n\nThe 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. \n\nSee https://docs.cron.cat/docs/contracts-tasks for more info.\n\n## Store WASM Code\n\nContract uploaded: croncat_tasks.wasm\n\nSource code: https://github.com/CronCats/cw-croncat/tree/main/contracts/croncat-tasks\n\n## Compile Instructions\n\nCronCat consists of several smart contracts, utilizing cargo workspaces. Look in the project root for a justfile that contains several helper utilities.\n\nTo compile the canonical way:\n\nsh\ndocker 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\n\n\nThe above will take a while. \ud83d\ude3c\n\nThis results in the following checksum:\n\n\n8f95ef9d61226a5797507b2eeb670c623d93e6a118824f5858a78a4149e40cc9\n\n\n## Verify on-chain contract\n\nsh\nstarsd q gov proposal $ID --output json | jq -r '.content.wasm_byte_code' | base64 -d | gzip -dc | sha256sum\n\n\n## Verify locally\n\nsh\nsha256sum artifacts/croncat_tasks.wasm\n\n\nHakuna matata.\n
Votes
Voter
Answer