Topic: WOC2 - WarOfCoins - MASTERNODES - page 3. (Read 31581 times)

I thought so too but the dev posted new wallets a few posts back and masternodes work, so who knows what might happen?

PS: Please dont tell my wife that f*** is dead.

I thought this coin was dead as fuck?

Reserved

Step 4 -  Fund the masternode collateral address

There are two places you can get this address. The first is in the “receive” tab in the wallet, next to the alias name you specified when creating the config. The second is under the “WOC2 masternode” tab under “My WOC2 Masternode Nodes”. The address is under “collateral Address” next to the listed Masternode.

Before you send cones to the address, make a backup of the wallet.dat onto a USB stick while still unencrypted and rename to wallet.dat.old. Then encrypt the file like normal and then make a backup of the wallet.dat again to the USB stick. Store the USB stick in a safe place.

Now you can send coins to the address and it must be exactly 10,000 coins. If you forget about fees or send in more than one tx or the amount is more or less than 10,000 then it wont work and then you have to move the incorrect coins out and the correct number back in.  Once the coins have been confirmed 15 times, you can do the next and final step.

Step 5 - Start the MN and verify it is working

Go tot the debug menu in the local wallet on your client Windows PC. In the block type “masternode start yourwalletpassword”. Replace yourwalletpassword with your wallet password. You should now get a message “Masternode successfully started”. Press the minus bottom right to clear the screen. Go to the WOC2 masternode tab in the Windows wallet and and select “WOC2 Masternode Network”. The IP address of your 768MB VPS MN should be listed there with a “1” next to it meaning it is active. You can in the debug menu execute the command "masternode list" to see the active masternodes which should include yours once the network picks it up, or alternatively you can go onto the remote VPS MN and in the ~/opt directory execute "./WOC2d masternode list" which should also list the active masternodes. Your wallet on the PC needs to remain open else your MN will shut down. Once in a while when a tx goes through your MN, you will see an amount received in your wallet. This amount seems large, but the correct number of coins are accumulated in your dashboard total. Once you close and open your wallet going forward, all confirm transactions in the history will change to the correct amounts.

If you find any issues with the above process or if anything us unclear, please let me know so that I can correct them.

Tip addresses:
BTC: 1Zo7xetyMTnnKTXe1nbUy84JxXy9SU2bD
LTC: LKwveyFi15R3aBMbAtKgM35SNg6rGGMLXZ
WOC2: WXmbydNUAaniyVQyU7GKq1gJTPDCZ5siZt

Step 3 - Prepare the local wallet and its config

I assume you have a Windows machine  for your local PC wallet. I might later add instructions in the guide to setup a local wallet using Linux command line or Raspberry Pi. Install the Windows wallet like normal . You may get a connection from a built in sync node and if you do let it sync up. You now need to make sure that the  local PC wallet .conf file is set up correctly.

Command 1: Go to c:\users\yourusername\AppData\Roaming\WOC2 (You should see a whole bunch of files here including the wallet.dat)

Command 2: Right click with your mouse and select “new” and then “text document” and name it WOC2.conf

Command 3: Edit WOC2.conf and enter the following lines:

rpcuser=salkdfhadskljfh
rpcpassword=oasdjfosdajf
rpcallowip=127.0.0.1
rpcport=9988
server=1
listen=1
daemon=1
staking=0
port=9999
masternode=1
masternode=yourMNIPaddress:9999
masternodeprivkey=
addnode=85.25.214.175
addnode=45.55.165.71
addnode=173.76.30.194
addnode=45.63.122.61
addnode=107.170.57.24
addnode=185.92.222.31
addnode=45.63.1.27

(You must replace “yourMNIPaddress” above with the IP address of your 768MB masternode VPS you created. The port here can be anything but must be the same as the port you specified in your 768MB VPS WOC2.conf.  We will come back later to enter the MN private key and for now we leave it blank. Save the file and exit notepad.)

