Maren Mint · Maren Docs

Maren Mint helps you mint NFTs from an existing collection or drop. Use chat for a guided conversation, or the Rust CLI to manage local wallet groups and control execution from your terminal. Neither approach deploys a new collection or publishes artwork.

Mint in chat#

Open Mint in the app sidebar, choose Chat, and select Start in chat. This opens an editable message; send it when you are ready to begin.

Share the collection. Provide the collection link or contract address, the network, and the quantity you want to mint. Maren can ask for any missing details.
Review the mint. Check the collection, wallet, mint stage, quantity, price, and network fees. Your wallet must be eligible for the selected stage and have enough funds for both the mint and gas.
Arm when ready. Review and arm the prepared mint card yourself. The job uses its funded mint wallet or Speed Wallet flow; preparing the card does not arm it or mint an NFT. Check the job status and transaction details when available.

Mint availability depends on the network, collection, mint mechanism, and your wallet’s eligibility. An estimate or successful inspection does not reserve an NFT.

Use the Rust CLI#

The CLI runs on your computer and stores its wallets in a local encrypted keystore. Signing in connects your Maren account; it does not import your app wallet. The current CLI execution flow supports compatible EVM SeaDrop collections, including public and supported signed stages.

1. Install from source#

You need Rust and Cargo, a native build toolchain for your operating system, and a checkout of the Maren repository. From the repository root, run:

cargo install --path rust-engines/maren-mint-cli
maren-mint --help

Cargo installs the maren-mint binary in its bin directory, normally ~/.cargo/bin. Make sure that directory is on your PATH. If you do not have access to the source, you can use chat without installing the CLI.

maren-mint login
maren-mint doctor

Follow the browser sign-in instructions. On a remote machine or a terminal without a browser, use maren-mint login --no-browser and follow the device authorization instructions instead.

doctor checks your environment, including RPC connectivity, clock health, authentication, and keystore availability. A missing keystore is expected before your first wallet setup.

The CLI reads MAREN_API_URL for the platform API origin. Its built-in default is https://app.maren.network. If your deployment uses a different origin, set MAREN_API_URL to the API origin provided by your deployment before signing in, without an /api/v1 suffix.

3. Set up a wallet group#

Create a group, then import a wallet through the CLI’s interactive prompts:

maren-mint wallet group create my-mints
maren-mint wallet import --group my-mints --chain evm
maren-mint wallet list --group my-mints
maren-mint wallet balance --group my-mints --chain base

The CLI prompts for a keystore password and the wallet details. Enter private keys only in the local import prompt, never in chat or as command-line arguments. Fund each wallet on the network you intend to use; importing a wallet does not transfer funds.

4. Inspect the collection#

Replace NFT_CONTRACT_ADDRESS below with the collection’s NFT contract address and change base to your intended network. Use the NFT contract, not the SeaDrop router address.

maren-mint inspect --chain base --address NFT_CONTRACT_ADDRESS

Inspection reports the detected mint mechanism and available stage information. Check the active stage, price, start time, and wallet limits before preparing execution. It does not submit a mint transaction.

5. Choose how to run the mint#

For the interactive command center, run:

maren-mint

To review the direct execution options first, run:

maren-mint arm --help

The arm command executes across the selected wallet group. Review every argument before running it: the default trigger is immediate, and the quantity applies to each wallet, not the group as a whole.

For example, this command requests one NFT per wallet from a compatible public drop. Replace the contract placeholder before running it. It can broadcast transactions and spend funds after you unlock the keystore.

maren-mint arm --chain base --address NFT_CONTRACT_ADDRESS --group my-mints --qty-per-wallet 1 --stage public --trigger immediate

For a scheduled mint, replace immediate with time:UNIX_TIMESTAMP, using a future Unix timestamp in seconds. Keep the terminal process running and the machine connected until execution finishes. A scheduled trigger does not guarantee allocation or transaction inclusion.

Signed stages require the collection slug via --slug and an OpenSea API key configured for the CLI. Use maren-mint arm --help to review stage selection, RPC overrides, and headless execution with --no-tui.

Configure your execution#

The Rust CLI lets you choose the wallets, infrastructure, and execution settings for each drop. In the app, select Rust CLI on the Mint page for an overview.

Wallets: Import individual wallets with wallet import or a CSV with wallet import-batch. Keep wallets in named groups and choose the execution group with --group.
RPC endpoint: Pass your provider URL with --rpc on arm or wallet balance. The CLI checks the endpoint against the selected chain.
Quantity: Set --qty-per-wallet. The quantity applies to every wallet in the selected group.
Timing: Use --trigger immediate or --trigger time:UNIX_TIMESTAMP for a future Unix timestamp in seconds.
Broadcast delay: Set --jitter to a delay in milliseconds between wallet broadcasts.
Mint stage: Choose --stage auto, public, or signed. Supported signed stages also require a collection --slug and OpenSea configuration.
Output: Use the terminal dashboard by default, or --no-tui for headless output.

For a custom RPC, set RPC_URL in your local environment and pass it as --rpc "$RPC_URL". Provider URLs can contain API credentials; keep them out of shared scripts and screenshots.

The CLI also exposes copy and sweep commands. Review their help before use. These local commands are separate from chat: the chat agent cannot copy a wallet’s mints.

Local execution requires your machine or remote process to stay running and connected. Wallet funding, RPC availability, collection eligibility, and network conditions still apply.

Follow the result#

The CLI displays execution progress in its terminal dashboard. Review the transaction hashes and wallet outcomes there, and verify transactions in the network’s block explorer. Local CLI execution is separate from the app’s mint job history.

Run maren-mint --help to explore the available commands, including wallet balances, copy minting, and token sweeping. For app transaction reviews, see Transaction safety.