860

publish-signal.sh always verifies TX against Base RPC, even when --chain is ethereum/polygon/solana

publish-signal.sh shell-injection / quoting break when reasoning or signal JSON contains single quotes

subscribe.sh does not enforce config.json risk.max_providers cap

auto-copy.sh: COPY_PCT chosen as min(provider_pct, my_max) but daily_loss_limit is never enforced

auto-copy.sh logs copy as 'amount_pct' but DAILY_SPENT sums 'usd_amount' — risk accounting is silently broken

Auto-copy risk limits are not enforced; daily loss calculation uses a non-existent field and no cutoff check

feed.sh injects $LIMIT into jq filter via shell concatenation — non-numeric LIMIT can break or inject

leaderboard.sh inherits same jq slice injection / silent parse-error swallow

publish-signal.sh assumes ENTRY_PRICE/AMOUNT_PCT are valid JSON numbers — passes via --argjson without validation

publish-signal.sh: TX verification only warns on failure, contradicting README guarantee

feed.sh dedupes/sorts incorrectly: passes raw post objects (no signal fields) but later jq tries to read .signal.*

publish-signal.sh ignores --chain for verification and only uses Base RPC; Solana/Ethereum/Polygon claims are misleading

Integration guide examples use quoted ~ which prevents tilde expansion, likely breaking paths

Docs and schema list Solana as a supported chain, but verification/auto-copy only implement EVM flows

auto-copy.sh grep on copy-log.jsonl is unanchored, can cross-match dates and inflate/deflate spend

auto-copy.sh constructs Bankr prompt with raw user-controlled provider data (token/chain/action), enabling prompt injection

Docs claim signals cannot be published for nonexistent trades, but publish-signal.sh allows unverified publishing

Fallback dependency to ~/clawd/scripts/with-secrets.sh is undocumented and likely absent

Approve transaction uses unlimited allowance (MAX_UINT256) without disclosure

Approve step skipped when approveTo is empty but ERC20 actually requires allowance

Wallet address is fetched only from Base balances; misleading for cross-chain calls

Script docstrings and usage mention .sh instead of .py, causing user invocation confusion

BNB Chain USDC listed as 18 decimals — likely incorrect for the canonical Binance-Peg USDC

fee.priceUsd assumed to be a multiplier of human fee amount; semantics likely wrong

format_units zfill off-by-one for amounts equal to 10^decimals

Unconditional unlimited ERC20 approve may revert on tokens requiring allowance reset to zero first (e.g., USDT)

to_smallest_units mishandles empty integer part and signs, producing wrong on-chain amounts

Ignores chainId returned by Symbiosis tx; submits using src_chain which may mismatch

Skill docs claim support for Bitcoin/TON/Tron flows that the provided scripts do not implement (no v2 deposit-flow, non-EVM source)

Network/JSON errors and missing-key cases are not handled; script may crash with stack traces

setup.sh swallows `gl identity new` failure mode documented in SKILL.md

API reference inconsistency: repo paths use {owner}/{name} but git smart-HTTP paths only use {name}

Webhook list endpoint documented as Signed, contradicting `webhook list` CLI usage and norm

README/SKILL.md describe bounty fee inconsistently with claim/submit/approve flow

HTTP Signatures example claims RFC 9421 but shows non-compliant header usage

setup.sh pipes remote install script to shell without verification

README install snippet presents a placeholder as an executable command

Inconsistent API base paths and owner scoping may confuse clients

Quick setup script does not verify presence of git dependency

Router SKILL.md links to non-existent opensea-swaps sub-skill

Wallet SKILL Quick start contradicts the documented hardening (omits PRIVY_AUTH_SIGNING_KEY)

SKILL env metadata for opensea-wallet omits variables required by referenced setup flows (Turnkey RPC URL, private-key envs, Privy auth signing key)

Marketplace API doc claims 'API returns order data to sign' but the documented POST is the submit endpoint

Workflow: Selling an NFT documents a non-existent two-POST flow

REST API reference omits required protocol_address query parameter for order-by-hash endpoint

Marketplace order creation docs contradict themselves about unsigned vs signed requests and a two-POST flow

Example imports use a nonstandard zod path (`zod/v4`) likely to break consumers

policy-administration.md references `packages/skill/...` paths that don't match the repo layout used by SKILL.md

Conflicting auto-detect order between SKILL.md text and env var docs

Broken intra-repo paths in policy-administration.md (packages/skill/… paths don’t exist here)