Configure your optional settings

Opening the configuration window

The configuration window may be opened by right clicking on the Off System logo in your computer's tray and selecting configuration from the menu.


Peers are predominantly discovered arbitrarily as a result of searches for content. The bootstrap section of the configuration window determines the peers hat your node will attempt to make connections with upon start up and during maintenance. Having no bootstrap peers will inhibit a node from making connections when searching for content.

Adding a Bootstrap Peer

  1. Obtain the locator of the Peer you wish to bootstrap

  2. Paste the locator text into the text field labeled Locator

  3. Click the add button

Removing a Bootstrap Peer

  1. Find the row with the Node ID of the desired peer in the table

  2. Click the x icon on the furthest right portion of the row

Boostrapping to Last Known Connections

This feature will upon restart attempt a best effort restoration of your node's most recent connections before it went offline.

  1. Check the checkbox labeled Bootstrap to last known connections


The network section of the configuration defines how your node will make connections to other peers as well as http clients. Your may need to configure your router or firewall to allow port forwarding for the ports listed in this configuration. By default peer connections are received on port 8200 and http clients are received on 23402.


The storage section of the configuration defines the size and location parameters of each of the node's block caches. There are three type of blocks in the system block, mini, and nano. Files that are over 128kb stored in the block cache. Files between 128kb and 1000b are store in the mini cache. Files less than 1000b are stored in the nano cache. You may want to size the storage of each cache based upon your usage of the node. Block Cache's are not free space and the network will try to fill or empty themselves based upon network usage and the size limitations created by their node's installers.

Last updated