Running Bitok - 0.3.19 Mainnet

[elvisjedusor]

A block explorer for Bitok is now available at:

bitokd.run

Bitok itself does not maintain address or transaction indexes, consistent with early Bitcoin design. The explorer operates using a separate external indexer that parses the blockchain sequentially and builds its own database for inspection purposes.

This does not change node behavior or protocol rules. It is an optional tool for observing the chain.

The explorer supports:

block and transaction lookup

chain height and block timing

basic network statistics

Address tracking is provided by the indexer, not by the Bitok node. Nodes remain wallet-centric, as originally designed.

The network and consensus remain unchanged.

[Tongpu]

A block explorer for Bitok is now available at:

bitokd.run

Bitok itself does not maintain address or transaction indexes, consistent with early Bitcoin design. The explorer operates using a separate external indexer that parses the blockchain sequentially and builds its own database for inspection purposes.

This does not change node behavior or protocol rules. It is an optional tool for observing the chain.

The explorer supports:

block and transaction lookup

chain height and block timing

basic network statistics

Address tracking is provided by the indexer, not by the Bitok node. Nodes remain wallet-centric, as originally designed.

The network and consensus remain unchanged.

This is amazing  
Really like this. Clean old-school look, very fast, and does exactly what it should. An explorer for 2010 Bitcoin code is something special. Time to mine BITOK.

[Tongpu]

I've been curious if the network hash rate is correct, that's an insane amount of power to throw at a new chain. - Mynta

Explorer shows hashrate, you can compare with yours

[elvisjedusor]

I've been curious if the network hash rate is correct, that's an insane amount of power to throw at a new chain. - Mynta

Explorer shows hashrate, you can compare with yours

Yes, network hashrate display on the block explorer.

The calculation:

Code:

hashrate = difficulty * 2^256 / max_target / avg_block_time

avg_block_time is measured from the last 50 blocks. This reflects actual mining conditions rather than the theoretical 600 second target.

[elvisjedusor]

Q&A

I mined coins but the explorer shows my addresses are empty

You mined blocks. Your gui bitok wallet shows a balance. But when you search Your Bitok Address (from wallet) on the block explorer - nothing. Zero balance.

Your coins are safe. Here's why this happens.

Bitok mining creates hidden addresses

When you mine a block, the software automatically generates a brand new address for that reward. This address goes straight into your wallet.dat file - but it does NOT appear in your gui wallet Address Book.

Your Receiving addresses from Address Book are ones you manually created to share with people. Mining addresses are created silently in the background, one per block you solve.

So when you check the explorer...

You're searching addresses from your Receiving list. But your mined coins live at completely different addresses that mining auto-generated. That's why the explorer shows zero - you're looking at the wrong addresses.

How to find your actual mining addresses

In the wallet console or via RPC:

listunspent - shows all addresses holding coins
listreceivedbyaddress 0 true - shows all addresses including unused ones
Search THOSE addresses in the explorer and you'll find your mined coins.

Your wallet knows everything

Your wallet.dat contains all private keys - both your Receiving addresses AND all mining addresses. The balance shown in your wallet is correct. The explorer just needs the right addresses to search.

Or consolidate if you really want to

You can create a new Receiving address and send all your coins there. After that transaction confirms, the explorer will show your full balance at that one address.

But ask yourself - do you actually need this? Your wallet already tracks everything perfectly. All you'd accomplish is putting your entire holdings on public display for anyone curious enough to search. Privacy has its perks.

[chn520]

Let more people know,we need pool and discord.

[elvisjedusor]

Let more people know,we need pool and discord.

The network doesn’t depend on coordination channels. If people find it useful, they’ll build what they need.
Bitcoin didn’t launch with pools, chat servers or promotion. It launched with working code.

[EKLETTICK]

If you want I have already set up a discord server for this project and it is ready to be launched, let me know if you are interested, a few posts above I had published a post with some ideas for the logo.

[cyferfonix]

If you want I have already set up a discord server for this project and it is ready to be launched, let me know if you are interested, a few posts above I had published a post with some ideas for the logo.

I like the way the original bitok logo looks, I'd suggest on not forcing a change

The code speaks for itself

If people like it, then they will use it

We're at an early stage

I'd like to keep what the founder has to say and I want to listen

And not miss what was being said

Discord can be useful I use it myself

