No description
418b7b0628* Use a strand in distributed_work Wrap all distributed_work socket handling in a strand. Could use one strand for each peer [I think], but with the very low amount of messages (2 sent and 1 received at max) this seems unnecessary Other fixes and enhancements: - Fix a rare issue where generation would finish before `start_work()` is done (by moving the local generation code to the end of the function) - TSAN race fix in rpc.work_peer_many - Wrap request parameters in a work_request class - No logging when ongoing operations are canceled - Make `backoff` a chrono object - Move the work_peer_request class into distributed_work and rename it * Document distributed_work and simplify one cancel_connection() signature * Wrap socket.cancel() in the strand and fix some logging * Even socket.is_open() |
||
|---|---|---|
| .github | ||
| ci | ||
| CL | ||
| cmake/Modules | ||
| cpptoml@5399650056 | ||
| crypto | ||
| docker | ||
| etc | ||
| gtest@dea0216d0c | ||
| images | ||
| lmdb@c6bb7edf9f | ||
| miniupnp@582375b64f | ||
| nano | ||
| nano-pow-server@32e7826865 | ||
| util | ||
| valgrind | ||
| .clang-format.base | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .gitmodules | ||
| asan_blacklist | ||
| CMakeLists.txt | ||
| doxygen.config | ||
| Info.plist.in | ||
| LICENSE | ||
| logo.png | ||
| Nano.icns | ||
| Nano.ico | ||
| Nano.rc | ||
| nanocurrency-beta.spec.in | ||
| nanocurrency.spec.in | ||
| qt.conf | ||
| README.md | ||
| rep_weights_beta.bin | ||
| rep_weights_live.bin | ||
| resources.qrc | ||
| tsan_clang_blacklist | ||
| tsan_suppressions | ||
| valgrind.supp | ||
What is Nano?
Nano is a digital payment protocol designed to be accessible and lightweight, with a focus on removing inefficiencies present in other cryptocurrencies. With ultrafast transactions and zero fees on a secure, green and decentralized network, this makes Nano ideal for everyday transactions.
Guides & Documentation
Other documentation details can be found at https://docs.nano.org.
Links & Resources
Want to Contribute?
Please see the contributors guide.
Contact us
We want to hear about any trouble, success, delight, or pain you experience when using Nano. Let us know by filing an issue, joining us on Reddit, or joining us on Discord.