Proposals of #180

CronCat Manager

Exec Legacy Content
passed
Expected result
Turnout / Quorum
71.32% / 20.00%
Voting start 2023.06.23 at 17:06:43
Voting end 2023.06.26 at 17:06:43
99.99%
573 192 767 stars
Yes
0.00%
7 923 stars
No
0.00%
450 stars
Veto
0.01%
38 161 stars
Abstain

Details

Proposer
-
Total deposit
50 000 stars
Submit time
2023.06.22 at 22:06:48
Deposit end time
2023.07.06 at 22:07:48

Description

CronCat Manager\n\nThe CronCat manager is a somewhat central contract in the factory architecture. This is the contract that will store and manage task funds, refunds, etc. It is also the contract that gets called by the agents when it's time to fulfill tasks.\n\nThere's a smooth interplay between the manager and the agents and tasks contract, where these contracts habitually query and execute methods with one another.\n\nSee https://docs.cron.cat/docs/contracts-manager for more info.\n\n## Store WASM Code\n\nContract uploaded: croncat_manager.wasm\n\nSource code: https://github.com/CronCats/cw-croncat/tree/main/contracts/croncat-manager\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\n229f1a91efdac64ce3271aa7d868baa85d7589521b9a9c0f9e816b13cb2bd049\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_manager.wasm\n\n\nHakuna matata.\n

Votes

Voter
Answer