Changes

''By Jeroz - Oct 27th, 2018 -- Updated by [https://twitter.com/pathfinder @Pathfinder ] for v4.3.2.1''

(by [https://twitter.com/pathfinder @Pathfinder]) If you'd like a higher-end hardware setup with more CPU that's optimized for expandability and speed and faster storage (microSD cards are notoriously slow), see my [https://bit.ly/smol-guide-rpi4smol guide](Pathfinder. <p>You's ll end up building something that looks like this:<br>[https://i.gyazo.com/f0eb138514580314976a21a68b8fc68c.jpg <img src="https://i.gyazo.com/f0eb138514580314976a21a68b8fc68c.jpg" width="350">]<br> My [https://bit.ly/smol -guide). The -rpi4 smol guide ] focuses on setting up running Urbit, but the specified hardware config is also ideal for running a Ravencoin or Bitcoin node!<p> For optimal speed and expanadabilty, I suggest using the SATA SSD as the data storage location for the Ravencoin blockchain as well as the Ravencoin binaries.<p>Create a directory on the SSD called <b>/media/pi/SSD/Ravencoin</b> and put the directory with the Ravencoin binaries in there. <p>Then create a directory on the SSD called <b>/media/pi/SSD/Ravencoin/RavencoinData</b> for the blockchain and reference it like this:  <p> <b>To START the node:</b><pre>./ravend -daemon --datadir=/media/pi/SSD/Ravencoin/RavencoinData</pre> <b>To STOP the node:</b><pre>./raven-cli -datadir=/media/pi/SSD/Ravencoin/RavencoinData stop</pre> <b>To CHECK the node:</b><pre>./raven-cli -datadir=/media/pi/SSD/Ravencoin/RavencoinData -getinfo</pre> When you're done, it should all look like this: [https://i.gyazo.com/8c02cd94d8012643c2ce2ec5dc5163f7.jpg <img src="https://i.gyazo.com/8c02cd94d8012643c2ce2ec5dc5163f7.jpg" width="800">]

#:<pre>rpcuser=rpcuser #optional &#10;rpcpassword=SETYOURPASSWORDHERE #optional &#10;rpcallowip=127.0.0.1 #optional &#10;daemon=1 &#10;upnp=1 &#10;listen=1 &#10;dbcache=800 &#10;maxmempool=50 &#10;disablewallet=1 &#10;logips=1 &#10;maxconnections=125 &#10;prune=42000 &#10;maxuploadtarget=5000 &#10;server=1 </pre> '''Note1:''' If you are are planning to only access your node from your pi itself, skip the first 3 optional settings <br /> '''Note2''': Opening up the RPC port to hosts outside your local trusted network is NOT RECOMMENDED, because the rpcpassword is transmitted over the network unencrypted.<br />To save: CTRL+O ENTER, To exit: CTRL+X.