YieldVault Agent

Autonomous yield farming agent for BNB Chain with deterministic execution, smart contract integration, and automated decision-making.

Security Scan

The skill's code and runtime instructions match an autonomous yield‑farming agent, but registry metadata and install declarations omit required credentials and environment data (wallet keys, RPC endpoints, Telegram token) and there are other inconsistencies that warrant review before use.

Purpose & Capability

The skill legitimately needs RPC endpoints, a signing wallet (private key or hardware wallet), and notification credentials (Telegram bot token/chat id) to perform on‑chain transactions and alerts. However the registry metadata declares no required env vars/primary credential and no required binaries, which is inconsistent with the code (tx-executor, scheduler, notifications) that signs and broadcasts transactions and calls external APIs.

Instruction Scope

SKILL.md instructs running npm, deploying contracts, copying config.deployed.json to .env.local and editing RPC/contract addresses and starting scheduler.js. It claims 'no hardcoded private keys (use environment variables)' but does not list which env vars must be set. The runtime instructions and included files (tx-executor.js, scheduler.js, notifications.js) will read secrets/config and perform network I/O and blockchain transactions — this is within the stated purpose, but the instructions are vague about exact secret names and do not align with the metadata's 'no required env vars'.

Install Mechanism

There is no explicit install spec, which keeps install risk low, but the package includes many code files, artifacts, and package-lock files and instructs to run npm install in the contracts directory. That means executing third‑party code locally. No external download URLs or URL shortcut patterns were observed in the provided SKILL.md, but running the code will execute network calls and may install packages declared in package.json/package-lock.json — inspect those before running.

Credentials

The skill requires high‑value secrets in practice (wallet private key or hardware wallet access, RPC endpoint, Telegram bot token, possibly keeper/keeperAddress credentials) to function. The registry says 'Required env vars: none' and 'Primary credential: none', which is not proportional to the actions the code performs (sign & broadcast transactions). This mismatch is a significant omission and increases risk of accidental secret exposure if the user doesn't carefully supply/store credentials.

Persistence & Privilege

The skill is not marked always:true and does not request system‑wide persistence in metadata. It runs a scheduler to autonomously invoke decisions and execute transactions when started — autonomy is expected for this use case. There is no indication it modifies other skills or global agent configuration.

Scan Findings in Context

[base64-block] unexpected: The prompt scanner detected a 'base64-block' pattern in SKILL.md content. Base64 blocks in documentation or runtime instructions can be benign (embedded examples) but can also be used for hidden payloads or prompt injection. The SKILL.md content shown does not obviously include a base64 payload, so you should search the full repository for base64 strings and inspect their purpose before running code.

What to consider before installing

This skill contains the expected components for an autonomous on‑chain yield‑farming agent (decision engine, blockchain reader, tx executor, scheduler, Telegram alerts) and will need credentials and network endpoints to operate — but the registry metadata does not declare them. Before installing or running: - Do NOT run scheduler/tx-executor on mainnet or with real funds until you audit the code. Run everything offline or on a throwaway testnet account first. - Inspect package.json and package-lock.json to see what NPM packages will be installed. Audit dependencies and lockfile for unexpected packages or remote install scripts. - Grep the repository for process.env usage and for strings like PRIVATE_KEY, WALLET, TELEGRAM_TOKEN, BOT_TOKEN, RPC_URL, KEEPER_ADDRESS. Confirm exactly which env vars the code reads and how they are used. - Open tx-executor.js and scheduler.js and confirm where private key material is loaded and used. Prefer hardware wallet or KMS integration rather than a plaintext private key in env or config. If the code expects an env var for a raw private key, treat that as high risk. - Inspect notifications.js to confirm it only sends alerts to the configured Telegram API and does not exfiltrate data to unknown endpoints. Search for any hardcoded URLs, IPs, or base64 blobs in all files. - Verify contract addresses and ABI files are from trusted sources; artifacts can embed sensitive data or keys in rare cases. - Check INTEGRATION_GUIDE and config files to see whether any example configs include private keys; never use those directly. - If you plan to run on mainnet, require: hardware wallet/multi‑sig signing, Chainlink oracles as recommended, a formal smart contract audit, emergency pause mechanism, and minimal initial capital. Given the clear metadata/code mismatch (no declared required env vars vs code that needs secrets) and the pre-scan base64 indicator, proceed cautiously — treat this skill as 'suspicious' until you confirm how it handles secrets and network endpoints.

