The PLSR wallet will run on both Windows and Linux.

The PLSR Desktop Wallet software runs on both Windows and Linux operating systems. Depending on the user's comfort and familiarity with the computer's chosen operating system, users might prefer one operating system over the other. However, since Microsoft Windows requires paid activation and oftens needs to reboot to install the latest Windows Updates, many in the Pulsar community run their wallet installation on the latest version of some flavor of Linux: Lubuntu, Linux Lite, Linux Mint, or Ubuntu to name a few.

Since choosing any particular Linux variant depends on many factors, such as OS resource requirements and support, we recommend that each user conduct their own research when it comes to picking a Linux flavor/variant. With that being said, many users run the Pulsar Wallet on Linux Lite on dedicated machines in their homelab.

Linux Lite Minimum Computer Requirements

• 1 Ghz processor
• 768mb ram
• 8gb HDD/SD
• VGA Screen capable of 1024x768 resolution
• DVD drive or USB port for the ISO image

Linux Lite Preferred Computer Requirements

• 1.5 Ghz processor+
• 1024 ram+
• 20gb HDD/SSD+
• VGA, DVI or HDMI screen capable of 1366x768 resolution
• DVD drive or USB port for the ISO image

The PLSR wallet can run on a VM for both Windows and Linux.

This section concerning Virtual Machine ("VM") platforms is intended for awarenesss and informational purposes. Use of a VM platform is not an offical recommendation as providing support for VM configurations is beyond the scope of this guide.

A Virtual Machine ("VM") operates as a digital computing resource, employing software to execute programs and deploy applications, rather than relying on a physical computer. It allows multiple virtual "guest" machines to operate on a single physical "host" machine. Each VM operates independently, with its own operating system, distinct and separate from other VMs hosted on the same physical machine.

Proxmox can be undersood as an independent operating system that deploys VMs either on a single physical machine or on a cluster of networked physical machines. Proxmox can be downloaded and implemented entirely for free, without any charges. However, acquiring a subscription provides an additional layer of stability for any node utilized in a production setting.

Proxmox is first installed on all physical machines in a local area network. When multiple physical machines running Proxmox are on the same local area network, Proxmox allows each individual machine to join a cluster -- which enables the user to manage each machine in the cluster through a single user interface accessible via a web browser. The VMs hosting the Pulsar desktop wallet operating under the umbrella of Proxmox usually run, but are not limited to, Lubuntu or Linux Lite.

We recommend that interested users watch Proxmox YouTube videos and conduct internet searches for Proxmox to become acquainted with this particular virtual environment. Users find that installing Proxmox as their primary operating system comes with benefits that other versions of Linux cannot provide.

The PLSR wallet runs best on its own dedicated computer hardware.

There are three main reasons to install the PLSR wallet on dedicated computer hardware:

• ↑ better security;
• ↑ better performance; and
• ↑ better granular control.

While it is not necessary to use dedicated hardware to host the PLSR wallet, there are certainly advantages of doing so especially when considering PLSR's faster blocktimes.

Hardware recommendations:

• ✅ 4+ CPU Cores;
• ✅ 16+ GB Ram; and
• ✅ 20+ GB SSD/NVMe;

Ideal hardware/network recommendations:

• ✅ A dedicated computer running a newer faster multi-core processor, newer faster ram, and newer faster NVMe storage;
• ✅ Dedicated External Static IP address assigned by ISP;
• ✅ Dedicated Local Area Network (LAN) Static IP address from router; and
• ✅ Allow and Forward Port 5995 (TCP) in the firewall/router to the computer hosting the wallet.

🖥 MiniPC Example

• MINISFORUM (Venus Series) UM773 Lite, Barebones.
• Equipped with the AMD Ryzen 7 7735HS processor, 8 Cores/16 Threads, base clock of 3.2 GHz, Up to 4.75GHz, Based on the RDNA 2 architecture.
• Crucial RAM 64GB Kit (2x32GB) DDR5 4800MT/s CL40 Laptop Memory - CT2K32G48C40S5.
• Crucial T500 2TB Gen4 NVMe M.2 Internal Gaming SSD, Up to 7400MB/s, Laptop & Desktop Compatible - CT2000T500SSD8.

