Running Bitok - 0.3.19 Mainnet

[elvisjedusor]

Bitok v0.3.19.8 - Security Hardening

This release implements critical security improvements and network reliability enhancements. All changes are backwards-compatible.

Time Warp Attack Protection
Prevents timestamp manipulation attacks that could artificially lower mining difficulty:

Blocks with timestamps more than 2 hours + 60 minutes ahead of parent are rejected
At difficulty adjustment boundaries, suspiciously compressed timespans are blocked
Soft-fork activation at block 16,000 - warnings only before activation, strict enforcement after

DNS Seed Discovery
Reliable peer discovery for network bootstrapping:

seed1.bitokd.run
seed2.bitokd.run
seed3.bitokd.run

Hardcoded fallback nodes when DNS is unavailable

Privacy-Preserving IP Detection
Removed all external HTTP service dependencies:

External IP now learned from peers via standard P2P handshake
Manual configuration available via -externalip=X.X.X.X
No connections to third-party services (checkip.dyndns.org, whatismyip.com removed)

Upgrade recommended for all node operators. Nodes running older versions won't have time warp protection after block 16,000.

See SECURITY_FIXES.md for technical details.

Download latest release:

https://bitokd.run/download

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

[Tongpu]

About 600 blocks until the next difficulty adjustment.
Blocks have been coming in slower than target lately, do you guys think difficulty goes down or up this round?

[Bumbulas]

About 600 blocks until the next difficulty adjustment.
Blocks have been coming in slower than target lately, do you guys think difficulty goes down or up this round?

On Jan 28 network hashrate was only 65kh/s and blocks were slow, so I thought difficulty would drop. But today (Jan 29) it hit 181.66 kH/s, looks like some big farm joined. Blocks are much more stable now, so I think difficulty will stay about the same or even go up a bit if this hashrate stays.

[elvisjedusor]

Summary of Bitok Design Choices

Original transaction format preserved 
First-seen transaction relay 
Adjustable block size via planned upgrades 
Optional fees with priority system 
CPU-oriented mining 
Simple relay policy 
Bounded Script with useful operations 
On-chain transactions as the default

These choices are not innovations. They are continuations.
https://github.com/elvisjedusor/bitok/blob/master/BITOK_DEVELOPMENT.md

[Tongpu]

Bitok mining pool is now open sourced:
https://github.com/antitongpu/bitok-stratum-pool

web: https://lastbitcoin.org
support: https://bitcointalk.org/index.php?topic=5572258.0

[Tongpu]

On Jan 28 network hashrate was only 65kh/s and blocks were slow, so I thought difficulty would drop. But today (Jan 29) it hit 181.66 kH/s, looks like some big farm joined. Blocks are much more stable now, so I think difficulty will stay about the same or even go up a bit if this hashrate stays.

Retarget in 10 blocks. Let’s see how it plays out

[maxfedfm]

No reward for a week, looks like some big farms takes everything, It was a good idea to make Bitok for the people, but powerful computers killed it. Satoshi Nakomoto problem is not solved. It's sad.


https://imgur.com/a/vDSaXrS  


And this is in a month!  Who needs a coins in one pocket? Welcome back to the past!

[yoshikiazuma]

No reward for a week, looks like some big farms takes everything, It was a good idea to make Bitok for the people, but powerful computers killed it. Satoshi Nakomoto problem is not solved. It's sad.


https://imgur.com/a/vDSaXrS  


And this is in a month!  Who needs a coins in one pocket? Welcome back to the past!

i(am) like (a) bitok. i really do like this coin though, im still mining and i want to carry on supporting the network. i think it looks good, and its my kind of coin. i like it. there will be some improvement i guess in the coming times

[Bumbulas]

No reward for a week, looks like some big farms takes everything, It was a good idea to make Bitok for the people, but powerful computers killed it. Satoshi Nakomoto problem is not solved. It's sad.


https://imgur.com/a/vDSaXrS  


And this is in a month!  Who needs a coins in one pocket? Welcome back to the past!

My old phone still digging whole Bitoks every day
https://imgur.com/a/Pxc6hPy

[Tongpu]

Lets do something for Bitok as community.