But I don't want people taking charge of the discord server

And then play a game of bossing around of the community and then taking the project in the wrong direction

I don't want the project falling in to the wrong hands like how the failed asic BTC coin did after 2010

[cyferfonix]

A block explorer for Bitok is now available at:

bitokd.run

Bitok itself does not maintain address or transaction indexes, consistent with early Bitcoin design. The explorer operates using a separate external indexer that parses the blockchain sequentially and builds its own database for inspection purposes.

This does not change node behavior or protocol rules. It is an optional tool for observing the chain.

The explorer supports:

block and transaction lookup

chain height and block timing

basic network statistics

Address tracking is provided by the indexer, not by the Bitok node. Nodes remain wallet-centric, as originally designed.

The network and consensus remain unchanged.

This is amazing  
Really like this. Clean old-school look, very fast, and does exactly what it should. An explorer for 2010 Bitcoin code is something special. Time to mine BITOK.

https://i.ibb.co/93f10q3k/Screenshot-from-2026-01-13-18-21-30.png

Yes it's looking very amazing

[cyferfonix]

There's a tiny problem I'm having with mining with an intel i7 14700

The hash rate seems low compared to my AMD

I'm getting 300h/s to 700h/s and system becomes laggy and not found a block in a while

I know you are probably working to optimise the software thought I'd let you know

I think I should be getting 2kh/s to 3kh/s

My AMD is working fine now that you released an update

Thanks for that

[elvisjedusor]

A new Bitok release is available: 0.3.19.4

This update focuses on mining performance and system behavior under load.

Several optimizations were added to the built-in CPU miner to reduce overhead, improve cache locality, and make better use of available cores. The result is higher and more stable hash rates, particularly on modern Intel CPUs, and improved system responsiveness while mining.

These are implementation-level changes only. The proof-of-work, difficulty retargeting, and network rules are unchanged.

Binaries are available for Linux, Windows, and macOS.

As always, the best feedback comes from running the code.

Downloads (latest)

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

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

Linux:
- bitok-gui-0.3.19.4-linux-x86_64.tar.gz - GUI (AppImage portable)
- bitokd-static-0.3.19.4-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

d89e9c2a10a2ac5937e7597413414c5982678e8ec704f9d761db0b769c2877a9  bitok-0.3.19.4-win64.zip
6d44626eb20ea0ae46b6ad173232f24b7ed6961bcb306b50276942b40ee1e100  bitokd-macos-arm64.zip
498ef29276849ecc849ac50b02f513837e82754f05d84a5dc1ed61d3100fb291  bitokd-macos-x86_64.zip
900d148cefd86ed07b3925b912545cdf55ff9b99f972b0eff0930c950a493e5a  bitokd-static-0.3.19.4-linux-x86_64.tar.gz
985eeaa190f8fa12ddd047cf726c163f03b148ef882f920b359435ee14b6bea0  bitok-gui-0.3.19.4-linux-x86_64.tar.gz
b4945c00e67a4f92a32c61e660e7f34c39424f4b3a4a131bbd2d17f7a23019cb  bitok-macos-arm64.zip
6d4a6deff1fb09136ee6afe51e29bb0d857025afbc6e6ccb39115e366408c18f  bitok-macos-x86_64.zip

[elvisjedusor]

There's a tiny problem I'm having with mining with an intel i7 14700

The hash rate seems low compared to my AMD

I'm getting 300h/s to 700h/s and system becomes laggy and not found a block in a while

I know you are probably working to optimise the software thought I'd let you know

I think I should be getting 2kh/s to 3kh/s

My AMD is working fine now that you released an update

Thanks for that

Thanks for the report. I’ve updated the miner to avoid some unnecessary work per hash and to keep threads from fighting the scheduler. The latest 0.3.19.4 release should give a more realistic picture of what the hardware can do.

Implemented optimizations: https://github.com/elvisjedusor/bitok/blob/master/MINING_OPTIMIZATIONS.md

git commit: https://github.com/elvisjedusor/bitok/commit/e5921df864a578ba99f2c224309e918d7c45d043

If you try the new 0.3.19.4 build, I’d be interested to hear how it behaves on your setup after it’s been running for a while. Software improves by being exercised.

[hhuaqing]

我运行报错，更换电脑也是一样的问题运行不起来