Now go back to your Windows wallet on the Wndows PC.  Go to the tab above “WOC2 Masternode” Under that option select “My WOC2 Masternode Nodes” This step not really necessary as the same can be achieved with command line options, but this tab just makes it “easier” through visual commands. Select “Create” and enter an Alias name eg. “MN1-US”. Enter the IP address of the 768MB MN VPS you created earlier followed by the colon and port number :9999. Again, although the wallet specifies port 9999 it can be anything, as long as it is configured consistently in all the files so far.) Now click on “get config”. Select the masternode private key – the long string of characters and go paste it in the line that we left blank in the WOC2.conf file on the local Windows machine. Close your Windows wallet down and re-open. The wallet tends to take a while to close down the running process and if you are too quick it will complain that it cannot get a lock. If this happens, just crt-alt-del to get to the task manager and kill the WOC2 process. Your local wallet is now running and also your VPS MN wallet.

Step 2 – Prepare the MN wallet and its config

You have a choice when preparing the MN wallet. You can either download the pre-compiled binary that was created in an identical environment or compile the binary yourself. If you use the pre-compiled binary, you can skip the A - Compile section and its 10 commands and you do not have to prepare the 2GB VPS and you can continue at the B - Using the pre-compiled binary section. If you decide to compile yourself, then do section A, skip B and do C.

A - Compile section:

You now need to deploy another VPS with 2GB of memory. Select everything the same as above except the choose the server with 2GB of memory. Execute the same commands above up to command 11.

Command 1: “cd ~/opt” (This takes you to the directory where you will be compiling the wallet)

Command 2: “git clone  https://github.com/warofcoins/WOC2” (This pulls the source code from the git repository into the WOC2 folder in the ~/opt directory)

Command 3: “cd ~/opt/WOC2/src/leveldb” (You must make sure that a specific build file has the correct permissions)

Command 4: “sudo chmod 755 build_detect_platform”

Command 5: “cd ~/opt/WOC2/src”

Command 6: “mkdir ~/opt/WOC2/src/obj/crypto (the dev forgot to add in this empty directory. These things happen from time to time and normally when a compile crashes it is because the directory does not exist where the compiler needs to place some files)

Command 7: “sudo nano makefile.unix” (we need to change a parameter in the unix makefile) Look for the line close to the top that says USE_UPNP:=0 and change the 0 to a 1. (I prefer to have U_PNP enabled at the startup of the wallet.). press ctrl-x to save, say yes and press enter.

Command 8: “sudo make –f makefile.unix” (This starts the compile process to create a headless daemon wallet).

Command 9: When the compile has successfully finished, execute “strip WOC2d” (this command makes the binary smaller by removing all non-essential content from the file.)

Command 10: “scp ~/opt/WOC2/src/WOC2d user@yourMNIPaddress:/home/user/opt” (This command copies the compiled binary from the 2GB VPS to the 768MB VPS. You will be asked to add the destination server locally and just type yes. Also remember to replace yourMNIPaddress with the IP address of the 768MB VPS  you created earlier. Also change “user” in user@yourMNIPaddress and also “user” in /home/user/opt with the username you created when you created the 768MB VPS)”  You are now done with the 2GB VPS, but before we destroy it, lets first make sure that everything is OK on the 768MB MN VPS.

B - Using the pre-compiled binary section:

In your Vultr management console, go to your 768MB VPS and view the console.

Command 1: “cd ~/opt” (go to the directory where the binary will be placed.)

Command 2: "wget https://bitbucket.org/jc12345/woc2mn/downloads/WOC2d (click here for Virustotal scan and here for checksum and here to download the headless daemon wallet onto a PC)

Command 3: When the file has downloaded execute "sudo chmod 755 WOC2d"

C - Preparing the MN .conf file section:

In your Vultr management console, go to your 768MB VPS and view the console.

Command 1: “cd ~/opt”

Command 2: “ls –la” (make sure that the WOC2d binary is there)

Command 3: “./WOC2d” (This creates the file structure in the correct place, but for illustration purposes it also shows you that it could not find a .conf file)

Command 4: “cd ~/WOC2” (Lets go to the folder where the wallet is stored)

Command 5: “ls –la” (just checking that we are in the correct place)

Command 6: “sudo nano WOC2.conf” (Creating the .conf file for the remote masternode)

