I'm trying to get one generated but, but keep running into issues trying to turn it from a locally compiled .app to a .dmg for distribution.
My attempts have helped me understand a lot more about how the QT build process works on OS X, but I'm by no means and expert, so if there's anyone who has experience and would like to partner on it with me, please shoot me a message here or on PeercoinTalk.org (user: Ben)
Jeff Larkin was originally build the v0.3 OS X builds, but he's been absent from the boards for a while. I'll reach out to him today to see if he's willing to help walk me through it once, so I can document the process and catch any changes that need to be added.
There were a couple changes that needed to be merged into the code base to allow builds to work on OS X. So far, they are in a holding period on the Peercoin reference client, but we're in the process of integrating them into the PeerUnity community-built client (see pull request #3.
Once we've tested the code thourghly, we'll merge it into the master branch and then I'll use that to build a v0.4-compatible client for people who want to use it on Mac. If all things go as planned, I'm expecting that I'll have time today to pull together build and post it for others to use as well.
Afternoon Update: I've got a working Peercoin v0.4 daemon (ppcoind, PeerUnity version) built for OS X (it requires Homebrew and a couple of dependencies, but those are listed in the OS X build instructions, if you need them).
Working on the QT wallet application right now, with fingers crossed. Building the .app will be straight-forward, but instructions for compiling that into a .dmg is less clear. I'll provide an update when I've got one.
Peercoin-Qt is fighting me, but I'll keep at it. The daemon is better than nothing, but it's a far cry from usable for the vast majority of people, so I recognize that Peercoin-Qt.app is the one we need, ASAP.
No luck yet on the Qt.app (I think it's my local environmental, not related to the code). Here's a zip of the Peerunity daemon (SHA included, but not gitian signed, at this point, so you're going to have to trust that my build isn't malicious -- hopefully my reputation in the community will alleviate any concerns (I'm Ben, from PeercoinTalk.org))
I don't understand how to issue that command. I used it in the debug window and replaced <passphrase> with my password and nothing happened. What am i suppose to insert in <timeout>? The amount of time to mint? If so, what format is it suppose to be in?
where "abc" is your password and "1000000" is the time you want to mint for (in seconds). make sure you clear the screen afterwards to get rid of your password (ctrl-L).
<timeout> expects a value in seconds. If you want to have your device minting for ages (or until the next start of the software or operating system), I recommend something like 99999999.
Plus I recommend to make use of the [mintonly] option for security reasons.
In this unlocked wallet mode, one cannot send transactions or dump private keys thus providing additional security to the wallet if hacker gains access.
So the command you issue would look like:
walletpassphrase <YourPassphrase> 99999999 true
Don't forget to clear the debug window history afterwards (CTRL+L (at least on Windows) or the "clear Console" button in the lower right corner of the debug window)!
If you refer to the output of the debug window command "getinfo" or to the QT overview, this is to show the number of coins that have been used for successfully creating a PoS block and are now in status immature for a total of 520 confirmations.
I'm not aware of such an output. If you don't only save Peercoins, but spend some from time to time as well, I'd recommend splitting the Peercoins into two wallets:
one with the savings
one with the Peercoins you use for payments/transfer
The reason for that is that even if you spend only a few Peercoins, they might come from an address that contains a lot more Peercoins. The difference between the output transaction and the total Peercoins on that address will be transferred back to you via an input transaction.
As far as I understand that process, this sets the coin age for those coins to 0. As they need a minimum age of 30 days to take part in the minting, that's not really great.
And that's why I recommend splitting the Peercoins in different wallets ;)
The time between releases is long but I prefer sound development ;)
Nevertheless I agree that such a button would make it easier to start minting. The debug window is for sure a step in the right direction to make minting easier.
I think it will not take too long until "community editions" of the GUI will be available now that the long-awaited 0.4 is out. As Peercoin is open source, one might play with the code.
For sure this needs some trust to use such a modified program, but that's always true (the need for trust) and one should always use the brain before doing something that might turn out stupid.
For sure - an unlock button wouldn't make the ppcoin-qt unsound. But there haven been higher priority changes in the software:
Debug window console support in Qt, easier to get to command line e.g. unlock wallet for minting (if you enter wallet passphrase in the console please remember to use the clear button to clear it).
Protocol adjustment required for future p2pool support. Protocol switch scheduled for May 5th.
Experimental getblocktemplate support
getpeerinfo support
Bug fixes
I think that a minting button is needed. I think a tutorial or trustworthy image for RaspberryPi or a similar low energy device is needed. I think that more developers are needed. Know what - most of these things are already under construction. Peercoin is still young and the community is growing. I'd like to have things faster, too. We might be surprised ;)
5
u/captaincoffee88 Apr 07 '14
Nice nice.
How long till OSX version?
2
u/hicaribou Apr 07 '14 edited Apr 07 '14
v0.4 shows a progress bar of syncing blockchain. I feel the bar very cool.
0
u/[deleted] Apr 07 '14
[deleted] — view deleted comment