deepseek-harness
deepseek-ai
DeepSeek Harness: Everything is a Plugin.
PROJECT TOPICS
INSTALL REFERENCE
dsh plugin --profile web add github:0xRabit/dsh-crypto-portfolio
该命令指向仓库当前默认分支;尚无绑定当前 commit 的完整验证结果。
PROJECT README
English | 中文
A free, 100% self-hosted DeepSeek Harness (DSH) plugin that unifies your on-chain and CEX assets into one self-contained web dashboard.
Requires dsh 0.1.1-rc.2 (Node ^22.19 || >=24) · Python 3.9+ · pip3 install requests pynacl
dsh plugin --profile demo add dsh-crypto-portfolio # npm
dsh --profile demo # dashboard at http://127.0.0.1:8080
Twin project. This dashboard is the twin of the SmartFolio Chrome extension: the extension puts the same wallets in your toolbar, this one is the self-hosted, all-chains view that runs on your own machine. Same idea, two shells — the dashboard is a DSH plugin and follows the DSH plugin conventions, so it keeps its own name.



Unofficial project, independently developed and maintained by community members.
I built it because the pain points are real.
EVM assets in DeBank, SOL and staking on-chain, BTC in a block explorer, plus Binance / Bybit / Backpack / OKX / Bitget — each with its own app. Checking "how much do I actually have" meant hopping between six pages, and it was easy to miss a wallet along the way.
This plugin puts all of it on a single screen.
Some money is genuinely invisible: native Solana stake accounts (getParsedStakeAccounts misses them), Hyperliquid L1 staked HYPE and spot balances, exchange earn/funding accounts. None of these are plain SPL/ERC-20 tokens, so ordinary tools never read them.
This plugin digs them out and prices them into your total — including the 12.1 SOL staked in the account above and the ~318 HYPE staked on Hyperliquid.
DeBank lists plenty of fake tokens — ETHG, for example, is a phishing token with a manipulated price that once inflated one account by $570K.
One-click blacklisting: every token you blacklist is removed from totals, trends and historical snapshots instantly.
Without history there's no peace of mind.
Every refresh saves the last snapshot of the day (SQLite, deduplicated by day); over time it draws a trend line that is uniquely yours:
<exchange>_read). Five exchanges are supported (Binance, Bybit, Backpack, OKX, Bitget). Read-only CEX keys cover spot, OKX's funding sub-account and Backpack's futures collateral account, including tokenised equities; on Bitget the spot account is summed with the real futures accounts and the S* demo products are skipped, so play money never enters the total.debank-pro (badged "PAID", with a registration link) and free keyless debank-public fallback; CEX rows always show Binance/Bybit/Backpack/OKX/Bitget with "get API key" links to each exchange (OKX and Bitget also take the key's passphrase). Each source displays when it last succeeded.default profile ships with public template wallets (vitalik.eth, genesis BTC, public SOL, public DOGE, public ADA) and empty keys; each profile can be renamed — its snapshots move with it — and keeps its own daily refresh time; your private wallets and keys live in a separately named profile with its own snapshot history.127.0.0.1 and masks API keys in its responses; writes are refused for cross-site requests (Sec-Fetch-Site: cross-site, foreign or opaque Origin, non-JSON bodies) and refresh is rate-limited to one run per minute. Snapshot history is kept as a 90-day window plus one per month, so the database does not grow without bound.html2canvas, no CDN, and no wallet address in the image.#pageSettings opens Settings and #pageSettings/secWallets opens one section, so a refresh (or a bookmark) returns you to the same place.Every box in the diagram is a real data pipeline:
Not a wrapper — a real plugin:
dsh.bundle manifest (cordis.patch.yml), so it installs with dsh plugin add.apply(ctx) hooks into the Cordis lifecycle: seeds user-local profiles/default from public templates on first run, spawns the dashboard as a child process, and stops it cleanly on ctx.on('dispose').GET /api/refresh, /api/history, /api/tokens, ...) that an agent can call directly, in addition to the web UI.This repository contains no private keys, no private wallets, no balances — tracker/config.py ships with WALLETS = [] and empty keys. All private configs live in git-ignored local profiles/. Clone it, review it, run it with confidence.
dsh 0.1.1-rc.2 (or a compatible release within the same pre-release line)
and Node ^22.19.0 || >=24.0.0 — the range DSH itself declares.
Python 3.9+ with two pip packages:
pip3 install requests pynacl
These are ordinary runtime dependencies, not vendored, so pip can pick the
build that matches your platform.
Installs prebuilt code and needs no build permission:
dsh plugin --profile demo add dsh-crypto-portfolio
dsh --profile demo
pnpm pack # produces dsh-crypto-portfolio-0.1.0.tgz
dsh plugin --profile demo add ./dsh-crypto-portfolio-0.1.0.tgz
dsh plugin --profile demo add github:0xRabit/dsh-crypto-portfolio#<commit-sha>
This package is plain JavaScript + Python with no build step, so its
prepare is a no-op and pnpm does not need you to allowlist a build script —
unlike plugins that ship TypeScript sources. Pin a commit SHA anyway, so a
later push cannot change what runs on your machine.
dsh --profile demo --dump-config # look for: # == dsh-crypto-portfolio
If that line is missing, the bundle did not activate — the package installed as a
plain dependency instead. Re-run the add and check the warning it printed.
A patch replaces the whole config of a row, so restate every key you need.
Put this in $DSH_HOME/profiles/demo/cordis.patch.yml:
- id: portfolio-tracker
name: dsh-crypto-portfolio
config:
port: 8199
host: 127.0.0.1
Or set PORTFOLIO_PORT in the environment.
python3 run.py --init-template --port 8080 # seeds profiles/default from public templates
profiles/default/ sources.json + wallets.json (public template, auto-seeded)
templates/ public example configs (no secrets)
tracker/ backend fetchers (debank/btc/solana/hyperliquid/cex/prices)
static/ web dashboard (vanilla JS, no external deps)
run.py / fetch.py web server / CLI snapshot
One command from the maintainer's working tree (the release scripts live there, not in this published bundle), and the flow is deliberately split in two:
scripts/sync_public.sh --push # publish code — the version does NOT move
scripts/sync_public.sh --push --release # bump + tag + refresh every market listing
| Action | Version | Changelog | Tag | Market listings |
|---|---|---|---|---|
--push |
unchanged | unchanged | — | untouched |
--push --release |
bumped | [Unreleased] stamped |
vX.Y.Z |
branch pushed, PR prepared per market |
package.json exactly as it is, so
installed users see no update until a version is cut on purpose.market/, so it is versioned with the code it describes and always matches
the version being shipped. A market whose text did not change is skipped instead of
getting an empty pull request.| Market | How it is fed | What the release does |
|---|---|---|
| awesome-dsh-plugin | one YAML file per plugin | market/awesome-dsh-plugin.yml → data/plugins/0xRabit__dsh-crypto-portfolio.yml |
| awesome-deepseek-harness | curated bilingual tables | market/awesome-deepseek-harness.json → the row in each language's 🧩 Tools, Workflows & Presets table |
| awesome-dsh-hub | hourly scrape of the dsh-plugin topic |
nothing to submit — the release only verifies the entry is present and current |
MIT — see LICENSE.
CLASSIFICATION EVIDENCE
系统优先读取 GitHub Topics,再与站内分类词典和词根规则比对。当前命中: 无有效分类标签。