stargaze

Prop 182: CronCat Agents

CronCat Agents

The CronCat agents contract keeps track of the \agents\ which are the accounts that are on the hook for fulfilling CronCat tasks. If an active agent stops participating, it is kicked, and a member from the pending agent queue is replaced. Each time a task is fulfilled, the agent earns a micropayment as an incentive.

Note: as suggested by our security audit from Oak Security, the agent network will go through progressive decentralization. See https://docs.cron.cat/docs/contracts-agents for more info.

## Store WASM Code

Contract uploaded: croncat_agents.wasm

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

## Compile Instructions

CronCat consists of several smart contracts, utilizing cargo workspaces. Look in the project root for a justfile that contains several helper utilities.

To compile the canonical way:

sh<br />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<br />

The above will take a while. \ud83d\ude3c

This results in the following checksum:

<br />5c610b033df34ef75a252247cd5d5926e28edc222174c5ad49177d2efbeaeb3f<br />

## Verify on-chain contract

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

## Verify locally

sh<br />sha256sum artifacts/croncat_agents.wasm<br />

Hakuna matata.