Using the PLSR desktop wallet means installing and running the wallet on your own hardware/network. As such, not only will the computer's hardware affect the wallet's performance but also running the desktop wallet in your own environment means that you are 100% responsible for maintaining the wallet's security, OS environment, and network settings. In addition, running the PLSR Desktop wallet means that you must keep up with and install mandatory PLSR wallet updates and version upgrades as they are made available.

In the Pulsar Coin ("PLSR") Ecosystem, nodes are desktop installations of the PLSR wallet software that interact with each other, forming the PLSR Network. Different types of nodes, such as Seed Nodes, Master Nodes, Full Nodes, Light Nodes, and Obsolete Nodes, exist based on variations in wallet program configurations and network setups.

• Seed Node: Pre-programmed in the source code.
• Master Node: Utilizes high-end hardware and requires a 1,000,000 PLSR provisioning investment.
• Full Node: Contains a complete copy of the latest blockchain.
• Light Node: Contains a partial copy of the latest blockchain.
• Obsolete Node: Runs an outdated wallet software version; blockchain files do not sync with a majority of peers.

Node states reflect the status of a wallet installation's communication protocol and network configuration, distinguishing between using the latest or older communication protocols and whether router/firewall configurations allow specific port communication. Latest and Open states indicate up-to-date software and proper network configuration, while Outdated and Closed suggest older software versions or misconfigured network settings, respectively.

• Latest: Wallet installation utilizes the latest communication protocol.
• Outdated: Wallet installation does not use the latest communication protocol.
• Open: User has properly configured their router/firewall to forward port 5995 (TCP) to the LAN address of their wallet installation.
• Closed: User has not properly configured their router/firewall to forward port 5995 (TCP) to the LAN address of their wallet installation.  

Open

• OPEN nodes contribute to the decentralization of the PLSR network and facilitate the transmission of transactions on the PLSR blockchain. There are two requirements for a PLSR desktop wallet to reflect an "open" status: (1.) the user must "open" port 5995 (TCP) in their firewall/router settings, and once opened, (2.) the user must assign a destination LAN IP address of the 5995 traffic. (Simply opening port 5995 in the router is necessary but insufficient until the user tells the traffic where to go from the router.) The destination LAN IP address in the router's settings must reflect the internal network IP of the computer hosting the user's PLSR desktop wallet.

pulsar.conf

• Editing the pulsar.conf file is reserved for advanced users and for special network configurations. There is no need to modify it unless there is a demonstrable need to do so. However, restarting the desktop wallet program after cleaning the pulsar.conf file might help certain users allow inbound connections.

# pulsar.conf

rpcuser=username
rpcpassword=password
server=1
listen=1
daemon=1
port=5995
rpcport=5996
rpcbind=127.0.0.1
rpcallowip=127.0.0.1

Closed

• CLOSED nodes, on the other hand, are not configured to allow communication originating from other nodes. Closed nodes themselves will, however, communicate to other nodes that have successfully opened and configured port 5995 (TCP) on the destination desktop wallet. But CLOSED nodes will not accept traffic from other peers in the network.

Written in the PLSR wallet source code.

Seed nodes do not spawn through any user action or configuration. Rather, seed nodes are hard coded by wallet developers and are defined in the wallet's source code.

Seed nodes can be understood as "trusted" up-to-date sources that distribute the peerlist and other blockchain transaction information to all connecting nodes, including to other seed nodes. Because of their vital role in the PLSR network, seed nodes demonstrate high reliable up time and allow/open/forward port 5995 (TCP) to the machine running the desktop wallet software on the local area network. Seed nodes often use VPS/dedicated hardware, a static dedicated external IP address, multi-core processors, an abundance of RAM, high capacity fast NVMe storage, and wider bandwidth.

Seed Node Communication Behavior:

IN DEVELOPMENT.

Master nodes will offer another layer of consensus and security to the PLSR network -- from 3x consensus to 4x consensus. The PLSR blockchain already achieves 3x consensus through its proof-of-work ("PoW") Curvehash, PoW MinotaurX, and proof-of-stake ("PoS") mechanisms. Master nodes will add the proof-of-service ("PoSe") 4x consensus method after proper configuration, after meeting minimum hardware/network requirements and after investing 1,000,000 PLSR (1M) for activation and provisioning.

