Help us build the world's largest Digital Payment Network & earn passive $PAC income

ROI / Year: 63.78%
MN Price: 0.145 BTC | 497 USD
Network: 6249 active Nodes
Get the Android App
Get the iPhone App
Masternode Setup Guide
Use the Calculator to see your Rewards!

IMPORTANT: As of October 2018, there has been a mandatory Update / Fork to the Blockchain! Please review the Forks Documentation to make sure that your Masternode is running on the correct Blockchain!

Why invest in a Masternode?

Multi-faceted benefits and rewards.

The Masternode system utilized by Peoples Alternative Choice (PAC), provides three powerful and unique benefits to becoming an investor. Compared to other alternatives in various currencies, PAC has structured the investor reward system to yield high benefits as a return for supporting and helping grow the project. Holding stakes of coins in the locked Masternode system offered by PAC is a way for investors to:

(1)Obtain direct voting stake in their investment organization as a direct percentage of their invested coins locked safely in a decentralized wallet system,
(2)Generate significant free cash flow (FCF) at an outstanding Return of Investment ROI rate shown in current statistics below (about %70),
(3)Support key underlying network structure to PAC financial; to operate lightning fast and secure transactions globally with almost no fee.

Support robust $PAC blockchain.

Stable, safe and speedy transactions of the PAC network is the product of our hybrid blockchain system that utilizes carefully chosen aspects two well-known technologies, Proof of Work (POW) and Proof of Stake(POS) methods of verifying blocks. For more information on our blockchain and our ambitious goals and achievements please read more in our whitepaper under our about section.

Store assets safely and let it grow.

Specifically, Masternodes provide the POS portion of the verification process. Coins locked in private wallets in a block of 500,000 $PAC are linked and broadcast through servers as discussed in the Setup Guide. As a reward for hosting a robust and expansive network, each Masternode is currently rewarded 10,350 $PAC when selected for block verification. This timeline is dependent on the total number of nodes which is detailed in statistics as detailed below.

Contribute guidance via structured governance

Shaping of $PAC is done through a governance structure known as the Decentralized Autonomous Organization (DOA). This system offers investors a unique structure in controlling the future of their assets. As a Masternode investor, you have voting stakes on the community driven PAC governance system where individuals or entities can make proposals for projects they think would add value to the Coin/Network. Please refer to the Governance Section for a detailed walk-through of this system.

How to invest in a Masternode?

Choose between full Masternode or shared options.

There are two methods currently to become a part of the full featured reward system described above; by either a full Masternode (500,000 $PAC) or a shared Masternode (as little as $100 PAC). Each method has its benefits can be outlined in the following way:

Full Masternode:

  • Masternode receives full rewards, minus any hosting fees
  • Availability for independent hosting
  • Full voting rights

Shared Masternode:

  • Lower collateral to generate rewards
  • Receive a weighted portion of rewards
  • Joint community voting system

Decide to host with a provider or independently via our guides.

Hosting your own node can be challenging and require technical ability and dedication to monitoring and maintaining the Masternode. To host a full Masternode in the PAC Network, you need to host a server with the PAC Masternode software installed while linking collateral of 500,000 $PAC. The collateral stays locked safely via a local wallet on a personal computer and cannot be spent while the Masternode is active.

The Node must be online 24/7 and in healthy condition to remain in the queue, a restart or disconnection from the network would result in a reset of the payment queue position.

Provider Hosted:

  • Hands off and worry-free service with almost zero downtime
  • Access to direct monitoring and service features
  • Direct customer support
  • Almost no technical skills required

Independently Hosted:

  • Lower fees at the cost of the hosting server of choosing
  • Advanced node setups, for technically advanced investors
  • Direct access to voting independently
  • Receive rewards directly and quicker access to funds

Learn more about the whole process!

The purpose of this web page is to inform new and existing investors of the elaborate and constantly evolving Masternode and governance system. Information contained in each section is aimed to help any investor become properly equipped; to be a driving force behind PAC as an organization. We hope every coin holder, regardless of the amount, discovers a place in our community and an enjoyable way to participate in their investment.

Page Development:
Special thanks to the community and PAC team members that offered prolonged effort into making this page possible. Discord members and their role:
@Lostintime#2827 – Development, page structure, stats, content
@dijida(US)#9874 – Content creation from his independently hosted setup guide
@Bearro#1284 – Development, content in all sections.

Get a hold of any of these members directly to comment and offer feedback. To offer suggested changes or site improvement ideas, please contact @Lostintime on discord!

Minimum number of coins needed:

As previously mentioned, the two methods currently to become a part of the full-featured reward system described above; by either a full Masternode (500,000 $PAC) or a shared Masternode (as little as $100 PAC).

Purchasing and storing coins:

If you are going to host your own Masternode on use a service that requires you to send $PAC; the first step in getting started with your investment is to purchase coins from currently available sources. Avenues are constantly growing for obtaining $PAC, please check our website for the latest price and locations to get a hold of your $PAC: Paccoin.net/exchanges/

Storing of coins:

Once you get the coins desired for your investment, we have a wide array of wallets to help you move and store your coins. Currently available we have an Android app, iOS app, paper wallets, Mac-Windows-Ubuntu core wallets and electrum wallets. Specifically, to store your coins for remote hosting, you will likely use standard desktop wallet. All the latest versions can be found at Paccoin.net/wallets/

Choosing how to host:

In the intro section, we discussed the benefits of hosting your own Masternode versus using a paid service to do the hosting. There are apparent challenges associated with hosting your own node, however, if you have the skills and are willing to overcome the difficulties of hosting your own server please see the Setup Guide for more detail. Note that by doing your own hosting you are responsible for your own setup. The guide and support PAC gives to independent node setup is solely support the community but does not guarantee the performance of your Masternode!

If you decided you’d like to have your coins hosted keep in mind that PAC is not responsible for your coins and your decisions to use a service. Currently, PAC does not operate an official service. Even though we have outstanding unofficial services, by using any of the following services are all 3rd-party, make sure to do your own research, PAC offers no liability for using them.

PACnode
URL: https://pacnode.net/
Discord: https://discord.gg/ce9c5rh

NodeHub.io
URL: https://nodehub.io/
Discord: https://discord.gg/WWMwmJE

SimplePOSPool
URL: https://simplepospool.com/
Discord: https://discord.gg/EfuYpAS

2masternodes
URL: https://2masternodes.com/pac-masternode
Telegram: https://t.me/en_2masternodes

PAC Masternode Setup Guide

If you have read all the considerations in the introductory sections, and have decided you’d like to take on the challenge of setting up and running your own Masternode; please keep in mind to do so at your own risk. PAC offers very limited support to independent hosting due to the complexity and solely as a service to better our investor’s options, however, we do not guarantee the performance of nodes you set up on your own.

The setup of Masternodes is technical and requires hands-on experience but can be rewarding in several ways. Huge thank you to the developers for their constant upkeep of the masternode system, and special thanks to @dijida in discord for his prolonged development of content for this masternode guide.

These Instructions Are ONLY for hosting your masternode on Ubuntu 16.0.4.

Although some masternode users have successfully used other Linux distributions/versions (e.g. Debian, Ubuntu 18) and even Windows, this guide is only meant to work with Ubuntu 16.Going through this guide for the first time should take around 30 minutes to an hour. If you have already set up a masternode, you can use the quick One Page Guide. Also, follow along with the One Page PDF document.

SAFETY WARNING:
Our discord community is a great place to get help and guidance, however, to protect your investment NEVER send any files or sensitive information to anyone helping you. There have been several fake accounts targeting investors seeking help. Please report any suspicious activity to a moderator.

Basic $Pac Network Overview

There are 2 separate parts to a Masternode setup: Your Cold Wallet (installed on the desktop) and your Hot Wallet (installed on the server). In this guide, we will be using “cold” and “desktop” interchangeably, as well as “hot” and “MN/server” as shown below.