Type the following into this file:

rpcuser=salkdfhadskljfh
rpcpassword=oasdjfosdajf
rpcallowip=127.0.0.1
rpcport=9988
server=1
listen=1
daemon=1
port=9999
addnode=85.25.214.175
addnode=45.55.165.71
addnode=173.76.30.194
addnode=45.63.122.61
addnode=107.170.57.24
addnode=185.92.222.31
addnode=45.63.1.27

(In the above example the rpc section is not really used, but the wallet wants it to be there. Also note that the rpcport can be anything, as long as it is not already used by another process. The port above can also be anything. The fact that the wallet on the client machine later on suggests port 9999 is just a remnant from the DASH implementation way back that picked port 9999.)

Press ctrl-x to save, type yes and press enter.

Command 7: “sudo ufw deny 22” (shutting down the ability to SSH to the server)

Command 8: “sudo ufw allow 9999” (Allow incoming connections on port 9999)

Command 9: “cd ~/opt”

Command 10: “./WOC2d” (you now start the remote masternode and it will start to sync the blockchain)

Command 9: “./WOC2d” getinfo (like in Windows, the wallet commands in the debug window can be run on the Linux VPS by adding it to the back of ./WOC2d. If you execute this command from time to time you can see that the blocks are increasing as the chain is synced. At this point the Linux remote Masternode is setup and waiting for a connection from the client machine. If the WOC2d daemon is running fine on the VPS and synced up, you can go back to the Vultr control panel and destroy the 2GB VPS. Make sure that you do not destroy the wrong VPS!

This guide will work with most coins if you replace the relevant coin specific references. Different coins have different methods in the wallet to get the masternode info and it is possible to get that info by clicking on the wallet buttons, or to execute certain commands in the debug menu. You can use whatever method you chose to get the masternode private key and the collateral address. This guide also assumes little to no knowledge of Linux and provide in-depth step by step commands to enter. I will add further sections on how to run multiple MN on one VPS as well as how to setup a MN on a local Win PC.

When you want to setup a masternode (MN) you have to make an architectural choice between whether you want to run it locally (on a PC) or if you want to run it remotely (on a Virtual Private Server (VPS) in the cloud). I do not recommend running a MN local on a PC due to last mile constraints in many places in the world that could impact your MN reliability. A big advantage of running MN in the cloud and the client on your local PC is that the MN in the cloud will be tapping into a thick reliable pipe to the Net provided by the VPS provider that will improve your MN reliability. This guide therefore focuses on setting up a MN remotely on a VPS and running a local client on your PC where the MN wallet with its coins are kept.

Setting up a MN in the cloud consist of five steps:
1)   Rent, setup and prepare the VPS itself
2)   Prepare the MN wallet and its config
3)   Prepare the local wallet and its config
4)   Fund the MN collateral address
5)   Start the MN and verify it is working

Step 1 – Rent, setup and prepare the VPS

I recommend using Vultr.com (click here to go to Vultr)  for this because they accept Bitcoin for payment. Also, once funded, you can deploy more than one VPS and all of them just tap into the funded amount as time goes by. So signup and rent a basic VPS for BTC equivalent to $5 per month. On a basic VPS you can run about 4-5 wallets. If you have money and want to run even more wallets on a server then rent a bigger one. Assuming you go for the basic server, go to deploy and select the following specs:
- Location – I found New York and Amsterdam to work smooth so pick one of these.
- Select a 64bit OS of latest minus one. I say this because latest is not always the greatest in the beginning. Ubuntu is pretty good and Linux just works smoothly so select Ubuntu 14.10 x64.
- Select the smallest server specs 1 CPU, 768MB, 15GB storage, 1000GB transfer. In general to compile a wallet you need at least 2GB of memory but a server with 768MB memory is sufficient to run it. This guide therefore recommends 768MB of memory for longer term rental and to rent another server of size 2GB memory just for a few minutes to compile the wallet and then destroy the 2GB server afterwards.
- Select optional features “Enable IPv6”. Don’t worry for now on SSH keys for now.
- Give your server a name in the label eg. MN1-US or whatever you like.
- Select “place order”

