Topic: PPCoin Proof of Stake Minting Setup Guide (Read 57034 times)

Hi guys,

I have a question about the minting, using only ppcoind, whithout the gui.

Other stake coins daemons (blackcoin, clamcoin...etc)  have the "getstakinginfo" commad which lets you know if you are staking atm.

Not sure how to find this out on ppcoind?


The normal "ppcoind getinfo" command gives me the "unlocked_unitl" value, which is different from -1, which means the "walletpassphrase [mintonly]" command worked.

But again, which command would be useful for checking the staking status in more detail with ppcoid?

thanks i will try in paycoin...

For the majority of users, the best option for a Peercoin wallet is now Peerunity. It is available for Windows, Linux, and OS X. It has more features than the standard client, and is also much easier to use (especially for minting).

Download it here: http://peercoin.net/download-peerunity

Read about Peerunity and FAQs: http://www.peercointalk.org/index.php?topic=2902.0

To mint using Peerunity:

Minting is now very easy. All you need to do is enable it in your client, and leave your client running with a connection to the Peercoin network. To start with, make sure you have encrypted your client with a strong passphrase that you will not lose. You will now need to get some coins in your wallet!

Then simply press the "Unlock Wallet for Minting Only" button, enter your passphrase and press OK.

https://i.imgur.com/Y4sDXDP.png

You can check you are minting by looking at the little padlock in the bottom right corner of the client. It should now be unlocked. If you hover your mouse over it, it should say "Wallet is encypted and currently unlocked for block minting only".

How long it takes you to mint a block will depend on how many coins you have, and how long you've had them. Here's a handy tool to work out your chances: http://poscalculator.peercointalk.org/ (The current POS difficulty can be found by entering the command getdifficulty into the debug console of Peerunity...go to help -> debug window -> console).

Edit: Peerunity v0.1.1 now has a minting tab which shows some of this information too.

The mint button is available on Peerunity (Peercoin community version)

http://www.peercointalk.org/index.php?topic=2648.0
http://www.peercointalk.org/index.php?topic=2785.msg24915#msg24915

it makes me sad that it's still this hard to mint coins after more than a year of PPC....
A big button with "mint" on it would be nice! really, not even kidding. Things like this are gonna make sure ppcoin gets left behind.

I Tried this a while back but it didnot work thanks to this official guide i think i can get it working now, thanks

Just in case anyone is as big of a noob as me... make sure you name your .conf ppcoin.conf and not peercoin.conf.   That's what caused my issues getting this started.  Works great, thanks for the guide

since cold lock is not available till the next version, let me share half of my secret recipe for "safe enough minting", it goes like this:

make a script named mint

and a script named query

- put rpcuser/rpcpassword in ppcoin.conf
- run ppcoind as daemon
- remove rpcpassword line from ppcoin.conf
- run the mint script to unlock wallet
- run the query script to control your ppcoind, for example "query getinfo", you'll have to enter the rpc password every time

The idea is the intruder has to be a bit smart in order to steal your coin, after he gets he can take the encrypted wallet, but he cannot command the unlock wallet to send coins to his, since rpcpassword is not left anywhere, he has to plant trojans/keyloggers/or put some effort into it in order to take it,

although if you just do this, and never come back to query it, it should be reasonably safe, or to make query a bit safer, you could try to use SSL option on rpc, listen rpc on localhost, and make a ssh tunnel to it, then query it from the tunnel, intruder will have a harder time I guess,

that is all

Folllowed the guide.  Bat opens fine, I hit enter a few seconds pause, no error message but the info line still says suspended.  Any ideas?

Nice guide, any apps for mobile?.

to get minting going on an encrypted/locked wallet, i have seen several post the command, but nobody has said where to run this command.

May be self-explanatory to some, but i read everything and still took me a bit to figure it out.  I needed to get the latest wallet, that actually has the ability to open the debug/console windows.

In the PPC wallet, open the debug window, then console.

The console command line is where you input your walletpassphrase arguments, as shown below.  Use your own password.  lol


walletpassphrase walletpassword 999999 true


this is what finally unlocked my wallet for minting.

You are a wanker.

How many of you actually hang on to these little copy cat coins for longer than the time it takes to hype them up and then dump them.

1 year?  Really?

Hello. Thanks for posting the information.

I'm new to this, and while I've some limited experience with setting up batch and conf files, I'm obviously missing something, as I still haven't gotten the batch file correct (mining still suspended), and i did find the conf template a little confusing due to the use of the hash tags that seem to have been either used inconsistently, or I'm just making an error (highly possible).

