Releases: Sid-352/Project-Arbiter
Arbiter v0.2.1
Release v0.2.1; thanks to the new contributors and their welcome additions.
Installation
- Download and extract the zip archive.
- Run
arbiter.exeas Administrator to start the background service. - Open Forge from the system tray icon (
Open Forge).
Configuration (ledger.toml and arbiter.vault) is created automatically in an arbiter-data directory next to the executables on first launch.
Arbiter v0.2.0
Release v0.2.0
Installation
- Download and extract the zip archive.
- Run
arbiter.exeas Administrator to start the background service. - Open Forge from the system tray icon (
Open Forge).
Configuration (ledger.toml and arbiter.vault) is created automatically in an arbiter-data directory next to the executables on first launch.
Arbiter v0.1.8
Release v0.1.8
Installation
- Download and extract the zip archive.
- Run
arbiter.exeas Administrator to start the background service. - Open Forge from the system tray icon (
Open Forge).
Configuration (ledger.json and signet.vault) is created automatically in an arbiter-data directory next to the executables on first launch.
Arbiter v0.1.6
Release v0.1.6
Installation
- Download and extract the zip archive.
- Run
arbiter.exeas Administrator to start the background service. - Open Forge from the system tray icon (
Open Forge).
Configuration (ledger.json and signet.vault) is created automatically in an arbiter-data directory next to the executables on first launch.
Arbiter v0.1.5
Release v0.1.5
Installation
- Download and extract the zip archive.
- Run
arbiter.exeas Administrator to start the background service. The control interface can be opened via the system tray icon. - Run
arbiter-forge.exeto open the control interface directly (not recommended for regular use).
Configuration (ledger.json and signet.vault) is created automatically in an arbiter-data directory next to the executables on first launch.
Arbiter v0.1.4
Release v0.1.4
Installation
- Download and extract the zip archive.
- Run
arbiter.exeas Administrator to start the background service. The control interface can be opened via the system tray icon. - Run
arbiter-forge.exeto open the control interface directly (not recommended for regular use).
Configuration (ledger.json and signet.vault) is created automatically in an arbiter-data directory next to the executables on first launch.
Arbiter v0.1.2
Release v0.1.2
Installation
- Download and extract the zip archive.
- Run
arbiter.exeas Administrator to start the background service. The control interface can be opened via the system tray icon. - Run
arbiter-forge.exeto open the control interface directly (not recommended for regular use).
Configuration (ledger.json and signet.vault) is created automatically in an arbiter-data directory next to the executables on first launch.
Arbiter v0.1.1
Release v0.1.1
Installation
- Download and extract the zip archive.
- Run
arbiter.exeas Administrator to start the background service. The control interface can be opened via the system tray icon. - Run
arbiter-forge.exeto open the control interface directly (not recommended for regular use).
Configuration (ledger.json and signet.vault) is created automatically in an arbiter-data directory next to the executables on first launch.
Arbiter v0.1
Release v0.1
Installation
- Download and extract the zip archive.
- Run
arbiter.exeas Administrator to start the background service. The control interface can be opened via the system tray icon. - Run
arbiter-forge.exeto open the control interface directly (not recommended for regular use).
Configuration (ledger.json and signet.vault) is created automatically in an arbiter-data directory next to the executables on first launch.