# Dexterm — source project research and archive notes

Read on October 18, 2026. This document describes the original Dexterm project and the initial preservation work. It is reference material, not a description of every current DEXOPUS feature.

Sources: [home](https://dexterm.xyz/), [features](https://dexterm.xyz/features/), [docs](https://dexterm.xyz/docs/), [beginner guide](https://dexterm.xyz/docs/beginners/), [installation](https://dexterm.xyz/docs/getting-started/), [trust](https://dexterm.xyz/trust/), [legal](https://dexterm.xyz/legal/) and the [linked public repository](https://github.com/dexterm-xyz/dexterm).

## What the original project is

Dexterm is a locally installed terminal for screening Solana assets. It combines public market data, on-chain risk information, a Claude analyst using the user's own Claude Code session, paper accounting and an experimental wallet-signing route. Its website presents demonstrations and documentation; it is not a browser exchange.

Its central idea is a compact keyboard-driven workspace for a noisy market: prices, liquidity, holders, wallet relationships and model explanations appear together. The project emphasizes local configuration, user-held credentials and public data sources.

The original homepage uses green glyph rain, a pixel wordmark and installation commands, followed by four animated terminal scenes. Links lead to the beginner guide, installation, repository, trust page and feature catalogue.

## Demonstrations versus verified behavior

The original homepage animations are not a live terminal recording. Scenes 01, 02 and 04 use fictional token names and sample data. Scene 03 uses a selected WIF historical interval from December 14, 2023 and a scripted conversation. The source explicitly identifies these as demonstrations, not a recorded Claude run, current prices or trading advice.

The screen-like tables and keyboard legends in those canvases are drawn illustrations. Their presence does not establish working browser trading controls. DEXOPUS's current product screens use their own real-data adapters; the original demonstration assets remain preserved as source evidence.

## Audience and workflow

The original product targets Solana researchers comfortable with a terminal, Claude Code users and developers interested in read-only agent tools. Its documented workflow is:

1. View the website and read the beginner or installation guide.
2. Install Node.js and the CLI, then run its diagnostic command.
3. Use the screener, token details and watchlist.
4. Request analysis using the user's existing Claude session.
5. Explore paper tickets and positions before considering the optional experimental live mode.

The later steps describe the installed CLI. They do not happen merely by opening the original website. The preservation work did not install or execute that third-party CLI, sign into Anthropic, connect a wallet, sign transactions or submit private information.

## Implementation and data sources

The original public HTML, CSS and JavaScript use Canvas 2D for glyph rain, tables, candles, scanning effects and analyst dialogue. A shared clock and scroll position control the scenes; the pointer affects the glow, and the wordmark uses color separation and glitch effects. Frame data is stored in the same-origin splash-frames.json file.

Sound is off by default. The observed toggle changes its label and pressed state and can be turned off again. Web Audio supplies ambience and low-frequency cues. The toggle behavior was checked; that is distinct from an independent acoustic measurement.

The document search uses a same-origin JSON index, an 80 ms debounce, keyword scoring, up to twelve results and keyboard controls. The original full index contains 322 entries. The preserved search is explicitly restricted to captured pages and sections. Code-copy buttons copy text; they do not run commands.

The official README lists DEX Screener, Jupiter and GeckoTerminal for market data; PumpPortal for launch events; RugCheck and GoPlus for risk information; and Solana RPC with optional Helius. Free sources do not supply every field. Missing fields need explicit unavailable or configuration-required states.

The original analyst launches the user's existing Claude process and exposes read-only MCP tools. Model usage belongs to the user's Anthropic account. MCP and agent modes are described in the source; they were not fully executed or independently security-audited during preservation.

The CLI can persist watchlists, caches and paper accounting in local SQLite. Its persistence model belongs to the CLI and should not be assumed to describe the original marketing website.

## Experimental trading scope

The official documentation describes paper mode as the default. A user-selected live route uses a separate signer, spending and slippage checks, Jupiter transaction construction and simulation, and a loopback bridge to the user's Phantom extension. The documented default is devnet; mainnet requires an explicit option. AI and read-only MCP tools do not sign or broadcast.

These are inspectable architectural claims, not evidence that a swap was completed during this research. The feature catalogue still labels non-custodial swaps and the Phantom bridge as in progress, and the source acknowledges known issues. No independent transaction, realized return or complete trading-risk validation was established.

An optional devnet fast-wallet command is a specific exception to broad claims about never storing a key: the README says it creates a local devnet key file when explicitly invoked. Custody claims must be interpreted in their actual configuration scope. They do not replace a security audit.

## Observed feature status

| Capability | What was observed | Verification boundary |
| --- | --- | --- |
| Four homepage scenes | Animated terminal tables, candles, dialogue and scanning | Website behavior and source assets inspected; underlying CLI not executed |
| Sound and motion | Toggle state, shared animation clock and visibility behavior | UI and source verified; no independent audio measurement |
| Guides and installation | Captured beginner and Node.js / CLI instructions | Reading documentation does not mean installing the software |
| Feature catalogue | 77 live, 19 in progress and zero coming entries; filtering and expandable screenshots | These are the publisher's status labels, not independent execution results |
| Search and document navigation | Local results, keyboard navigation and section anchors | Preserved-page scope is labeled |
| Market, holders and alerts | Provider and configuration descriptions in official materials | Original CLI capability was not independently run |
| Claude and read-only agents | Official source architecture and scripted homepage examples | Homepage dialogue is not evidence of an actual model call |
| Paper / live routes | Documented manual and wallet confirmation boundaries | No transaction or return was verified |
| Builds and third-party scans | Published provenance and scan disclosures, including five flags out of 75 engines | No release executable was run or independently rescanned |

## License, token and terminology

The original public repository identifies its license as AGPL-3.0-only. The cloning template's MIT license does not replace the original project's license or notices. No explicit SaaS price table was observed. Claude usage and optional upstream APIs remain subject to their providers' costs and limits.

The original site discloses an optional DEXTERM meme token launched by its authors on October 15, 2026. Its stated contract is 2huJ1cxDXpGrh2bPYxptaoLj89to8CnzdVC5aYTEpump. This is the original project's token, not the DEXOPUS contract. The original disclosure describes no required access, discounts, fee share, revenue rights, airdrop promise or product rights. Issuance, permissions and market claims were not independently verified here.

Paper means simulated accounting with virtual capital. Live means an explicitly chosen wallet-signing route. Non-custodial describes key control; it does not guarantee fair quotes or successful execution. Website credibility heuristics, model stances, build provenance, dependency inventories and automated scans each have distinct limits. None independently certifies safety or investment returns.

## Preserved material and current boundaries

Seven captured pages, their source HTML / CSS / JavaScript, public assets, frame data, screenshots, document content and original notices were retained. Uncaptured internal documentation links remain labeled source links. The implementation remains editable Next.js source with a lockfile rather than an iframe or a flattened whole-page screenshot.

The initial archive verification included lint, TypeScript, static builds, browser checks, animation lifecycle checks and search checks. These verify the preserved frontend and its stated boundaries; they do not establish every advertised original CLI capability.

The current DEXOPUS application has since added its own real market feeds, four separately configured AI providers, a persistent backend and other product features. Consult the current product interface and release records for their actual availability. Historical source statements in this archive should not be presented as current DEXOPUS verification.