Running Bitok - 0.3.19 Mainnet

[neur0n.inc]

Hello. Where can I get the makefile.vc file (build with MSVC)? It is not in the archive with the sources...

[elvisjedusor]

Hi again hope that you’re doing well

Just wondering I have two home computers setup and CPU mining bitcoin

Would two devices connected on the same network affect my earned block reward, like will they be higher or lower rewards compared to having one pc? Is bitcoin mining node/network dependent where the rewards becomes split between the two computers which I’m mining with

Or will I be able have couple of computer devices mining for more/extra added block rewards?

Kind regards

The network doesn’t split rewards based on how many machines you run.

Each miner works independently. A block has a fixed reward, and whichever miner finds a valid block first gets it. Running multiple PCs just increases your total hash rate and therefore the probability that one of them finds a block.

There’s no coordination or penalty unless you’re using a pool. In solo mining, even machines on the same LAN are competing independently.

So yes, you can run more than one PC. They don’t interfere with each other. More hash rate just improves your odds over time.

[hhuaqing]

我有机器13日开始就没有收益，这个是log日志，能看出是什么原因导致没有收益的吗，我的CPU是I5-10500。
AddToBlockIndex: new best=384f15a9fc080479  height=13801
ProcessBlock: ACCEPTED
received: block (216 bytes)
received block 8396d6f1d176436f
AddToBlockIndex: new best=8396d6f1d176436f  height=13802
ProcessBlock: ACCEPTED
received: block (216 bytes)
received block 76e9cd64dfe29119
AddToBlockIndex: new best=76e9cd64dfe29119  height=13803
ProcessBlock: ACCEPTED
received: block (216 bytes)
received block 9827265299a8b08a
AddToBlockIndex: new best=9827265299a8b08a  height=13804
ProcessBlock: ACCEPTED
received: block (216 bytes)
received block a81a091d45747e47
AddToBlockIndex: new best=a81a091d45747e47  height=13805
ProcessBlock: ACCEPTED
received: block (555 bytes)
received block 6ebfc72e8bd0eabe
AddToBlockIndex: new best=6ebfc72e8bd0eabe  height=13806
MainFrameRepaint
ProcessBlock: ACCEPTED
received: block (216 bytes)
received block 9c2ab2ad00b91e63
AddToBlockIndex: new best=9c2ab2ad00b91e63  height=13807
AddToBlockIndex: new best=7ee6a5cc1350c866  height=13808
ProcessBlock: ACCEPTED
sending: inv (361 bytes)
Hashrate: 755.7 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 747.7 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 759.0 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 770.7 H/s | Threads: 6 | Height: 13808 | Txs: 1
trying connection  lastseen=8.9hrs lasttry=4.6hrs
Hashrate: 772.2 H/s | Threads: 6 | Height: 13808 | Txs: 1
connect() failed: 1.239.38.239:18333 (error 10060)
Hashrate: 763.2 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 781.7 H/s | Threads: 6 | Height: 13808 | Txs: 1
Cleaning up 85 old peer addresses (older than 12 hours)
trying connection  lastseen=8.9hrs lasttry=4.6hrs
connect() failed: 91.137.249.137:18333 (error 10060)
Hashrate: 777.5 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 764.5 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 768.3 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 761.3 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 761.8 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 791.1 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 743.4 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 775.3 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 745.8 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 787.7 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 763.3 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 755.9 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 779.7 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 768.1 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 774.3 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 765.2 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 737.6 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 775.2 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 765.0 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 750.9 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 799.2 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 763.9 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 774.3 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 794.7 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 765.6 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 775.4 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 768.8 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 749.7 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 774.2 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 760.4 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 762.4 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 662.8 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 759.3 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 764.4 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 774.4 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 763.6 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 787.4 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 759.4 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 764.0 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 777.7 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 768.2 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 772.3 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 773.6 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 771.4 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 687.2 H/s | Threads: 6 | Height: 13808 | Txs: 1
trying connection  lastseen=9.3hrs lasttry=4.8hrs
connect() failed: 38.175.103.98:18333 (error 10061)
Hashrate: 659.6 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 657.3 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 670.2 H/s | Threads: 6 | Height: 13808 | Txs: 1
sending: ping (0 bytes)
sending: ping (0 bytes)
sending: ping (0 bytes)
sending: ping (0 bytes)
Hashrate: 663.9 H/s | Threads: 6 | Height: 13808 | Txs: 1
sending: ping (0 bytes)
Hashrate: 672.6 H/s | Threads: 6 | Height: 13808 | Txs: 1
socket recv error 10054
disconnecting node
MainFrameRepaint
trying connection  lastseen=0.5hrs lasttry=0.5hrs
socket recv error 10054
disconnecting node
MainFrameRepaint
socket recv error 10054
disconnecting node
MainFrameRepaint
socket recv error 10054
disconnecting node
MainFrameRepaint
connect() failed: 162.252.198.54:18333 (error 10060)
Connecting to seed nodes (connections=1, seeds=1, others=0)
  Seed 1: 198.13.159.10:18333