Before I bost the code I've entered sans sensitive data, I wanted to ask if using an old 856 MH/s BFL FPGA unit would work, since I know that their ASICs work  - since both are obviously SHA-256. I could pull one of my slower ASICs offline and not make much of a dent in my BTC operation, but I'm mainly wanting to test this out, since it's likely that I'll migrate to another SHA-256-based coin as my hardware becomes obsolete for BTC mining. So, should the FPGA work as well? Is difficulty already too high for a rig hashing under 1 GH to earn a little coin?  I earned ~6 on it from late-November 2012 to early-April 2013, and BTC was at about the same price when I started. Just curious if it, too, should work, and if not, I can pull my slowest ASIC off the line, which I might find myself doing anyhow. Got to get this other mess sorted out first...and if it's a mess, I made it that way.

First the .conf:

Not sure how to tell if this is correct or not, but these seemed like the only elements that were not meant as explanation, but rather the actual code. I realize my spaching may be at issue you here, but am not sure how many lines of spacing to include.

The .bat file I find a bit more confusing. I've tried several different methods of including my password in the file, including the most logical, which is to substitute the term 'variable' each time with my password. I've tried both my actual password used for encryption (my wallet passphrase) and the supposedly arbitrary password I included in the .conf file. At the bottom line, I've left the bracketing '%' and omitted them. I always get an error that there is a mismatch. Here's what it kind of looks like now:


Sorry if these are easy questions for the rest of you. It all seems fairly straightforward, but I'm missing some crucial piece. Also, and this is the edit, I did enable the function to allow me to see the extensions - I do have working .bat and .conf files... They are not simply doing what I'm asking them to do. I'll be trying to sort this out on my own, too, but any help will be appreciated.

Cheers!

Solved it!

Thank you for your consideration (reading) and sorry for waisting your time (reading).

For others with the same issue, here's the "solution" (as instructed in the video...):

Windows prevented me from seeing the file extension.
I noticed I did't see any extensions exept the .conf
Once I enabled extensions I saw there was still .txt
[please don't laught]

So after deleting the .txt extension and a restart it worked like a charm...

Sorry, but I'm really getting stuck here. Followed the tutorial to the letter, watched the youtube instruction and tried debugging and searching for the solution online (one member here has mentioned the same problem, but still no solution):

After I run the mint.bat file and enter the right (wallet) simple (only normal characters) password I keep getting this error message:

error: You must set rpcpassword= in the configuration file: C:\Documents and Settings\Pc\Application Data\PPCoin\ppcoin.conf
If the file does not exist, create it with owner-readable-only file permissions.

Just to state the obvious:
- The file DOES exist (I followed the instruction, remember);
- The rpcpassword= in the configuration file is set (rpcpassword=password); and,
- The appdata folder in WinXP is C:\Documents and Settings\Pc\Application Data\PPCoin\ppcoin.conf

The only part of the error message I do not understand (and I didn't see in any tutorial/clip) is: [...]create it with owner-readable-only file permissions. I've tried setting the file to read-only, but that didn't help...

Please help.

Ok, nobody answered over here. No audience or considered off-topic, I suspect. For who is interested I've added my thoughts and some models with calculations in a thread on Peercointalk here:

http://www.peercointalk.org/index.php?topic=809.0 (You may use my referral to post: http://www.peercointalk.org/index.php?action=refferals;refferedby=28779)

First part of thread is about interest earned, second part is about the time and chance you have to earn that interest given some assumptions.

I'm kind of frustrated as well. Been looking and querying for weeks to understand the chance to mint a block given a certain amount of coindays. Other answers than random or depends on the network haven't come up.

It seems that wallets with low coinage have a very hard time to mint a block. And with a 90-day cap on the stake they might never be able to mint a block.

If chance of minting somehow depends on the network, which parameters would influence the chance of minting a block beside coinage. Number of total coindays at stake across all active wallets/nodes? If more coindays would give me a higher chance of solving a block what mechanism would cause this. Would I produce more hashes or is there just another formula somewhere hidden in the source code? And what does the PoS difficulty mean in this equation.

Who in the world can answer those questions or just provide some idea how it might work, please.

i will throw in some PeerCoin for this and dev, see peercoin forum I have suggested it thier, maybe fuzzy bear and ors can admin the fund

I can't seem to get minting working.

I open my Peercoin wallet with the -datadir switch, the data directory is kept on a different drive.

I run minting.bat in a command shell from the Peercoin application directory.

It gives the following message:

error: You must set rpcpassword= in the configuration file:
C:\Users\*\Appdata\Roaming\PPCoin\ppcoin.conf

-

OK, so it's looking in the default directory for the config file. I create a config file there with the same password as the config file in my -datadir directory.

Now I get this:

error: {"code":-14,"message":"Error: The wallet passphrase entered was incorrect."}

-

Is there a solution for this?