savenode Core is the original savenode client and it builds the backbone of the network. However, it downloads and stores the entire history of savenode transactions; 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. Thankfully you only have to do this once.
The following are some helpful notes on how to run savenode on your native platform.
Unpack the files into a directory and run:
- bin/32/savenode-qt (GUI, 32-bit) or bin/32/savenoded (headless, 32-bit)
- bin/64/savenode-qt (GUI, 64-bit) or bin/64/savenoded (headless, 64-bit)
Unpack the files into a directory, and then run savenode-qt.exe.
Drag savenode-Qt to your applications folder, and then run savenode-Qt.
- See the documentation at the savenode Wiki TODO for help and more information.
- Ask for help on BitcoinTalk or on the savenode Forum.
- Join one of our Discord groups savenode Discord Groups.
The following are developer notes on how to build savenode on your native platform. They are not complete guides, but include notes on the necessary libraries, compile flags, etc.
The savenode repo's root README contains relevant information on the development process and automated testing.
- Developer Notes
- Multiwallet Qt Development
- Release Notes
- Release Process
- Source Code Documentation (External Link) TODO
- Translation Process
- Unit Tests
- Unauthenticated REST Interface
- Dnsseed Policy
- Discuss on the BitcoinTalk .
- Join the [savenode-Dev] Discord groups savenode Discord Groups.
Distributed under the MIT/X11 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 ([email protected]), and UPnP software written by Thomas Bernard.