For the purposes of this guide, there are 3 main components of the $PAC Masternode Network that are important (this is not meant to be an exhaustive explanation of how the network is constructed. If you need more information, you can Google it).

  1. Desktop with $PAC Wallet installed (also known as the cold wallet): This is the main $PAC wallet, where you can send and receive $Pac, where the 500,000 $PAC collateral will be stored, as well as remotely starting your Masternode and broadcasting its address and collateral id onto the $PAC Network.
  2. VPS with $Pac Masternode software and Sentinel installed (also known as the hot wallet): This is where the $Pac MN process paccoind participates in the second tier of the $Pac network, supporting instant sends (instantPAC. It is also where the sentinel program resides, which periodically broadcasts your MN presence to other Masternodes.
  3. $Pac Network: This is where the core nodes and all of the other $Pac Masternodes reside. Both your desktop as well as your Masternode connect to the network to synchronize their copies of the $Pac blockchain and, importantly, this is where your Masternode gets validated. The network of $Pac MNs also decides which MN will receive the next block reward.

Section 1: Configure Your Desktop (cold) wallet

You now have a text editor, ssh environment, and (optionally) ssh key pair generated.
We are now ready to install the official $PAC Desktop (cold) wallet.

Make sure that you download and install the latest $Pac wallet from the official $PAC website at https://wallets.paccoin.net/. The current version is v0.12.5.1 which you can verify by going to “About PaccoinCore” in

  • Windows: File -> About
  • Mac: Paccoin Core -> About

Prerequisite of 500K $PAC Masternode Collateral

You will need 500k $PAC in your cold desktop wallet in order to collateralize your masternode.

IMPORTANT SECURITY TIPS!
Now that you have larger stakes stored in your wallet, it is HIGHLY RECOMMENDED to ensure you have several security measures in place.

  • Make sure wallet is encrypted by going to Settings -> Encrypt Wallet… and choose a very strong quality password that you will always remember or keep track of!
  • Store backups of your wallet in a safe location, preferably on an encrypted flash drive separate from your computer running the masternode. To backup go to File -> Back Up Wallet…

Step 1: Enable Masternode Tab

Your cold wallet (desktop wallet) is used to remotely “start” your masternode on the $PAC network. What starting it does is broadcast your MN onto the $PAC network along with its IP Address and Collateral Output, which will be verified and then synchronized across all running MNs (Your MN is actually running remotely in your VPS which we will install in step 3 later). This is an important step as the network of masternodes needs to verify, validate, then include your masternode onto the network.

In order to enable this capability, first, we need to show the “MasterNodes” tab along the left-hand side of the cold wallet, which normally isn’t visible. Follow the steps below based on your computer’s operating system:

Windows:

Choose Settings -> Options to open the options window.
win-pacoptions

Mac OS:

Choose Paccoin Core -> Preferences to open the options window.

mac-pacoptions

Adding the masternode tab on both Windows and Mac :

1. Click on the Wallet Tab
mac-wallet-pref

2. Select “Show Masternodes Tab”

You may want to also select “Enable coin control features” for convenience (recommended). If you don’t know what coin control is, don’t worry about this or any of the other checkboxes for now. The only one you really need to select is “Show Masternodes Tab”.
3. Click “OK” to close the options window
4. Close and restart the cold wallet. You should now see the “Masternodes” tab on the left hand side below “Transactions”.
mn-tab

Step 2: Generate Private Key

Now that we’ve restarted the $Pac cold wallet to show the masternodes tab, we need to generate a Masternode Private Key for your Masternode.

Each Masternode has a unique set of parameters used for identification and validation in a unique set of values for each Masternode:

  • Unique Masternode Private Key for secure remote starts from cold/desktop to hot/masternode (this step).
  • Unique Masternode IP Address for your MN VPS to participate in the MN Network and second-tier functions e.g. InstantSend
  • Unique Masternode Wallet Address – the address where your MN rewards are sent.
  • Unique Masternode Collateral Output – transaction output id of the 500K $PAC that you sent to yourself.
  • Unique Masternode Label to be used in your desktop/cold wallet’s masternode.conf file

Don’t worry if all of the above doesn’t make sense to you now, they will be explained as we continue the masternode setup.

The Private Key is used as a shared secret between your desktop cold wallet and your remote masternode, which is then used to authenticate RPC (remote procedure call) commands from your cold wallet. You’ll need the Private Key in subsequent steps. Be sure to have your [Text Editor](/first-steps#text-editor) ready.

  1. From your $Pac Desktop Wallet, select Tools -> Debug Console
    PAC Tools Debug
  2. You will see the following window, with a command line box at the bottom where you can type in commands:
    PAC Debug Console
  3. Type the following command in the input field (see the blue arrow above), or you can also just click the copy icon below to copy the command onto your clipboard and paste into the field using: Ctrl+V (or Command+V for Mac).
    masternode genkey
  4.  Press Enter, and you will see a long alphanumeric string of characters as in the screenshot below. This is a new Private Key for your Masternode.
    PAC Masternode Genkey
  5. Select the whole sequence of characters, making sure you don’t miss any characters, then copy/paste them into your text editor. We will need the MN Private Key you just created in 2 different places as part of the setup. Once you’ve copied the MN Private Key to your text editor, close the Debug Console and return to the main wallet screen.

Step 3: Collateralize Masternode

The number of $PAC coins needed to collateralize a Masternode is exactly 500k (500,000). You will need to send this exact amount to yourself from your desktop wallet. You will need a little bit extra to cover transaction fees (1 extra $PAC will be more than enough to do the trick). But first, let’s create a new address to hold onto these coins.

Create Unique MN Wallet Address

Every MN you own needs to have a unique label. If this is your first Masternode, you can label it “MN1”, or whatever else suits your fancy. Follow these steps and refer to the screenshot:
PAC Masternode Receive Address

  1. Select the Receive tab on the left-hand side of the cold wallet.
  2. Type the name for your Masternode’s _receive_ address (e.g. “MN1”, in the screenshot it is labeled “MyMN1”).
  3. Type in 500000 in the Amount field (make sure “Subtract fee from amount” is NOT selected)
  4. Click the “Request Payment” button. A new dialogue window will appear, similar to the screenshot below:<
    PAC Masternode Request Payment
  5. Click the “Copy Address” button, which will copy the address into your clipboard. Close the dialogue window to return to the main wallet and proceed to the next step.
The image above is just an EXAMPLE please don’t send any $PAC to that address. The address you generate with the steps above will be unique to your wallet.

Step 4: Send 500k Collateral

We will now send the required 500k $PAC collateral to the unique address we just created above. Since we also created a unique label (e.g. “MN1”), we can easily identify the correct address when sending it to ourselves. See the screenshot below and carefully follow the steps:
PAC Masternode send collateral

    1. Select the Send tab on the left-hand side of the desktop wallet.
    2. Click your cursor into the “Pay to” field and paste the address we just copied (Ctrl+V for Windows, Command+V for Mac). The “Label” field will automatically display the unique name we entered previously. *If* it doesn’t auto-populate, then return to the Receive tab, select your newly created receive address, double-click it to open up the dialogue and copy the address again (step 5 above), and paste it again.
Be Careful!
Make sure to double check that you are sending to the correct address in the steps above. Additionally, if this is not your first Masternode, be sure to create a unique label and address for each one of your Masternodes. Not doing so will cause you a lot of grief as reusing addresses will mean you will only get paid for each unique.
  1. Type in exactly 500000 in the “Amount” field, making sure “Subtract Fee From Amount” is NOT selected or the instant send feature
  2. Click “Send” at the bottom of the screen.
  3. Enter your passphrase when prompted, select “Yes” to send, and your 500k $Pac transaction will be sent to the network to be confirmed on the blockchain.

Step 5: Get Collateral Transaction Id

Now that you’ve sent yourself the necessary 500k $PAC collateral to a unique MN wallet address, we need to wait for 15 confirmations of the transaction. You can see how many confirmations your transaction has by selecting the “Transactions” tab and hovering your cursor over the transaction entry.

Initially, your transaction is sent to the memory pool to be validated for its first confirmation. Every block that is mined “confirms” all previous transactions on the blockchain. $Pac aims to average 2.6 minutes per block, and you need 15 blocks to be mined and added to the blockchain before your MN collateral is valid to enable your Masternode. These times vary with network difficulty and network hashing power. You can see updating blocks as they move from the official $PAC explorer or the $PAC Insight Explorer. You can also get average daily blocks mined as well as a wealth of other information from sites such as Masternodes.online.

Once your transaction has at least 15 confirmations, follow the steps below to create the Collateral Tx Id needed:

  1. From your $PAC Desktop Wallet, select Tools -> Debug Console
    PAC Debug Console
  2. You will see the following window with a command line at the bottom to type commands:
    PAC Debug Console
  3. Type the following command in the input field (see the blue arrow above). You can also click the copy icon below to copy the command onto your clipboard and paste them into the field using: Windows: Ctrl+V or Mac: Command+V.
    Display Collateral Tx Id

    masternode outputs
  4. Press Enter, and you will see a long alphanumeric string of characters in quotation marks, a colon, then either “0” or “1”, as in the example below:
    This is an EXAMPLE ONLY, you must use your UNIQUE values for every new MN instance:

    {

    “a89rhtuyf23jd84120942acce447830aa83lkdl3k39s73m” : “1”

    }

Step 6: Prepare and save masternode output for later

  1. Copy only the line and full string(not the ‘{‘ and ‘}’ brackets) and paste onto your text editor.
  2. Remove all quote characters (“) as well as the colon (:) and make sure that there is a single space between the end of the long string and the “0” or “1”. From the example above, your final string should look similar to this:
    This is an EXAMPLE ONLY, you must use your UNIQUE values for every new MN instance:

    a89rhtuyf23jd84120942acce447830aa83lkdl3k39s73m 1

    This is your unique collateral tx id for this Masternode.

    If this isn’t your first Masternode, you will see multiple entries (1 for each MN’s worth of 500K you’ve sent to yourself). Make sure you choose the new entry for the MN you are currently configuring. Not doing so will cause a lot of grief and prevent your Masternode from properly starting.
  3. Close out of the Debug Console and return to the main wallet screen.

Section 2: Communicating with your hosted MN Server

Step 7: Prepare SSH connection

In this step we will set up a secure connection method we will use whenever we need to access our masternode server. Some servers have consoles for connecting directly on their sites however the smoothest method is to connect via a client and terminal directly from your computer.

7.1 SSH Client:

SSH is a secure network protocol for communicating with your remote Masternode server. If you are using Mac OSX as your desktop wallet, then you already have an ssh client installed via the terminal application. If you are on Windows, you can download the free and opensource Putty program. Another good Windows ssh client is Bitvise. Once downloaded and installed, proceed to the next step.

7.2 Generating SSH Keys:

Configuring SSH keys for your local desktop machine will save time as you can export your public key to your MN server and only remember a single password instead of having to type the password to your remote server every time you login.

Windows

Easy Instructions from the Joyent docs for configuring a new ssh key pair for Putty. If you are using Bitvise, easy instructions are found here

Follow all of the steps including step 8. Now that your public key is copied to the clipboard, paste it into your text document of your choice and save in a secure location for later use.

Mac OSX

Follow this link from the Github help docs for instructions on generating a new ssh key pair.

Once you’ve followed those steps, then:

  1. Execute the command below to copy your newly generated public key onto the clipboard:
    pbcopy < ~/.ssh/id_rsa.pub
    
  2. Paste them into your text editor (Command-V).
We’ll be using the public ssh key you just generated above when we deploy our virtual private server to install the Masternode software. Be sure to follow the steps and paste the public key into your text editor to have it ready to go.

Section 3: Install Your Masternode Server (VPS)

Your Virtual Private Server (VPS) hosts the $PAC Masternode software and contains your hot wallet. While your cold wallet (running on your desktop or laptop) can be shut down and offline, your hot wallet must be always running and connected to the internet. We are now ready to install the Masternode server on your VPS.

Choosing a VPS Host Provider

There are many VPS hosts out there. This part of the guide will walk you through setting up your $Pac Masternode on one of the most popular hosting providers, Vultr.

Attention
While this Guide is based on Vultr, $PAC is in no way affiliated to them. Your hosting contract will be between you and the VPS provider you choose. The setup process will be similar across providers as long as using Ubuntu 16.04.
Here is a list providers that have been proven stable and are recommended by our community:

If you are setting up your Masternode on a different VPS host, most of the general process should be the same except for Vultr specifics. Once you have finished registering and setting up your account information, you can proceed.

When setting up your VPS hosting account, please make your passwords are secure.

Step 8: Create New VPS

Setup using (Vultr): Skip to 8.4 for Amazon Lightsail

Once you login into your Vultr dashboard, click on the “Server” tab on the left-hand side. Refer to the screen shot below:

  1. Click on the blue circle to create your virtual private server to host your $Pac Masternode.
  2. Choose any server location, as seen in the screenshot below. Just please don’t pick Miami. I don’t know why, but I’ve had several users with issues in that datacenter location with Vultr. I myself have had issues there as well, with random reboots. Any other location should be fine.
    Vultr has a lot of data centers you can choose from to host your VPS instance. Refer to the screenshot below and follow the next step:

PAC Masternode Vultr Location

Although you can pick whatever you want, I personally recommend choosing a US-based server. Why? As of this writing, almost 45% of the Masternodes currently on the network reside in US-based datacenters. MNs, especially when first starting, need to constantly sync and communicate with each other. If you choose a data center location that is far away from a community of MNs then it will take a little bit longer for each communication. You can see the current $Pac Masternodes map at the $Pac Explorer site

8.1 Choose Server Type and Size

In this step, you will select the operating system for your Masternode as well as the virtual server size. The recommended operating system is Ubuntu 16.04 and the recommended VPS size is the $5/mo plan on Vultr which has 1024 Mb of RAM for the VPS.

Please note, 512 Mb servers are much more likely encounter errors. This is because the installation running the node uses almost the full amount of available memory, any spikes in RAM usage can lead to failures and crashes. Therefore, it is reccomended to allocate 1024 Mb to any device hosting a Masternode, to avoid overloading the instance and provide reliable performance.

I know lots of users host multiple masternodes on their vps, or use Debian, or install the MN on a Raspberry Pi. More power to you if you can do it. However, using Ubuntu 16.04 and 1Gb RAM ($5/mo plan) is the recommended configuration and will give you the smoothest Masternode experience.

  1. Select Ubuntu 16.04
  2. Select the $5/mo plan (25GB SSD, 1 CPU, 1024MB Memory

PAC Masternode Server Type

8.2 Configure SSH

If you recall from the First Steps section, we generated ssh keys for communicating securely with our Masternode server. Have your text editor ready where you previously copied your public ssh key and follow the steps below, referencing the screenshots:

  1. Click “Add New” button under the “SSH Keys” section which will lead you to the screen below:
    PAC Masternode add SSH
  2. Enter whatever name you would like in this field.
  3. From your text editor, copy your public SSH keys and paste it into this field.
  4. Click the “Add SSH Key” button.

Now you are back to the previous screen. We are nearly done setting up the vps.

8.3 Set Hostname and Deploy

Setting a unique hostname for your Masternode vps can be quite handy, especially if you plan on setting up more than one Masternode. I recommend setting a name for your vps host which is the same as the Unique MN Receive Address you configured in Setup Step 2. This will help you keep track of your Masternodes, especially when you are running multiple MNs.

Refer to the screenshot below as you follow the next steps:
Deploy PAC Masternode Server

  1. Enter a hostname for your vps, e.g. “MyMN1”.
  2. Click the “Deploy Now” button.

You will be sent back to the Servers tab of your Vultr dashboard and see something like the screen shot below:
Vultr Servers

  1. Click the “copy” icon next to the VPS “IP Address” and paste it into your text editor. We will need that IP Address in the next section when we install the $Pac Masternode software.

Make sure to double check all of your information. You’ll notice that following the naming scheme (MN1, MN2, etc) as explained in this guide will make your life much easier, especially as you invest in more $Pac masternodes. Also, in the screenshot, in the upper right, you’ll see some icons that may come into use at a later point in time to stop and restart your VPS.

8.4 Amazon AWS Lightsail (stock limit 2 per location)

Create a similar instance like the one created in Vultr example above. Using light sail has a few extra steps to consider we will outline. There is only small numbers running on this setup so assume the risk in trying this setup. More detail will be added as we hear more verifed instances up and running.

  1. Create new instance- 1gb, name as MN number and other desired details, such as location, size and version.
  2. On network tab edit firewall exceptions, remove only HTTP TCP 80 add new exception for Custom TCP 7112 this will allow PAC network to connect to your node. If you have any connection errors check back here and make sure it is set up correctly
  3. Create Static IP from networking page and make sure its attached to your node and name it with MN #. This will be your MN IP so keep this static IP documented and use with any step requiring MN IP.
  4. Connect using SSH or via the network browser. Read Amazon documentation on how to use either method.
  5. Uniquely Amazon instances login “ubuntu” user and this won’t work for a PAC masternode setup so we will always have to login into root after we do our main login to Ubuntu.

Login to root and navigate to root directory (to proceed with proper installation):

sudo su
cd /root

Proceed through the rest of the process as normal. When you run out of instances in a location you can request new amount using support or start up to two more per location. Amazon has approved 10 instances, after asking for the purpose of this guide. This was done creating a support ticket and telling them about the use with PAC and clearly stating this is not mining, rather network support.

Section 4: Install $Pac Masternode Software

Step 9: Login via SSH to your Remote VPS

From your desktop, we’ll first set up a secure remote ssh session to the VPS you just created. Follow the instructions below for your particular operating system. You will need the IP Address of the newly-created VPS.

  • Windows:
    You can find instructions on connecting to your VPS via putty using the link below. Go to the section labeled “Log in to PuTTY with the private key”. These instructions can be found here:
    https://support.rackspace.com/how-to/logging-in-with-an-ssh-private-key-on-windows/.
  • Mac:
    Open Launchpad and search for the application “Terminal”. A basic terminal shell window will open. You may want to resize the window so it is easier to see the output. Type the following into your terminal shell
ssh [email protected]_IP_ADDRESS
    1. In your terminal shell at the prompt, type the line above, replacing ‘YOUR_IP_ADDRESS’ with the IP address of your VPS. For example, if the IP Address is 127.0.0.1, you would type ‘ssh [email protected]’. See the screenshot below as an example:
    2. Press Enter.
    3. You will be prompted for the passphrase you entered when generating your ssh key pair. Type in your passphrase and hit enter.

Step 10: Update VPS (optional), 

It is optional but recommended to keep your server up to date with the VPS Service provider’s updates, when convenient. Shouldn’t change from 16.04.x version but may address security risks and bugs recognized by the VPS host provider.

When loaded into the server using the update command:

sudo apt-get update && sudo apt-get dist-upgrade

When prompted to continue to choose yes by inputting “Y” and hit Enter. You May also be prompted for additional settings depending on the update. In those cases choose the default option by pressing Enter.
This will take some time, please wait for everything to finish and the server to return to awaiting next command.

Step 11: Add swap space (required!), then reboot

As a new requirement to the $PAC network, VPS servers must have at least 1 Gb of ram and adequate swap space installed.

To install swap space to your VPS, use the command:

sudo fallocate -l 4G /swapfile && chmod 600 /swapfile && mkswap /swapfile && swapon /swapfile && echo '/swapfile none swap sw 0 0' | sudo tee -a /etc/fstab && free -h

Lastly, finish these two steps by re-booting the VPS. This can be done manually via the hosting website or remotely using the SSH window with the command:

sudo reboot

This will disconnect from your SSH session please allow about 20 seconds or more for the server to start up again and proceed to the next step.

Step 12: Re-login, Check version, swap memory, and Set Language Locale

Re-login to your VPS and first take a look at the welcoming screen at login. It should say that you have 0 updates pending and you should have noticed your version change to 16.04.x -this means your update was successful and can continue with setup. If there’s still updated re-run the update commands from the previous section and reboot.

Now check to make sure your memory allocation took properly by running this memory check command:

free -h

Here you should see that you have a total of 1 Gb of ram and 4 Gb of swap space. If for some reason the change did not take effect, re-try the memory commands from the previous section and check again. Ensuring you have adequate memory is an important step!

The last step before installing the masternode software is addressing potential issues with language locale.

If you are not using English on your desktop machine, you will need to execute the following steps. This is necessary because part of the $Pac Masternode install process involves setting up a support process called Sentinel. However, this process will fail if your VPS is set to a non-English locale. When you connect to your VPS remotely via ssh (as in the prior step), your ssh client will automatically set your desktop locale to the ssh session of your remote VPS. This means that if you are in Paris, even if your VPS location is in New York, your ssh session will be set to the French locale and your $Pac MN install will fail.

Copy and paste the following into your ssh client and press enter to set english locale:

export LC_ALL="en_US.UTF-8"

Step 13: Install $Pac Masternode Script

Next, we will install the $Pac Masternode software from the official $Pac Github Repository.

Navigate to root directory (AWS Lightsail or non-root servers):

sudo su
cd /root

The next command will pull down the installer script for the $Pac MN process (paccoind) as well as the Sentinel process (more on this later).

$Pac MN Installer

wget https://raw.githubusercontent.com/PACCommunity/PAC/master/pacmn.sh && chmod +x pacmn.sh && ./pacmn.sh

If you copied the code, you can simply paste using – Windows: Ctrl+V or Mac: Command+V into your ssh client. In Putty, you might have to paste via SHIFT+Right Click.
If you typed it in, press Enter to continue.

PAC Masternode SSH Client

You will be prompted for 2 pieces of information:
1) Your VPS IP Address from the previous step, and
2) Your Masternode Private Key (Output from “Masternode Genkey”).
Both of these should be in your text editor from previous steps. Enter the information when prompted and press enter.

PAC Masternode SSH Installer

You’ll see a lot of information scrolling through your ssh terminal session as the installer script first installs, and then starts your Masternode server process paccoind and the support process sentinel (along with its entry into crontab).

You will see a lot of information scrolling in the window as the installer progresses.
If you see ANY ERRORS, do not continue with the following steps, just bookmark your progress here, and refer to the troubleshooting section of this guide. Most of the errors I’ve seen are with the sentinel install at the end of the process.

At the very end, you should see a message indicating that your $Pac MN and Sentinel has been successfully installed.

PAC Masternode SSH Installed

Step 13 Install $Pac MN Service

Next, we will add an entry into systemd which will do two very important things:

      1. Auto-start your $Pac Masternode paccoind” process when your  VPS boots up (or reboots). This rarely happens, but it can happen if there are issues on the Vultr side with their hosting equipment.
      2. Restart your paccoind” process immediately if the process fails for whatever reason. This is also rare, but better safe than sorry.
Note This script is from @foxD#0976, one of the $PAC developers. Give him a huge thanks on Discord!
$Pac SystemD Service:
wget https://gist.githubusercontent.com/foxrtb/b703ae761472c5599c4d83ab0d3d62ae/raw/e8913deb9e1b7cc9c649febd2942930e4f6f5127/add-systemd-from-script && chmod +x add-systemd-from-script && ./add-systemd-from-script

You should see something similar to the screen shot below:

PAC MASTERNODE SSH-Restart

Step 14: Verify Synchronization

Before our masternode can be remotely started from our desktop wallet, we want our MN’s local blockchain, masternode list, governance objects, etc, to be fully synchronized with the $PAC network. To do this, execute the following command and wait until the “AssetId” field shows as “999” in the screenshot. This can take 30 – 60 minutes. To check again, simply press the ‘UP’ arrow to display the previous command and hit enter.

Check Sync Status:

./paccoin-cli mnsync status

You should see something similar to the screenshot below when your MN is fully synced:
PAC Masternode SSH Synced

Section 5: Start Your Masternode

Next we’ll edit a special file on your desktop wallet named `masternode.conf` and “Start” your MN on the $Pac network.

Step 15: Edit Masternode Configuration

On your cold (desktop) wallet installation, there is a special file called “masternode.conf” which contains information needed to properly remote start and broadcast your new MN to the $Pac network. To access this file, from the main toolbar on your wallet, go to Tools -> Open Masternode Configuration File:

PAC Masternode Configuration File

This will open the file `masternode.conf` in your text editor. The first 2 lines of the file are commented out using the `#` character and show the format needed. We’ll need to enter the following 4 pieces of information that you should already have in your text editor:

      1. alias – this is the unique name for your Masternode. If you followed the recommended naming convention this will be something like MN1, MN2, etc.
      2. IP:port – this is the IP Address of your Masternode VPS. Your IP Address in this file needs to be appended with ‘:7112’. For example: 175.145.10.150:7112
      3. Masternode Private Key / Genkey – this is the private key we generated by typing “masternode genkey” in the Tools Console of the PAC Web Wallet.
      4. Collateral Output and Index – this is the collateral id and index of the 500K $Pac we sent to collateralize our Masternode, which we received by typing “Masternode Outputs” in the Tools Console of the PAC Web Wallet after our Transaction had received 15 confirmations.

PAC Masternode Config

Referring to the screen shot above, add your Masternode information on the 3rd line. Make sure that you have exactly one space between sections 1, 2, 3, and 4. Also, verify that you have `:7112` on the end of your IP Address, and that there is a space at the end between your collateral tx id and index (the index will be either a `0` or a `1`).

Once you’ve double checked the entries, save the file, and close out of your editor.

Go back to the $Pac Desktop Wallet, and close the program. Restart your $Pac Desktop Wallet so that it can read the configuration information for your newly configured remote MN.

Step 16: Start Your Masternode

Once you restart your desktop wallet, go to the “Masternodes” tab. From there you should see your newly configured Masternode displayed in the table as shown below:

PAC Masternodes Tab

      1. This is the alias you configured previously (“MyMN1” in the screen shot).
      2. This is your remote MN’s VPS IP Address with `:7112` appended at the end.
      3. This is your **Unique** $Pac receiving address where your Masternode Rewards will be paid to.

These next steps will “start” your Masternode on the $Pac network as well as broadcast to the network your MN’s IP Address and collateral tx id (needed for validation).

      1. Select your Masternode in the Masternode’s table.
      2. Click the “Start Alias” button:
        PAC Start Masternode
      3. Select “Yes” and enter your wallet passphrase when prompted, then hit ok.

Now that the Masternode is started, let’s check to see that it started sucessfully on the remote VPS.

DON’T WORRY ABOUT THE “STATUS” FIELD ON YOUR DESKTOP WALLET!
The status field is incorrect much of the time. It is a known bug that will be addressed in future updates (inherited from the Dash wallet), so don’t worry about what is displayed there.

Section 6: Verify Your Masternode Status

The following commands to help verify your overall setup, these are also a few key commands when verifying problems on a server.
Use the up arrow to re-run the commands and you are monitoring status changes. They remain in log as long as the server is up and can be quickly accessed even after you relog in. If locked into the wrong command use Cntrl + C to exit certain commands.

Step 17: Check Masternode Status

Go back to your ssh client and copy/paste the following into your terminal:

./paccoin-cli masternode status

You should see something similar to the screenshot below. Make sure that the status says “Masternode successfully started”:
PAC Masternode Status

Double Check Service Status (If installed)

If you had installed the systemd service copy/paste (or type) the following:

$Pac SystemD Service

systemctl status pacd --no-pager

Check to make sure status is green and there are no errors. This service will help prevent downtime due to failures in the future so it is important is running properly after the status of the rest of your system is running.

As of 2018-10-04 Large percentage of masternodes crashed due to swap memory, even if they were hosted with 1GB RAM. The service above could have potentially saved those masternode servers from crashing. If the service not installed yet make sure to do so with via SSH:

wget https://gist.githubusercontent.com/foxrtb/b703ae761472c5599c4d83ab0d3d62ae/raw/e8913deb9e1b7cc9c649febd2942930e4f6f5127/add-systemd-from-script && chmod +x add-systemd-from-script && ./add-systemd-from-script

Double Check Free Memory Allocation

As stated before, it is not a good idea to max the memory. If future updates or something causing the memory to spike it may cause your instance to crash.
Use this command to check memory status now that everything is installed to confirm you have at plenty of free memory available.
Checking memory

free -h

As of 2018-10-04 swap memory is REQUIRED.  Large percentage of masternodes crashed due to swap memory, even if they were hosted with 1GB RAM. If the above step returns no swap memory, please use this script when connected to your Masternode server via SSH:

sudo fallocate -l 4G /swapfile && chmod 600 /swapfile && mkswap /swapfile && swapon /swapfile && echo '/swapfile none swap sw 0 0' | sudo tee -a /etc/fstab && free -h

Note that Linux memory is different and the buff/cache is the available memory.

Congratulations!

Once your masternode has the Enabled status you have set up your node correctly! This doesn’t mean your hands-off now, however. Because you chose to host a masternode independently, it is your responsibility to constantly monitor and maintain your masternode! Closely watch discord, twittter, and the PAC main websites for any updates that may affect your node.

To monitor your node you’ll find more information in the Monitoring section of this page. Keep a close watch as its more likely for an error to arise within a couple days of setup.  If an error occurs, please see our Troubleshooting section to diagnose where the error is coming from.

Lastly, now that you are officially a masternode investor, head over to the Governance section to learn more about how you vote and help grow your investment to new heights! You’ve now unlocked crucial responsibility of directing your portion of the PAC organization!

Quick Setup (QS) Guide

For those of you who have gone through the setup process before, here is an abbreviated setup list. Check with the main setup guide for any details you may need. The numbers of this quick setup guide correspond to steps in the detailed guide. Feel free following along with the one page PDF document.

QS.1. Enable Masternode Tab in your Desktop Wallet: Tools -> Options/Preferences -> Show Masternode Tab. Restart Desktop Wallet.

QS.2. Generate Masternode Private Key: Tools -> Debug Console. Enter the following:

masternode genkey

Copy the key generated into your text editor, save for later.

QS.3. Collateralize Masternode: Create a unique Receive Address (e.g. “MyMN1”, “MyMN2”, etc), and copy this address to your standby text editor. Each MN you own needs its own unique address.

QS.4. Send exactly 500K $Pac to the address you generated above. Wait for 15 confirmations.

QS.5. Get your output: Tools -> Debug Console, type the following to display collateral Tx Id:

masternode outputs

You will see a line for each masternode’s 500K collateral, so if this is your second MN, you will see 2 lines. Copy the new line to your text editor (or the single line if this is your first MN).

QS.6. Edit the output string in your standby text editor. Remove all double quotes, and make sure there is a space between the end 0 or 1. It should look something like the following in your text editor. This is an EXAMPLE ONLY, you must use your UNIQUE values for every new MN instance:

a89rhtuyf23jd84120942acce447830aa83lkdl3k39s73m 1

QS.7. Prepare SSH login tools and set up SSH software and keys.

QS.8. Create a new VPS instance and choose Ubuntu 16.04 and the $5/moplan with minimum 1Gb of space. Set your ssh keys, set the hostname to the same name as your Receive address in step 3, e.g. “MyMN2” and deploy your instance. Select your VPS and copy its IP Address into your text editor.

QS.9. Log into your VPS instance via SSH.
Navigate to root directory (AWS Lightsail or non-root servers):

sudo su
cd /root

QS.10. Update VPS (Optional),

When loaded into the server, it is an optional upgrade to use update command:

sudo apt-get update && sudo apt-get dist-upgrade
  • When prompted to continue to choose yes by inputting “Y” and hit enter.
  • If prompted by any additional screens choose the default option by hitting enter

QS.11. Add Swap Space (REQUIRED), Reboot VPS

To install swap space to your VPS, use the command:

sudo fallocate -l 4G /swapfile && chmod 600 /swapfile && mkswap /swapfile && swapon /swapfile && echo '/swapfile none swap sw 0 0' | sudo tee -a /etc/fstab && free -h

Lastly, finish these two steps by re-booting the VPS. This can be done manually via the hosting website or remotely using the SSH window with the command:

sudo reboot

This will disconnect from your SSH session please allow about 20 seconds for the server to start up again and proceed to the next step.

QS.12. Login to VPS again, and Install $Pac Masternode Script via $Pac MN Installer

Navigate to root directory (AWS Lightsail or non-root servers):

sudo su
cd /root

Install the PAC masternode software following commands:

wget https://raw.githubusercontent.com/PACCommunity/PAC/master/pacmn.sh && chmod +x pacmn.sh && ./pacmn.sh
  • Enter your MN IP Address and Private Key when prompted

QS.13. Install $PAC MN Service (this helps restart your masternode if server crashes). Special thanks to @foxD in Discord.

wget https://gist.githubusercontent.com/foxrtb/b703ae761472c5599c4d83ab0d3d62ae/raw/e8913deb9e1b7cc9c649febd2942930e4f6f5127/add-systemd-from-script && chmod +x add-systemd-from-script && ./add-systemd-from-script

QS.14. Verify Sync, wait for “AssetID”  to get to “999”, check via command:

./paccoin-cli mnsync status

QS.15. Edit the masternode.conf file on your Desktop Wallet. Use a new line with MN alias, IP Address :7112, Masternode Private Key, Collateral Output and Index, all separated by spaces as shown below:

Save the masternode.conf file and close your text editor. Restart your $Pac Desktop wallet to apply the changes.

QS.16. Click the Masternode tab, select your MN, then choose Start Alias button on the bottom.

QS.17. Verify the status on your VPS using the terminal command:

./paccoin-cli masternode status

Make sure that the status says Masternode successfully started”.

$PAC Masternode Network Statistics

Total Masternodes: 6823
ENABLED: 6249
NEW START REQUIRED: 235
WATCHDOG EXPIRED: 16
PRE ENABLED: 0
POSE BAN: 11

Monitor Your Masternode

Congratulations! You now have your very own brand new $Pac Masternode!

Your cold wallet (installed on your desktop or laptop) synchronizes with the $Pac network and the distributed blockchain whenever it is online and connected. However, your $Pac Masternode must stay online and connected all the time in order to provide second-tier services to the network. What this means is that you can shut down your desktop/cold wallet for as long as you’d like, as long as your hot wallet on your VPS is running. This is where monitoring becomes handy and important.

When you first create a new $Pac Masternode, it goes through several stages from inception to its first payment. Masternodes have a status on the $PAC network. When they are new, they have the WATCHDOG_EXPIRED state for about 15-30 minutes while the MN’s IP Address, Collateral Tx ID is broadcast, validated, and propagated through the network. It will then go to ENABLED state. This is the state you want your Masternode to be in All the Time as it means that it is available to receive reward payments.

In order for a $Pac Masternode to receive its first reward, it has to achieve Active Time status. Active Time is achieved by being on the network in the ‘ENABLED’ state for a minimum of X minutes which is calculated as:

X = (Number of MNs) * 2.6 minutes

So, if your MN is created when there are 5,000 MNs on the network, your new MN will achieve Active Time in 5,000 * 2.6 minutes, or 13,000 minutes or about 9 days and 40 minutes. Once your Masternode achieves Active Time, it will be put into Position #1 in the Payable Pool. Refer to the diagram below as we walk through the life-cycle of Masternode payments.

PAC Masternode Payment Cycle

  1. $Pac Masternode is brand new on the network, and in about 15 minutes should go to Enabled status. As noted previously, DO NOT REFER TO YOUR DESKTOP WALLET’S MASTERNODE TAB FOR STATUS!! Instead, we’ll use one of the monitoring websites described in the next section.
  2. Once your new Masternode goes from WATCHDOG_EXPIRED to ENABLED status, your MN now needs to achieve Active Time as described above.
  3. Now that your new MN has achieved Active Time, and is in ENABLED status, it will immediately get “pushed” into position 1 in the payable pool, which is the front 10% of enabled MNs active on the network. As an example, if there are 5,000 MNs enabled in the network, the front 10% payable pool would be those MNs in position 1-500.
  4. The network uses Quorum selection for the Masternode to get paid in the next mined block on the blockchain uses an algorithm that is random with increasing probability of getting selected based on the amount of time spent in the payable pool. Remember, your position has a relative probability. As new MNs join the network, achieving their own active time, all other MNs will get pushed back 1 in the queue.
  5. Each block mined on the blockchain distributes 10,350 $Pac to the selected MN for a reward payment, and then every MN in the queue moves up 1 in position.
  6. Your Masternode gets selected and rewarded! Your MN will now go to the end of the payable queue and repeat.

$Pac Masternode Monitoring Websites

Next, we will use one of the web-based monitoring tools for your new $Pac Masternode. The web-based monitoring apps are important, and you should get to know them. Not only do they have some important information, but they can also be sent as links to your mobile phone (in addition to the mobile monitoring apps in the next section).
The reason why we want to use a monitor site/app AND NOT the desktop wallet is because of 2 reasons: 1) Monitoring sites are connected to the network, and how the $Pac network sees your Masternode in terms of status is all that matters in terms of getting rewards (it is, after all, a decentralized, quorum based network) and 2) as mentioned previously, the desktop wallet has a known bug that shows the wrong masternode status and it will probably freak you out.

