Sure. Your welcome.

Step 1 - Install the wallet

1. Download wallet at this link as per the OP https://mega.co.nz/#!c8YijQSY!8yNURZtHvEfDVPFYuMcfcgnzqJ0K7ESi9S6h1HRTSwg
2. Bypass all warnings from your anti-virus and force the file to be downloaded and extracted. If Google Chrome moans use Windows Explorer.  Actually, if you are concerned you can upload the file first to www.virustotal.com to have it analysed for viruses.
3. Extract the file in your download directory to the suggested directory ...\downloads\MasterTrader-qt-win
4. Execute the file called MasterTrader-qt.exe in the directory where it was extracted. A wallet will come up with possibly some error messages. Just close the wallet once it has opened and open it again.
5. In the case of MasterTrader the nodes are picked up by the wallet and you do not have to specify anything in a .conf file.

Step 2 - Download the blockchain

1. The opened wallet will connect to the network. You will see a message that the wallet is out of sync and it will start downloading and processing the blockchain. Blocks are records of transactions (coins sent from one address to another) that have been verified by the network. You can consider it a public ledger of a bunch of transactions. As the wallet processes the blocks and follow the trail of the money, you will see the number of blocks increasing up to the current block. This process can take 30min to 1 hour depending on how many transactions are in the blocks so far in the coin's life. (The proper Bitcoin wallet can take a week to download and process all the blocks). To watch the process you can select Help at the top, then Debug Window and then Information. The current block count is in the middle of the window. The blocks will increase as the wallet downloads and processes the blocks until it is current. Once the wallet gets to this point, you will see a "correct mark" at the bottom right of the wallet. If you hover over this with your mouse, you will get a popup that the wallet is up to date.

Step 3 - Backup and protect your wallet file

1. The most important file of everything of a coin is the wallet.dat file. Your private keys are stored in this file and is necessary to be able to access coins linked to your public address.  If you lose this file all your coins are gone. The wallet.dat file on a Windows machine is in c:\users\yourusername\appdata\roaming\mastertrader
2. Insert a USB stick into your PC and create a directory called MasterTrader. Go to the directory where your wallet.dat file is and copy the file called wallet.dat to the memory stick into the MasterTrader directory. Rename the file wallet.dat.old
3. Go to your wallet and select Settings at the top and select encrypt. It will ask you for a password that you have to enter twice. Select a difficult password and write it down somewhere safe and remember it. The wallet will close and then open it again. Now your wallet file is encrypted and money cannot be stolen from it without knowing the password.
4. Go back to where your wallet.dat file is and copy the file again to your memory stick. You must now store the memory stick in a safe place like a physical safe. If something ever happens to your wallet file, you can use the backup one. If you want to be extra security, you can encrypt the USB stick with BitLocker and remember the password.

Step 4 - Setup your address for payment and receipt of coins

1. Assuming you have some coins on an exchange, go to the exchange to your MTR balance and select withdraw. Go to your wallet and select the receive coins on the left. Right click and copy the address. Go to the exchange and enter that address in the withdraw address block. Enter just 1 coin in the amount for now. Select withdraw. A popup will come up with the transaction about to happen. Enter your 2FA if it was setup and let it withdraw. Some exchanges also requires a confirmation by clicking on a link in an email.
2. Now you wait and watch your wallet until a popup comes up bottom right that 1 coin has been received. Once this happens, go back to the exchange and withdraw the rest of the balance.
3. If all went well your coins will now be in your wallet on your PC.
4. Go back to the exchange to your MTR balance. Generate an MTR address. Right click and copy that. Go back to your wallet and select Address Book on the left. Create a new address and paste the exchange address there and call it the exchange name.
5. Select "send coins" on the left of your wallet and select the exchange that you just created. This is needed so that you don't have to manually enter the address every time. This is one of the the biggest risks in crypto to send coins to an incorrect address as they will be gone then forever. I wish exchanges would create a facility to traders to create address books on the exchange. Enter 1 coin again and select send. You have to enter your password and agree to the small transaction fee. Watch the exchange to make sure that the 1 coin appears there after a while. You now know that you have a proper two way channel between your wallet and exchange.

Step 5 - Setup your wallet for staking

