MaxPane

Terminal dashboards for onchain games, NFT collections, and trading on Base, Abstract, and Ethereum.

Track leaderboards, signals, trends, and analytics for onchain projects — all from your terminal.

Every dashboard is read-only and keyless: public RPCs and public APIs only, no API keys of any kind, no wallet, no signing, no transactions.

Dashboards

FWA — Fake World Assets

A gachapon machine for NFTs. Depositors list an NFT with committed ETH backing; that backing sets an inverse draw weight — the cheaper the position, the more likely it is drawn — and simultaneously funds an irrevocable standing bid. A purchaser pays one price for one Chainlink-VRF-selected random position, then chooses, after seeing what they drew: keep the NFT, or take 85% of its backing.

The dashboard takes the purchaser's seat and answers one question continuously:

Is a pull worth it right now?

Everything on screen either feeds that number or explains it. The flagship figure is a band, not a point: keyless floor prices cover 26 of the 38 collections holding live positions, but those 26 account for only about a fifth of the draw weight, so roughly 79.6% of what you are actually likely to draw has no keyless floor. A single confident EV number would be a lie that costs someone ETH, so the band ships with an inseparable coverage badge. The harmonic-vs-arithmetic backing gap — the protocol in one number — is computed live at the current block and never printed as a constant.

Surfboard — surfsurf.eth

The onchain experiments of the FrenPet dev, watched from the front-runner's seat. He announces by sending UTF-8 calldata to himself — a channel that emits no logs at all, so every event-driven watcher is structurally blind to it and a nonce poll sees a post within one refresh interval. That asymmetry is the whole point of the dashboard.

Six detectors answer one question continuously:

Did something just happen in the surfsurf universe — and how early am I?

New post · LP migration · identity gate · new deploy · bridge staging · burn. Each renders state · age · one-line detail, and a detector only re-fires on a new event: baselines advance on the successful read that detected the last one, and never on a failed read — an outage cannot fire a burn or un-fire a migration.

The NFT floor is shown as n/a — no keyless source, not estimated. There is no keyless floor feed for this collection, and a made-up number on a dashboard people trade against is worse than an honest gap.

Install

pipx (recommended)

pipx install maxpane

uv

uv tool install maxpane

pip

pip install maxpane

Requires Python 3.11+

Full install (with Matrix intro sequence)

The full experience includes a Rust-powered Matrix-inspired intro animation. This requires Rust in addition to Python.

git clone https://github.com/banse/maxpane.git
cd maxpane

# Build the intro binary
cd maxpane && cargo build --release && cd ..

# Install the Python dashboard
pip install -e .

# Run with intro
./maxpane/target/release/maxpane && maxpane

Or add an alias to your shell config (~/.zshrc or ~/.bashrc):

alias maxpane='~/path/to/maxpane/maxpane/target/release/maxpane && command maxpane'

Usage

maxpane                        # launch dashboard (default: fwa)
maxpane --game fwa             # start on Fake World Assets view
maxpane --game base            # start on Base trading view
maxpane --game frenpet         # start on FrenPet view
maxpane --game cattown         # start on Cat Town view
maxpane --game ttt             # start on Ten Thousand Tokens view
maxpane --game talismans       # start on Talismans view
maxpane --game surf            # start on surfsurf.eth Surfboard view
maxpane --theme minimal        # use minimal theme
maxpane --poll-interval 60     # poll every 60s instead of 30s
maxpane --font-size 12         # smaller font = more columns (see below)
maxpane --font-size 0          # leave my terminal exactly as I set it
maxpane --version              # which build is this, and which Python runs it

Making the panes fit ("‹ widen")

Widgets drop columns when their slot is too narrow and say so in the title — ACTIVITY ‹ widen for amounts, CHASE BOARD ‹ widen: TOKEN. That is terminal width in columns. Check yours with tput cols. Across every dashboard the last marker goes out at:

The table starts at 109 rather than running down to zero because narrower terminals light more markers, not the same ones: below 109 surf's DEV ACTIVITY marker changes wording to ‹ widen: time, kind, ETH as the time and kind columns go too, and below 89 surf's IDENTITY.MD runs out of room to name its shed field beside the title and falls back to a bare ‹ widen. It stays bare down to 76; at 75–74 the stats row sheds transfers/24h as well, and the shorter wording that names both — ‹ widen: 24h /2000, 18 columns against 25 — fits beside the title again, so the hint is descriptive at a narrower terminal than the bare one it replaced. Below 74 the floor line is what overflows, and it has no field to shed, so the marker is bare again. Every one of those is a panel saying what it dropped, which is the system working; the table lists the last few to go out, not every marker a narrow terminal can show.

IMD MARKET is the one row that moves with the data rather than with your terminal. Its widest line carries the IMD/FP gap in dollars, and prices under a cent print with six decimals instead of four — so a tighter peg is a wider panel: $0.007100 where a 2.75% spread would print $0.0200. The table shows the wide case, which is also the normal one for a 1:1 bridge; on a day the peg is loose the marker goes out around 140.

