feat: initial commit

Author: johnnyonline

.claude/CLAUDE.md

@@ -0,0 +1,59 @@
+# Dutch Taker Bot
+
+A Silverback bot that automatically takes (executes) flex dutch auctions on the blockchain.
+
+## Tech Stack
+
+- **Framework**: [Silverback SDK](https://docs.apeworx.io/silverback/stable)
+- **Blockchain**: [Ape Framework](https://docs.apeworx.io/ape/stable)
+- **Python**: 3.12+
+- **Package Manager**: uv
+
+## Project Structure
+
+```
+dutch-taker/
+├── bot/
+│   ├── __init__.py
+│   ├── bot.py           # Main bot logic
+│   ├── config.py        # Network config, addresses
+│   └── tg.py            # Telegram notifications
+├── .claude/
+│   ├── CLAUDE.md
+│   └── skills/
+├── pyproject.toml
+└── README.md
+```
+
+## Development Guidelines
+
+### Principles
+
+- **DRY** - Don't Repeat Yourself
+- **KISS** - Keep It Simple, Stupid
+- **Clean Code** - Self-documenting, minimal comments
+- **Single Responsibility** - Each function does one thing well
+- **Fail Fast** - Validate early, raise exceptions clearly
+
+### Code Style
+
+- Super clean and minimalistic
+- Format: `ruff format .`
+- Lint: `ruff check .`
+- Type check: `mypy bot`
+- Line length: 120 characters
+- No unnecessary abstractions
+- No premature optimization
+
+### Risk Management
+
+- Never hardcode secrets - use environment variables
+- Implement configurable limits
+- Use `CircuitBreaker` for emergency stops
+- Test with print debugging before enabling transactions
+
+## Running
+
+```bash
+silverback run --network ethereum:mainnet
+```

.claude/skills/writing-bots.md

@@ -0,0 +1,93 @@
+---
+name: writing-bots
+description: Write a bot to continuously listen and respond to events on a public blockchain network.
+compatibility: Requires uv installed
+---
+
+This skill describes when and how to a bot using the Silverback SDK.
+
+The user provides operational requirements such as which blockchain network they want it to run on,
+which smart contracts they want to interact with, what types of actions they want to take.
+They may provide additional context about technical constraints, or scenarios it must avoid.
+
+## Using This Skill
+
+**CRITICAL**: Before writing any Silverback bot code, you MUST:
+1. Use `web_fetch` to retrieve the latest documentation from https://docs.apeworx.io/silverback/stable
+2. Specifically fetch relevant pages like:
+   - Development guide: https://docs.apeworx.io/silverback/stable/userguides/development
+   - API reference: https://docs.apeworx.io/silverback/stable/methoddocs
+
+**DO NOT** rely on general knowledge about Silverback - always fetch the current documentation first to ensure accuracy.
+
+## Designing a Bot
+
+Before writing the bot, understand the types of actions you want to perform,
+and which on-chain or off-chain events you might want to monitor in order to trigger them
+- **New Block**: Do you want to perform an action on every block?
+- **Event Log**: Do you want to perform an action when a smart contract emits a particular event?
+- **Cron Job**: Do you want to perform an action on a time-based interval?
+- **Metrics**: Do you want to perform an action when a [metric](#defining-metrics) meets certain conditions?
+
+**CRITICAL**: Have a good understanding of the requirements first before proceeding to write any code.
+
+Then implement event handlers, which are callbacks implemented that trigger logic which might:
+- send a message on Telegram or Discord to a group or channel
+- send a social media post on X or Farcaster
+- send a POST request to another backend service
+- sign and broadcast a transaction on the listening chain and/or other blockchain(s)
+- measure a simple or derived [Metric](#defining-metrics)
+- provision a product or service
+
+### Defining Metrics
+
+In order to have visibility into the operation of the bot,
+it is often useful to define key "Metrics" or signal values that you can monitor over time to understand the real-world operation of the bot.
+This can also be very useful for monitoring purposes, but Silverback also lets you define event triggers based on the value of the metric.
+For example, if you've defined a complex metric based on the amount of trading volume occuring on a particular decentralized exchange pool in the latest block,
+you might want to trigger an action to occur when that volume signal is above or below a certain threshold.
+This can create more complex, reactive behaviors beyond what basic blockchain events can tell you.
+
+## Maintaining State
+
+Sometimes the actions you want to take in a bot depends on the results of other actions,
+so it is useful to maintain some internal state to track those results.
+Use internal state sparingly, and try to rely as much as you can on the blockchain state,
+or the state of other external services you've integrated the bot with in order to make correct decisions.
+
+## Managing Risk
+
+Overall, bots can do potentially risky actions and may end up being a part of critical user infrastructure.
+It is best to advise them on proceeding slowly and verifying the correctness of their implementation in stages,
+before more drastic steps like adding a signer to submit transactions or giving it access to a critical communications channel.
+You can easily do this through `print` debugging at first,
+or build-in operational modes based on the presence of a specific environment variable such as the availability of an API key,
+whether the `bot.signer` is configured, or based on other on-chain information like account balances.
+
+Also, you should suggest things like adding configurable limits (using environment variables via `os.environ`),
+emergency stop conditions (raising the `silverback.CircuitBreaker` exception), or others ways to effectively manage risk.
+
+## Running the Bot
+
+Only after the user thinks that the bot seems well-written and ready for testing should you install silverback and run it.
+
+To install silverback, run the following command with `uv` installed:
+
+```bash
+$ uv tool install silverback
+```
+
+This will make the `silverback` cli command available.
+You can then run the bot on the `ecosystem` and `network` they want (such as "ethereum:mainnet") using:
+
+```bash
+$ silverback run --network <ecosystem>:<network>
+```
+
+You can make the bot shutdown manually via ctrl+C, or sending the SHUTDOWN or KILL signal to the process.
+
+Monitor the bot's operations via it's logs and try to resolve errors until they rarely happen.
+Silverback can handle the occasional error, so you can't figure out exactly why something is failing,
+it could be okay to continue testing with.
+
+Ask the user to monitor their bot as well via the logs, and then ask if they like how the bot is working.

.env.example

@@ -0,0 +1,7 @@
+TAKER_PRIVATE_KEY=""
+BOT_ACCESS_TOKEN=""
+GROUP_CHAT_ID=""
+ERROR_GROUP_CHAT_ID=""
+ETHERSCAN_API_KEY=""
+ETH_RPC_URL=""
+ETH_WS_URL=""

.github/workflows/ci.yml

@@ -0,0 +1,46 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  check-code:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v3
+
+      - name: Set up Python
+        uses: actions/setup-python@v4
+        with:
+          python-version: "3.12"
+
+      - name: Install uv
+        run: |
+          curl -Ls https://astral.sh/uv/install.sh | sh
+          echo "$HOME/.cargo/bin" >> $GITHUB_PATH
+
+      - name: Set up project
+        run: |
+          uv venv
+          source .venv/bin/activate
+          uv sync
+
+      - name: Run Ruff format check
+        run: |
+          source .venv/bin/activate
+          ruff format . --check
+
+      - name: Run Ruff linter
+        run: |
+          source .venv/bin/activate
+          ruff check .
+
+      - name: Run mypy
+        run: |
+          source .venv/bin/activate
+          mypy bot

.gitignore

@@ -0,0 +1,57 @@
+# Python cache files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# Distribution/packaging
+dist/
+build/
+*.egg-info/
+
+# Virtual environments
+venv/
+env/
+.env/
+.venv/
+
+# IDE settings
+.vscode/
+.idea/
+*.swp
+*.swo
+
+# Testing
+.pytest_cache/
+.coverage
+htmlcov/
+
+# Local development settings
+.env
+.env.local
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# Logs
+*.log
+
+# Type checking
+.mypy_cache/
+
+# Editor configs
+.cursorrules
+
+# Cache files
+cache-id.txt
+*.cache
+.uv/
+.ruff_cache
+.DS_Store
+
+# Ape stuff
+.build/
+.silverback-images/
+.silverback-sessions/
+
+# Local storage
+bot_state.json

Dockerfile

@@ -0,0 +1,18 @@
+FROM python:3.12
+
+WORKDIR /app
+
+# Copy source
+COPY . .
+
+# Install deps
+RUN pip install uv && uv sync --no-dev --no-cache
+
+# Fix shebang
+RUN sed -i '1 s|^#!.*python3$|#!/app/.venv/bin/python3|' /app/.venv/bin/silverback
+
+# Ensure the project venv is on PATH so 'silverback' is found
+ENV PATH="/app/.venv/bin:${PATH}"
+
+# Default entrypoint, compose will pass rest of the args
+ENTRYPOINT ["silverback"]

README.md

@@ -0,0 +1,72 @@
+# dutch-taker
+
+<p align="center">
+  <img src="assets/pfp.jpg" alt="Flex Silverback" width="700" height="500"/>
+</p>
+
+## Installation
+
+1. **Clone the repository**
+   ```bash
+   git clone https://github.com/flexmeow/dutch-taker.git
+   cd dutch-taker
+   ```
+
+2. **Set up virtual environment**
+   ```bash
+   uv venv
+   source .venv/bin/activate  # On Windows: .venv\Scripts\activate
+   ```
+
+3. **Install dependencies**
+   ```bash
+   # Install all dependencies
+   uv sync
+   ```
+
+   > Note: This project uses [uv](https://github.com/astral-sh/uv) for faster dependency installation. If you don't have uv installed, you can install it with `pip install uv` or follow the [installation instructions](https://github.com/astral-sh/uv#installation).
+
+4. **Environment setup**
+   ```bash
+   cp .env.example .env
+   # Edit .env with your API keys and configuration
+
+   # Load environment variables into your shell session
+   export $(grep -v '^#' .env | xargs)
+   ```
+
+## Usage
+
+Run:
+```shell
+silverback run --network :mainnet
+```
+
+Run using docker compose:
+```shell
+docker compose up --build
+```
+
+Stop docker compose:
+```shell
+docker compose down
+```
+
+## Code Style
+
+Format and lint code with ruff:
+```bash
+# Format code
+ruff format .
+
+# Lint code
+ruff check .
+
+# Fix fixable lint issues
+ruff check --fix .
+```
+
+Type checking with mypy:
+```bash
+mypy bot
+```

ape-config.yaml

@@ -0,0 +1,5 @@
+node:
+  ethereum:
+    mainnet:
+      uri: "${ETH_RPC_URL}"
+      ws_uri: "${ETH_WS_URL}"

assets/pfp.jpg

@@ -0,0 +1 @@
+from .bot import bot as bot