openmath-claim-reward

Claims earned rewards from the OpenMath platform. Use when the user wants to query claimable imported/proof rewards or withdraw verified Shentu rewards after...

Security Scan

The skill's code and instructions match its stated purpose (querying and claiming OpenMath rewards via the local shentud CLI); it shells out to local binaries and reads a small per-user config but does not appear to contact unexpected endpoints or request unrelated secrets.

Purpose & Capability

Name/description (claiming OpenMath rewards) align with included files and instructions: scripts query rewards and read an openmath-env.json. The SKILL.md requires python3 and shentud which are appropriate. Minor inconsistency: the registry metadata lists no required env vars while SKILL.md documents optional environment overrides (OPENMATH_ENV_CONFIG, SHENTU_CHAIN_ID, SHENTU_NODE_URL); this is a small documentation mismatch but not a functional red flag.

Instruction Scope

Runtime instructions are narrowly scoped: they read a project/user config (openmath-env.json), call the local shentud CLI to query rewards or tx status, and instruct the user to run shentud tx for withdrawals. The instructions explicitly require user confirmation before broadcasting and limit file access to the named config locations. No instructions ask to read unrelated system files or exfiltrate data.

Install Mechanism

No install spec (instruction-only with small helper scripts). No downloads or extracted archives. This minimizes risk; the only actions are running the included Python scripts and invoking the local shentud binary.

Credentials

The skill documents optional env vars for configuration (OPENMATH_ENV_CONFIG, SHENTU_CHAIN_ID, SHENTU_NODE_URL) which are appropriate for a blockchain RPC tool. It does not require unrelated credentials or secrets. Note: registry metadata reported 'Required env vars: none' while SKILL.md lists these as optional — the difference is informational only.

Persistence & Privilege

always:false and no special persistence or system-wide configuration changes are requested. The skill will invoke local binaries (normal for this task) but does not attempt to modify other skills or agent-wide settings.

Assessment

This skill appears to do exactly what it says: query claimable rewards and help with withdrawing them via your local shentud CLI. Before using it: 1) verify you have a trusted shentud binary on PATH (don’t run with an untrusted or downloaded binary), 2) check the openmath-env.json config paths it will read (~/.openmath-skills or ./.openmath-skills or the file pointed to by OPENMATH_ENV_CONFIG) to ensure it contains the expected prover_address, 3) confirm the exact key name/address with shentud keys show before broadcasting any tx (the skill explicitly requires user confirmation), and 4) verify the RPC node URL (default https://rpc.shentu.org:443 or your SHENTU_NODE_URL) — avoid pointing to unknown third‑party nodes when signing transactions. The included scripts are small and readable; if you plan to use the withdraw flow, follow the checklist in SKILL.md and do not broadcast transactions until you are certain the local key controls the reward address.

Instructions

Query and withdraw rewards for verified OpenMath activity on Shentu. Flow: query bounty rewards → withdraw via bounty withdraw-rewards → wait 5–10 s → re-query. Uses SHENTU_CHAIN_ID and SHENTU_NODE_URL for runtime chain/RPC settings, with built-in mainnet defaults if unset. Shared config resolution order: --config <path> → OPENMATH_ENV_CONFIG → ./.openmath-skills/openmath-env.json → ~/.openmath-skills/openmath-env.json. If OPENMATH_ENV_CONFIG is set, treat it as the selected config path. If that file is missing or invalid, stop and fix it instead of silently falling back.

Requires trusted local python3 and shentud binaries on PATH. Read-only reward queries shell out to local shentud and query a Shentu RPC endpoint. Withdrawals additionally rely on the local OS keyring via shentud --keyring-backend os. Before any withdrawal, confirm the key name, resolved address, and node URL with the user.

First-run gate

If the user already provided an address explicitly, reward query can run immediately.

If no address was provided, auto-discover prover_address from OPENMATH_ENV_CONFIG when it is set; otherwise check only ./.openmath-skills/openmath-env.json or ~/.openmath-skills/openmath-env.json. If no usable config exists, or if the config exists but prover_address is missing, do not guess the address. Follow references/init-setup.md.

For withdrawals, do not proceed until a local os keyring key is known for the same address. Do not broadcast a withdrawal until the user confirms the matching key name/address and the RPC node they want to use.

Workflow checklist

• Env: If needed, export SHENTU_CHAIN_ID / SHENTU_NODE_URL, or set OPENMATH_ENV_CONFIG to a specific openmath-env.json; otherwise use the built-in mainnet defaults and standard config auto-discovery.
• Address: Use an explicit address, or let query_reward_status.py rewards auto-discover prover_address from OPENMATH_ENV_CONFIG or the standard openmath-env.json locations.
• Query: Run query_reward_status.py rewards [address] (or shentud q bounty rewards <address> --node <shentu_node_url>) to see imported_rewards and/or proof_rewards.
• Withdraw: If any bucket is non-empty, first make sure a local os keyring key controls the same address, confirm shentud keys show <your-key> -a --keyring-backend os matches the reward address, then run shentud tx bounty withdraw-rewards --from <your-key> --keyring-backend os --chain-id <shentu_chain_id> --node <shentu_node_url> --gas-prices 0.025uctk --gas-adjustment 2.0 --gas auto (use SHENTU_CHAIN_ID / SHENTU_NODE_URL or the built-in defaults).
• Wait: 5–10 s for block inclusion.
• Re-query: Run query_reward_status.py tx <txhash> --wait-seconds 6, then query_reward_status.py rewards <address> --wait-seconds 6 to confirm withdrawal; empty buckets are reported as zero, not error.

Scripts

Script	Command	Use when
Query rewards	python3 scripts/query_reward_status.py rewards [address] [--config <path>] [--wait-seconds 0]	Checking claimable imported_rewards and proof_rewards for an address, or auto-discovering prover_address from --config, OPENMATH_ENV_CONFIG, or the default config locations when omitted.
Query tx	python3 scripts/query_reward_status.py tx <txhash> [--wait-seconds 6]	After withdraw broadcast to confirm inclusion.

Withdraw is done with raw shentud tx bounty withdraw-rewards --keyring-backend os (see workflow above).

Notes

• Buckets: imported_rewards (theorem imported/referenced), proof_rewards (proofs verified). One withdraw pulls both if present.
• Mainnet: Default --chain-id shentu-2.2 --node https://rpc.shentu.org:443.
• Config override: Set OPENMATH_ENV_CONFIG=/path/to/openmath-env.json or use --config if you want a non-default config path.
• Requirements: Requires trusted local python3 and shentud on PATH.
• Env vars: OPENMATH_ENV_CONFIG, SHENTU_CHAIN_ID, and SHENTU_NODE_URL are optional overrides, not required for the default mainnet flow.
• Keyring: Always use --keyring-backend os for reward withdrawal commands generated from this skill.
• Trust boundary: Reward queries shell out to local shentud; withdrawals also sign through the local OS keyring. Verify the key name, resolved address, and RPC/node URL before broadcasting.

References

Load when needed (one level from this file):

• references/init-setup.md — Reward address discovery and withdraw-key setup.
• references/reward_claim_flow.md — Address-based buckets, withdraw behavior, and on-chain claim flow.

Identity setup for theorem submission still lives in openmath-submit-theorem, but reward querying itself does not require openmath-env.json.