Powerloom BDS — Uniswap V3 (ClawHub skill)

Autonomous Uniswap V3 monitoring + onchain provenance verification, in minutes. Decentralized data, not trust-me data.

Every data point this skill fetches is finalized onchain by Powerloom's decentralized sequencer-validator network. The verify_data_provenance tool compares API CIDs to onchain commitments so alerts can carry a cryptographic receipt, not a vendor's word.

Recipes

• Whale Radar — USD-threshold alerts: bds_mpp_snapshot_trades_pool_address for each pool in poll_fallback_pools. For cron / OpenClaw heartbeats over all pools in one bounded batch, use node scripts/whale-cron.mjs (bds_mpp_snapshot_allTrades + pool metadata).
• Token-Flow — all swaps touching a configured token (default USDC) across pools derived at runtime.
• Threshold Guard — bracket alerts from premium tokenPrices (threshold-guard.mjs); live swaps via bds-agent guard run.
• Autonomous DeFi Analyst — default multi-pool bds_mpp_snapshot_allTrades + all-pools token volume; set filters.scope: single_pool in recipes/defi-analyst.yaml for single-pool snapshots only.

Integrators (OpenClaw, cron)

End-to-end one-shot prompts — pick by onboarding state:

Variant	Use when	Reference
Free-key cron	You already have sk_live_... from bds-agent signup (2 free credits, no wallet)	references/09-openclaw-one-shot-free-key.md
Pay-signup + cron	You want autonomous wallet-funded onboarding for a 10-credit plan in the same prompt	references/08-openclaw-one-shot.md

Default behavior: whale-radar.mjs, token-flow.mjs, and defi-analyst.mjs each run one bounded round and exit (safe for cron). Use --daemon only if you want a local repeat loop (heartbeat.interval_seconds between rounds).

For scheduled heartbeats, prefer whale-cron.mjs (exits) or the recipe scripts without --daemon. This repo does not ship streaming trade consumption.

Setup

cd powerloom-bds-univ3
npm install
export POWERLOOM_API_KEY=sk_live_...
node scripts/ensure-credits.mjs

Where to get POWERLOOM_API_KEY:

• Free (no wallet, 2 credits): bds-agent signup — browser device flow on the metering service. Same sk_live_... works against this skill, the hosted MCP server, and any pay-signup top-up later.
• Wallet-funded (10-credit plan): node scripts/signup-pay.mjs --dry-run (quote summary only), then node scripts/signup-pay.mjs --yes once after verifying stderr output — prefer argv over env so confirmation bypass is not persisted in OpenClaw skill config. CI may use POWERLOOM_SIGNUP_PAY_CONFIRM=yes for a single invocation only. Native or ERC-20 per quote.payment_kind (POWER CGT on 7869 = native).
• More credits, existing key: node scripts/credits-topup.mjs — same --dry-run → --yes pattern (or one-shot env for CI only). See SKILL.md.

Optional: POWERLOOM_TELEGRAM_BOT_TOKEN, POWERLOOM_TELEGRAM_CHAT_ID, and dispatch.channel: telegram in recipes/*.yaml.

Links (metering service)

One deploy (npm run build + npm start on bds-agenthub-billing-metering) serves both:

• Agent signup (CLI / API) — origin only: bds-metering.powerloom.io (BDS_AGENT_SIGNUP_URL / bds-agent signup --base-url …).

• Browser signup + billing UI — bds-metering.powerloom.io/metering

• Hosted MCP SSE: https://bds-mcp.powerloom.io/sse

Naming (ClawHub skill vs MCP tools)

What	Name
ClawHub / OpenClaw skill folder & slug	powerloom-bds-univ3
MCP tools on the hosted server	bds_mpp_*, get_credit_balance, verify_data_provenance — there is no tool named bds_univ3.

To print the live tool list from the API (same handshake as callTool):

export POWERLOOM_API_KEY=sk_live_...
node scripts/list-mcp-tools.mjs

Test locally (without publishing to ClawHub)

Publishing is optional for trying the scripts and SKILL.md instructions:

1. Scripts only — From this directory, with POWERLOOM_API_KEY set, run node scripts/ensure-credits.mjs, node scripts/list-mcp-tools.mjs (proves tool names), node scripts/powerloom-mcp-client.mjs get_credit_balance '{}', or a recipe (whale-radar.mjs, etc.). That validates MCP wiring end-to-end against the hosted server.

2. OpenClaw / ClawHub — If skills list and the dashboard show powerloom-bds-univ3 as ready, the skill is on disk and registered. That is not the same as “the main chat always loads SKILL.md into the model on every turn.” If chat still acts blind, check your OpenClaw agent actually uses that skill (per-agent skill selection / defaults), then new session after changes. The reliable execution path is still node scripts/… with POWERLOOM_API_KEY; chat is best-effort unless you also wire BDS MCP for tools in the tool list.

   • Registry: clawhub install powerloom-bds-univ3 only pulls published builds. Local dev: copy this repo’s root into …/workspace/skills/powerloom-bds-univ3/ with SKILL.md at the folder root, set POWERLOOM_API_KEY in openclaw.json skill entries, restart the gateway.
   • Compose / OPENCLAW_WORKSPACE_DIR: The stack usually reads a .env file next to docker-compose.yml. Docker Compose substitutes ${OPENCLAW_WORKSPACE_DIR} from: that .env file, or exported variables in the shell you run docker compose from, or a .env override your vendor documents. It is not magic — if unset, the mount line can be wrong or empty. Set it to the host path that should map to …/workspace in the container (often your user’s …/.openclaw/workspace as an absolute path). Check docker compose config to see the resolved value.

   Docker bind mounts, ENOENT, symlinks, UI quirks: references/06-troubleshooting.md.

3. After publish — clawhub install powerloom-bds-univ3 (or the slug you published).

Publish (maintainers)

npx clawhub login
npx clawhub publish . --slug powerloom-bds-univ3 --version 0.1.0

Repository

Source: github.com/powerloom/powerloom-bds-univ3 (mirror this folder into that org repo).