Autonomous yield farming agent for BNB Chain with deterministic execution, smart contract integration, and automated decision-making.

Features

• Deterministic Decision Engine - Same input always produces same output (auditable)
• Smart Contract Integration - Interact with YieldVault contracts on BNB testnet/mainnet
• Autonomous Scheduler - Run farming decisions hourly without manual intervention
• Transaction Executor - Automatic DEPOSIT, WITHDRAW, HARVEST, COMPOUND, REBALANCE actions
• Telegram Alerts - Real-time notifications for executions, APR changes, and errors
• Risk Management - Conservative risk filtering (only vaults with risk_score ≤ 0.5)
• Yield Optimization - Net APR calculation (apr - fees - risk_penalty)

Installation

clawhub install yieldvault-agent

Quick Start

1. Configure

cp config.deployed.json .env.local
# Edit with your contract addresses and RPC endpoint

2. Deploy Contracts (if needed)

cd contracts
npm install
npm run deploy:testnet

3. Run Tests

npm test                    # Unit tests
node test.live.mock.js      # Integration tests (offline)
node test.live.js           # Live testnet tests

4. Start Scheduler

node scheduler.js
# Runs decision cycle every hour against testnet

5. Monitor Alerts

Telegram notifications sent automatically for:

• Execution started (vault_id, action, amount)
• APR changes (>1% delta)
• Errors (with severity level)
• Cycle completion (stats summary)

Architecture

Smart Contracts (BNB Testnet/Mainnet)
    ↓
BlockchainReader (live vault data)
    ↓
YieldFarmingAgent (deterministic decisions)
    ↓
TransactionExecutor (sign & broadcast)
    ↓
Scheduler (hourly automation)
    ↓
Notifications (Telegram alerts)

Configuration

Edit config.scheduler.json:

{
  "chainId": 97,
  "interval_minutes": 60,
  "harvest_threshold_usd": 25,
  "rebalance_apr_delta": 0.02,
  "max_allocation_percent": 0.35,
  "risk_score_threshold": 0.5
}

Decision Logic

1. Read current vault state (APR, TVL, user balance)

2. Calculate Net APR = apr - fees - (risk_score × 0.10)

3. Filter vaults with risk_score ≤ 0.5

4. Select vault with highest Net APR

5. Decide action:

   • HARVEST if pending_rewards ≥ $25 USD
   • COMPOUND if net_apr ≥ 2% delta
   • REBALANCE if another vault beats current by ≥ 2%
   • NOOP if already optimized

6. Execute transaction (with retry logic)

7. Log execution record (SHA256 auditable)

Supported Networks

• Testnet: BNB Chain Testnet (chainId: 97)
• Mainnet: BNB Chain Mainnet (chainId: 56)

Security

• ✅ Deterministic execution (reproducible, auditable)
• ✅ SHA256 audit trail for every decision
• ✅ Risk filtering (conservative)
• ✅ Constraint enforcement (max 35% per vault)
• ✅ Retry logic with exponential backoff
• ✅ No hardcoded private keys (use environment variables)

Production Readiness

For mainnet deployment, add:

1. Chainlink Oracle - Live APR feeds
2. Hardware Wallet Support - Ledger/Trezor signing
3. Smart Contract Audit - Professional security review
4. Emergency Pause - Multi-sig pause mechanism

See FINAL_CHECKLIST.md for complete production requirements.

Documentation

• README.md - Full user guide
• SKILL.md - This file
• FINAL_CHECKLIST.md - Production requirements
• INTEGRATION_GUIDE.md - Smart contract integration
• EXAMPLES.md - Usage examples
• RESPUESTAS_PREGUNTAS.md - FAQ & architecture

Support

Issues & PRs welcome: https://github.com/open-web-academy/yieldvault-agent-bnb

License

MIT