Raspberry Pi & Secure Nodes


#1

In the future I’m wanting to set up multiple ZenCash secure nodes on Raspberry Pis. Will this be possible? Will I be able to use a single VPS, or will I need to set up multiple? Thanks for any feedback.


#2

raspberry pi does not have the 64 bit processing capability to complete a shielded transaction. You can use one VPS per secure node.


#3

Pine a64–

would this work? I have used them on some random projects…

“PINE A64 is Single Board Computer powered by Quad-Core ARM Cortex A53 64-Bit Processor. It provides PI-2 Bus, Euler Bus and many others peripheral devices interface for makers to integrate with sensors and devices. Various Operating System (OS) are made available by open source community such Mainline Kernel, Linux Distro, Android, Remix OS, Windows IoT and many more to come.”

https://www.pine64.org/


#4

Yes it will run BUT the Instruction engine that enables encryption and decryption is not good, addressing the 3rd point point below:

The basic requirements of Secure Nodes are:

  • Maintain a minimum of 42 ZEN in transparent address per node. Demonstrates the operator cares enough about ZenCash to own some.
  • Create and maintain a valid TLS certificate from a known Certificate Authority. This enabled encrypted data transport.
  • Run the node on a server with enough processor and memory so that it can meet a computational challenge. This protects against DDoS attacks.
  • Maintain a full copy of the ZenCash blockchain. This makes sure no UTXO’s or commitments are lost.
  • Keep the node up and running at least 92% of the time.

A single one is fine as long as it passes the 5 points above.

Side note, I have some UDOO x86 running in some fly over locations, remote, that will be running as ZEN nodes, they have extremely fast hardware encryption and decryption for openssl, ssh, vpn and disk encryption:

  • Intel® AES New Instructions
$ lscpu | grep '^CPU(s):'
CPU(s):                4

Fast as any VPS going when it comes to encryption and decryption:

$ openssl speed -evp aes-256-cbc
Doing aes-256-cbc for 3s on 16 size blocks: 19964256 aes-256-cbc's in 3.00s
Doing aes-256-cbc for 3s on 64 size blocks: 7814405 aes-256-cbc's in 3.00s
Doing aes-256-cbc for 3s on 256 size blocks: 2372896 aes-256-cbc's in 3.00s
Doing aes-256-cbc for 3s on 1024 size blocks: 626869 aes-256-cbc's in 3.00s
Doing aes-256-cbc for 3s on 8192 size blocks: 79618 aes-256-cbc's in 3.00s
Doing aes-256-cbc for 3s on 16384 size blocks: 39858 aes-256-cbc's in 3.00s
OpenSSL 1.1.0f  25 May 2017
built on: reproducible build, date unspecified
options:bn(64,64) rc4(16x,int) des(int) aes(partial) blowfish(ptr) 
compiler: gcc -DDSO_DLFCN -DHAVE_DLFCN_H -DNDEBUG -DOPENSSL_THREADS -DOPENSSL_NO_STATIC_ENGINE -DOPENSSL_PIC -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DRC4_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -DPADLOCK_ASM -DPOLY1305_ASM -DOPENSSLDIR="\"/usr/lib/ssl\"" -DENGINESDIR="\"/usr/lib/x86_64-linux-gnu/engines-1.1\"" 
The 'numbers' are in 1000s of bytes per second processed.
type             16 bytes     64 bytes    256 bytes   1024 bytes   8192 bytes  16384 bytes
aes-256-cbc     106476.03k   166707.31k   202487.13k   213971.29k   217410.22k   217677.82k