You’ll want to use one of these sites when your MN is running to see the status and position of your Masternode in the Payment Queue. Next, let’s check out some mobile apps for monitoring your masternode.

Mobile $Pac Masternode Apps

One of the best ways to monitor your $Pac Masternode when you’re on the go is using the $Pac Mobile Masternode Monitoring App. Once you have your $Pac Masternode in the app, you will be able to see your position and status, as well as getting push notifications when your MN gets paid or enters the payable pool. You can find versions for both iOS and Android via the links below:

PAC Masternode Troubleshooting

See below for a list of helpful commands as well as a section on troubleshooting your $PAC Masternode if you run into problems. As you use these commands, keep track of their function and think of them as tools. Learning to self-diagnose errors quickly to get your nodes up and running as fast as possible will help you achieve rewards faster and help provide a robust network for $PAC.

This section will be constantly evolving, if you have a suggestion of a new error or solution please contact one of the contributors listed in the contact section!

WARNING:
Our discord community is a great place to get help, however, to protect your investment NEVER send any FILES or sensitive information to anyone helping you. There have been several fake accounts targeting those in need of help. Please report any suspicious activity to a moderator.
Also, make sure your wallet is encrypted property to protect your investment!

Recent Updates, Soft Forks & Forks - October 2018

This section contains information regarding recent updates to the master node system. This is a secondary source, for the most recent and primary source see all the social media channels such as Twitter, and Discord, see links on the main PAC site to access.
Reminder, hosting a masternode requires constant upkeep. By hosting independently you are accepting the risk that you have to solve problems as they come through and the performance of your node is guaranteed. Updates are part of growth and security and are necessary over time, and they may come with some after effects that need tuning. Make sure to acknowledge the hard work that goes into them, rather than be frustrated with the inconvenience.
The following sections offer details for specific updated in as a secondary resource. The information provided in this section is intended to be secondary tool to help collect and describe actions needed to take. Please check important news channels and social media before using this update guide in reference to last edited date as it may lag behind in current information.

