|SHI 5d86a68c53 main - > Starwels MAI||2 lat temu|
|gitian-building||3 lat temu|
|man||2 lat temu|
|release-notes||2 lat temu|
|.gitignore||3 lat temu|
|Doxyfile.in||2 lat temu|
|README.md||2 lat temu|
|README_osx.md||2 lat temu|
|README_windows.txt||2 lat temu|
|REST-interface.md||2 lat temu|
|assets-attribution.md||2 lat temu|
|benchmarking.md||2 lat temu|
|bips.md||2 lat temu|
|build-openbsd.md||2 lat temu|
|build-osx.md||2 lat temu|
|build-unix.md||2 lat temu|
|build-windows.md||2 lat temu|
|developer-notes.md||2 lat temu|
|dnsseed-policy.md||2 lat temu|
|files.md||2 lat temu|
|fuzzing.md||2 lat temu|
|gitian-building.md||2 lat temu|
|init.md||2 lat temu|
|reduce-traffic.md||2 lat temu|
|release-notes.md||2 lat temu|
|release-process.md||2 lat temu|
|shared-libraries.md||2 lat temu|
|starwels_logo_doxygen.png||2 lat temu|
|tor.md||2 lat temu|
|translation_process.md||2 lat temu|
|translation_strings_policy.md||2 lat temu|
|travis-ci.md||2 lat temu|
|zmq.md||2 lat temu|
Starwels is the original Starwels client and it builds the backbone of the network. It downloads and, by default, stores the entire history of Starwels transactions (which is currently more than 100 GBs); depending on the speed of your computer and network connection, the synchronization process can take anywhere from a few hours to a day or more.
To download Starwels, visit GitHub.
The following are some helpful notes on how to run Starwels on your native platform.
Unpack the files into a directory and run:
Unpack the files into a directory, and then run starwels-qt.exe.
Drag Starwels-Core to your applications folder, and then run Starwels-Core.
The following are developer notes on how to build Starwels on your native platform. They are not complete guides, but include notes on the necessary libraries, compile flags, etc.
The Starwels repo’s root README contains relevant information on the development process and automated testing.
Distributed under the MIT software license. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. This product includes cryptographic software written by Eric Young (firstname.lastname@example.org), and UPnP software written by Thomas Bernard.