Well i’m a bit late to respond to the ping, and it seems like everything has been answered. I don’t know if I saw it mentioned somewhere but I always had to set up a swap space to compile it from source.
Those are the commands I was running to set it up. It may not be as much of a problem on the RaPi2, but on the first one I needed it. It took a LONG time to compile. I think upwards of two hours sometimes.
I think you should distinguish a full node that invites all the world to connect and a minting wallet node that security is important. The former has no fund and is barely more an empty R-pi on the net. There is not a lot motivation to break into it and default security setting is almost enough (get a good password though). The latter has funds and should have better security but overkill steps discourages adoption.
what I do specifically -
Either use user pi for simplicity or create a user of random name.
Only needed for full node.
[quote]enable ssh keys and disable password login
[/quote]
Keep passwd login for situation when you want to get into the pi without network connection. Do use a strong password.
starting nud -daemon is good enough for me.
I got everything working on my laptop and ftp the data directory (with the database subdirectory) to the pi. The wallet on the pi can be used with the same balance, passwd, and doesn’t need to download the full block chain. Remember to chmod 600 all data files.
see below
peerbox links .bash_history to /dev/null so there is no history
I have made a few scripts since I tend to forget -
start (start the daemon) ./nud -daemon
pass (Type in the password to start minting. There is no prompt! the password shows! type password, press return, press control-D) ./nud walletpassphrase `cat` 999999999 true
I also have these aliases in .bashrc for status, logfile, pi temperature, recent blocks
alias g=’~/.nu/nud getinfo’
alias deb=‘less ~/.nu/debug.log’
alias temp=’/opt/vc/bin/vcgencmd measure_temp’
alias tx=’~/.nu/nud listtransactions | less’
Sure. After thinking it through this tutorial will illustrate how to run a minting node for securing the network via voting and staking. Will do a full node version when there is demand for it.
[static ip]Only needed for full node.
So you suggest to hide ssh from outside the network as a security measure?
What do you mean?
That’s actually a good point… What are the pros and cons of having a raspi minting on the same wallet you use somewhere else via GUI (on a laptop, like you said) ?[quote=“mhps, post:11, topic:490”]
I have made a few scripts since I tend to forget -
[/quote]
this is also why you’d want nud to run as a service
I thought you meant that the Pi should have a static IP to the outside world. I set up the router so that it always assign the same LAN IP to the Pi according to the MAC address. So the pi doesn’t need to change from DHCP, and internally it is easy to remember where to ssh to.
I recommend set up the router to block any connection of in bound ssh.
When you said “disable password login” did you mean it wouldn’t be possible to login from a plugged-in keyboard and monitor? If yes you could lock yourself out if you don’t have the other computer whose key is stored in the Pi.
I don’t mean they should mint at the same time. Usually the pi mints. The lap top is either off or running the client in locked mode to monitor new block rate remotely as a pi/nu-network health indicator.
peerbox has ppcoind in service mode. I find it very difficult to remember where all the files are located after a while. There are 3-4 places… /var/lib/ppcoind for the blkchain, /etc/conf.d for the service start conf file, ~/.ppcoin/ppcoin.conf for a user config… of course they are all different for a different kind of linux… nud stop is not enough to stop the service, you have to do a systemctl stop ppcoind … How confusing!
terminate called after throwing an instance of 'std::runtime_error'
what(): locale::facet::_S_create_c_locale name not valid
Aborted
I’ve googled and tried pretty much all the suggestions without success. A dirty fix is running an export everytime after I ssh into the raspberry ( export LC_ALL=“en_GB.UTF-8” ) .
I remember the same was happening to me with the old rpi last year .
I have only skimmed through it so far.
It looks very good and comprehensive! Good job!
It’s good to see that the basic installation of an operating system on a RaPi is included as well.
I’m not familiar with making pull requests at github. Please forgive me making suggestions here.
This was a hack I once needed. Not sure whether it’s required in standard setup:
To not discourage those who already have Raspberry Pi 1 B and 1B+, I think it should be pointed out that running nud on R-pi 1 does work, although R-pi 2 is faster, especially when there are more than 1 million shares (100+ outputs).
The SD card should have more than 4GB or there will be shortage in disk space… Buying a faster SD card helps to shorten start up time.
Compiling is not necessary if official binary is available.
The steps can be scary to someone who is new to R-pi. I think providing a pre-installed R-pi image for downloading will be really convenient.
Alrighty, I already found that line in the guide - that’s why my config line (sudo ln -s /usr/lib/libminiupnpc.so.5 /usr/lib/libminiupnpc.so.10) looks so shiny It’s a link to that line in the documentation on github.
Only I wasn’t sure whether that was necessary due to some buggy installation on my side…
I’m not sure how long it will take to free some time for an installation following that ingenious guide. Maybe I don’t have the time, before other users test it. It looks very well and I bet it’s close to what one needs to know.
As we are talking about scripts - I have another one that backups my ppc wallet monthly (by crontab). It can be used for comfortable backups beyond the monthly backup. As I backup the whole “~/.ppcoin” folder regularly, I found it convenient to put all right there.
I adjusted it to be used for backing up the NSR wallet:
[backup script]
echo '#!/bin/bash
nud backupwallet ~/.nu/walletS.dat.$(date +%F)' >> ~/.nu/backup-nsr-wallet
chmod +x ~/.nu/backup-nsr-wallet
[/backup script]
[add backup script to crontab]
crontab -e
#append line to have a monthly backup at the first day of the month, 22:00:
0 22 1 * * ~/.nu/backup-nsr-wallet
[/add backup script to crontab]
This is highly optional, but as you lose all information about the points of time at which you minted successfully, you need to make backups of your wallet to restore not only the keys, but the details about transactions from a backup wallet.
I don’t know why the time stamps of blocks (there are time stamps, right?) are not used to translate that into a date and time, but…
To just have the keys backed up this might not be necessary as the minted blocks use the address of the UTXO that minted the block, right?
Anyway - all this belongs in the “advanced” or “highly optional section” of the guide…
Maybe someone is happy about that. Integrating it into the base guide would complicate things.
I tried nud on RaPi1; the RAM is almost too small to compile it… and using swap during the compiling doesn’t speed the process up
8 GB or even 16 GB shouldn’t be way more expensive than 4 GB. I’d recommend class 10 speed as it’s already as fast as the RaPi can read form the card reader.
That would be awesome! The compiling is the hardest part. And if you have a RaPi1 it really takes for ages.
+1 something like NuBox (made by peerchemist?) would be awesome!
I agree, we said earlier that there won’t be an official binary on the download page, or it will require proper testing and maintenance. However, no one stops us to link to an independent build from the tutorial, providing a proper disclaimer is shown.
Can we get a permalink to a community-maintaned nud-pi ? I’ll add the link to the tutorial … A torrent maybe?
)