Skip to content

Clarify portfolio note: complete bot, not an excerpt #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nullfox merged 1 commit into from
Jul 13, 2026
+4 −3
Merged

Clarify portfolio note: complete bot, not an excerpt #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,10 @@ The original use case — sniping a liquidity pool the instant it opens — is w
forced those problems into the open. That use case is described below, but it is
the *problem domain*, not the point. The point is the execution infrastructure.

> **Portfolio note.** This repo is a sanitized version of a bot I ran a few
> years ago, brought up to date as a portfolio piece. It ships no wallets, no
> keys, and no private configuration — only public contract addresses. The
> **Portfolio note.** This is the complete bot I ran a few years ago — not a
> partial excerpt — brought up to date as a portfolio piece with the live keys
> and private configuration stripped out. It ships no wallets, no keys, and no
> trading edge — only public contract addresses. The
> [`CHANGELOG`](./CHANGELOG.md) records the 2026 modernization pass, and the
> [Design Observations](#design-observations-gaps--risks) section is a candid
> account of what I'd keep, what I fixed, and what I'd still change.
Expand Down
Loading