1. Go back to your wallet. The message at the bottom of the wallet to the left of the up arrow will say "Your wallet is encrypted and currently locked". Next to it will be an up arrow and a message if you hover over it that your wallet is not staking because your wallet is locked (encrypted)
2. Go to the top of your wallet and select Help and then Debug window and then console. In the bottom bar type the following command:
"walletpassphrase yourwalletpassword 99999999 true" if successful you will see this command in green in the console. Now click the little "-" sign to the right of that bar so that it clears the screen. Close the console window.
3. If you hover over area just to the left of the little up arrow it will say "Your wallet is encrypted and currently unlocked"
4. If you hover over the little up arrow at the bottom you see a message "Your wallet is not staking because you do not have mature coins". After 3 hours or so this message will disappear and your coins while be staking. After several stakes you will get to a point where your stake become very small. Once this happens, move your coins to another address (I use another wallet on another PC) and then move it back so that your coin age can reset. Your coins will mature again for 3 hours after which it will start staking again.

Step 6 - General pointers

1. Every time you send money from your wallet somewhere else, your wallet will lock up again. You then have to go back to the console and enter the walletpassphrase like above to unlock it for staking.
2. Every time you hit a stake (verify a block of transactions) also called solve a block, your balance of coins will reduce and move to a different line. For a while it might also disappear until the required number of confirmations have occurred. You can watch the progress in the transactions tab at the top of your wallet. Once the required confirmations have happened, the coins become available again in your wallet and the coins that staked are reset and have to mature for an hour again before they can become eligible for staking again.
3. Sometimes you will see a message popup that you have received a stake amount of coins, but if you go to the transactions tab it is grey with a question mark next to it. This means that your wallet thought it solved the block but actually someone else did so just before you and the network rejected your claim. It is called an orphan block. Ignore those but feel sad for a moment that you did not get those coins.
4. It is possible to create more receiving addresses in your wallet for in case you want to use a unique address for each time you receive money from someone or some place. Every time you add a new receiving address, you have to fetch your USB stick from the safe, rename the wallet.dat file there to wallet.dat.old2,3,4 etc. and copy the new wallet.dat to the USB stick. The only drawback is that if you ever forget your wallet password, all later wallet.dat files will be encrypted and the first unencrypted one will only have your first address in it. You can therefore consider creating 50 or so addresses before you encrypt the wallet.dat file, if you foresee using unique addresses a lot.

The .conf file

This is a file where you can specify parameters that the wallet .exe file can understand when you execute it. You can either run the wallet in the command line and specify the parameters behind the .exe, or you can list them in a .conf file that the wallet reads when it starts.  The typical entries for a .conf file are:
- Setting a daemon and server for solo mining
- Adding nodes for when the wallet does not have them coded into the wallet through either hard codes or DNS seeders
- Adding IP addresses of your miners that will connect to your PC with the wallet on
- Setting up the parameters of the remote procedure calls to enable another computer (miner) to remotely connect top your computer over your network
- Since MTR POW ends tonight there will be no more solo mining and the nodes are picked up by the wallet itself and that is the reason why you don't need a .conf file for MTR.

When there is consensus.

It is irrelevant. Once the (correct) fixes are implemented, the price should recover. Have a look at what happened yesterday when a solution was ready to be implemented - the price suddenly turned around in force. The price went down again when plan B was given a chance first. It is only temporary while everyone waits for the POS block that the price is going down. This is mainly due to the uncertainty of the future of the coin with this approach. The approach is necessary though to give the current dev a chance. The next steps will be discussed by the community after the 48 hours staking test. Remember that price reflects market sentiment and the result of supply vs demand.

Addnodes not necessary. Ill write and post a modified set of instructions for MTR for you shortly.

You can read this and replace all references to 10K with MTR.

https://bitcointalk.org/index.php?topic=942977.msg10388060#msg10388060

If all just remain calm, professional, respectful and mature, chances are better for a successful outcome. Go with the flow and take it one step at a time. For now, lets wait and see if POS comes up with the full Bittrex weight behind it.

There is no real rush. Even if it is so in the end that the new chain has to be created and the coin swop done, let the current dev's plan be given a chance (some might see it as just a formality). The price is irrelevant now because if the new chain is eventually implemented, the price will move upwards because the specs that Spots suggested looks exciting and still broadly in line with the current dev's vision. It is a matter of giving the current dev a chance. If the current dev does however rather decide to keep the current code, then the coin has a high probability of dying down rapidly.

I agree with Richie, give the coin 24-48 hours and the situation can be re-assessed then with the benefit of adding an actual outcome to the decision process.