Network Fork -October 2018- Block 155000: Mandatory Upgrade- Prevention of network performance attacks

Last edited: November-9-2018
The October update is a MANDATORY upgrade in the form of a network fork to address a network performance risk occurring from micro-transactions. The official press release and details can be found https://blog.paccoin.net/october-pac-mandatory-security-patch/, https://blog.paccoin.net/pac-overcoming-adversity/, and on the announcements in #important-news in Discord.

The October update has two scenarios and mandatory block count check as the fork occurred in two stages of updates, and may have done partial update already. Read each an follow the option that best suits your scenario, it is important you are up to version 12.5.1 and on the correct block count and block hash:

Scenario 1: You haven’t done any action on this fork, and your wallet version is 12.3 and your protocol of your masternode is 70213. You will need to update to desktop wallet version 12.5.1 and your VPS protocol 70214 and version 120501, this scenario requires you to start alias at the end of the update. See the detailed section below.

Scenario 2 : You did the first part of the update and are on 12.5.0 and your VPS protocol 70214. At this point, you need to update to desktop wallet version 12.5.1 and update VPS to version 120501. See the detailed section below.

NOTE: Both scenarios will require you to check your block count to make sure you successfully are on the right chain fork!

Scenario 1: Freshly updating desktop wallet version 12.5.1 and MN to protocol 70214 and version 150501 – Start Alias

