Wallet desktop application
Clone or download

README.md

CS Desktop Wallet

What's CS Desktop wallet?

CS Desktop Wallet - the client application is a desktop version of the wallet. Wallet Desktop is implemented in Java. This version of the wallet provides a high level of security, privacy and stability. Wallet Desktop only works in conjunction with the network node running on the user's computer and includes the Smart Contract executor module. Current functionality:

  • View the balance
  • View transaction history
  • View transactions with smart contracts
  • Create a transaction
  • Creating a new token, using a smart contract
  • Create and download a smart contract
  • Operations with smart contracts

System requirements:

Minimum system requirements:

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

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.

Contribution

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-Wallet-Desktop, 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 Java Style Guide
  • Code must be well documented adhering 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

Resources

CREDITS Website

Documentation

Whitepaper

Technical paper

Developers portal

Credits forum

Community links