-
Notifications
You must be signed in to change notification settings - Fork 28
Upgrading to Mintlayer Version 1.0.0
Welcome to the upgrade guide for Mintlayer Version 1.0.0. This release brings significant improvements, new features, and some breaking changes. Please follow the instructions below to ensure a smooth transition.
- Prerequisites
- Step-by-Step Upgrade Instructions
- Breaking Changes in Version 1
- Updating Docker
- Additional Notes
- Support
- Backup Data: Before proceeding, ensure you have backed up the wallet and you have stored the mnemonic phrase is a safe location.
- Administrator Access: You may need administrator or root access to perform some of these steps.
Visit the Mintlayer Download Page and download the appropriate package for your platform.
-
Node-GUI Users:
-
Windows: Download the Windows installer (
.exe
). -
macOS: Download the macOS installer (
.dmg
). -
Linux: Download the
tar.gz
orzip
archive.
-
Windows: Download the Windows installer (
-
CLI Users:
- Available as
tar.gz
/zip
archives. - Linux users can also download:
-
Debian-based distributions:
.deb
packages. -
Red Hat-based distributions:
.rpm
packages.
-
Debian-based distributions:
- Available as
Before installing the new version, you must stop your running Mintlayer node.
# If running as a service
sudo systemctl stop mintlayer
# If running manually
pkill node-daemon
- Open the Task Manager.
- Find the
node-daemon
process. - Right-click and select End Task.
- Windows/macOS: Run the installer you downloaded and follow the on-screen instructions.
-
Extract the Package:
tar -xzf Mintlayer_Node_linux_1.0.0_aarch64.tar.gz
-
Move Binaries to the Desired Location:
sudo mv mintlayer_* /usr/local/bin/
-
Note: Binaries are now prefixed with
mintlayer_
. For example,node-daemon
is nowmintlayer_node-daemon
.
-
Note: Binaries are now prefixed with
mintlayer_node-daemon
- Launch the Mintlayer application from the Start Menu or desktop shortcut.
Version 1 introduces several breaking changes that may affect your existing setup.
-
Node-GUI:
- Now available with platform-specific installers:
-
Windows Installer (
.exe
) -
macOS Installer (
.dmg
)
-
Windows Installer (
- Also available as
tar.gz
/zip
archives for all platforms.
- Now available with platform-specific installers:
-
CLI Packages:
- Contain all binaries in a single package.
- Available as:
-
tar.gz
/zip
archives -
.deb
packages for Debian-based Linux distributions -
.rpm
packages for Red Hat-based Linux distributions
-
- All binaries are now prefixed with
mintlayer_
.-
Example:
- Previous:
node-daemon
- Now:
mintlayer_node-daemon
- Previous:
-
Example:
- Action Required: Update any scripts, shortcuts, or service files to reflect the new binary names.
-
account_balance
Function Extended:-
New Argument:
utxo_states
-
Usage:
"utxo_states": ["Confirmed", "Conflicted", "Inactive", "Abandoned", "InMempool"]
-
Default Behavior: Previously, only the "Confirmed" state was considered.
-
Note:
-
utxo_states
accepts an array of strings. - Strings are case-sensitive.
-
-
-
Bech32 Encoded Token IDs:
-
The following functions now return Bech32 encoded token IDs instead of hex-encoded:
account_balance
transaction_create_from_cold_input
transaction_inspect
transaction_compose
standalone_address_details
-
Impact:
- Bech32 encoded token IDs can be directly passed to
token_*
functions without conversion. - Update any client applications or scripts that parse these return values.
- Bech32 encoded token IDs can be directly passed to
-
For users who prefer using Docker Compose, you can refer to our Docker Compose Wizard (Beta). Please note that this feature is still in beta and is currently untested, so use it with caution.
-
Pull the Latest Docker Image:
docker pull mintlayer/mintlayer:v1.0.0
- Alternatively, you can use the
latest
tag:
docker pull mintlayer/mintlayer:latest
- Alternatively, you can use the
-
Stop and Remove the Existing Container:
docker stop mintlayer_node docker rm mintlayer_node
-
Start a New Container with the Updated Image:
docker run -d --name mintlayer_node -p 3030:3030 mintlayer/mintlayer:v1.0.0
- Adjust any additional flags or environment variables as needed for your setup.
- Update Scripts and Integrations: Ensure all your custom scripts and third-party integrations are updated to accommodate the changes in binary names and RPC outputs.
- Test Thoroughly: After upgrading, perform thorough testing to confirm that all functionalities are working as expected.
-
Case Sensitivity: Remember that the
utxo_states
strings are case-sensitive. Incorrect casing may lead to unexpected results.