C:\Users\Administrator\Desktop\bitok-0.3.19.4-win64>bitokd
SHA256: Using SSE4.1 acceleration
SHA256 implementation: sse4(1way)
CPU: Intel(R) Core(TM) i5-10500 CPU @ 3.10GHz
Yespower optimizations: AVX2 + SSE4.1 + SSE2
Bitok version 0.3.19
Bound to port 18333
Loading addresses...
dbenv.open strLogDir=//.bitokd/database strErrorFile=//.bitokd/db.log
************************
EXCEPTION: 11DbException
DbException: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
C:\Users\Administrator\Desktop\bitok-0.3.19.4-win64\bitokd.exe in AppInit()
************************
EXCEPTION: 11DbException
DbException: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
C:\Users\Administrator\Desktop\bitok-0.3.19.4-win64\bitokd.exe in AppInit()

[elvisjedusor]

我运行报错，更换电脑也是一样的问题运行不起来

C:\Users\Administrator\Desktop\bitok-0.3.19.4-win64>bitokd
SHA256: Using SSE4.1 acceleration
SHA256 implementation: sse4(1way)
CPU: Intel(R) Core(TM) i5-10500 CPU @ 3.10GHz
Yespower optimizations: AVX2 + SSE4.1 + SSE2
Bitok version 0.3.19
Bound to port 18333
Loading addresses...
dbenv.open strLogDir=//.bitokd/database strErrorFile=//.bitokd/db.log
************************
EXCEPTION: 11DbException
DbException: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
C:\Users\Administrator\Desktop\bitok-0.3.19.4-win64\bitokd.exe in AppInit()
************************
EXCEPTION: 11DbException
DbException: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery
C:\Users\Administrator\Desktop\bitok-0.3.19.4-win64\bitokd.exe in AppInit()

This is a Windows-specific issue affecting the daemon (bitokd.exe).

As a workaround, start the daemon from PowerShell with an explicit data directory:

Code:

.\bitokd.exe -datadir=C:\Users\<User>\AppData\Roaming\Bitok -debug

This uses the same path as the GUI.

The daemon currently resolves an incorrect default path (//.bitokd/) on windows, which Berkeley DB refuses to open. Changing machines does not affect this.

The Windows GUI (bitok.exe) resolves the correct data directory and works normally.

I’m fixing the default Windows path handling so the daemon and GUI use the same location.

[hhuaqing]

我尝试使用cpuminer挖矿，因为我有多台PC电脑，但是始终报错。
cpuminer-sse2  --algo=yespower  --param-n=2048 --param-r=32  --param-key="BitokPoW" --url http://127.0.0.1:8332 --user=123456 --pass=123456

         **********  cpuminer-opt 26.1  **********
     A CPU miner with multi algo support and optimized for CPUs
     with AVX512, SHA, AES and NEON extensions by JayDDee.

[2026-01-16 02:51:10] Yespower parameters: N= 2048, R= 32
[2026-01-16 02:51:10] Key= "BitokPoW"

CPU: Intel(R) Core(TM) i5-10500 CPU @ 3.10GHz
SW built on Jan 13 2026 with GCC-9.3.0 Windows MinGW-w64
CPU features:  AVX2    AES
SW features:   SSE2
[2026-01-16 02:51:10] CPU affinity [!!!!!!!!!!!!]
[2026-01-16 02:51:10] 12 of 12 miner threads started using 'yespower' algorithm
[2026-01-16 02:51:10] getblocktemplate failed, falling back to getwork
[2026-01-16 02:51:10] json_rpc_call failed, retry after 10 seconds
[2026-01-16 02:51:20] json_rpc_call failed, retry after 10 seconds
[2026-01-16 02:51:30] json_rpc_call failed, retry after 10 seconds
[2026-01-16 02:51:40] json_rpc_call failed, retry after 10 seconds


./bitokd.exe -rpcuser=123456 -rpcpassword=123456 -server  -datadir=C:\Users\Administrator\AppData\Roaming\Bitok -debug

ThreadRPCServer request={"method": "getwork", "params": [], "id":0}
ThreadRPCServer request={"method": "getwork", "params": [], "id":0}
ThreadRPCServer request={"method": "getwork", "params": [], "id":0}
ThreadRPCServer request={"method": "getwork", "params": [], "id":0}
ThreadRPCServer request={"method": "getwork", "params": [], "id":0}