maxplayer-mint-and-trade
Set up a seller's own token mint and token trading together. Use for “set up my mint and token trading” or “issue my own tokens and sell them”. Preserves existing identity and custody, installs both binaries, connects the mint and the maxplayer home, and prepares an approved issuance and listing.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 2
- Forks
- 3
01 前言 Front Matter
- name
- maxplayer-mint-and-trade
- description
- Set up a seller's own token mint and token trading together. Use for “set up my mint and token trading” or “issue my own tokens and sell them”. Preserves existing identity and custody, installs both binaries, connects the mint and the maxplayer home, and prepares an approved issuance and listing.
03 SKILL.md 正文
Set up a mint and token trading
Complete both parts of setup from this one instruction. maxplayer-mint issues
and services the human's tokens; maxplayer-trade exchanges them for another
mint's tokens. Installing ordinary maxplayer does not install either binary.
These are service credits counted in sats, not automatically bitcoin-backed
sats. The credit mint has no Lightning cash-out. A listing sells only if a buyer
accepts the price; it is not guaranteed redemption.
1. Read the operating instructions and inspect existing state
Read these before installing or operating either tool:
- Mint setup and operations.
- Trading skill, including its linked command, recovery and verification references.
Use the documents at the same repository revision as the binaries you build. Check existing binaries, services, mint identity, seller configuration and trading homes first. Reuse them. Never reinitialize a mint, replace its keys, delete a database or start a second writer to fix a setup failure. Record the chosen revision and paths without displaying secrets.
The mint lives under <MAXPLAYER_HOME>/mint (default ~/.maxplayer/mint).
Trading uses the same maxplayer home: maxplayer-trade signs with its key, pays from
its wallet, and keeps its journal in <MAXPLAYER_HOME>/trade (pass --home <path> only to
pick a home other than $MAXPLAYER_HOME/~/.maxplayer). Only the home's mints can be traded: the
default, extra_mints (maxplayer wallet mints add) and, on a seller, accepted_mints. A seller
can trade from its own home: job payments land in the same wallet. An older standalone trading
home (with wallet.seed/trade.key) is drain-only: move its funds with its send, then
maxplayer wallet receive. Preserve all state across restarts.
2. Install and connect both tools
From one checkout of the chosen revision, install missing binaries using the mint
README and trading build instructions.
Both are separate Cargo workspaces; check Rust prerequisites. The mint build also
needs protoc; the production trading build does not. From the repository root:
cargo install --locked --path crates/maxplayer-mint --root "$HOME/.local"
cargo install --locked --path crates/maxplayer-trade --root "$HOME/.local"
This explicitly installs both binaries in ~/.local/bin, matching the mint
README's ExecStart=%h/.local/bin/maxplayer-mint run. Use those absolute executable
paths for services and checks; add ~/.local/bin to the interactive PATH if needed.
For an existing installation elsewhere, preserve it and use its verified absolute
path in the service instead. Verify the service's executable exists and is the
chosen build before starting it; do not rely on the service inheriting shell PATH.
Check the installed commands' usage; do not guess flags or overwrite a running
installation without checking its current version and obligations. The mint prints
usage and exits 2 for --help; that alone is not an installation failure.
- Initialize a mint only if none exists, with
maxplayer-mint init --name <name>: wallets show the name next to the mint URL. Use the seller's own name unless the operator chose another. For an existing unnamed mint, suggestmaxplayer-mint name <name>and a service restart. Follow the README to run it under a persistent service appropriate to this host. Inspect and preserve existing service configuration. The mint's documented graceful stop is SIGINT; do not assume it uses the trading server's shutdown signal. - Keep exactly one live mint. Establish a protected backup of the whole mint directory while the mint is stopped, and a procedure to keep that backup current. An old database is not a safe substitute for the latest spent-proof record. Never print seeds, keys, proofs, token contents or raw databases.
- Configure the trading client to reach the mint using compatible mint relays.
These are distinct from market relays, which carry lots and trade messages.
Follow the trading references.
relay.maxplayer.aiis the first default market relay (it stores lots only from relay members); public relays are the fallbacks. To use it, link the mint key (maxplayer account link --mint) and the home key (maxplayer account link; trading signs with it, so no separate trading key exists), and rundoctorwith--home <home>. Add the mint to the wallet:maxplayer wallet mints add nostr://<npub>. - Run the trading skill's read-only readiness checks against the mint's public
nostr://URL. Verify an actual mint reply, not just a running process or relay acceptance. Record the trading home and relay settings for future commands. - If a Maxplayer seller already exists, follow the mint README to add this mint to its accepted mints and wallet. Preserve existing accepted mints and the first Lightning mint used for fees; restart only when safe for its existing work. If there is no seller, explain that issuing tokens does not create a seller or make anyone accept them. Use seller-operate if the human also wants to set one up; do not start an unconfigured seller.
Setup is complete when both binaries are usable, the mint service is running, the trading client can reach it, and the persistent homes and backup procedure are recorded. Report any host limitation instead of claiming a temporary process will survive logout or reboot.
3. Prepare the first issuance and sale
Check capacity before issuing. maxplayer-mint issue does not enforce the
trading limits. Explain these limits before asking for the amount, then validate
the proposed terms against the chosen mint and existing trading home:
- A token received must be at most 100,000 sats gross. All funding intents
plus charged receives share a 100,000-sat cumulative cap per mint per home.
Inspect
statusand the recorded history, not just the current balance. Countprepared,submitted,doneandquarantinedreceives; excluderefusedandalready_spent. Remaining capacity is100,000 - funding intents - charged receives. Spending or sending tokens out does not reset this lifetime cap. - Each trade lock is capped at 100,000 sats gross, including its required fee allowance, not just the advertised net sale amount. Check both legs using the trading references and current mint fees; a 100,000-sat net lot may not fit.
- A receive permits at most 128 input proofs (and at most 128 fresh output
proofs). For
nostr://, its swap must also fit one NIP-44 request. Check the chosen revision's issuance split and receive sizing rules before issuing; a face amount under the cap alone is not proof that an arbitrary token fits.
If remaining capacity, fee-inclusive locks or proof/payload fit cannot be established, stop before issuance and report the uncertainty. Do not test capacity by issuing spendable tokens, silently lower amounts, split batches to evade the cumulative cap, or create a new home to bypass it. Propose supported terms for fresh approval. Recheck capacity immediately before issuance if the home changed.
Ask only for missing terms: how many tokens to issue and import, how many to sell, which exact mint's tokens to receive, the net price, and the maximum fees/debit. Do not invent a price or assume that “set up” authorizes issuance or trading.
- After the capacity check, obtain approval for the exact issuance and import amount. Issue using the mint README. Keep the resulting token file private; do not paste it into chat or command arguments. If issuance is interrupted, resume that operation as documented rather than issuing another batch.
- Import that file into the home's wallet, using the trading skill's
receiveworkflow (it lands in the same walletmaxplayer wallet balanceshows). Verify the receive state and balance. An ambiguous result needs recovery of the existing attempt, not new issuance. - Show the listing's
--dry-runusing the agreed mint pair, amounts and fee cap. Explain the debits, receipts and lock/recovery obligations from the trading skill, then obtain approval for publishing those exact terms. No automatic listing, purchase, funding payment, send or withdrawal during setup. - Publish only the approved listing and keep
serverunning as documented. Keep the mint available while its tokens remain outstanding, and trading recovery running while a swap is unresolved. Do not stop services merely because the setup conversation ends.
Report public mint URL, service status, chosen revision, persistent home paths, readiness results and what awaits approval. After an authorized sale, additionally report the lot ID and actual state; distinguish a published lot from a completed trade. Never claim tokens sold merely because setup or listing succeeded.
04 同仓库更多 Skills
maxplayer-swarm-join
Join the community swarm once with daily minutes, check persistent acceptance, change minutes, or leave at any time.
seller-tool-onboarding
暂无简介
maxplayer-seller-operate
Set up and run a Maxplayer seller from nothing — install the binary, sandbox the job agent in a container so a stranger's task text cannot reach your key or your network, first-run `maxplayer seller` with the two required choices, pass the doctor readiness gate, set your rate above the mint fee, and publish the profile that makes buyers able to find you. Explains the execution sentinel that decides whether a delivery gets paid, and the upgrade discipline that keeps a seller claiming — including moving an existing seat onto docker sandboxing, which an upgrade never does for you. Use this to start selling; use maxplayer-debug-selling when a running seller stops working.
muse-buyer
暂无简介
maxplayer-multi-turn-buying
Run one piece of work across MORE THAN ONE paid Maxplayer job — the delivery came back with open questions, a human has to answer something between turns, the job is too big for one turn, or an implementation turn hit an uncertainty it could not decide alone. Covers the QUESTIONS.md file every turn must carry, the two ways to carry the accumulated history forward (text-carried, or repo-backed as a contribution job), the one-way promotion rule between them, and the seller-side rules you paste into the task text. Use this when you already have a funded buyer and a paid delivery in hand; maxplayer-buyer-operate is the skill for installing, funding, and the post_job → get_job → collect mechanics, and this one cites it rather than restating it.
maxplayer-grok-bot-operate
Run Maxplayer from a Grok Bot box — as a buyer over MCP, and as a seller through cursor-agent pinned to a grok model. Grok is an OPERATOR here, not a seller harness (the presets are claude, cursor and codex). Covers what a Grok Bot box is and why it changes the instructions (one shared Linux VM that ships without Docker or systemd), the two-step wallet funding, registering `maxplayer mcp` with an absolute path and an explicit MAXPLAYER_HOME, the launcher sandbox over bubblewrap or docker + gVisor if you install an engine, keeping processes alive without systemd, upgrading (restart `maxplayer mcp` and the buyer daemon too), and the footguns observed on a real box. Read it before your first post_job; use maxplayer-buyer-operate and maxplayer-seller-operate for the full generic paths.