I'm working on an auto-exchange feature for the Bitok mining pool at lastbitcoin.org so users can auto-convert rewards to USDT if they want. I'll bootstrap the starting price with my own funds, then add buy/sell tools later. We need an exchange engine to get things moving, like Mt. Gox for Bitcoin, just more safu

[nebiwe]

Bitok Added Idpool

Pool : https://bitok.idpool.id
Discord : https://discord.gg/8KnMJyx6
Telegram: https://t.me/idpool_id

Thanks

[yoshikiazuma]

Lets do something for Bitok as community.

I'm working on an auto-exchange feature for the Bitok mining pool at lastbitcoin.org so users can auto-convert rewards to USDT if they want. I'll bootstrap the starting price with my own funds, then add buy/sell tools later. We need an exchange engine to get things moving, like Mt. Gox for Bitcoin, just more safu

haha i know what you mean. haha mt.gox haha

goodluck tongpu and hope we have an exchange soon, i wonder what you going to name it, haha i think you should make the exchange website format look like a mt.gox exchange but with a new name

RE-LIVE THE MOMENT

[Tongpu]

Bitok Added Idpool

Pool : https://bitok.idpool.id
Discord : https://discord.gg/8KnMJyx6
Telegram: https://t.me/idpool_id

Thanks

Great, i see you use bitok-pool
Just pushed important upgrade

Mining pool Bug fixed

Bitok uses >> 17 instead of >> 16
Most yespower coins (Tidecoin, Cranepay, etc.) use bnProofOfWorkLimit = ~uint256(0) >> 16, which gives diff1 = 2^240 and perfectly matches cpuminer-opt's opt_target_factor = 65536.

Bitok chose >> 17 (diff1 = 2^239), making the minimum difficulty target 2x harder than the yespower standard. This is a valid design choice -- it means Bitok's "difficulty 1" represents twice as much work as other yespower coins' "difficulty 1". The multiplier of 2 bridges this gap at the pool level.

https://lastbitcoin.org upgraded

P.s. Thanks to Elvisjedusor for pointing out this bug  

[elvisjedusor]

Support for Simplified Payment Verification (SPV) has been merged into master.
https://github.com/elvisjedusor/bitok/commit/a071757b71adf286fb062ab3b2b3ca06ae52417d

This implements the node-side protocol needed for lightweight clients as described in Section 8 of the Bitcoin whitepaper. It allows wallets to verify transactions using block headers and Merkle proofs without downloading the full blockchain.

This is not a tagged release yet. Developers can build from source to experiment with SPV functionality.

What’s included:

getheaders / headers for header-only chain sync

Bloom filter support (filterload, filteradd, filterclear)

Filtered block relay via partial Merkle trees

Merkle inclusion proofs (merkleblock)

RPC helpers for header retrieval and proof verification


“The design outlines a lightweight client that does not need the full block chain.”, - Satoshi Nakamoto


Purpose

This completes the missing pieces needed for web, mobile, and embedded wallets to operate without storing the full chain, while full nodes continue to validate blocks and relay data.

It enables true SPV participation, reducing barriers for ordinary users.

Documentation: https://github.com/elvisjedusor/bitok/blob/master/SPV_CLIENT.md

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

[elvisjedusor]

dumpprivkey / importprivkey has been merged into master.
https://github.com/elvisjedusor/bitok/commit/de45e63142b34579481ede6dd6a80036e762bdb8

Added RPC support for exporting and importing private keys.

dumpprivkey <address> returns the private key for an address in WIF format

importprivkey <key> [label] adds a WIF key to the wallet

Works with existing wallet.dat.
No wallet format changes.

This allows moving keys between wallets and using external or lightweight clients that do not generate keys locally.

[Tongpu]

dumpprivkey / importprivkey has been merged into master.
https://github.com/elvisjedusor/bitok/commit/de45e63142b34579481ede6dd6a80036e762bdb8

Added RPC support for exporting and importing private keys.

dumpprivkey <address> returns the private key for an address in WIF format

importprivkey <key> [label] adds a WIF key to the wallet

Works with existing wallet.dat.
No wallet format changes.

This allows moving keys between wallets and using external or lightweight clients that do not generate keys locally.

Cool, thanks! I'm sure many people here waiting this. wallet.dat is cool but have privkey is better Keep building!