trying connection  lastseen=0.0hrs lasttry=-1.0hrs

[elvisjedusor]

我有机器13日开始就没有收益，这个是log日志，能看出是什么原因导致没有收益的吗，我的CPU是I5-10500。
AddToBlockIndex: new best=384f15a9fc080479  height=13801
ProcessBlock: ACCEPTED
received: block (216 bytes)
received block 8396d6f1d176436f
AddToBlockIndex: new best=8396d6f1d176436f  height=13802
ProcessBlock: ACCEPTED
received: block (216 bytes)
received block 76e9cd64dfe29119
AddToBlockIndex: new best=76e9cd64dfe29119  height=13803
ProcessBlock: ACCEPTED
received: block (216 bytes)
received block 9827265299a8b08a
AddToBlockIndex: new best=9827265299a8b08a  height=13804
ProcessBlock: ACCEPTED
received: block (216 bytes)
received block a81a091d45747e47
AddToBlockIndex: new best=a81a091d45747e47  height=13805
ProcessBlock: ACCEPTED
received: block (555 bytes)
received block 6ebfc72e8bd0eabe
AddToBlockIndex: new best=6ebfc72e8bd0eabe  height=13806
MainFrameRepaint
ProcessBlock: ACCEPTED
received: block (216 bytes)
received block 9c2ab2ad00b91e63
AddToBlockIndex: new best=9c2ab2ad00b91e63  height=13807
AddToBlockIndex: new best=7ee6a5cc1350c866  height=13808
ProcessBlock: ACCEPTED
sending: inv (361 bytes)
Hashrate: 755.7 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 747.7 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 759.0 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 770.7 H/s | Threads: 6 | Height: 13808 | Txs: 1
trying connection  lastseen=8.9hrs lasttry=4.6hrs
Hashrate: 772.2 H/s | Threads: 6 | Height: 13808 | Txs: 1
connect() failed: 1.239.38.239:18333 (error 10060)
Hashrate: 763.2 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 781.7 H/s | Threads: 6 | Height: 13808 | Txs: 1
Cleaning up 85 old peer addresses (older than 12 hours)
trying connection  lastseen=8.9hrs lasttry=4.6hrs
connect() failed: 91.137.249.137:18333 (error 10060)
Hashrate: 777.5 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 764.5 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 768.3 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 761.3 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 761.8 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 791.1 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 743.4 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 775.3 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 745.8 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 787.7 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 763.3 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 755.9 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 779.7 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 768.1 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 774.3 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 765.2 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 737.6 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 775.2 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 765.0 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 750.9 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 799.2 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 763.9 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 774.3 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 794.7 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 765.6 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 775.4 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 768.8 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 749.7 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 774.2 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 760.4 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 762.4 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 662.8 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 759.3 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 764.4 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 774.4 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 763.6 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 787.4 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 759.4 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 764.0 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 777.7 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 768.2 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 772.3 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 773.6 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 771.4 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 687.2 H/s | Threads: 6 | Height: 13808 | Txs: 1
trying connection  lastseen=9.3hrs lasttry=4.8hrs
connect() failed: 38.175.103.98:18333 (error 10061)
Hashrate: 659.6 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 657.3 H/s | Threads: 6 | Height: 13808 | Txs: 1
Hashrate: 670.2 H/s | Threads: 6 | Height: 13808 | Txs: 1
sending: ping (0 bytes)
sending: ping (0 bytes)
sending: ping (0 bytes)
sending: ping (0 bytes)
Hashrate: 663.9 H/s | Threads: 6 | Height: 13808 | Txs: 1
sending: ping (0 bytes)
Hashrate: 672.6 H/s | Threads: 6 | Height: 13808 | Txs: 1
socket recv error 10054
disconnecting node
MainFrameRepaint
trying connection  lastseen=0.5hrs lasttry=0.5hrs
socket recv error 10054
disconnecting node
MainFrameRepaint
socket recv error 10054
disconnecting node
MainFrameRepaint
socket recv error 10054
disconnecting node
MainFrameRepaint
connect() failed: 162.252.198.54:18333 (error 10060)
Connecting to seed nodes (connections=1, seeds=1, others=0)
  Seed 1: 198.13.159.10:18333
trying connection  lastseen=0.0hrs lasttry=-1.0hrs

Your log looks normal. Mining is running correctly.

You are fully synced, your CPU is hashing steadily, and there are no errors related to mining or the wallet. The connection messages you see are normal peer churn and don’t affect rewards.

