Skip to content

v1.0.2

Choose a tag to compare

View all tags
@github-actions github-actions released this 24 Aug 15:11
· 8 commits to main since this release
v1.0.2
5b3e384

MINTER v1.0.2

Two builds — pick the one that matches how you run it.

Windows — run it on your own machine

  1. Download minter-desktop-*-windows-x64.zip
  2. Check the hash against the matching .sha256
  3. Unzip anywhere (e.g. C:\Minter\) and run minter-desktop.exe
  4. SmartScreen → More info → Run anyway (the build is unsigned)

No server needed. Your machine has to be awake at mint time.

Updating — Windows

Unzip over your existing folder, replacing minter-desktop.exe.

Your wallets and settings live in that folder — keys.vault,
config.json, auth_cache.bin, results and logs. The archive holds
only the program and its documentation, so nothing of yours is
touched. Unzipping somewhere new gives you a second, empty install
while everything stays behind in the old folder.

Updating — Linux VPS

Nothing to unzip: re-run the installer below. It upgrades in place,
keeps the previous binary under /opt/minter/backups/, and refuses
to replace a build while a mint looks active.

Your data never lived beside the binary — it stays in
/var/lib/minter, untouched.

Linux VPS — run it 24/7 near the chain

On a fresh Linux server — Ubuntu, Debian, Fedora, RHEL or Arch, no desktop required:

curl -fsSL https://raw.githubusercontent.com/MaxBetov-pdd/Minter-rs-v2/main/deploy/linux/install.sh | sudo bash

The installer pulls minter-desktop-*-linux-x64.tar.gz from this
release, sets up the service, and prints how to connect.

Then drive the GUI from Windows with the connector:
https://github.com/MaxBetov-pdd/minter-connect

Safety

  • Burner wallets only.
  • Dry Run is on by default; a live OpenSea run needs you to type LIVE.
  • Never share keys.vault, config.json or auth_cache.bin.
  • Never expose port 3021 to the Internet — reach it through the tunnel.

Full Changelog: v1.0.1...v1.0.2

Assets 6
Loading