What is CS NODE?
CSNODE is the main module that provide an opportunity to run a node and participate in CREDITS blockhain network. The node performs processing and storage of transactions, execution and confirmation of the terms of smart contracts, processing requests from third-party systems, and provides data upon request. Each node on the network has the same functionality. The node consists of the following elements:
- Desision-making module(Solver)
- Transport protocol
How to Build
- Clone the repository:
git clone https://github.com/CREDITSCOM/CSNode.git
- Make a directory build64:
- Change directory:
- Run a CMAKE command:
cmake .. -A x64
- Open a project in Visual Studio:
Also, you can use the assembly for a specific program
cmake -G "Development Environment x64"
Operating system: Windows® 7 / Windows® 8 / Windows® 10 64-bit (with the last update package) Processor (CPU): with frequency of 1 GHz (or faster) with PAE, NX and SSE2 support; Memory (RAM): 2–4 Gb HDD: 1 Gb Internet connection: 3 Mbit/s Minimum system requirements:
Recommended system requirements:
Operating system: Windows® 7 / Windows® 8 / Windows® 10 64-bit (with the last update package) Processor (CPU): Intel® Core ™ i3 or AMD Phenom ™ X3 8650 Memory (RAM): 4–8 Gb SSD: 1 Gb Internet connection: 5 Mbit/s.
Thank you for considering to help out with the source code! We welcome contributions from anyone on the internet, and are grateful for even the smallest of fixes! If you'd like to contribute to CS-NODE, please fork, fix, commit and send a pull request for the maintainers to review and merge into the main code base. If you wish to submit more complex changes though, please check up with the core devs first on our Developers portal and Contribution file to ensure those changes are in line with the general philosophy of the project and/or get some early feedback which can make both your efforts much lighter as well as our review and merge procedures quick and simple. Please make sure your contributions adhere to our coding guidelines:
- Code must adhere to the Google C++ Style Guide
- Code must be well documented adhering to the Google’s guidelines
- Pull requests need to be based on and opened against the master branch
- Commit messages should be prefixed with the package(s) they modify