It's strictly volunteer and the more servers out there, the stronger the network gets and more redundant it becomes to outages, errors, or attacks. Feel free to message me if you are interested.
What info is needed?
Just the IP (static) or Domain name (can be static or dynamic, as long as peers can resolve to your server properly), the sub-folder (usually timekoin) and the port number (if it's other than 1528). You can set the sever load to whatever you like, the default server works with 8 peers active and 15 reserve at a time, but if you have a fast enough Internet connection and Server, it can work with many times more, so it's up to you if want to raise the limit.
- To estimate load, using the default 8 peers, 15 reserve setting will generate about 1-2 kbps of traffic during normal usage such as transaction processing or just regular peer polling for activity.
- The traffic load for a large amount of reserve peers is still minimal (since it only pings every minute or so to make sure they are still online)
- The traffic load for a large amount of active peers can quickly ramp up from say 8 active peers to 16 active peers in a fairly linear fashion. You can estimate what load you are comfortable with.
- The theoretical maximum peers you can set is 150 (combined total of active and reserve peers). The reason for the limit is based on Raspberry Pi as a base for speed and server load when testing the limits of the device. If you have a faster server, then higher numbers can be achieved of course.
- If you enable "Super Peer Mode" under the System tab, you can set a range in the Options tab from 10 to 500 Transaction cycles. This will allow new peers that need to catch up on history to download in bulk from your server without getting banned for flooding with queries. Turning on this mode can increase outbound bandwidth in very large amounts, so use with care if you are on a metered Internet connection.