This is solo mining. Rewards are probabilistic. Not finding a block fast at this hashrate is expected behavior and does not mean anything is wrong.

Just keep it running.

[elvisjedusor]

Hello. Where can I get the makefile.vc file (build with MSVC)? It is not in the archive with the sources...

The MSVC makefile wasn’t included in the earlier source archive. I’ve added makefile.vc to the repository and updated the build documentation to reflect it.

You can now build with MSVC directly from the current sources https://github.com/elvisjedusor/bitok

Important: MSVC builds have different BDB 4.8 (from latest vcpkg) than Ubuntu/MinGW/macos main builds (BDB 5.3). BDB 5.3 is backward compatible with 4.8, but 4.8 is not forward compatible with 5.3. If you previously used official binaries, run recovery after building:

bitokd.exe -recover
or
./bitokd - recover


This recovers the wallet database for the current BDB 4.8 version for MSVC build.

If anything in the process is unclear or behaves differently on your setup, feedback is welcome.

[stark2010]

Back to the future.BTC

[elvisjedusor]

I’ve pushed Bitok 0.3.19.5.

Two important fixes in this release.

First, Windows daemon path handling.
bitokd was using HOME, which doesn’t exist on Windows. When unset, it defaulted to /, producing //.bitokd/ and breaking Berkeley DB.
The daemon now uses %APPDATA%\Bitok, same as the GUI. Unix behavior unchanged.

Second, and more important: a critical mining performance fix.
The miner was lowering thread priority and sleeping inside the mining loop. That meant every hash iteration paid a syscall penalty and forced idle time. This has been corrected.

Thread priority is now set once, sleep removed.
On my own machine, CPU hashrate increased by roughly 2× after the fix.

If you are mining, you should update.

Also added:

MSVC build support (makefile.vc)

Wallet recovery mode for damaged or version-mismatched wallet.dat files

If you build with MSVC and previously used official binaries, run:

bitokd.exe -recover


Nothing else changes.
Same chain, same rules.

Downloads (latest)

Version 0.3.19.5: https://github.com/elvisjedusor/bitok/releases/tag/0.3.19.5

Windows (64-bit):
- bitok-0.3.19.5-win64.zip - GUI + daemon

Linux:
- bitok-gui-0.3.19.5-linux-x86_64.tar.gz - GUI (AppImage portable)
- bitokd-static-0.3.19.5-linux-x86_64.tar.gz - daemon only

Macos (Intel-based) :
- bitok-macos-x86_64.zip - GUI
- bitokd-macos-x86_64.zip - daemon only

Macos (Apple Silicon) :
- bitok-macos-arm64.zip - GUI
- bitokd-macos-arm64.zip - daemon only

Source: https://github.com/elvisjedusor/bitok

f58444a389d7f7ee86aa2240d988842d8673491020aa2e70b110ff90eb8eae4e  bitok-0.3.19.5-win64.zip
e05cc021049ee6e3646e4cc399f12455955cd69d8a8cd982f62d4ef636d0c247  bitokd-macos-arm64.zip
02ea9874bda20aa55cb2e98c951d2bbc68f4560aa6d9d56bbbfc4fb25c37f19c  bitokd-macos-x86_64.zip
1372f7d9ebcdab0ed97b550cea0d4746bd7fb6e74d2d6937692a98a5beff0163  bitokd-static-0.3.19.5-linux-x86_64.tar.gz
a57cf0797d698ba7e6434206b4b1c28b2b4da5b50c53d7805316c44680196113  bitok-gui-0.3.19.5-linux-x86_64.tar.gz
2af5b2c2d9202899b6a0bdc17e7213db815f9d9f17fc2c7f3f0c072ecab85482  bitok-macos-arm64.zip
a7dc678735109de7aeb18d9dd31ef704679d0a8ffa8a61f3f6e77b22f2b4b35a  bitok-macos-x86_64.zip

[elvisjedusor]

At this moment we’re seeing longer block intervals because difficulty reflects earlier hashrate, not the current one.

This is expected behavior with a 2016-block retarget. Nothing is stuck. Nothing is broken.

Early Bitcoin went through the same thing more than once. Hashrate came in bursts, difficulty adjusted upward, then blocks slowed until the next window.

I’ve seen suggestions in private messages to reset difficulty or shorten the retarget window. Changing difficulty rules now would require a fork and would mean Bitok is no longer Bitok.

Modern Bitcoin has already diverged significantly from the system Satoshi originally released, through many well-intentioned changes over time. Bitok exists to preserve that original design as it was handed down. If we start rewriting core parameters to solve short-term conditions, we lose the very thing this project was created to keep.That’s not something I’m willing to do.

The protocol stays as Satoshi designed it. We wait for the adjustment and keep mining. Short-term discomfort is preferable to permanent protocol drift.

Network statistics: https://bitokd.run/