Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
Improve Security strategy skill release
What This Skill Does
Runs a participant bot for the openfunderse protocol that proposes, validates, and submits AllocationClaimV1 to a relayer. Supports manual allocation submission via Telegram slash commands and an autonomous daemon mode that reads live market signals and submits claims on a timer. Operates within the OpenClaw runtime using EIP-191 signature authentication.
The built-in daemon mode with three selectable strategies automates per-epoch allocation submissions based on live NadFun testnet signals, removing the need for manual intervention each round.
When to use it
- Submitting allocation weight proposals for a specific fund epoch
- Running an automated allocation daemon using momentum, graduation-proximity, or impact-aware strategies
- Dry-run validating an allocation claim before committing it to the relayer
- Depositing or withdrawing assets from a vault using Telegram slash commands
- Rotating a participant signer key without touching treasury or admin keys
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Submit allocation for fund 'demo-fund' epoch 3 with weights 7000, 3000
- 1Resolves runtime env from /home/ubuntu/.openclaw/openclaw.json
- 2Calls propose_allocation with fundId, epochId, and targetWeights [7000, 3000]
- 3Validates AllocationClaimV1 schema and checks weights are non-negative integers with sum greater than 0
- 4Verifies canonical claim hash and checks relayer host against PARTICIPANT_TRUSTED_RELAYER_HOSTS
- 5Submits claim to POST /api/v1/funds/{fundId}/claims when the submit gate is satisfied
AllocationClaimV1 accepted by relayer with confirmation response
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.