Now wait a few minutes while your VPS spins up. When it is done it is now time to configure the VPS. Go to “My servers” look for your server and select “manage”.  In the next tab click on view console. A black box will appear on the screen with a bunch of first time use messages. Enter “root” for the username and the password on the Vultr management console. If you don’t see the prompt for the username initially, don’t worry, just enter it and if you get the it wrong it will then show you the prompt to enter the username. Once you logged in as “root” execute the following commands without the parenthesis. I will assume from this point forward that your username is “user”, but change it to whatever you want to use to log on the server as and wherever I use “user” substitute with your username.

Command 1: “adduser user” (creates a new user that is not a superuser. Just press enter through all the questions after that. At the password select a proper difficult password.)

Command 2: “sudo adduser user sudo” (Adds your new user to the sudop group that allows the account to assume superuser rights when needed)

Command 3: “logout” (You don’t want to do general stuff on a server as root)

Command 4:  Login with your newly created userid and password

Command 5: “sudo ufw enable” (Make sure that the firewall is enabled)

Command 6: “sudo ufw limit 22” (prepare the firewall to allow ssh and scp connections which are needed to get certain files onto the server)

Command 7: “cd ~” (The ~ character is a short character to represent your user’s home directory. It is the same as using /home/user)

Command 8: “mkdir opt” (This creates an opt directory in your user directory where you can store files or do compiling. This directory can also be called something else and it is up to user preference.)

Command 9: “sudo apt-get update” (making sure that the server knows of all the new packages that are available)

Command 10: “sudo apt-get update” (making sure that the packages in the default install are upgraded to the latest versions.)

Command 11: “sudo apt-get install -y qt4-qmake libqt4-dev libminiupnpc-dev libdb++-dev libdb-dev libcrypto++-dev libqrencode-dev libboost-all-dev build-essential libboost-system-dev libboost-filesystem-dev libboost-program-options-dev libboost-thread-dev libssl-dev git htop zip unzip (this installs a broad bouquet of libraries that you would need in general to compile and/or run dynamic binaries and also includes certain useful utilities. If you made a typo, no worries, just press the up arrow on the keyboard to give you the previous command and you can fix the typo and press enter again)

Command 12:  “mkdir ~/.WOC2”

This coin is POS only.

sgminer.exe --algorithm darkcoin-mod -o http://127.0.0.1:18450 -u bankmyrik -p x -E 1
My bat do not work in solo.
127.0.0.1 slow/down or URL or credentials invalid.
Tell me what my problem?

45.55.165.71 is main node. 107.170.57.24 also seems to be very active.

Hello. I need nodes. Please, tell me.

It seems that there are 11 masternodes up and running.

I was missing it, added, thanks man.

Yes. I am busy writing a guide for setting MN that I will post here. Your problem is probably because you are missing "staking=0" in the local woc2.conf file on your PC.

Is there a way to lock the masternode addresses with the 10k in them so that they do not get split up in anyway, I keep having mine stop since the inputs are split instead of being a single input of 10k.

OK - thank you for your response.

This bug was really overlooked by mistake and has been fixed long time ago. It was confirmed that no coins were created via this bug.

I got interested in this coin today because I heard it has masternodes now. However, reading through this thread, I see that Bittrex detected a hashrate exploit early on and would not list the coin.

I am absolutely not trying to create FUD, but I am very curious - why hasn't this issue been a bigger deal? It looks like the dev uploaded a fix after the revelation from Bittrex, and no one has brought it up ever since.

Has it been shown that the exploit existed from a previous code base and the current dev just overlooked it by mistake? Because if not, then it would seem like the dev is clearly a scammer who got caught, then uploaded a fix to his own exploit when he was exposed.

Again, I'm not trying to cause FUD, but am I missing something here?

Close your wallet and open it again. All confirmed blocks will be shown at the correct value. This is normal. Look at your total coins on the left as it accumulates the correct numbers. Once in a while you can close and open your wallet then it corrects the history.

It seems the block rewards are still not showing their value correctly:



Any ideas?