IMPORTANT! – This update was required at block height 155000 – approximate time 30 Oct 2018 07:12:12 the wallet/masternode will be disconnected from the network if you missed this timeline, and needs to be updated to re-connect.

Please follow the steps below to implement the update for the new code release:

Step 1: Update your wallet

Download the 12.5.1 wallet for your platform here https://www.paccoin.net/wallets – your wallet is already backed up on windows Mac platforms, but please ensure you have your wallet.dat file backed up, and safely secured, to ensure recovery of your funds if a failure occurs.

Step 2: Upgrade your VPS

The minimum size of a $PAC masternode in terms of disk space needed that we are recommending is a VPS with an SSD size of 25 GIGs going forward. https://masternodes.paccoin.net/#setup-vps (right click- open in new tab) for details on tested providers and additional information.

Step 3: Updating your masternode – Is your server already installed yes or no?

If the answer to this question is no, please skip to the next portion.

Yes? – I have a 1 GIG VPS with an SSD size of 25 GIG

Ensure your wallet that your is updated first!

In the rare case, your on a VPS is NOT logged in as “root” user:

sudo su
cd /root

In your Linux VPS and copy/paste the following update command:

wget -q -O- https://raw.githubusercontent.com/PACCommunity/PAC/master/pac-update.sh | bash

