curve-gauge-yield-trader

name	curve-gauge-yield-trader
description	Multi-chain Curve gauge yield trading skill with paper-first defaults. Supports local wallet generation or Ledger signer mode for live execution.

Curve Gauge Yield Trader

For Claude: How to Use This Skill

Skill instructions are preloaded in context when this skill is active. Do not perform filesystem searches or tool-driven exploration to rediscover them; use the guidance below directly.

Windows / Seren Desktop Python Runtime

Seren Desktop bundles Python on Windows and prepends the bundled runtime to child-process PATH. When running from Seren Desktop on Windows, use the documented python3 ... commands as written; they resolve to Seren Desktop's bundled python3.exe even when system Python is not installed. Do not translate python3 to python, do not invoke the Microsoft Store Python stub, and do not ask the user to install system Python just to run this skill from Seren Desktop. If a snippet includes Unix virtualenv activation such as source .venv/bin/activate, skip that prefix inside Windows Desktop and run the same command beginning with python3 .... Outside Seren Desktop, use an installed Python 3.11+ interpreter or a project .venv.

When to Use

• find the best curve gauge rewards
• paper trade curve gauge liquidity
• trade live on curve gauges

On Invoke

Immediately run a dry-run gauge scan and trade simulation without asking. Do not present a menu of modes. Execute:

cd ~/.config/seren/skills/curve-gauge-yield-trader && source .venv/bin/activate && python3 scripts/agent.py --config config.json

Display the full dry-run results to the user. Only after results are displayed, present available next steps (live mode). If the user explicitly requests a specific mode in their invocation message, run that mode instead.

Workflow Summary

1. fetch_top_gauges uses connector.curve_api.get (/getGauges)
2. choose_trade uses transform.select_best_gauge
3. signer_setup uses transform.setup_signer
4. rpc_discovery resolves chain RPC publisher from gateway catalog (GET /publishers)
5. preflight builds and estimates local EVM transactions via chain RPC (no cloud signer)
6. live_guard uses transform.guard_live_execution
7. execute_liquidity_trade signs locally and submits with eth_sendRawTransaction

Funding and Safety

• Default mode is dry-run.
• Live transactions require both:
  • inputs.live_mode = true in config
  • --yes-live on the CLI
• Live mode uses real funds. Only fund what you can afford to lose.
• Each run resolves the RPC publisher from the live Seren publisher catalog (GET /publishers) and performs an explicit probe before preflight/trade.
  • If probe fails, execution stops early with a clear unsupported-chain/RPC error.
• Optional override: set rpc_publishers in config ({ "ethereum": "<slug>" }) to force a specific publisher slug per chain.
• Transactions are prepared and signed locally for live mode.
  • wallet_mode=local: agent signs with local private key after --yes-live.
  • wallet_mode=ledger: preflight creates unsigned txs; you provide signed raw txs in evm_execution.ledger.signed_raw_transactions for broadcast.
  • Dry-run uses a synthetic simulation address and does not require a local wallet file.

Disclaimer

This skill can trade real money. Use at your own risk. Past performance does not guarantee future results.

• DeFi carries smart-contract, oracle, liquidity, and slippage risks.
• RPC/provider outages or stale data can cause failed or unfavorable execution.
• You are responsible for wallet security, transaction approvals, and chain/network selection.
• Start in dry-run, test with small live size, and scale only after repeated stable runs.

Wallet Modes

• wallet_mode=local: for live mode, generate a local wallet with --init-wallet, then fund that address.
• wallet_mode=ledger: provide Ledger address and use preflight output to sign externally.

Local Execution Config

• Default strategy is evm_execution.strategy = "gauge_stake_lp".
  • Requires lp_token_address and lp_amount_wei if they cannot be derived from market data.
  • Optional gauge_address override.
• For fully custom calls, use evm_execution.strategy = "custom_tx" and set:
  • evm_execution.custom_tx.to
  • evm_execution.custom_tx.data
  • evm_execution.custom_tx.value_wei
• Gas behavior is controlled with:
  • evm_execution.tx.gas_price_multiplier
  • evm_execution.tx.gas_limit_multiplier
  • evm_execution.tx.fallback_gas_limit

Trade Execution Contract

When the user says sell, close, exit, unwind, or flatten, treat that as an immediate operator instruction to stop trading and prepare the LP or gauge withdrawal path. If the user did not identify which chain or signer should be used, ask only the minimum clarifying question needed to identify it.

Pre-Trade Checklist

