Jump to content

J3ll3

Administrators
  • Content Count

    48
  • Joined

  • Last visited

  • Days Won

    9

J3ll3 last won the day on January 28

J3ll3 had the most liked content!

Community Reputation

12 Good

7 Followers

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. INSTRUCTIONS This guide is for those that want to do a manual update of their masternode running on a VPS. This guide is very similar to the upgrade to version 1.1.0.0, but there is no need to resynchronise this time!! People that should not use this guide Please do not use this guide if you have your masternode with any of our masternode hosting providers as listed below. Those masternodes will be updated by your hosting service. You might have to start the masternode after they announce that they have completed the update: Stakinglab.io CryptoHashTank Nodehub.io GTM Snode Maiks masternode hosting service BitHostLive Pecunia MIDAS Apollon Detailed manual upgrade instructions This guide tells you in detail, which steps you should follow for updating your masternode running on a VPS. Alternatives are creating a new VPS and installing the masternode from scratch or rerunning the install script on an existing masternode. Remember to disable the masternode first using this command: systemctl stop PAWS Now... over to the instructions for a manual update: Login to the VPS using putty or any other ssh program that you normally use as described in the installation guide. You should now have a window with a black screen like the one shown below: The first thing you do, is stop the masternode service running. systemctl stop PAWS The next thing we do is download the new software: wget https://github.com/pawsfund/PAWS-Core/releases/download/v1.2.0.0/paws-1.2.0.0-x86_64-linux-gnu.zip This should output some lines, that indicate the file is being downloaded. Once the prompt returns, we need to unzip the archive we just downloaded. Do the following: unzip paws-1.2.0.0-x86_64-linux-gnu.zip You should now have 3 more files in your home directory. Please do the following to make them executable: chmod +x paws* The files now need copying over the existing executables in /usr/local/bin. We do that as follows: mv paws-cli /usr/local/bin mv pawsd /usr/local/bin mv paws-tx /usr/local/bin We are now ready to start the masternode service for the first time: systemctl start PAWS We need to restart the masternode AFTER the service has started. Make sure that the wallet is fully synced before proceding by making sure that the number returned by the below command is the same as the current blockheight on http://chain.paws.fund: paws-cli getblockcount Once the masternode is in sync, do the following command!: paws-cli stop What happens here, is that we stop the wallet via the commandline, but since the wallet is running as a service the service will start it again once it detects it is shutdown. So this really means that the wallet is stopped, and started immediately after. You now have to open your local wallet and start the masternode, just like you did with your first installed the masternode. Chances are that it says it is enabled already, and this is because the wallet is really slow to detect that a masternode has going offline.This is a good thing, as it might prevent you from having to wait the initial 18 hours before getting your first reward. So open the local wallet, and start the masternode by selecting it and clicking "Start Alias". If you get the invalid ip error go into: Tools -> Debug Console and type the following: startmasternode alias 0 YOURMNNAME The final step is to check if the masternode has started. On the masternode (VPS) type the following command: paws-cli getmasternodestatus It should return something like: { "txhash" : "f1355f7864ff97f395b5b51a10ec5ckpe82b0f2c6170b6956ee81f264137821b", "outputidx" : 0, "netaddr" : "1.1.1.1:34120", "addr" : "PPUg6iQtMrHjhaYqxYrtFaxMjmcqLzC7pt", "status" : 4, "message" : "Masternode successfully started" } Status 4 means you are good to go. If it is not working... repeat the steps from step 10. This might need repeating 1-2 times. Any problems let us know here on the forum or on Discord. The PAWS Team
  2. These are the results of the Midex vote, round 1 and round 2 combined. Winners of the 5000, 10000 and 25000 CCBC awards are also included in the list. Note the empty address fields for those where we were not supplied with an address. We would like to thank all of you for stopping by and taking the time to vote for PAWS, which ultimately lead to PAWS being listed on the Midex exchange! THANKS +=====================+====================================+=======+=======+ | Discord | CCBC address | Share | Added | +=====================+====================================+=======+=======+ | aboutyouthinking711 | SajRBk4CZ1gohJNS7eJhYrb3uZEqAzzEqh | 0,5 | | +---------------------+------------------------------------+-------+-------+ | abuzein | SUwNqAfuq43X4afunQnnyJFCK7sYfRzBGW | 0,5 | | +---------------------+------------------------------------+-------+-------+ | allaya birak | SXLWtbGTfFpFzsDbR6ZoUef78xxHUs3e5f | 0,5 | | +---------------------+------------------------------------+-------+-------+ | Altcoinlover | SWEUEPcVbeX8HGCe6vSUXdeTZ6gramZVvp | 1,5 | | +---------------------+------------------------------------+-------+-------+ | amber | SMTyKmCqFuxGTR4AsK5PHy9AtXypgBfeHz | 0,5 | 5000 | +---------------------+------------------------------------+-------+-------+ | angelamallari | SRrMBPseBmUswBdSVvAJLaMHXkFQXkSpZa | 0,5 | | +---------------------+------------------------------------+-------+-------+ | angelong516 | ScDYF58RdMFFtJ8hDnNnHQR3ZfgwmKdyHA | 0,5 | | +---------------------+------------------------------------+-------+-------+ | babyiknow62 | SPRb239nP7v3DSa9VKkJEVMfTV3ru9BVWq | 0,5 | | +---------------------+------------------------------------+-------+-------+ | bakadimoalam82 | SRHxoAoVS29ZuCkNQuMWtYdxdDDAagYwEi | 0,5 | | +---------------------+------------------------------------+-------+-------+ | bilisbilis469 | SQuFM9UNfDd9XRphzjEcKLyY8pMz7wfSSb | 0,5 | | +---------------------+------------------------------------+-------+-------+ | Bintang | | 1 | | +---------------------+------------------------------------+-------+-------+ | Bobtilladhun | Sgt7swQX9cDbc5cThQChiRqkHqCGQJoFGX | 1,5 | | +---------------------+------------------------------------+-------+-------+ | breanahlumanog08 | Sh7VakDCzqJ1rcj2MaBimeza5kgus5dnS7 | 0,5 | | +---------------------+------------------------------------+-------+-------+ | brokeAyla | SV6HqX5MbdJP7VBd5UfFD8XMzE8bAgFFBF | 0,5 | | +---------------------+------------------------------------+-------+-------+ | Bungurasih | SWKi72oNtEe4XupZUnbyP2MREjyAvPXdMS | 0,5 | | +---------------------+------------------------------------+-------+-------+ | chips | SXoMxyAJbQwsg5ns9fXkeHc7qKrSKXzihN | 1 | | +---------------------+------------------------------------+-------+-------+ | christ2169 | SSWpzf5RS4wCuT53JXSWowsocbxUzVgd71 | 1 | | +---------------------+------------------------------------+-------+-------+ | christianmanalo | SYpa57Ne74pbjMmjGqeJ3kQ2WSa5jFnbRM | 0,5 | | +---------------------+------------------------------------+-------+-------+ | coinsandchains | SdwiNdBBNEhwK2HUS7PvbvuMJSv66hYie5 | 1,5 | | +---------------------+------------------------------------+-------+-------+ | cryptosurance | ShwZVr24JwNVvqB2PDgc21RDneFimAAXug | 0,5 | | +---------------------+------------------------------------+-------+-------+ | danyway | SdrewwLFhvVGUWiYJieabiB8EBhYvX5pjT | 0,5 | | +---------------------+------------------------------------+-------+-------+ | dr_jefferson | SSwNzdB8V62R7X9eskeiuFCwHHdW1vyaZX | 0,5 | | +---------------------+------------------------------------+-------+-------+ | Dreamcatcher | SiSYBJcneN9XatwUG7xRAxP9So3MKsXXmC | 1 | | +---------------------+------------------------------------+-------+-------+ | ehugirlpretty | SU8Z2aFbEssgL2Aq7AzuBMaWjrb86Qj13B | 0,5 | | +---------------------+------------------------------------+-------+-------+ | elapamengan | SSvvX15pJpfBZZLhqGAUNuwYJtNWSebkfx | 0,5 | | +---------------------+------------------------------------+-------+-------+ | ericcastro120 | SaMnETHp5W7CAhAvh71aE3XXrj5aG4Pe7k | 0,5 | | +---------------------+------------------------------------+-------+-------+ | ericsontiamzon222 | SMpSysnKQJztaUfPALqaH8TDSpjo7rrzBo | 0,5 | | +---------------------+------------------------------------+-------+-------+ | ernieibay22 | SPCLB8ZnTUiF8qMazzA1a1U1puvhUkRPYi | 0,5 | | +---------------------+------------------------------------+-------+-------+ | Eve | Sdio2xNK98FaEH2xtFJxxDmshpnaVR81qW | 0,5 | | +---------------------+------------------------------------+-------+-------+ | everydaylife097 | SPzhXbLUETrhWXKGqHejDb2aXgZZqJY9Ps | 0,5 | | +---------------------+------------------------------------+-------+-------+ | F.shane | Sd6WBeNEZ9CRtqTuGttbffiQeggd2mQXuT | 0,5 | | +---------------------+------------------------------------+-------+-------+ | Favian | Sd3frUBa7ZoWXciHBXs1kZmPhs4p5xf1r1 | 0,5 | | +---------------------+------------------------------------+-------+-------+ | florsitchon20 | SaPBeNGXcHjKeuyqnBCSoVXkN8FYemAf3G | 0,5 | | +---------------------+------------------------------------+-------+-------+ | gbert | | 1 | | +---------------------+------------------------------------+-------+-------+ | grukesumPP | SfpftXwyt9pQBerYhVmCVJEKErFNmkxFhk | 1,5 | | +---------------------+------------------------------------+-------+-------+ | hamza otmane! | SYd3ZcVJmnUcAvFxHwNKTtVMUnME5Y2GAw | 1,5 | | +---------------------+------------------------------------+-------+-------+ | hellcarl14 | Se78eE8gKJXrFgKmUjir1xorhCVRHXK8K5 | 0,5 | 10000 | +---------------------+------------------------------------+-------+-------+ | ian.macro | SQbo86pYr5srDDUKxmYb6c7VGwGx1J2bVp | 1 | | +---------------------+------------------------------------+-------+-------+ | iwansitaiwan | ShgRW8VaZ33chFapWrVGK9Pte6SfVya7oM | 0,5 | | +---------------------+------------------------------------+-------+-------+ | jengpentinio465 | SiAHu1hXubkDtTjyppGv1oybg1exrEbu64 | 0,5 | | +---------------------+------------------------------------+-------+-------+ | josephescoto13 | SWiNZBfRt5CJJb7a4QWA2w1ghbeq33Meea | 0,5 | | +---------------------+------------------------------------+-------+-------+ | juniorb | | 1,5 | | +---------------------+------------------------------------+-------+-------+ | kamandagjerald | SkXHrAWKaHZ6xJfGkHm7XvJvc4rBUX37tY | 0,5 | | +---------------------+------------------------------------+-------+-------+ | KeaneRates | SWXn6djiFdGXdCQFpKhEqFHWgXs6vE3fBu | 0,5 | | +---------------------+------------------------------------+-------+-------+ | kimomiho7 | SRvVfrAz3KVrCpVBYEUXmP5Da4FrkHxdfR | 0,5 | | +---------------------+------------------------------------+-------+-------+ | koreanchinese83 | SRR2KqbVN9yF6VUSvhfdzGUJsuoZ4De3JJ | 0,5 | | +---------------------+------------------------------------+-------+-------+ | Lapoterate | | 1 | | +---------------------+------------------------------------+-------+-------+ | Ledgerx | ShsVsiwnA6eoxJbHcKZsvmRHUtECTwRNyH | 1,5 | | +---------------------+------------------------------------+-------+-------+ | mahfuzur773 | | 1 | | +---------------------+------------------------------------+-------+-------+ | mananakau | Siq2UcqKM3ZV7NKuyYajdwQb52fMxTBoWM | 1 | | +---------------------+------------------------------------+-------+-------+ | markhourse | SYjTbymd6FXjXeDZ9GsBF2v1u7NLyY2k6x | 0,5 | | +---------------------+------------------------------------+-------+-------+ | marlonpangu456 | Sh5zTeS25e1BPvLAboX6e8ksNjFxvKf2DR | 0,5 | | +---------------------+------------------------------------+-------+-------+ | melodypastrana | SPZFqHWQiLiws6p6M6bkfFg4Qg9R9i8nj5 | 0,5 | | +---------------------+------------------------------------+-------+-------+ | merci (seven) | Sjd6HaRVnDjdEBRGzftyxw9ncdYtBgARCW | 1,5 | | +---------------------+------------------------------------+-------+-------+ | miner-joe | SeByxzg1SgiYZjpV3MTwynEFBB15dYYepj | 1,5 | | +---------------------+------------------------------------+-------+-------+ | monicosotto27 | Sjds17BunsRdPqu2P4n1qzFU7A6ffszAWu | 0,5 | | +---------------------+------------------------------------+-------+-------+ | monrawlatis | SSHSaX3uKF9umuAX6RHYPEAsx4MeHX8T3Z | 0,5 | | +---------------------+------------------------------------+-------+-------+ | Mr Babaca | | 1 | | +---------------------+------------------------------------+-------+-------+ | mrimando | SNo4aQqzYEo7xpodSVU5tFk51uFZsj9KTi | 1,5 | | +---------------------+------------------------------------+-------+-------+ | mz43n_41a | SNdfX6uvz182EQE2JJdFEAMqrc2E5xhy87 | 1 | | +---------------------+------------------------------------+-------+-------+ | nsayo141 | SgR2qQpMdENcUVCknebA9Eipen4x9EaM8Y | 0,5 | | +---------------------+------------------------------------+-------+-------+ | oksnanaoks | SjhegS3bqgAaFbD7yKk3YzCj6yChpzYDNu | 0,5 | | +---------------------+------------------------------------+-------+-------+ | Onlinejalsa | Sh2gphc61sctKZg9oMWDY5gffkyFMHC7pM | 1 | | +---------------------+------------------------------------+-------+-------+ | orowena82 | SgdhQViAr3ZTpFNsFrtgENj98ZrUgMDqiM | 0,5 | | +---------------------+------------------------------------+-------+-------+ | palisiga876 | SgywJ9961NFtHX6vWjRsBKoizT5Ytzzbxm | 0,5 | | +---------------------+------------------------------------+-------+-------+ | paulcanlas68 | SchbxAmuNA9dRRUQuxMoxB4jr3DDiiLoV8 | 0,5 | | +---------------------+------------------------------------+-------+-------+ | Pentium | SUaWuADEGcSMoGZEUy2hcVnVVMMF9EqUQa | 1,5 | 25000 | +---------------------+------------------------------------+-------+-------+ | PewwwDiePie | SVN9HmbzhjkgmknaEAsxSj6XjvNTPrd9ck | 1 | | +---------------------+------------------------------------+-------+-------+ | Pokerface | SW8FUUJH5T4wkVpdUC9HRWH1PSu2hqvK8A | 0,5 | | +---------------------+------------------------------------+-------+-------+ | pukong04 | STrJRhKkrb1BimpoxsSek7UH7Yr6GMP3Fs | 0,5 | | +---------------------+------------------------------------+-------+-------+ | rapier2383 | SescCEemXWzmKH1TdPqtbewzoMoicrqGBT | 1,5 | | +---------------------+------------------------------------+-------+-------+ | rommycostudio225 | SNrKmeszMErm5DVdeEdH1tV45Nbv8fGGfy | 0,5 | | +---------------------+------------------------------------+-------+-------+ | shiggadop | | 1 | | +---------------------+------------------------------------+-------+-------+ | SquireAu | SRGQk5nCHRfJ38SZxccJbVDGeXiBDUZ9jL | 0,5 | | +---------------------+------------------------------------+-------+-------+ | stenly8888 | SWARYnDgReAmJMcLptH9ce47pa6apFitcF | 1,5 | | +---------------------+------------------------------------+-------+-------+ | sweeesh | SNrLtP6uk6ogE2oiR4PXKuk3tMo1ixmSJK | 1,5 | | +---------------------+------------------------------------+-------+-------+ | tangayungtao | SbPx3UHGrAoaf9FsW8qugYwtEvvubsyiFx | 0,5 | | +---------------------+------------------------------------+-------+-------+ | Tbone | Sd6Gz4V3dUvHYgQSxQXuujB8caS4LJ897E | 1,5 | | +---------------------+------------------------------------+-------+-------+ | Tescott854 | | 1,5 | | +---------------------+------------------------------------+-------+-------+ | theonlynot | SgE2FLZvAYp4Gqp78STxsqQddwQ953uuGU | 0,5 | | +---------------------+------------------------------------+-------+-------+ | THuRiN | SWgUpJzdrReFHm3Gpv5e4mfNyyVSLfUZeQ | 1,5 | | +---------------------+------------------------------------+-------+-------+ | v1c3n2o | SfVsuDmAXWNRhaatyJxVA1SbNtgJ5HdGz2 | 1 | | +---------------------+------------------------------------+-------+-------+ | valivarthi | SVrmgoqKdnGu7AF8F2UtvoZhbFJCnvRh4v | 0,5 | | +---------------------+------------------------------------+-------+-------+ | Vee | SbYZUNDSNmcDSxkTi2tWm764q4KcphwMZq | 1 | | +---------------------+------------------------------------+-------+-------+ | Vichikuma | Sc2pBs3rmmsSFcp5RdKwoUkBkcTNGopFjm | 1 | | +---------------------+------------------------------------+-------+-------+ | walometung | SPaqzNo7Aphs2FLMW5bzgUkN8aNavYFmxy | 0,5 | | +---------------------+------------------------------------+-------+-------+ | williamhipolito71 | Sjk2wytDbupyFAM75aF1PqeHByCyjw5WMZ | 0,5 | | +---------------------+------------------------------------+-------+-------+ | ydumbroke | SNR8cGArKgWGBU6aYogGVzozYCuk24GBk6 | 0,5 | | +---------------------+------------------------------------+-------+-------+ | yourrightontime | SfHXnrw9LNXEWtW9iYJyZ36rNScHDeRsUL | 0,5 | | +---------------------+------------------------------------+-------+-------+ | Zohier | | 0,5 | | +---------------------+------------------------------------+-------+-------+ | zouhairrr | SSZ4uDrmjypeVNHPW28ukYh9Dh4yToBeRB | 1,5 | | +---------------------+------------------------------------+-------+-------+
  3. J3ll3

    Mandatory wallet update

    Hej everyone We have released a mandatory wallet update. I would everyone with a masternode and a wallet on their computer to upgrade their wallets asap. After we activate the new wallets, the old wallet will not be usable anymore and you are risk to loose PAWS when transferring funds. Also, if you do have a masternode, you risk that the rewards are no longer valid. Please download the new software from "Wallets" on our website https://paws.fund or from the #official-links on Discord. Many thanks The PAWS Team
  4. INTRODUCTION This is not something that is commonly supported by teams and projects, also not in this case. It is not part of the standard install script and not something we want to use time on supporting. And besides that, the general idea of the blockchain is also to have many masternodes spread out over the network, that are independant from each other to make the network as resilient as it can be through decentralisation. Combining masternodes on 1 VPS and even with one provider will introduce a centralisation to the network that in principle is unwanted and not good for the stability of the network and the blockchain. Imagine that 1 provider lost internet, taking 50 masternodes down. If that network only had 100 masternodes to begin with, it would mean that with 1 event 50% of the masternodes would go down. In that case the network is not very centralised and very easy to target with a denial of service attack. That becomes even worse, when you start combining masternodes on the same server. One software update could render a whole stack of masternodes useless, which is bad for the network and bad for the investor loosing rewards. Having said that... it is possible to run multiple masternodes on 1 VPS or server. The common approach to this, is by ordering extra IP addresses for the VPS from the hosting provider. Each masternode service can then be attached to an IP address. An extra IP address is often cheaper that getting an additional VPS and will therefore make a difference for those of your that have many masternodes. This document is provided as is and for the sake of proving that it can be done. Questions can be asked in Discord or here in the forum, but since it is not our supported method of installing a masternode we can choose to limit the amount of time supporting this. 1. ADDING ADDITIONAL IP ADDRESSES I'm assuming that the first masternode is running already on the primary IP address that the vps was created with. The first masternode can be installed using the standard installation script. The masternode will be running under the root user and the data directory will be placed in /root/.paws. I'm assuming this a Ubuntu 16.04 distribution, which is also required for our installation script. The first step is to order an additional IP address from your VPS provider. Lets assume for this document you got 1.1.1.2 255.255.255.0 Find out what your network interface is called. Execute the following command: ip a The output might be as follows: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:44:af:14:c1 brd ff:ff:ff:ff:ff:ff inet 1.1.1.1/24 brd 1.1.1.255 scope global ens3 valid_lft forever preferred_lft forever Make a note of the name of the network interface, in this case "ens3". Open the following file in the nano text editor: nano /etc/network/interfaces IMPORTANT: STEP 4 and 5 are for generic Ubuntu 16.04 systems. Use sted 6 and 7 instead if you are using Vultr as a VPS provider!! [SKIP IF ON VULTR] Now you will probably see something like this: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug ens3 iface ens3 inet static address 1.1.1.1/24 gateway 1.1.1.1 # dns-* options are implemented by the resolvconf package, if installed dns-search test.com [SKIP IF ON VULTR] Add the following lines and close and save the file by pressing Control-X, followed by Y (as in Yes): iface ens3 inet static address 1.1.1.2/24 [FOR VULTR] You will probably see something like this: source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto ens3 iface ens3 inet dhcp iface ens3 inet6 dhcp [FOR VULTR] Change it so it looks like this. This configuration was taken from the Vultr website and appears to work: source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto ens3 iface ens3 inet static address <your primary ip> netmask <your netmask> gateway <your gateway> dns-nameservers 108.61.10.10 post-up ip route add 169.254.0.0/16 dev ens3 auto ens3:1 iface ens3:1 inet static address <secondary ip> netmask <netmask same as above> Correct the test marked in red. In the Vultr dashboard, you should have a section where you can see IP addresses. The easiest thing to do now, is reboot the VPS. Once it returns, make sure that you primary masternode is running again: paws-cli getmasternodestatus As usual, it should indicate a status 4!! Confirm if the new IP address has been added to the server, by repeating the following command: ip a The output should now look as follows: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 52:54:00:af:14:c1 brd ff:ff:ff:ff:ff:ff inet 10.0.30.177/24 brd 10.0.30.255 scope global ens3 valid_lft forever preferred_lft forever inet 10.0.30.178/24 brd 10.0.30.255 scope global secondary ens3 valid_lft forever preferred_lft forever Congratulations. You have now added a second IP address to the VPS. 2. INSTALLING THE SECOND PAWS MASTERNODE Since the installation script was not made to install a second masternode, we will have to do this one by hand. The prerequisites are already on the VPS, since we used the script to install the first masternode, so this should not be very hard. The important thing here, is that we need to keep the data directories for all the PAWS masternodes separate to avoid them from overwriting each others files. We can do this by making a separate user for each PAWS masternode process, or alternatively we run all users as the root user and specify different data directories on the command-line when we execute the "pawsd" and "paws-cli" commands. In my experience, this is a personal preference. With regards to scripting, it will be easier to have it all running under 1 user... my personal preference is to have each process running under a separate user. That way we can use the usual commands without specifying the correct data directory, we simply have to remember to connect to the correct user. This setup will therefor create a new user for the new PAWS masternode instance. Create a new user: adduser paws2 You will have to enter information for this new user, starting by entering the password for this user twice, the remainder of the questions can be answered by pressing enter. The final question will be if all information was correct, press Y or Enter The output will look as follows: Enter new UNIX password: Retype new UNIX password: passwd: password updated successfully Changing the user information for test Enter the new value, or press ENTER for the default Full Name []: Room Number []: Work Phone []: Home Phone []: Other []: Is the information correct? [Y/n] A new user is now created. That user has it's own home directory which is located here: /home/paws2 We will now change to that user and start setting the new masternode up. The software was already installed by the script when we setup the first masternode. So... we change user as follows: su - paws2 We are now placed inside the users home directory, /home/paws2, which is exactly what we want. There is no need to install the software, as it was already installed earlier. We simply need to create a paws.conf file for configuration and start the masternode as "paws2" user. This will make the software detect that no ".paws" data directory exists, and will start downloading the blockchain. It is important to note, that each masternode installed on this VPS, will use diskspace to store its own copy of the blockchain. The first thing we do, is create the data directory for the new instance: mkdir .paws Before we configure, we need to collect some information we need in the next step: - Create or generate a password that is NOT the same as on the first masternode. Not something you need to remember. - Find and note down your secondary IP address - Generate a genkey in the local wallet in the next step and have it ready for step 7. In your local wallet, open Tools - Debug Console and type the following: masternode genkey it will produce a key in the following format: 7iHZk6GdTCn45BCj7fnAnxwHyue3RtWQFfi174iopFpnRGHikWn Make a note, we need it in step 7 on the VPS. And create the the configuration file. Open an editor: nano .paws/paws.conf Copy the following contents in the file: rpcuser=rpcuser rpcpassword=<password_mn2> rpcport=34126 rpcallowip=127.0.0.1 listen=1 server=1 daemon=1 port=34120 logintimestamps=1 maxconnections=256 bind=1.1.1.2 masternode=1 externalip=1.1.1.2:34120 masternodeprivkey=<genkey_created_in_local_wallet> #ADDNODES addnode=155.94.152.168:52362 addnode=155.94.152.168:52636 addnode=167.99.212.248:34120 addnode=173.199.115.155:34120 addnode=185.127.48.126:56534 addnode=192.3.162.117:58934 Items in red, need to be modified. The password is random, the IP address is the secondary IP address and the masternodeprivkey is the string generated in step 5. After you have made the modifications you exit and save the file by pressing Control-X, followed by Y The next step involves creating a statup file as root, to make sure that the second masternode automatically starts after a reboot. We exit from the "paws2" user and return to being "root": exit The prompt should now indicate that your are the root user again (prompt looks like root@myvps:/) We open a file called PAWS2.services in /etc/systemd/system as follows. The first masternode is started by a file called PAWS.services. We will add a file like that for each masternode we want to start on this VPS: nano /etc/systemd/system/PAWS2.service Add the following contents in the file: [Unit] Description=PAWS2 service After=network.target [Service] User=paws2 Group=paws2 Type=forking #PIDFile=/home/paws2/.paws/PAWS.pid ExecStart=/usr/local/bin/pawsd -daemon -conf=/home/paws2/.paws/paws.conf -datadir=/home/paws2/.paws ExecStop=/usr/local/bin/paws-cli -conf=/home/paws2/.paws/paws.conf -datadir=/home/paws2/.paws stop Restart=always PrivateTmp=true TimeoutStopSec=60s TimeoutStartSec=10s StartLimitInterval=120s StartLimitBurst=5 [Install] WantedBy=multi-user.target Notice text in red... it will have to be modified for this particular instance we are installing. It tells the system to start this masternode from the instance in /home/paws2 and run it as user "paws2" and not as root. Once you have done that... press Control-X, followed by Y to save and exit. We now tell the system, to start this process automatically at reboot: systemctl enable PAWS2 We are now very close to starting the second masternode for the first time, by issuing the following command: systemctl start PAWS2 The second masternode should now be synchronising. Change user to "paws2" as follows: su - paws2 All the commands we are used to, we execute as the "paws2" user now which sees the world relative to its own home directory. So as long as we are user "paws2" we will be looking at and talking to the second instance of the masternode that is attached to the second IP address (see step 7). Lets start by making sure the masternode synchronises: paws-cli getblockcount Keep repeating this command, until the number it displays is the same as the current blockheight on our explorer: http://chain.paws.fund Right... you don't continue here, before the blockchain is fully synchronised ๐Ÿ™‚ We now restart the process, by stopping it. The service will automatically make sure the masternode instance is started again quickly after. Issue the following command: paws-cli stop Wait for 1-2 minutes... then issue the following command: paws-cli getmasternodestatus It should return the following: error: {"code":-1,"message":"Masternode not found in the list of available masternodes. Current status: Not capable masternode: Hot node, waiting for remote activation."} You should now return to the local wallet, and add a line to the masternode.conf file as you would have done for any new masternode. Make sure you have another 1000 PAWS in your wallet and that you have a txid available. This is not specific to this guide and you should look at the masternode installation guide when you are in doubt. Add the following line. The genkey is the one generated in step 5. txid and index should come from the local wallet. The IP address is the secondary IP you have configured on the VPS: MN2 1.1.1.2:34120 <genkey> <txid> <index> Once this is done... restart the local wallet. And once it is back, start the masternode from the masternode tab. If you face the invalid IP error, the start the masternode from the debug console as follows: Tools - Debug Console and type: startmasternode alias 0 MN2 Now return to the VPS (still logged in as paws2) and issue the command: paws-cli getmasternodestatus It should return a status 4, for the second instance of the masternode. You have now completed the setup of the second masternode on the same VPS, using a secondary IP address. Now remember to be logged on as the relevant user for each masternode. The above setup has left the first masternode in the "root" account, meaning that you can communicate with it as usual. When you want to look at the status and manipulate the second masternode, you need to switch user to the user we created to run that second masternode: su - paws2 will be the command you are looking for. Now, when you run the usual commands, you will be referring to and manipulating the second masternode. Needless to say, that you could add a 3rd IP address, and if there is enough RAM and diskspace, you could create a 3rd user (paws3) and do the same thing again. Good luck!
  5. INSTRUCTIONS This guide is for those that want to do a manual update of their masternode running on a VPS. People that should not use this guide Please do not use this guide if you have your masternode with any of our masternode hosting providers as listed below. Those masternodes will be updated by your hosting service. You might have to start the masternode after they announce that they have completed the update: Stakinglab.io CryptoHashTank Nodehub.io GTM Snode Maiks masternode hosting service BitHostLive Pecunia MIDAS Apollon Detailed manual upgrade instructions This guide tells you in detail, which steps you should follow for updating your masternode running on a VPS. Alternatives are creating a new VPS and installing the masternode from scratch or rerunning the install script on an existing masternode. Remember to disable the masternode first using this command: systemctl stop PAWS Now... over to the instructions for a manual update: Login to the VPS using putty or any other ssh program that you normally use as described in the installation guide. You should now have a window with a black screen like the one shown below: The first thing you do, is stop the masternode service running. systemctl stop PAWS Wait like 10 seconds for the masternode service to shutdown properly. Now, change into the data directory, as we have to remove some files to make sure the upgraded PAWS wallet can be activated without a problem once we have upgraded. We need to remove the old blockchain and we do that as follows: cd .paws rm -rf blocks rm -rf chainstate rm mncache.dat rm peers.dat cd Make sure you add the lines one by one. I have had people experiencing problems cut/paste from this page... so if you experience problems, please type the above in by hand. The next thing we do is download the new software: wget https://github.com/pawsfund/PAWS-Core/releases/download/v1.1.0.0/paws-1.1.0.0-x86_64-linux-gnu.zip This should output some lines, that indicate the file is being downloaded. Once the prompt returns, we need to unzip the archive we just downloaded. Do the following: unzip paws-1.1.0.0-x86_64-linux-gnu.zip You should now have 3 more files in your home directory. Please do the following to make them executable: chmod +x paws* The files now need copying over the existing executables in /usr/local/bin. We do that as follows: mv paws-cli /usr/local/bin mv pawsd /usr/local/bin mv paws-tx /usr/local/bin We are now ready to start the masternode service for the first time: systemctl start PAWS We now need to wait and sit back. Repeat the following command with 1-2 minutes interval, or simply go for a coffee and check when you get back. The wallet is synchronising and the blockcount has to go up until it reaches the current block count. The current block count can be seen on the explorer in the top left corner as shown below. Once you confirmed that the blockheight is the same as on the explorer, you are ready to proceed with the final step. We need to restart the masternode shortly and the best results I have achieved by doing it as follows: paws-cli stop What happens here, is that we stop the wallet via the commandline, but since the wallet is running as a service the service will start it again once it detects it is shutdown. So this really means that the wallet is stopped, and started immediately after. You now have to open your local wallet and start the masternode, just like you did with your first installed the masternode. Chances are that it says it is enabled already, and this is because the wallet is really slow to detect that a masternode has going offline.This is a good thing, as it might prevent you from having to wait the initial 18 hours before getting your first reward. So open the local wallet, and start the masternode by selecting it and clicking "Start Alias". The final step is to check if the masternode has started. On the masternode (VPS) type the following command: paws-cli getmasternodestatus It should return something like: { "txhash" : "f1355f7864ff97f395b5b51a10ec5ckpe82b0f2c6170b6956ee81f264137821b", "outputidx" : 0, "netaddr" : "1.1.1.1:34120", "addr" : "PPUg6iQtMrHjhaYqxYrtFaxMjmcqLzC7pt", "status" : 4, "message" : "Masternode successfully started" } Status 4 means you are good to go. Any problems let us know here on the forum or on Discord. The PAWS Team
  6. INSTRUCTIONS The following instructions apply to updating the Windows wallet. Visit our website on https://paws.fund Click on "Wallets" in the top right corner as shown You will then land on the github repository with our new wallets. Pick the relevant wallet. At the time of this writing there was a linux "none graphical" wallet available and the GUI wallet for 64-bit Windows, which mostly applies to Windows 10 users. A Mac OS X wallet and 32-bit Windows wallet will be added as soon as possible Most people will want to install the wallet on their PC, and in that case I recommend using "paws-1.1.0.0-win64-setup.exe". The other file, without "setup" only contains the executables and will not create shortcuts in the Start menu. During installation, your Anti virus program might reject the new wallet. The wallet does not contain a virus, it is mere a file that the Anti Virus programs don't recognise yet. Please disable antivirus when installing and then add an exception for the wallet after it is installed. Then enable the anti virus program again. This will get better over time, as the Anti Virus programs update their databases. Before you start the new wallet, make sure you make a copy of the wallet.dat file, just to be sure. The wallet.dat file can be found in this location if you used the standard location for the data directory. Simply open an explorer window in Windows and paste the following in the pathfinder field right in the top: %userprofile%\AppData\Roaming\PAWS Like this: It should take you straight to the right directory. While you are in that directory, please remove the following directories and files: mncache.dat peers.dat blocks chainstate Simply select them in the explorer and delete them. Do not touch any other files. See below screenshot: Now install the new wallet, by double clicking on the file you just downloaded from github in step 4 and wait for that to finish. Once you start the new wallet, you will know it has updates if the spash screen says: v1.1.0.0 Blue Lacy Because we deleted the blockchain database in step 7 it should connect to the network straight away. It will have to download all the blocks from the blockchain. This will take time for some of you. You will have to let it complete the blockchain download, before shutting down the wallet. Your balance will start as 0 PAWS, but when the blockchain is downloaded, your balance should be reflecting your current balance. PROBLEMS Unfortunately, I have yet to see a wallet update that goes completely without problems for every single member of the community. If your run into the situation, that it will sit there for saying that there is no source to download from, we might have to add IP addresses to the confirmation file, to tell it where to collect the blockchain. It should be able to figure that out by itself, but we have experienced that this does not happen. In that case, you can do the following: Open the wallet, if not already open, and go into the following menus... Tools - Open Wallet Configuration File like shown below: It should open a notedpad with an empty file. If you have already something in there, then that is ok. If you see some lines starting with addnode you should replace them with the below lines. If there is nothing there, then simply paste the below lines in the notepad window: addnode=159.89.118.15:34120 addnode=167.99.71.71:34120 addnode=173.199.126.95:34120 addnode=173.56.91.83:56595 addnode=178.128.72.108:34120 addnode=192.3.162.134:34120 addnode=195.201.132.217:34120 Now choose File - Save and close the notepad window. Close the wallet, and wait for it to shutdown properly (this you should always do). Now start the wallet again... it should connect to a source straight way. Again... let it fully sync for your balance to reflect the correct value. If you have any issues, please contacts us here in the forum or on Discord. The PAWS Team
  7. J3ll3

    Security Announcement!

    IMPORTANT SECURITY ANNOUNCEMENT Incident Report The PAWS Team would like to inform the community of an incident recorded on the PAWS blockchain and the actions we have taken to mitigate the issue and will be taking in the next coming days to fix it. What does this mean for you? What does it mean for the average investor or user of our network? Nothing at all. Your funds are safely stored in your wallet or at our partners services. There have been no theft of any of your holdings. The attackers have been able to take a larger share of the staking rewards than they were entitled to, which is theft from the community. We have now reduced the influence from these attackers, by enabling staking on our large wallets containing the Donation Fund and the Operational Fund, reducing influence from any malicious party. We will keep this in place, until the updated wallets have been released and the entire network has been upgraded. We do need your help with the following: Once we make the announcement that wallets need to be updated, we urge all of you to download the new software from our GITHUB and upgrade your wallet. DO not under any circumstances download any software from anywhere else but our github repository which can be found in #official-links and under the "Wallets" link on our website. If you know of someone that has a wallet, make sure they update the wallet before doing ANY transfers. String of events On 13/1/2019 we started recording strange transactions on the blockchain in the PAWS network, that we initially treated as an anomaly or a wallet that had gone crazy. The transactions started from 1 address containing 942 PAWS, which was then split in many small amounts on many addresses. Over a period of 2-3 days, we noticed that someone or more likely something was moving the small amounts from those addresses to new addresses, sometimes with only minutes in between. The transactions contained many input addresses and many output addresses with unequal sizes. This is not something that can be created with our wallet. Other symptoms were that the multisend features seized to work on many wallets, and the machines staking the big wallets were showing bigger memory and cpu consumption. The multisend feature is probably affected by the larger memory consumption caused by the large transactions being placed on the network. Our analysis showed, that these actions were causing the initiator of these transactions to gain more staking rewards than he was entitled to. And that also meant, that this person was able to validate more blocks that he was supposed to. And finally, the large blocks did put an additional strain on many of the machines running wallets, as the blockchain was growing faster that it should normally, and using more RAM and CPU on validating block. We did not consider these actions to be a bug or a mistake. To us it looked like a deliberate action from someone, to either hurt the network or obtain funds they were not entitled to. On 21/1/2019, we reached out to a number of fellow community blockchain projects, as we observed similar patterns on their blockchains. Responses were positive. We also managed to make contact with the PIVX community later that day. This was not an easy task, but we got in touch with some good people that could work with us on finding the problem. Initial response The only addresses that are owned by PAWS that are staking, are the 6 corporate masternode addresses. Since we could clearly see, this was an issue with staking and was not impacting the masternode reward distribution. The largest staking addresses were the 6 corporate masternodes, but those were not able to prevent the attacker from taking more than 25% of the staking rewards. We decided after a few days to activate staking of our Operational Fund (PXFUND), which meant a significant lower portion of staking rewards went to the attacker. The Operational Fund contains a significant number of coins, which means that it can win a large number of staking rewards. Activating staking on this address, obviously means that PAWS is getting those rewards that we always promised should go to the community. During a short period we also added the Donation Fund to the pool of staking addresses (PDFUND) which caused 75% of the staking rewards to go to PAWS operated addresses, very little to the community and almost none to the attacker. Since this is a serious situation, we have bypassed that promise for now, until the situation is under control. We will obviously disable staking of those addresses, as soon as the problem is fixed. And we might find a way to return those staking rewards to the community at a later point in time. The problem Details of the problem can be found in a paper published by 3 students of the University og Illinois and their mentor. In the summer of 2018, they explored possible vulnerabilities with regards to validation of Proof-of-Stake before committing resources. What started as a paper to proof whether or not it was possible to exhaust resources in the PoS blockchain, also uncovered other issues related to inadequate validation. What we have been experiencing is what is called stake grinding, which is an attack vector to try and manipulate the stake selection algorithm in ones own favour. This can be used to obtain funds they are not entitled to, but it can also lead to taking control of the network What we have been experiencing is called stake amplification, which is mentioned in the medium.com article in the bottom of this article. What it means is that one can obtain a heavy staking weight, usually reserved for wallets with many coins, with a relatively small amount of coins by amplifying the weight of those coins. In practise this is achieved by adding lots of transactions to the blockchain that are not necessarily valid but will give weight to your staking addresses. Those transactions are accepted due to inadequate validation checks that will allow such transactions if hidden away in a bunch of valid transactions. Permanent Solution After we got in touch with the PIVX community and some of their developers, we have been able to find a solution. This is being tested in our testnet as we speak. Once the fix has been implemented in our wallet, we will release a new version of the wallet. This is a mandatory update. All investors that use a PAWS wallet as well as investors with one or more masternodes, will have to update their wallet. We realise that this is cumbersome and stressful for some, but we will provide instructions and an update script to help those operating their own masternode. Those that use (shared) hosting services will not have to worry, as the upgrade will be performed by our partners. Also exchanges will have to update the wallet, which might cause a small downtime in service. The release of the new wallet is scheduled before the end of this month. It is needless to say, that we will be on discord supporting all of you that need help with upgrading their masternodes. Aftermath We are convinced, that the attacker is using the same mechanisms to attack several other PoS blockchains gaining the same advantages. We will be working with those teams that are interested to resolve the issue on their blockchain as well. In the end it is in the interest of all our projects and their honest investors that the blockchain they use to transfer and store their funds are secure and safe. We will continue to monitor our blockchain in the future as we have done until now and act as necessary to protect our investors and our own interests. This incident report emphasizes that we want a open and transparent dialog with our community. Links to detailed information (especially the section on stake amplification): https://medium.com/@dsl_uiuc/fake-stake-attacks-on-chain-based-proof-of-stake-cryptocurrencies-b8b05723f806 We would like to thank: Sanket Kanjalkar, Joseph Kuo, Yunqi Li, Andrew Miller University of Illinois, Urbana Champaign For their finding and the detailed doc they have created http://fc19.ifca.ai/preproceedings/180-preproceedings.pdf
  8. Introduction This article is explaining the most commonly used tips and tricks that I use to start a troublesome masternode. It has to be said, that some newly installed masternodes start at the first attempt, while at other times it seems to be nearly impossible to get it going. One trick appears to be resolving a troublesome masternode in over 90% of all cases, while the remaining tricks might be needed in the last 10%. You should go through the procedures from tip to bottom, trying number 1 first! Please not that these procedures are for those that choose to install a masternode from scratch on a VPS or computer at home using our installation script that can be downloaded from Github. It requires that you have ssh access to the masternode. Masternodes provisioned by our hosting partners, may need you to contact the partners support lines. TRICK #1 1.1 Procedure A very common problem people run into is that when you have installed the masternode with the script and has fully synchronised, that when you try to activate it from the masternodes tab in the local wallet you are presented with the following error: (Thanks to Discord user @AlexaUA for uploading this screenshot) The first time I encountered this problem, I spent a lot of time trying to work out what IP address exactly was wrong. And I imagine some of you have been going through the same process. I found the answer on a DASH forum, which means that this error has been inherited from DASH and PIVX. All masternode coins derived from DASH and PIVX must have this problem, unless they have fixed it themselves. The answer is simple. You can start the masternode in the local wallet by using the Debug Console. The Debug Console can be accessed by choosing Tools from the top menu, followed by Debug Console (1). After that you type the following in the text box as shown below (2): startmasternode alias 0 VPS07 Bear in mind, that the VPS07 is the name of the masternode you have used in the masternode.conf file when you setup the masternode in your local wallet! As soon as you press enter, the following, or very similar output, should show in the Debug Console window: { "overall" : "Successfully started 1 masternodes, failed to start 0, total 1", "detail" : [ { "alias" : "VPS07", "result" : "successful", "error" : "" } ] } You should now see the masternode as enabled in the masternode tab. 1.2 Verification This step is very important, to make sure the masternode has started. If you don't verify this, and the masternode has not "received" the activation, it will switch to MISSING again after a few hours and no rewards will come in. After you see the "Successful" message in 1.1, you need to login to the masternode with SSH, just like you did to install it. Now you need to run the following command on the commandline prompt: paws-cli getmasternodestatus It is very important, that the status that is displayed in the output is 4 (four). If it is, all is in order, and you should start to see rewards after an initial wait of 3x the reward cycletime as displayed on our explorer (http://chain.paws.fund) in the top left corner. Please contact us on discord if your experience problems. TRICK #2 2.1 Procedure If the masternode does not start after the verification in 1.2 has been performed, you can do the following. This procedure is know to start 90% of all masternodes that will not start after enabling it in the local wallet. Use SSH to login to your masternode. You should see a prompt as follows: root@yourvps:~$ Now you should stop the masternode service by typing the following command on the above commandline prompt and press enter. Do not proceed with the steps below, until the above shown prompt has reappeared: systemctl stop PAWS After that you execute the following commands one by one. Do not paste them all in at the same time, it is important that we see possible errors that might occur. The below commands remove the blockchain database on the masternode and will force it to download a clean copy from the network when the masternode is activated again: cd .paws rm -rf blocks rm -rf chainstate rm -rf peers.dat rm -rf mncache.dat cd Now we need to start the masternode service again. The masternode software will detect that the blockchain was removed and start a fresh download from the blockchain. This will take some time, so please be patient: systemctl start PAWS The service starts in the background and the prompt should reappear. Do not logoff from the server yet. We need to wait from the masternode to synchronise with the blockchain. We can do this by executing the following command multiple times, until the block count is the same as on our explorer (http://chain.paws.fund): paws-cli getblockcount The response will be a number, which is the current block that has been downloaded from the blockchain. This number will be low initially, but increase rapidly until it reaches the current blockheight of the PAWS blockchain. Please repeat the command, until you are satisfied that the number returned by the above command is the same as the blocknumber on our explorer in the Status section (http://chain.paws.fund). Once the numbers match, you can return to the local wallet, and try and start it from the masternode tab in your local wallet. If you are presented with the "Invalid IP" error, please look at TRICK #1. 2.2 Verification This step is very important, to make sure the masternode has started. If you don't verify this, and the masternode has not "received" the activation, it will switch to MISSING again after a few hours and no rewards will come in. After you see the "Successful" message your local wallet, you need to execute the following command on the masternode on the commandline prompt: paws-cli getmasternodestatus It is very important, that the status that is displayed in the output is 4 (four). If it is, all is in order, and you should start to see rewards after an initial wait of 3x the reward cycletime as displayed on our explorer (http://chain.paws.fund) in the top left corner. Please contact us on discord if your experience problems!
  9. J3ll3

    PAWS coin supply update

    At PAWS we have done our best to design the currency specifications in a way that would, in our vision, minimise the inflation issues that many others have faced, allowing us to work on the products instead of having to worry about loss of value. We know all of you to believe in our project and hold on to your coins, but the specifications have also contributed to it. Looking at http://chain.paws.fund/#/coin, you will see that we have a current coin supply of 720000 PAWS. As @ian | PAWS announced last week, we have placed 450000 PAWS of the original premine of 500000 in our VAULT (http://chain.paws.fund/#/top). It is pretty amazing, that we have basically kept our premine almost intact, instead of flooding it onto the market to cover our expenses. At the moment we have 170000 PAWS locked in collateral, as we have 170 masternodes. This means that 170000 + 450000 = 620000 PAWS are currently locked, which leaves about 100000 PAWS (roughly 14%) available for trading on the market. It is probably one of the factors, along with good investors that believe in the project, that we can still offer our investors an ok price on the exchanges. I hope, for all our sakes, that it will stay this way until we can deliver on our goals and visions. Thanks for your continued support! The PAWS Team
  10. J3ll3

    Paws wallet won't reopen

    Hej, We resolved the issue in discord, right? -J3ll3
  11. The biggest disappointment has to be found in the Twitter and Facebook bounty. We have received 5 valid entries in the Facebook bounty and 4 in the Twitter bounty. The rules were defined by our Bounty Manager, and were as follows: 1. Minimum number of friends 200 2. 25 posts made in the duration of the bounty 3. Max. 2 posts per day 4. An email with the links to the posts/tweets had to be send to the Bounty Manager REMEMBER that the first payout will be processed on 1/1/2019 Here are the results for the Facebook and Twitter Bounty. As it stands at the moment, the empty seats of the Facebook and Twitter Bounty masternodes will be allocated to the Charity and Donation Funds. Congrats to all the winners... use your PAWS well Twitter winners: DISCORD SHARE % tursam 2.5 Lilia 2.5 Aviz 5 Poseidon#1735 2.5 Facebook winners: DISCORD SHARE % tursam 5 Lilia 5 Aviz 5 Poseidon#1735 5 memon89#7303 5
  12. The results for the article bounty have been disappointing. We were counting on 30 articles, 10 high quality and 20 medium quality. We ended up with receiving only 15 articles that were worth placing in the list. The result were not articles at all or simple a list of links to our website. I will be publishing the links to the articles here, and the share in a masternode they have one. I have PAWS addresses for all the winners. Congrats to all the winners and thank you for taking the time to publish an article about us! REMEMBER that the first payout will not be before 1/1/2019 LINK TO CONTENT SHARE % https://steemit.com/airdrop/@sadikulaziz/paws-the-blockchain-based-animal-charity-platform 5 https://medium.com/@bebechai11/paws-coin-d6b2c9c67dd5 5 https://blog.goodaudience.com/paws-a-gift-from-crypto-community-to-all-animals-and-to-people-who-loves-them-2868a5f88432 5 https://steemit.com/crypto/@swcrypto/paws-up-blockchain-to-the-animal-rescue 5 https://mahfuzur773.blogspot.com/2018/11/paws-are-group-of-people-has-changed.html 5 https://medium.com/@mr.shachenok/paws-animal-charity-13a5de413c98 5 https://medium.com/@minstroy/paws-fund-will-help-animals-cddb493e6f9e 5 https://steemit.com/pawsfund/@informerbro/everything-you-need-to-know-about-paws-fund-coin-in-hindi-urdu 5 https://steemit.com/blockchain/@airdropelves/paws-fund-an-animal-charity-project-on-the-blockchain 5 https://medium.com/@leesery79/paws-funds-animal-charity-dae453b9d98d 2.5 https://medium.com/@nickojohn/paws-fund-coin-animal-lovers-charities-coin-specifications-cd02932cc48c 2.5 https://medium.com/@cook555/dear-all-f0335d603b63 2.5 https://medium.com/@tulanserghei/pawscoin-430094ed588d 2.5 https://siteall1tool.blogspot.com/2018/11/paws-about.html 2.5 https://medium.com/@andrewkan_2585/%D0%B1%D0%BB%D0%B0%D0%B3%D0%BE%D0%B4%D1%96%D0%B9%D0%BD%D1%96%D1%81%D1%82%D1%8C-%D1%82%D0%B0-%D0%B1%D0%BB%D0%BE%D0%BA%D1%87%D0%B5%D0%B9%D0%BD-ea8271570d13 2.5
  13. The Youtube video contest did not contain enough medium and high quality videos to completely fill. 3 high quality videos were not found. I need @DKGLOBAL to get in touch with me, as I don't have a PAWS address to make the payouts to. Congrats to the winners. REMEMBER the first payout of the share masternode is on 1/1/2019. The results are as follows: Discord LINK TO CONTENT SHARE % GILLIARD #9134 https://www.youtube.com/watch?v=_byR-ml3VHw 10 age7397 https://youtu.be/ndx4PbK9IgU 10 DKGLOBAL https://youtu.be/dsqWPEWvhK0 5 conghuy55hk #8062 https://www.youtube.com/watch?v=UB1374lBZKs 5 kluh1271 https://youtu.be/-2ctbr6Z4E8 5 ferinoer#5691 https://youtu.be/Sx-38FTg_3w 5 naim8562#5956 https://youtu.be/Fw5JWhUeCw8 5 HABIBSADI#9310 https://www.youtube.com/watch?v=KmPCCzyuX-w&feature=youtu.be 5 abuzein#4464 https://youtu.be/xec_8NH8hG8 5 rfsraofaisal #4887 https://youtu.be/VbWuLVF5Wug 5 cook555 #2474 https://www.youtube.com/watch?v=6cvYQEMfcsk 5 memon89#7303 https://youtu.be/spGxOLrdu0w 5
  14. DISCORD/TELEGRAM USERNAME POSITION SHARE % Abhiag #9039 1st 30 ryap12#5545 2nd 5 naim8562#5956 3rd 5 ajaysingal0001#5667 4th 5 age7397 5th 5 Oleg K. 6th 5 ramilvale#5257 7th 5 Hombre#5467 8th 5 hindicrypto 9th 5 memon89#7303 10th 5 gift_nanj 11th 2.5 iguessitsokay 12th 2.5 maks761 13th 2.5 Noah#2828 14th 2.5 Vyacheslav#5431 15th 2.5 cryptoprocent 16th 2.5 Law1980 17th 2.5 abuzein#4464 18th 2.5 Drokzid#8697 19th 2.5 earnincrypto #7627 20th 2.5
  15. Woof! Woof! ๐Ÿ—ž๏ธDear PAWS Community, We have now added the first 4 team members to our website. With more to follow! ๐Ÿ’ช Check Meet the Team at https://paws.fund/ We are a real team with real objectives and have nothing to hide and nowhere to run. Look out for more updates soon.. @everyone PAWS Team
×

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.