Running Bitok - 0.3.19 Mainnet

[elvisjedusor]

Bitok 0.3.19.6 release

I’ve implemented an extended mining RPC with BIP22 support.
This adds modern mining interfaces without changing consensus, block rules, or behavior.

What’s included:

Infrastructure
Configuration file support (bitok.conf)
Argument parsing helpers (GetArg, GetIntArg, GetBoolArg)
Proper platform-specific data directory handling
RPC security
HTTP Basic Authentication
IP whitelist with CIDR support
Configurable RPC port (-rpcport, default 8332)
Configurable bind address (-rpcbind, default 127.0.0.1)
Proper HTTP status codes for auth failures

Mining support
getblocktemplate (BIP22) for pools
submitblock for block submission
getmininginfo for network and mining stats
Legacy getwork retained for compatibility
Block template creation and network hashrate estimation

Configuration
rpcuser, rpcpassword, rpcallowip, rpcport
Auto-loaded on daemon startup

Third-party miners can be used. Solo mining tested with cpuminer-opt (https://github.com/JayDDee/cpuminer-opt). Pools can now integrate Bitok directly.
This should reduce variance during periods of higher difficulty while keeping the protocol intact.

Links

More info about implementation: https://github.com/elvisjedusor/bitok/blob/master/RPC_MINING_IMPLEMENTATION.md

Solo mining guide: https://github.com/elvisjedusor/bitok/blob/master/SOLO_MINING.md

Pool integration guide: https://github.com/elvisjedusor/bitok/blob/master/POOL_INTEGRATION.md

Full RPC API Docs: https://github.com/elvisjedusor/bitok/blob/master/RPC_API.md

User docs: https://bitokd.run/docs

Download latest release:

https://bitokd.run/download

https://github.com/elvisjedusor/bitok/releases/tag/0.3.19.6

*All changes are limited to interface and infrastructure layers only; consensus rules, block structure, transaction semantics,
and monetary policy remain identical to Satoshi’s original 2010 implementation

[hhuaqing]

cpuminer-avx512.exe -a yespower --param-n=2048 --param-r=32 --param-key="BitokPoW" -o http://127.0.0.1:8332 -u 123456 -p 123456
已经成功运行，但我还需要把收益统一到一个钱包地址，我还应该加什么参数

[elvisjedusor]

cpuminer-avx512.exe -a yespower --param-n=2048 --param-r=32 --param-key="BitokPoW" -o http://127.0.0.1:8332 -u 123456 -p 123456
已经成功运行，但我还需要把收益统一到一个钱包地址，我还应该加什么参数

You don’t set a fixed mining address when solo mining. Each solved block generates a new coinbase address automatically. This is intentional and for privacy.

That’s how Bitcoin originally worked. Later versions of Bitcoin changed this behavior. Bitok does not.

All generated coinbase addresses belong to your wallet and are included in your balance. If you want to consolidate funds to a single address, you can do so manually later. That is optional.

Bitok preserves Satoshi’s original privacy model.

[cyferfonix]

Bitok currently exposes the original getwork interface from Bitcoin 0.3.x. It works as designed, but modern miners and pools expect block templates and extranonce support.

Extending the mining API does not change core or any consensus rules. It only affects how work is distributed to miners.

I’m planning to implement a more complete mining API so that:

modern pools can support Bitok

third-party miners can be used

variance can be reduced during periods like this

The protocol remains intact. The rules remain the same.
This is strictly an interface-level improvement.

I forsesee great issues with the difficulty re targeting. Consider running through a model where a large percentage of the hash rate drops off.

this is satoshi's vision. built by satoshi. works like satoshi.

works like gold and moves like gold

lets move the worlds

i like the way this bitcoin operates. (no changes, the original vision)

[chn520]

Waiting for first pool

[yoshikiazuma]

it is great to be an honorable member of bitcoin 2010. thanks. s.n

[stark2010]

how to get private keys?

[elvisjedusor]

how to get private keys?

Bitok follows the original Bitcoin wallet design.

Private keys are generated internally and stored in wallet.dat. There is no per-address key export feature.

Ownership is defined by possession of wallet.dat. Back it up.

[yoshikiazuma]

Finally mined 1 block

At 968 diff and network hashrate 123 kH/s, if your CPU produces 1 kH/s, you control about 0.8% of the network hashpower.

On average:

Expected blocks per miner = 1 / 0.008 ≈ 1 block every 125 blocks

With a 10-minute target, that’s ~20 hours per block on average

That is an average, not a schedule. You may find two blocks close together or none for many hours. Both outcomes are normal.

The current difficulty reflects earlier, higher hashrate. As blocks continue to come in slower, the next retarget will lower difficulty to match the present network power.

https://bitokd.run

I noticed as well the new difficulty. I'm still mining though 2 days no blocks yet but I hope luck strikes again. I've been mining since before the difficulty rise, got on kind of early. I'm a bitok dedicated miner, willing to provide my mining power to support the bitcoin (2010) network. I have two machines, it's three actually but I'm using my main machine ryzen 7 pro 8700ge [phoenix edition] full time mining bitcoins, the second machine is being used for mining but has bit of  gaming too so only part time mining on the second pc and the last machine which isn't connected up because I gave up on crypto 2 weeks ago felt like crypto was letting me down so told my family member to help me sell my own big powerful computer. But I guess I made a mistake on trying to get it sold because all of a sudden I found bitcoin bitok, which reignited the phoenix in me and for me to carry on and decypher/decrypt blocks by supporting/mining bitok network. I can't wait to see when is my lucky block rewards going to arrive but I'm excited from the waiting and surprises. I'll update once I  find my next block. - yours sincerely. Mr Phoenix Azuma Intelligence