If the new code base is not used, then many people might step away from the coin including Spots which might just kill the coin off. There is more to the errors than just getting it to stake, which has been proven by the review. Who wants to be involved with a coin with poor code?

Whatever is chosen in the end, has to be based on a new chain that works from the base up and in all scenarios it is not worth it to just fix or amend the existing code. This will be the least effort for Spots currently and for future enchancements and ensure that the coin uses tried and tested technology.

Richie has shown maturity regarding the issue at hand. It is much better for a takeover to be a handover as it sorts out all sorts of potential complications.

Spots has showed maturity by rising to the occasion when the community was in need. Since he has no stake in this, and did not ask for any compensation, he can set the conditions for his assistance. His conditions make perfect sense as it will make the coin code errors go away, improve compatibility with his other existing smooth running coins, improve performance of the coin, remove the premine which is normally a bane due to human nature and lastly reduce administration. Spots' conditions therefore cover people, process and technlogy to provide overall enhancement in the systems' integrity, performance, robustness and resilience.

The dev showed maturity by pitching up and owning up to his mistakes and not just disappearing. as current owner of the coin, it is his right to come up with a plan to fix the situation - actually, it is his job to come up with a plan as "MD".

A lot can be said about his plan, because the code has been proven to be poorly written and will take a lot of effort to fix existing code. The basics principle of design is that the later in the process an application is fixed the more expensive it is and the bigger the operational and production impact. The best way to get good applications is to design good code upfront. There is a lot of positives that can be said about rather just use a whole new code base using the principles of something that exist already that works, hence Spots' recommendation to use his existing genesis block. Using the Spots genesis block also means that there is no more premine by design. I would call the current dev's plan plan B since it is clear that the code has to be re-written anyways even if the staking does cause the chain to move again because the blocks would move but the design is flawed and will not execute according to the business requirements.

Plan A will have to happen, but there is perhaps a way to meet in the middle. Maybe the current dev's skills are in advertising since that is the business objectives he tried to push and enable through the coin tech. It has been proven conclusively that coding is not his skill. My suggestion is for the current dev to be "MD" and Spots to be "CIO". Spots would have full control and rights over the technical aspects of the coin including coding, merging, compatibility and staking on his nifty staking hardware devices etc. The current dev can focus on the business plans of advertising where his strengths lie, subject to the technical decisions and parameters of Spots' new chain. A new development fund can be created by the community by upfront agreement and serve the same purpose of the old premine and be held in escrow - it was not that large anyways. Creating the development fund can be done when the coins are swopped and taxing each swopout with 1-2% and could perhaps be implemented by Bittrex if they do the swopout to coins on the new fixed Spots chain.

POW seems to be racing along. While making some tea the block count has increased to 8055. Money supply for the POW phase was 7805 just now meaning that @ 1 coin per block, there has been 250 POS blocks so far.  If POS blocks continue to grow POW phase might end up with maybe only 9000 coins for the phase. Also, the blocks might accelerate the end time bringing estimated end of POW closer to end of phase 2.

Now that is the million dollar question. You have to calculate that based on 3 factors - phase 2 unit price at the time, cost of mining and the market price. Mining is running out though and with 1 coin per block there are only 1957 blocks left as at posting this. POS is also running and finding blocks which accelerates the end goal. Estimated end of POW is Tuesday 7am GMT. End of phase 2 is Monday 8pm GMT.

Are you sure that it was not a temporary reduction due to the coins staking? They should reappear when the staking is finished and the stake confirmed.

The community's knight in shining armor.

It seems the community has some decisions to make.

1) Wait for the dev to appear and fix the code
2) Ditch the dev and get a third party to fix the code asap. Get a new committed dev.
3) Ditch the coin

A coin dev has a vision and commitment to make something with a coin. A new dev might be just a hired hand that is not necessarily committed to a coin's future. There has been exceptions to this though where a takeover was done successfully.

Due to my risk management strategy I am not materially exposed to emoney that is stuck in my wallet so I am indifferent to the option chosen. If it is going to be a lot of effort to fix the code, to hire a third party for the fix or to get a new committed dev, then it might be best to just ditch the coin and move on. But then there are many who are heavily invested with coins stuck in their wallet and their interests have to be considered as well.

Seems so, unless there is some hidden. Dont know if that has been checked.

ocminer is holding the premine of 40k coins.

It seems then that the "dev" has torpedoed his own coin.


getdifficulty

{
"proof-of-work" : 4021311.22263795,
"proof-of-stake" : 0.06249911,
"search-interval" : 1
}