After a little while you should see:

Press (CTRL-C) and type the following:

./paccoin-cli getinfo

You should see a window with version 120501 and protocol 70214 as seen below:

You have now updated your masternode successfully, now go to your wallet’s masternode’s section and restart your masternode. To do this go to desktop wallet -> masternodes tab -> select the MN being updated -> start alias

Now you should see the protocol in the third column of desktop wallet change from 70213 to 70214.

Wait 20-30 minutes and your masternode should move to Enabled

No? – My SSD size is lower than 1 GIG memory and 25 GIG SSD:

You need to update your masternode to the required specs- some VPS providers allow you to do this by a setting step to transfer the IP over. But in most cases, you’ll need to re-create and can be handled on a case-by-case basis. See https://masternodes.paccoin.net/#issues (right click- open in new tab), specifically “Scenario 5: I Need to Re-host or Re-setup My MN” and use the main guide for details if recreating.

Step 4: Checking VPS block number (MANDATORY)

You need to check your VPS and Cold wallet versions for being on the right block count and chain. From your VPS use command:

./paccoin-cli getblockhash 158418

you should see results:
0000000000000595a2a004a27026439bbfeddcbff7200585421a7fe3a51237be

For details and for re-indexing instructions, see Scenario 9 at https://masternodes.paccoin.net/#re-index-vps (right click- open in new tab) to see the steps necessary.

Step 5: Checking Cold wallet block number (MANDATORY)

To check your cold wallet to ensure you are on the correct blocks and re-index if necessary. On your desktop wallet under Tools > Debug Console and enter:

getblockhash 158418

you should see results:
0000000000000595a2a004a27026439bbfeddcbff7200585421a7fe3a51237be

For details and for re-indexing instructions, please see scenario 10 https://masternodes.paccoin.net/#re-index-cw (right click- open in new tab) for how to check cold wallet.

This is very important to ensure you are on the correct fork!

Scenario 2- Updating PAC desktop wallet to 12.5.1 and VPS to version 120501 (REQUIRED)

Step 1: Update your wallet

Download the 12.5.1 wallet for your platform here https://www.paccoin.net/wallets – your wallet is already backed up on windows Mac platforms, but please ensure you have your wallet.dat file backed up, and safely secured, to ensure recovery of your funds if a failure occurs.

Step 1: Updating your masternode VPS:

In the rare case, your on a VPS is NOT logged in as “root” user:

sudo su
cd /root

Now to update use the following commands. The first command may fail, if so please continue to the second option:

rm ./pac-up*.sh* && wget https://raw.githubusercontent.com/PACCommunity/PAC/master/pac-update.sh && chmod +x pac-update.sh && ./pac-update.sh

If the above fails try without the remove feature:

wget https://raw.githubusercontent.com/PACCommunity/PAC/master/pac-update.sh && chmod +x pac-update.sh && ./pac-update.sh

Step 2: Check that it updated with the command:

./paccoin-cli getinfo

Check Final Status:

./paccoin-cli masternode status

Step 3: Checking VPS block number (MANDATORY)

You need to check your VPS and Cold wallet versions for being on the right block count and chain. From your VPS use command:

./paccoin-cli getblockhash 158418

you should see results:
0000000000000595a2a004a27026439bbfeddcbff7200585421a7fe3a51237be

For details and for re-indexing instructions, see Scenario 9 at https://masternodes.paccoin.net/#re-index-vps (right click- open in new tab) to see the steps necessary.

Step 4: Checking Cold wallet block number (MANDATORY)

To check your cold wallet to ensure you are on the correct blocks and re-index if necessary. On your desktop wallet under Tools > Debug Console and enter:

getblockhash 158418

you should see results:
0000000000000595a2a004a27026439bbfeddcbff7200585421a7fe3a51237be

For details and for re-indexing instructions, please see scenario 10 https://masternodes.paccoin.net/#re-index-cw (right click- open in new tab) for how to check cold wallet.

This is very important to ensure you are on the correct fork!

1. Helpful commands

  • Checking Your Masternode Status
    – Checking the status of your Masternode on your VPS, copy/paste (or type) the following:

    ./paccoin-cli masternode status
    

    An additional method to check that is more reliable than either a website or wallet status, and has a better network-wide evaluation of your Masternode. Use this command in your VPS by replacing “PUT-MN-IP-HERE” with your masternode IP.

    ./paccoin-cli masternode list full PUT-MN-IP-HERE
    
    

    Careful sharing this information, other than the status report, directly with others as it has sensitive information regarding your setup node.

  • Checking Sync Status
    – On your VPS, copy/paste (or type) the following:

    ./paccoin-cli mnsync status
    

    The first line of the output should say AssetId : 999 when it is fully synched.

  • Checking to see if the $Pac Masternode process is running
    The $PAC MN daemon process is named paccoind. To see if it is running use any of the following methods:
    A) Copy/paste (or type) the following:

    ps aux | grep pacc
    

    You should see one entry for the paccoind process

    B) Copy/paste (or type) the following:

    ./paccoin-cli masternode status
    

    or any of the paccoin-cli commands. This will attempt to connect locally to the running paccoind process and will return an error if it is not running.

    C) If you had installed the systemd service copy/paste (or type) the following:

    systemctl status pacd --no-pager
    

    You will need to Ctrl+C to break out and return to the command prompt.

  • Checking to see if Sentinel is installed
    As mentioned previously in the guide, the sentinel process is installed as part of the master $PAC install script. A cron entry is created so that every minute the sentinel process runs to broadcast your MN’s status to the $PAC network. To check to see if it has been properly installed, copy/paste (or type) the following on your VPS:

    crontab -l
    

    you should see the following output:

    * * * * * cd ~/sentinel && ./venv/bin/python bin/sentinel.py 2>&1 >> sentinel-cron.log

    If you don’t see an entry like above, then sentinel wasn’t properly installed. You may need to reinstall your MN.

2. Troubleshoot Scenarios

Some common troubleshooting scenarios are found below:

