Running It Double click the mc64.exe file to launch MicroCash. Currently it listens for peer to peer connections on a UDP port. It also has an in built web browser which you can access by typing http://127.0.0.1 into your web browser. Linux Version Notes: Currently, the Linux build doesn't open up a terminal when it runs, so it's pretty silent. If you run it from a terminal, you'll see the same text debug output messages as the Windows build, in case you're interested in that stuff. You can also shut it down with a Ctrl-C, whereas just double-clicking it to run it will require ending the task less gracefully. Download Please see below the post for the attachment. You may need to be logged in to download it. SYSTEM REQUIREMENTS -Windows Vista, 7, 8, 10 or Linux (any distro with 64bit support) -64bit CPU -4GB RAM -IPv4 or IPv6 Network card NOTES MicroCash is a single binary solution requiring no DLLs/libraries or anything else besides noted above, written exclusively in C++ using the C++11 standard (and eventually C++17) and compiled with all optimizations to native x64 code. Is is portable, in that you can put it in any directory and it only interacts with the contents in that directory, it does not use any system registration functions unless wanted, for example installing as a windows service. MicroCash will not officially support 32bit or provide 32bit builds due to limits in RAM. Though it will be possible to run a 32bit node with minor source changes it is highly discouraged. There have also been numerous efforts to optimize for a 64bit CPU with memory alignments, memory copying, and in the encryption and hashing functions. All advanced instructions sets will be targeted for use though nothing beyond SSE3 is currently. While the alpha uses barely any RAM the way MicroCash is designed may require bursts of high RAM usage during a financial type denial of service attack. This could easily force 32bit apps to crash due to running out of RAM due to their ability to only address 2-3GB of RAM in the best of cases. settings.txt values and meanings P2P_PORT=777 This is the the UDP port used by MicroCash node to communicate to other nodes. Depending upon whether you have IPv4 or IPv6 you may need to open the port to let it communicate to the internet. HTTP_SERVER_ENABLED=1 Set to 0 to disable. This determines whether the inbuilt wallet server and node configuration web server is enabled. Without it your ability to interact with the node is limited but it may be useful in some instances. It is currently only bound to localhost so will be unable to be accessed over the internet. HTTP_SERVER_PORT=80 The TCP port used by the http server. Currently there is no SSL/tls so all communications between node and web browser are unencrypted like normal web traffic. HTTP_SERVER_THREADS=1 Accept value from 1 to 32. The number of threads to be used in the web server. For nearly all use cases it only needs to be 1. If serving a huge number of users for some reason increasing this number would help as it would increase the total number of connections able to be processed. HTTP_SERVER_IPV6=0 If set to 1 then the web server will listen and accept requests on both IPv4 and IPv6 DIR_NETWORK=./network The directory for the P2P node to dump any relevant data into, eg the transaction chain, log files, etc Command Line options -benchmark If this is set when the binary is run it will run a series of tests and output the results to console. No node or web server is run and when the benchmark is finished it closes. -installservice On windows it installs MicroCash as a service so that you can use to control the execution of MicroCash within the usual Windows framework. Currently does nothing on Linux/MacOS -removeservice Removes the service. Directory structure mc64.exe (binary, currently less than 1MB) settings.txt (list of program settings) network\ (directory for MicroCash network data) network\log.txt (P2P node log) wallets\ (directory for wallet files) wallets\username.mcx (example wallet created after logging into node) web\ (directory that serves HTML content web\index.html (default file that is used to serve content) web\jquery.js (latest jquery) web\style.css (style sheet for wallet) web\*.png (image files used for various things in the wallet HTTP SERVER Anything placed in the web directory itself will be available to be served to whoever connects to 127.0.0.1 on IPv4 or :: on IPv6 . You cannot go deeper than that directory, any attempt to will result in a 404 error. Only API requests can go deeper than the root web directory, but it is only a virtual directory space, not actual directory space (ie /user/password/api_command). The web server only accepts GET requests and currently there is a maximum request size of 4KB. GET responses can be as large as the file/data returned, no maximum set.