Similiarities to Seed Nodes:

• Similar to seed node hardware/network requirements, each master node requires high up time reliability, the use of VPS/dedicated hardware, a static and dedicated external IP address, allow/open/forward port 5995 (TCP) to the machine running the desktop wallet software, multi-core processors (4+ CPU cores), an abundance of RAM (8+ GB), and high capacity fast SSD/NVMe storage (20+ GB).

Differences from Seed Nodes:

• Unlike seed nodes, master node IP/DNS addresses are not programmed into the wallet's source code. And unlike most types of nodes, master nodes do not use the wallet.dat file to store transactions. Rather, master nodes are provisioned by another node type under the user's control and the masternode runs on different hardware separate from the provisioning wallet. In exchange for reliable master node security services, master nodes earn a portion of the daily blockchain emission.

Master Node Communication Behavior:

BEST: FULL Blockchain Storage.

In order to be considered as a "full node," the PLSR wallet installation possess a full and up-to-date copy of the PLSR blockchain.

Since each full node maintains a full copy of the PLSR blockchain, security is enhanced for all connected peers across the network in a trustless fashion.

Full Node Communication Behavior:

BETTER: PARTIAL Blockchain Stoage.

A light node does not possess a full copy of the PLSR blockchain. Rather, a light node only saves and distributes the latest blocks to connected peers.

Light nodes rely on and inherently trust the full version of the blockchain kept on seed nodes, master nodes, and full nodes.

Light Node Communication Behavior:

BAD: Uses older version of the desktop wallet on an outdated blockchain.

Obsolete nodes will continue to chatter among themselves in a separate, invalid, and old blockchain after a fork. Obsolete nodes arise when users fail to upgrade their wallet software to the latest valid version in a timely fashion.

While seed nodes, master nodes, exchanges, and a majority of users operate on the newest version of the wallet and blockchain, obsolete nodes form their own secluded community and operate apart from valid nodes on the current blockchain.

These obsolete nodes continue to generate proof-of-stake rewards and give the APPEARANCE of normal operation.

Avoid Operating an Obsolete Node:

• Download the latest desktop PLSR wallet: Pulsar Coin ("PLSR") Desktop Wallet;
• Use the discord PLSR wallet: Pulsar Coin ("PLSR") Discord Wallet; and
• Follow Team Pulsar Coin on social media.
• Verify your wallet version: Click Help → About Pulsar; or Click Help → Debug window → Information.

Obsolete Node Communication Behavior:

Updating binaries is necessary but alone might be insufficient.

Windows PLSR File(s): Default Locations:

• The wallet.dat file is located in: %appdata%\Pulsar\wallets.
• The blocks and chainstate folders are located in: %appdata%\Pulsar%.
• pulsar-qt.exe is located in: C:\Program Files\Pulsar.
• pulsar-cli.exe and pulsard.exe are located in: C:\Program Files\Pulsar\daemon.

Linux GUI PLSR File(s): Default Locations:

• The wallet.dat file is located in: /home/<user>/.pulsar/wallets.
• The blocks and chainstate folders are located in: /home/<user>/.pulsar/.
• pulsar-qt is located at a chosen location (I created a 'Pulsar' folder on the Desktop and place it there).
• pulsar-cli and pulsard are located in a chosen location: (I created a 'Pulsar' folder on the Desktop and place them there).

Update Procedure

1. Back up the wallet.dat file to a secure location, such as a removable thumb drive, while the old wallet program is running;

2. Shut down the old wallet program.
3. Edit pulsar.conf. Remove all entries of addnode= and banscore= and maxconnections= if present.

• An optimal pulsar.conf file uses as few entires as necessary and instead relies on hardcoded values in the source code.

# pulsar.conf

rpcuser=username
rpcpassword=password
server=1
listen=1
daemon=1
port=5995
rpcport=5996
rpcbind=127.0.0.1
rpcallowip=127.0.0.1

4. Update the PLSR binary files to the latest version.
5. To fix an OBSOLETE node, delete the blocks and chainstate folders while the wallet is shutdown/closed.

6. Restart the wallet.