The exception is a post, not a panel. When an announce post links a transaction, its own punctuation can glue the URL to the 66-character hash into a single token no column budget can break — the captured one is 91 columns wide — so surf's ANNOUNCE FEED truncates it and keeps its ‹ widen lit above 143 (that particular post needs 216). The marker is right: the link really is cut. The table's 143 is the width at which every layout is whole, and the next post linking a transaction arrives with a token of its own length, so no fixed number can promise more than that.

A maximized window is already as wide as your display, so font size is the only lever: roughly 169 columns at 17 pt on a laptop screen, about 205 at 14 pt. maxpane sets 17 pt on launch, so zooming out beforehand gets overwritten — pass --font-size 13 (or export MAXPANE_FONT_SIZE=13) to change it, or --font-size 0 to have maxpane leave your terminal alone entirely. At 17 pt a laptop lands at 169, which already clears the 143 the full layout wants — you need --font-size for a smaller screen, not for the full layout.

Checking your version

$ maxpane --version
maxpane 0.5.0
Python 3.13.2 (/Users/you/.local/pipx/venvs/maxpane/bin/python)

The interpreter path is there for a reason. pipx and uv both put their shims in ~/.local/bin, and neither will overwrite a maxpane it doesn't own — the second one you use prints a warning and declines:

⚠️  File exists at ~/.local/bin/maxpane and points to
    ~/.local/share/uv/tools/maxpane/bin/maxpane, not
    ~/.local/pipx/venvs/maxpane/bin/maxpane. Not modifying.

When that happens the install succeeds and reports the new version, but the older tool still answers to maxpane. If the version above isn't the one you just installed, that's the cause — uninstall the copy you don't want (uv tool uninstall maxpane or pipx uninstall maxpane) and reinstall with the other, so a single manager owns the command.

Keyboard shortcuts

Terminal size

The widest layout wants 143 columns. That is the width at which every widget on every dashboard can render its full column set for the data it holds today. The 143 is FWA's, and it is FWA's again: surf set this number at 176 and then 152 for part of 2026-08-10, came down to 142, and now reads 143 as well — level with FWA rather than under it, because surf's IMD MARKET needs one more column than the announce feed once the IMD/FP peg is tight (see the note under the table above). Either way the app-wide number is the max of the two and has not moved. One thing 143 does not promise is a clean announce feed on every possible post: a post that links a transaction can carry a single unbreakable token wider than the panel, and the feed correctly truncates it and says so at any width (see the note under the table above).

143 is inside the ~169 columns a laptop gets at the 17 pt maxpane sets on launch, so the full layout is reachable without touching --font-size. It briefly was not: surf's number stood at 176 for part of 2026-08-10, until the seam between its two columns moved from 3:2 to 7:6 and handed the announce feed exactly the share it needed instead of 24 columns more. Only the split moved to get there, and at 152 and above nothing at all was given up.

What took surf the rest of the way down was the two panels either side of that seam getting narrower, not the seam moving again. The announce feed lowered its own wrapping threshold from 76 to 71 columns, so it wraps posts from 142 instead of 151. The dev-activity panel was reserving 12 columns for a wallet cell whose whole vocabulary is dev and ops and one column too few for its widest transaction kind, so it was both padded and cutting fwa claim mid-word; sizing both cells to what the data actually contains took the panel from 66 columns to 58 and it now clears from a 135-column terminal. That is why the table above no longer has a band where the dev-activity panel is the only thing still asking for width.

One honest caveat on the seam. 7:6 was measured when the feed needed 81 columns and the rail 71; they need 76 and 63 now, which a seam nearer 76:63 would collect at 139 rather than 142. The three columns are real and deliberately unspent: the app-wide number is FWA's 143, so a surf screen clearing at 139 would not change a single width a user sees — and that seam is no longer what binds surf anyway, since the market panel in the row below it asks for 143.

On FWA, press c to swap the odds board for the activity feed — they share the wide middle-left slot, so the bottom row belongs to the chase board and the settlement table alone. That split is why FWA's requirement is 172 and not 198: with the feed in the bottom row, three widgets needing 79, 54 and 55 columns had to share it, and none of them fit until the terminal was very wide. Shortening the buy-gate signal then took it from 172 to 143. TTT and Talismans use the same c pattern; surf does not, because nothing on it is hidden.

Below that the widgets do not wrap or clip silently: each one drops its least important columns and says so in its own title with a ‹ widen marker. That is deliberate, tested behaviour, not a bug — a table that quietly loses a column still looks complete, which is the failure mode the marker exists to prevent.

What a narrow terminal costs you, in the order things go:

The hero row (PULL EV · PRICE · CROWN), the odds board and the sparkline have no column-dropping tiers, so nothing disappears from them. And no number changes with the width — a narrow terminal costs you fields, never correctness.

Available themes

matrix minimal bloomberg htop retro bakery frenpet base talismans fwa

Ten themes. talismans and fwa are game-specific palettes that pair with their dashboards (maxpane --game fwa --theme fwa), but any theme works with any game.