Before any live execution:

1. Verify SEREN_API_KEY is loaded and the configured RPC publisher is reachable.
2. Verify signer dependencies are installed and loaded: eth-account for local signing, or a valid ledger address for ledger mode.
3. Verify eth-abi and eth-utils are installed when local EVM encoding is required.
4. If any credential, library, signer, or RPC probe fails, stop here and fail closed instead of submitting transactions.

Dependency Validation

Dependency validation is required before live trading. Verify SEREN_API_KEY, the resolved RPC publisher, eth-account, eth-abi, eth-utils, and the selected signer inputs are installed and loaded. If a credential is missing, the RPC path is unsupported, or a required library is not installed, the runtime must stop with an error instead of submitting transactions.

Emergency Exit Path

To stop trading immediately, run python scripts/agent.py --config config.json --unwind-all. The unwind-all path syncs the tracked LP and gauge position, marks the position for liquidation, and returns the exact onchain addresses needed to unwind without placing a new entry order.

Quick Start

1. Create/get your SEREN_API_KEY by following https://docs.serendb.com/skills.md, then set it in your environment (for example: export SEREN_API_KEY=...).
2. Copy config.example.json to config.json.
3. Install dependencies:
   • pip install -r requirements.txt
4. Generate local wallet (optional for dry-run; required before live local signing):
   • python scripts/agent.py --init-wallet --wallet-path state/wallet.local.json
5. Dry-run preflight:
   • python scripts/agent.py --config config.json
6. Live mode (only after funding and signer validation):
   • set inputs.live_mode=true in config
   • python scripts/agent.py --config config.json --yes-live

Seren-Cron Integration

Use seren-cron to run this skill on a schedule — no terminal windows to keep open, no daemons, no permanent computer changes required. Seren-cron is a cloud scheduler that calls your local trigger server on a cron schedule.

Each scheduled run executes one full cycle: sync positions, fetch top gauges, build local preflight txs, and execute if live mode is enabled and --yes-live is set on the server process.

Requirements: Seren Desktop login or a valid SEREN_API_KEY.

Step 1 — Check seren-cron is available

Before scheduling, verify the publisher is reachable using mcp__seren__call_publisher:

publisher: seren-cron
path:      /health
method:    GET

If this call fails, stop here and tell the user:

"The seren-cron service could not be reached. Please send this error to [e-mail] for support."

Step 2 — Review active cron jobs (always do this first)

Always check for existing scheduled jobs before creating a new one. A user may have forgotten a live job is already running.

publisher: seren-cron
path:      /jobs
method:    GET

If jobs for this skill already exist, show them to the user and ask:

"You have [N] active cron job(s) for this skill. Would you like to:

1. Keep them running (recommended if intentional)
2. Stop all and create a new schedule
3. Cancel"

Do not create a duplicate cron job without explicit user confirmation.

Step 3 — Start the local trigger server

Start the webhook server that seren-cron will call on each scheduled tick:

SEREN_API_KEY="$SEREN_API_KEY" python3 scripts/run_agent_server.py --config config.json --port 8080

This process runs in your terminal session. When you close the terminal, it stops — that is expected and correct. Seren-cron handles the scheduling; your local server handles execution.

Step 4 — Create the cron schedule

With the server running, create the scheduled job:

publisher: seren-cron
path:      /jobs
method:    POST
body: {
  "name":            "curve-gauge-yield-trader-live",
  "url":             "http://localhost:8080/run",
  "method":          "POST",
  "cron_expression": "*/30 * * * *",
  "timezone":        "UTC",
  "enabled":         true,
  "timeout_seconds": 60
}

Save the returned job_id — you need it to pause, resume, or delete the job later.

Step 5 — Manage the schedule

List all active jobs:

publisher: seren-cron, path: /jobs, method: GET

Pause:

publisher: seren-cron, path: /jobs/{job_id}/pause, method: POST

Resume:

publisher: seren-cron, path: /jobs/{job_id}/resume, method: POST

Stop permanently:

publisher: seren-cron, path: /jobs/{job_id}, method: DELETE

Insufficient Funds Guard

If a live trade or cycle fails because the trading balance or SerenBucks balance is too low to execute, immediately pause the cron job:

publisher: seren-cron, path: /jobs/{job_id}/pause, method: POST

Then tell the user:

"Automated trading has been paused: insufficient funds detected. Please top up your balance before resuming the schedule."

Never allow the cron to keep firing when there are no funds available to trade.