Peercoin on Raspberry Pi

Could you tell us a bit more about it or is it too early?[/quote]

I am very curious too now :stuck_out_tongue:

Peerbox project will cover Beaglebone too, however dev does not have access to Beaglebone so it’s on the wait list.[/quote]

Hi Peerchemist,

Going back thru old messages on this thread I found the above one that somehow earlier I missed. If you are still interested in including Beaglebone then PM me your address and I will have one sent to you. I will be leaving for traveling in a week, so best if you want before that.

Thanks for your Peerbox efforts. :slight_smile:

I read something about remotely forwarding a port through a VPN provider, and decided to experiment with it since I have a feeling my ISP may be responsible for my low number of connections on Peerbox.

So I set up openVPN on my Peerbox and it appears to work fine, but unfortunately the 9901 port was unavailable from the VPN provider. I saw on bitcointalk that you can change the port in the bitcoin config file. I added this to ppcoin.conf:

port=9901 rpcport=9902

and changed the port to one that was available through the VPN. It hasn’t seemed to work though since I still only have 8 connections. Any idea where I went wrong, or if this would even work for Peercoin?

If this can work, it probably wouldn’t be a great solution for everyone anyway since you have to pay for the VPN, but maybe for people who already have one it might be a way to get more connections.

I don’t think this will work, since all the others on network look you up on 9901.
I guess this applies: https://support.google.com/postini/answer/136697?hl=en

But someone with more knowdlege on Peercoin/bitcoin protocol should comment on this.

Can you map XXXX on your VPN to 9901 local?

From getpeersinfo I could see many peers with ports other than 9901. Since every node will download a node list from connected nodes, I guess if your node is connected, it will broadcast its port number to its peers, who will spread this knowledge to the network by sending your IP:port to everyone downloading from them…

This is perfectly logical and should be the way that it works…

…however, in practice I have yet to see any node with a custom port attain more than 8 connections on its own. In my experiments, I can manually force more than 8 connections by using “addnode” from other external nodes that I control. This verifies that the tested node is in fact listening on the custom port and is able to accept new connections from the Internet. (Of course I must also manually specify the custom port number along with the IP address when using “addnode” externally; e.g. “addnode=IP:port”)

Unfortunately, the information from “getpeerinfo” is unhelpful if you are listening on the default 9901 port. This is because the port numbers you see are the outgoing ports of the connected peers. If you are running a full node with default settings, you will see many peers with ephemeral port numbers connected to your 9901 port. This does not mean that those peers are listening on those port numbers.

So unless someone can show proof of full node running on a custom port I am convinced that this is either a bug or an important “missing feature” in the network protocol. The latest versions of Bitcoin include additional arguments such as “externalip=” which may be helpful for this problem but are not yet pulled into the official Peercoin builds. I wish that someone more familiar with the source could clarify exactly how new peers are broadcast on the network… I will try to start plowing through it myself, but I’m far from being a professional coder so I’m likely to get lost before I find anything useful!

Greetings for river333 and all members of the community. Another PI is running as a node for the Peercoin net in Brazil. I salute my friend RR for telling me about this project. 8)


Boa! MissĂŁo cumprida.

Hi rob_fer, welcome to the forum.

Can you let me know what email address to send the tip to? You can send it to me by PM if you would like. If you have already tried but it didn’t work, I think you might need to have made at least two posts on the forum before you are allowed to send a PM, so you can just reply here or somewhere else on the forum :smiley:

Edit: Got it, thanks. Tip sent :slight_smile:

Thanks learnmore. I have just tried more than 20 nodes whose port number reported by getpeerinfo is not 9901. You are right none of them accepts inbound connection via the the non-standard port. Hope there is a fix/improvement for this.

Yes, I tried this too but no success.

[quote=“river333, post:249, topic:2353”]Hi rob_fer, welcome to the forum.

Can you let me know what email address to send the tip to? You can send it to me by PM if you would like. If you have already tried but it didn’t work, I think you might need to have made at least two posts on the forum before you are allowed to send a PM, so you can just reply here or somewhere else on the forum :smiley:

Edit: Got it, thanks. Tip sent :)[/quote]

Got it! :))

Just came back from vacation and discovered that my Raspberry Pi had minted its first stake!

It took almost 3 months but it seems to work!

Congratulations :pbjt:

I am in the process of setting a node to spread the blockchain -
But People are one order of magnitude or 2 more motivated by minting, ie seeing money growing in their wallet.

I need the minting guidelines as soon as possible to spread the word explosively.

[quote=“crypto_coiner, post:255, topic:2353”]I am in the process of setting a node to spread the blockchain -
But People are one order of magnitude or 2 more motivated by minting, ie seeing money growing in their wallet.

I need the minting guidelines as soon as possible to spread the word explosively.[/quote]

in the debug window console type

walletpassphrase YOUR_PASSPHRASE_FOR_THE_ENCRYPTED_WALLET 999999 true

or

ppcoind walletpassphrase YOUR_PASSPHRASE_FOR_THE_ENCRYPTED_WALLET 999999 true

from the commandline

also helpful: http://www.peercointalk.org/index.php?topic=1104.msg30602#msg30602

And a second good news!

After going down steadily for several weeks since May, the number of active full nodes securing the Peercoin network seems to be willing to go back up (MA30), probably due to peerchemist and its great Peerbox project.

You can check the chart here:

http://cryptocities.appspot.com/peercoin-fullnodes-daily-stats-2.html

[quote=“mably, post:253, topic:2353”]Just came back from vacation and discovered that my Raspberry Pi had minted its first stake!

It took almost 3 months but it seems to work![/quote]

Nice. The time the block was found was when POS difficulty dipped below 10.

Hello everybody!
I managed to set up my Raspberry Pi node with peerbox and 17 connections.
Thanks river333, peerchemist, and the community for the great work!
Is the bounty still up?

[quote=“lum, post:259, topic:2353”]Hello everybody!
I managed to set up my Raspberry Pi node with peerbox and 17 connections.
Thanks river333, peerchemist, and the community for the great work!
Is the bounty still up?[/quote]

Hi lum, welcome to the forum.

Yes the bounty is still up, just post here or PM me with an email address and I’ll send you the tip through peer4commit :slight_smile: