Skip to content

Releases: Sid-352/Project-Arbiter

Arbiter v0.2.1

17 May 09:51

Choose a tag to compare

Release v0.2.1; thanks to the new contributors and their welcome additions.

Installation

  1. Download and extract the zip archive.
  2. Run arbiter.exe as Administrator to start the background service.
  3. 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

03 May 10:21

Choose a tag to compare

Release v0.2.0

Installation

  1. Download and extract the zip archive.
  2. Run arbiter.exe as Administrator to start the background service.
  3. 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

01 May 10:46

Choose a tag to compare

Release v0.1.8

Installation

  1. Download and extract the zip archive.
  2. Run arbiter.exe as Administrator to start the background service.
  3. 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

20 Apr 10:15

Choose a tag to compare

Release v0.1.6

Installation

  1. Download and extract the zip archive.
  2. Run arbiter.exe as Administrator to start the background service.
  3. 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

19 Apr 15:42

Choose a tag to compare

Release v0.1.5

Installation

  1. Download and extract the zip archive.
  2. Run arbiter.exe as Administrator to start the background service. The control interface can be opened via the system tray icon.
  3. Run arbiter-forge.exe to 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

19 Apr 14:59

Choose a tag to compare

Release v0.1.4

Installation

  1. Download and extract the zip archive.
  2. Run arbiter.exe as Administrator to start the background service. The control interface can be opened via the system tray icon.
  3. Run arbiter-forge.exe to 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

19 Apr 05:39

Choose a tag to compare

Release v0.1.2

Installation

  1. Download and extract the zip archive.
  2. Run arbiter.exe as Administrator to start the background service. The control interface can be opened via the system tray icon.
  3. Run arbiter-forge.exe to 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

18 Apr 14:25

Choose a tag to compare

Release v0.1.1

Installation

  1. Download and extract the zip archive.
  2. Run arbiter.exe as Administrator to start the background service. The control interface can be opened via the system tray icon.
  3. Run arbiter-forge.exe to 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

17 Apr 17:39

Choose a tag to compare

Release v0.1

Installation

  1. Download and extract the zip archive.
  2. Run arbiter.exe as Administrator to start the background service. The control interface can be opened via the system tray icon.
  3. Run arbiter-forge.exe to 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.