https://github.com/belfz/mpsc-crypto-mining

An example of using rust's `std::sync::mpsc` with multiple threads of execution to find a hash of given difficulty.
https://github.com/belfz/mpsc-crypto-mining

Last synced: 3 months ago
JSON representation

An example of using rust's `std::sync::mpsc` with multiple threads of execution to find a hash of given difficulty.

• Host: GitHub
• URL: https://github.com/belfz/mpsc-crypto-mining
• Owner: belfz
• License: mit
• Created: 2017-10-24T21:09:34.000Z (about 7 years ago)
• Default Branch: master
• Last Pushed: 2019-01-01T01:21:49.000Z (almost 6 years ago)
• Last Synced: 2024-06-30T12:35:30.436Z (5 months ago)
• Language: Rust
• Size: 13.7 KB
• Stars: 24
• Watchers: 3
• Forks: 5
• Open Issues: 2
• Metadata Files:
  • Readme: readme.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# mpsc-crypto-mining

An example of using `std::sync::mpsc` with multiple threads of execution.

The computation-heavy algorithm used in this example is a **basic implementation of an idea** behind cryptocurrencies mining process (so-called "Proof of Work", or solving the cryptographic problem).

### About the cryptographic algorithm

An example: given a number 42 (the "constant base"), find a number _x_ to multiply it by, so that the result of this multiplication hashed by SHA-256 will produce a hash string ending with `000000`.

The actual solution is 3,305,951, which - while multiplied by 42 gives 138,849,942, producing a `2a44903ffc6affe69d514ffe47721cc3a6475cbb43b37538686f2c5b46000000` hash.

### About `std::sync::mpsc`

This example uses `std::sync::mpsc` as a channel of communication between four worker threads and the main thread. Each worker thread analyses unique numbers (by starting the iterations at different "points" and having constant step). For more info, see the large comment inside `src/main.rs`'s `main()` function.

### How-to

This example uses unstable feature - the [step_by method](https://doc.rust-lang.org/std/iter/trait.Iterator.html#method.step_by) from `std::iter::Iterator`'s implementation for `std::ops::Range`. This is why `#![feature(iterator_step_by)]` attribute is present at the top of `src/main.rs`. **For that reason, this project will currently compile with nightly only!**

To compile with nightly: 

1. `cd` to project's root,

2. run `rustup override set nightly`

**For maximum performance, instead of running with bare `cargo run` I recommend to add the `--relase` flag:**

1. `cd` to project's root,

2. run `cargo run --release` and enjoy!

Feel free to experiment - change the value of `DIFFICULTY` constant in `src/main.rs` and/or `THREADS`! Please note that a change by one extra desired character in `DIFFICULTY` (eg. one more `0`) can increase the overall difficulty of the problem dramatically, thus noticeably extending the time needed to find the solution!

### License

MIT