Scenario 1: New Masternode Status is WATCHDOG

  • Make sure that your MN collateral has at least 15 confirmations.
  • Did you Remote Start your Masternode?
  • Wait 15-20 minutes after remote starting your MN, and check your status again using the web based monitoring sites. It usually takes this long for the network to synchronize and validate your masternode.
  • If after 15-20 minutes, your MN status (using the web-based monitor and NOT YOUR DESKTOP WALLET sentinel may not be properly installed see Scenario 6. If not, you may need to reinstall your MN.

Scenario 2: Masternode Status is NEW START REQUIRED

    Did you check the status using the web-based monitoring sites? If you are seeing this in your desktop wallet’s Master node tab, IGNORE IT, and check the web-based monitors in the Monitoring section.
    • If the web based monitoring sites indicate that your MN is in NEW START REQUIRED, your MN’s paccoind process may not be running. Check the status using the commands in the previous section.
    • If your paccoind process isn’t running, you can:
      • Install the systemd service, as explained in Part 4.4. of the Setup Guide – software installation, which is highly recommended, as it will bring your process back up (and on reboot) if it ever goes down.
      • For quick install of this service use this command:
        wget https://gist.githubusercontent.com/foxrtb/b703ae761472c5599c4d83ab0d3d62ae/raw/e8913deb9e1b7cc9c649febd2942930e4f6f5127/add-systemd-from-script && chmod +x add-systemd-from-script && ./add-systemd-from-script

        Note, if the paccoind process wasn’t running before, it should automatically start once this is installed, re-check with the commands above.

      • If you choose not to install the systemd service, then you can bring your process up by copy/paste (or typing):
        sudo ~/paccoind
        
      • Check that paccoind is running as explained in the earlier section.
      • Once you get your paccoind process back up and running, you’ll need to issue a Remote Start of your MN from your desktop wallet. Unfortunately, this will also start your Masternode As If it were a new Masternode, meaning, you will first have to achieve `Active Time` before becoming payable.
      • Check the web-based monitors after 15 minutes to make sure that your MN is in ENABLED state.

    Scenario 3: Masternode Status is EXPIRED

    Follow the same steps to troubleshoot above for when your MN is showing NEW START REQUIRED

    Scenario 4: My MN Isn’t Getting Paid

    • Using the web-based monitors (or mobile apps) is your MN’s status ENABLED (required).
    • Is your MN’s position using the web-based monitor in the payable pool?
    • The payment logic for the payable pool is random with increasing probability of selection
    • See stats from Masternodes Online. These are updated and an average. For example, if the average payout cycle is 9 days, your MN’s current reward cycle may go longer, or shorter. Be sure that it is in the correct status of ENABLED and your MN will eventually get paid. Over time, your own average cycle time should converge to the network average.

    Scenario 5: I Need to Re-host or Re-setup My MN

    Follow these steps if you need to migrate your $Pac MN to another VPS instance or if you are rebuilding onto another server with a different IP address:

      1. Shut down your old VPS instance. Eventually, your old IP Address will show EXPIRED on the monitoring sites.
      2. Install the $Pac MN server just like you would a New MN with the following differences:

    – Keep the existing Private Gen Key when you set up on your new VPS.
    – Update your Desktop Wallet’s masternode.conf file and change only the IP Address to the IP Address of your new VPS instance. Restart the desktop wallet to pick up the new configuration.
    – Install everything the same on the VPS server as if it were new
    – Remote Start your new VPS from the desktop wallet
    – Check the status on the new VPS instance: Copy/paste (or type) the following:

    ./paccoin-cli masternode status
    

    -On your VPS as a result of the above command, you may see something like ‘invalid IP Address’ or ‘rebroadcast new IP Address’. Wait 10-15 minutes and check the status again. It will take a while for the new IP Address to propagate through the network. If after 20 minutes, you still don’t get a valid status, choose `Start Alias` again from your desktop wallet.

    Scenario 6: Error Starting MN Process

    If your MN process paccoind stopped due to out of memory errors, your local files may have been corrupted and you will see errors when starting the process. If you installed the pacd service, you can look for errors and status with systemd service:

    systemctl status pacd --no-pager

    Take the following steps to repair your process: Start your process with the re-index command option:

    sudo ~/paccoind -reindex

    Check your status using various commands on this page
    Verify your MN status on the web monitors.

    Scenario 7: Issues with Sentinel installation

    As mentioned previously in the guide, the sentinel process is installed as part of the master $PAC install script. A cron entry is created so that every minute the sentinel process runs to broadcast your MN’s status to the $PAC network. To check to see if it has been properly installed, copy/paste (or type) the following on your VPS:

    crontab -l

    you should see the following output:

    * * * * * cd ~/sentinel && ./venv/bin/python bin/sentinel.py 2>&1 >> sentinel-cron.log

    If you don’t see an entry like above, then sentinel wasn’t properly installed. The most likely issue is from issues with language locale interfering with the installation. To fix this, a reinstall of the masternode instance might be necessary – see Scenario 6. If the error persists then contact an #masternode support in the PAC discord for assistance.

    Scenario 8: Masternode is crashing due to Memory Issues

    You can use this script on your remote VPS to add a memory swap:

    sudo fallocate -l 4G /swapfile && chmod 600 /swapfile && mkswap /swapfile && swapon /swapfile && echo '/swapfile none swap sw 0 0' | sudo tee -a /etc/fstab && free -h

    Scenario 9: Masternode VPS is on wrong block and needs re-index:

    It is possible your VPS has gotten on the wrong block chain during a network fork or has incurred an error that is preventing proper block progression. Use the following steps to confirm your blocks are moving properly and that your masternode is on the correct chain.

    Step 1) First check in your VPS console if your masternode is on the correct block count and block hash with:

    ./paccoin-cli getblockcount && ./paccoin-cli getbestblockhash

    Compare the results with http://explorer.paccoin.net/ or http://explorer.foxrtb.com/ by selecting the specific block that was reported with the has provided. The correct hash should be in the address bar of your browser if the main page isn’t showing it correctly.

    NOTE: there is a bug where the blockhash on the page doesn’t show correctly- please refer to the address bar of your browser to check in that case.

    It should be within a few blocks of what is reported on the site. If your masternode is reporting current block far off or the wrong block-hash you may need to re-index to sync with the network again. Only continue if those conditions are met. You can also check multiple times. Comparing to the block rate on explore sites, if blocks don’t change over time then re-index is needed. Ask support if you are unsure.

    Do the following steps and wait for it to fully complete as they take time, re-indexing can be periodically checked once initiated but the re-indexing takes time.

    Step 2) Stop the paccoin-cli service and re-index:

    ./paccoin-cli stop | ./paccoind -reindex

    This process takes about 30 minutes or more, be patient and wait for re-indexing to take place. Please don’t interrupt the process!

    Blocks will slowly get sorted through as the VPS gets caught up, you can periodically check block count again during the process by:

    ./paccoin-cli getblockcount

    Wait until the block reach current state as described in Step 1) 

    Step 3) Once fully synced you may have to issue start alias from your desktop wallet after following steps above to complete the re-indexing the MN.

    Scenario 10: Desktop Wallet (Cold Wallet) Re-indexing:

    These steps will ensure your cold wallet is up to the correct block.

    Step 1: Create a backup of your wallet File->Backup Wallet… save it to a safe place and additional on a flash drive or similar. Also ensure your computer is connected to power if using a laptop and ensure process wont be interrupted as the next step can a long process.

    Step 2: Make sure your wallet is the latest version that matches
    https://paccoin.net/wallets check by going to your desktop wallet and click Help->About $PAC Core wallet.

    Step 3: Check block status using the following command and comparison,

    In your desktop wallet go to Tools-> Debug Console and in the command line type

    getblockchaininfo

    Hit enter and you should see info pop up (you’ll need to scroll to the start of the results) for the most recent block which should match results with http://explorer.paccoin.net/ or http://explorer.foxrtb.com/.

    NOTE: there is a bug where the blockhash on the page doesn’t show correctly- please refer to the address bar of your browser to check in that case.

    If your wallet does not match hash from an online explorer as shown above in the image above then you may need to re-index your wallet. Keep in mind they blocks move dynamically on the explore web-page so make sure to refresh when checking if your wallet is close in block count. To re-index follow the next step. Ask in support channels if you are unsure.

    Step 4: Go to Tools->Wallet Repair then click “Rebuild index”  this will reboot the wallet and begin the index process. This may take several hours depending on your computer, but could be as fast as 20 minutes.

    You may notice a slight change in transactions and should check your block count again as previously done in the start of Scenario 10 – Step 3 above

    Scenario 11: Desktop Wallet (Cold Wallet) Update Procedure:

    These steps will ensure your desktop wallet is up to the correct block.

    Step 1: Create a backup of your wallet File->Backup Wallet… save it to a safe place and additional on a flash drive or similar. Also ensure your computer is connected to power if using a laptop and ensure update process wont be interrupted.

    Step 2:  Visit the official PAC wallets page at https://paccoin.net/wallets and download the latest version.

    NOTE: Make you you match the current format of the existing wallet you have whether it is 32bit or 64bit and correct platform.

    Step 3: Close you PAC wallet completely and run the newly downloaded update file.

    NOTE: You will likely need to grant permission and may be flagged by virus software. Virus software is sensitive to any cryptocurrency applications, ignore the warning for the $PAC wallet. Please allow in either instance.

    Step 4: After completing the update re-open the PAC wallet via the shortcut on the desktop or how you previously did before. Allow time for the new wallet to index and connect to the blockchain. NOTE: if the update was mandatory by a certain date such as a network fork, and you carried out transactions after this date, then it is fully loaded, you may notice some change in transactions during this period. If you have any problems please see the network

    Step 5: As and additional step to make sure the update carried out correctly, you can check block status using the following command and comparison,

    In your desktop wallet go to Tools-> Debug Console and in the command line type

    getblockchaininfo

    Hit Enter and you should see info pop up (you’ll need to scroll to the start of the results) for the most recent block which should match results for the specific with http://explorer.paccoin.net/ or http://explorer.foxrtb.com/.

    NOTE: there is a bug where the blockhash on the page doesn’t show correctly- please refer to the address bar of your browser to check in that case.

    If your wallet does not match hash from an online explorer as shown above in the image above then you may need to re-index your wallet please see Scenario 10 above.

     

    About the PAC DAO / Governance System

    What is DAO?

    PAC utilizes a system called DAO which stands for Decentralized Autonomous Organization, which represents how a portion of PAC funding and structure is run by the investment community. This form of governance system allows the community to be involved in the decision-making regarding projects related to PAC, providing a unique backbone to the core organization structure, while maintaining decentralization of budgetary decisions.

    Funding with the DAO is done through a multi-step process outlined in detail in this section. Proposals are generated by anyone who can bring a service or product to PAC and voted for using a system easy to use by any Masternode investor. Anyone in the community can create proposals for funding through the DOA funding system, to be reviewed by the voting stakeholders. Whether an individual is an independent or shared Masternode owner, they are granted voting rights to determine the best direction of projects to best improve the coin and their investment. Funding approved through the DAO are new coins generated into the $PAC blockchain as new supply so funding doesn’t come from any individuals’ coin supply.

    How does it work?

    Funding Cycles:

    The release of funds into the network is done at a time known as a Superblock, which correlates to a specific block on the PAC blockchain, timing estimates are provided on the Paclyfe Governance page. Also shown on this page is the funding available, a fixed budget per Superblock. Two scenarios can occur in this system:

    Scenario 1: If the total passing proposals of $PAC, exceeds the available budget, percentages of the total available budget will be given based on vote performance.

    Scenario 2: If a lesser amount of $PAC is approved than the available budget is requested, the remaining $PAC is never generated into the blockchain.

    It is important to evaluate funding with a thorough understanding of how the releasing funds will affect the value of $PAC. Since the coins are added to the circulating coin supply, voters should consider when voting: The total value of a proposal in cost to the network should add equal or greater value to the value of PAC to promote growth to PAC as an entity and investment.

    Step-by-step DAO funding process:

    1- Idea Needing Funding:

    1.1 DAO Funding needed (larger amounts, slower, 5,000 $PAC fee):

    Individuals, partners, or companies can submit proposals for funding. Anyone submitting is encouraged to brainstorm with the community and the core team. The goal is to discover a product or service that will directly relate and benefit PAC and is a large enough scale to justify the DAO process and fee. Please note that funds are only released on Superblock timelines which may take up to 30 days.

    1.2 Alternative funding needed (Smaller amounts, faster, free):

    If the idea or project is small, there may be alternative funding or resources to complete the project without needing the DAO. This can be done by connecting with community members and check out any ongoing community funds such as the Community PAC Fund (CPF). This community fund can provide funding (up to $1500) on a faster timeline and without a submitting fee for small projects such as PAC awareness, meetups, ect. For more background information about the CPF and how it was created please see the corresponding PAC blog page.

    2- Draft Using Community Feedback:

    One of the most important stages is early community feedback. The more connection with the community and awareness spread, the better chance of receiving funding. Utilize several resources for communications and be open to constructive feedback. Keep in mind if the time isn’t right, save a proposal for a later date. There are several resources for connecting with the community.

    • Paclyfe – Create an account and post ideas in the corresponding Pre-proposal ideas section
    • Discord – Post your idea in the #pre-proposal-ideas-here section and kindly invite people in the #general-chat to take a look and provide feedback

    3- Proposal Creation & Tuning:

    Proposals can be created in several ways, though it is important to do so in a professional and detailed manner to increase your possibility of funding. Providing a document to link that can be edited after- such as a Google Docs shared link allows for tuning of your proposal as you receive more feedback. If this method is used, however, clearly show and announce amendments to the document. The cost to submit can vary over time but currently is about 5,000 $PAC. Proposals can be submitted manually into the blockchain, however, the Paclyfe platform offers a unique and easy-to-use way to generate the code needed for creating a proposal. The coded generated is then submitted through the debug console of the PAC desktop wallet.

    IMPORTANT NOTE: once a proposal is submitted on the blockchain via code described in section 3, the submission is final, and the fee is non-refundable. Be certain about your willingness to proceed with your idea and triple check your information and any links used in the proposal.

    3.1 – Single Payment Cycle:

    Requesting a large single payment cycle can be difficult for investors to review, especially if it is your first proposal submitted. If the amount requested is a large amount, chances are the proposal will be denied because the risk by investors committing is too high. Consider smaller amounts for a single payout or divide total amount into an incremental funding option.

    3.2- Incremental Funding Cycle:

    This method of funding is done in incremental stages (smaller amounts) this allows for you to get feedback in case your proposal doesn’t pass and get lasting funding for a long-term project. The project will be re-evaluated after each funding cycles so it is important to keep investors updated. Avoid too long of instances as the future of PAC will constantly be evolving and outdated funding requests may become obsolete.

    4- Convey Proposal Importance:

    The creators of proposals will consistently need to convince the community why their proposal is important. Consider doing a video interview and constantly talking with community members through channels mention in step 2. Proposal creators should aim to gain their trust and grow your project to its highest quality in preparation for final votes, whether it is a first round or a incremental funding.

    5- Evaluation and Voting before the Superblock:

    As previously mentioned, voting is done by both full node owners and shared node owners. There are three vote classes available: Vote Yes (positive count), Vote No (negative count), or Vote Abstain (no count, vote removed from total).

    5.1 Evaluating Proposals

    Evaluating proposals is a difficult and important task. Masternode owners should take pride in helping improve their investment by choosing to vote on a regular basis and take time to evaluate proposals in detail. Engaging in a discussion on social platforms with the proposal creator and the community will help everyone make an informed decision and help spur an important discussion of the proposal.

    5.2 Submitting of Votes

    Submitting of votes is done through the Proposals tab on desktop wallets or the servers hosting the Masternode. A wallet hosting multiple nodes votes all nodes at the same time for a decision. The several shared node services available offer their own ways to vote your share for the node, requiring a login to prove your investment into the system. Information on shared nodes should be found on the respective websites for up to date information.

    5.3 Evaluating the total votes

    The votes are totaled and used to figure out the running percentage by the following equation.

    Vote % = [(Yes Votes – No votes)/(Total MasternodesAbstain Votes)]*100

    If Vote % is greater than 10% at the time of the Superblock then the proposal passed. Less than %10 the proposal fails the current round. Votes remain active until changed for a proposal with multiple funding cycles and can be changed and re-evaluated before each Superblock funding release.

    5.4 Monitoring Proposals

    Monitoring can be done using sever different sites available showing an updated count of votes and detailed information on the proposals. This information can also be found in the wallet directly. For up-to-date information on proposals and their status see the following pages.

    The following pages contain information regarding votes, status, voting deadlines, budget information and budget cycles of proposals. Bookmark for quick reference when evaluating props.

    6- Approval to Receive Funds:

    A proposal wins only if the approval is greater than the 10% vote at the time of a Superblock, as detailed in section 5.3. Funds are generated in the blockchain and deposited in the address provided in the proposed code. It is very important to keep strong security in place, ensuring the computer and the wallet storing the funds are password protected. To avoid excessive down pressure at early stages of the coin, plan any sales of the coin in at logical times and to also make the most use of the funds.

    7- Update Community of Progress:

    Constant updates to the community and public will help keep your relationship with supporters. Also allowing others to appreciate the work you’ve done and help to keep the project to its designated timeline. If using a multistage funding cycle, in between superblocks is a perfect time to keep supporting investors happy with updates regardless if there is good or bad news. Utilize the wealth of skills and knowledge the community has to make your project the best it can be!

    $PAC Masternode ROI Calculator

    Estimated Revenue per Masternode

    Daily Income:

    954.01 $PAC
    0.00027666 BTC
    0.95 USD
    Monthly Income:

    28,620.26 $PAC
    0.00829988 BTC
    28.45 USD
    Yearly Income:

    348,213.15 $PAC
    0.10098181 BTC
    346.12 USD

    $PAC Masternode ROI Calculator

    Average revenue per day: 0

    Average revenue per week: 0

    Average revenue per month: 0

    Average revenue per year: 0


    Days until a new Masternode can be started (500k $PAC earned): 0

    $PAC Market Data:

    Price:
    0.00000029 BTC

    0.000994 USD
    Market Cap:
    1,499.39 BTC

    5,152,003.49 USD
    Volume(24h):
    11.4909961928 BTC

    39483.8533693 USD
    Change(1h):
    8.746% (BTC)

    9.4464% (USD)
    Change(24h):
    15.9234% (BTC)

    16.8652% (USD)
    Change(7d):
    24.8629% (BTC)

    15.8458% (USD)
    Circulating Supply:
    5,181,067,717.52 $PAC
    Total Supply:
    5,599,049,792.00 $PAC
    Max Supply:
    100,000,000,000.00 $PAC