Bitcoin Forum
May 28, 2026, 02:25:15 PM *
News: Latest Bitcoin Core release: 31.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1] 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 »  All
  Print  
Author Topic: Running Bitok - 0.3.19 Mainnet  (Read 7167 times)
elvisjedusor (OP)
Jr. Member
*
Offline

Activity: 74
Merit: 5


View Profile
January 10, 2026, 11:28:01 PM
Last edit: March 16, 2026, 06:46:19 AM by elvisjedusor
Merited by Tongpu (1)
 #1

Bitok - Bitcoin v0.3.19 Completed

Bitcoin before the compromises. Satoshi's unfinished work, finished.

Quick Links

Block explorer: bitokd.run
Download latest release: bitokd.run/download
Quick Docs: bitokd.run/docs
GitHub: github.com/elvisjedusor/bitok
Web wallet: wallet.bitokd.run
Faucet: freebitok.com
WEB3 SDK: github.com/elvisjedusor/bitok-sdk
RPC API docs: RPC_API.md
X: x.com/bitok_coin



Downloads - Bitok 0.3.19.13 ATOM. The Lost Bitcoin Layer 🜂

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

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

macOS Intel:
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: github.com/elvisjedusor/bitok/releases/tag/0.3.19.13

---

What This Is

Between 2009 and 2010, Satoshi built a peer-to-peer electronic cash system with a programmable script engine, free transactions for established coins, CPU mining, lightweight client support, and built-in privacy primitives. Then he left.

What followed was a decade of things being removed. The script opcodes were disabled. Free transactions were eliminated. Mining went to ASICs. Privacy was never implemented. Replace-By-Fee made zero-confirmation payments unreliable. The system that arrived was narrower than the one that was designed.

Bitok starts from Bitcoin v0.3.19 Satoshi's last release, December 2010, and takes the design in the direction it was pointing.

  • The full script engine - every opcode works and is safe.
  • Transactions are free for coins held a day or more.
  • Mining is CPU-optimized. Your laptop can compete.
  • SPV lightweight wallets work as Satoshi described in the whitepaper.
  • Native stealth addresses - Satoshi's key blinding, implemented.
  • Raw transaction toolkit for arbitrary script contracts.

Same 21M supply. Same halving schedule. Same 10-minute blocks. New genesis. Separate network.

---

Specifications

Code:
Algorithm:          Yespower 1.0 (N=2048, r=32) pers="BitokPoW"
Block time:         10 minutes
Block reward:       50 BITOK
Halving:            every 210,000 blocks
Max supply:         21,000,000
Difficulty adjust:  every 2016 blocks
Coinbase maturity:  100 blocks
P2P port:           18333
RPC port:           8332
Network magic:      0xb40bc0de

---

Script Engine

In August 2010, Bitcoin Core disabled most scripting opcodes, citing denial-of-service risk. The practical consequence was the removal of Bitcoin's native programmability. A decade later, restoring OP_CAT alone remains one of the most contentious proposals in Bitcoin development.

Bitok kept every opcode and made the VM safe with deterministic execution limits. The script engine activated at block 18,000 and has been live since.

Active opcodes:

  • OP_CAT - concatenation. Covenant patterns work.
  • OP_SUBSTR, OP_LEFT, OP_RIGHT - string slicing and extraction.
  • OP_MUL, OP_DIV, OP_MOD, OP_2MUL, OP_2DIV - on-chain arithmetic.
  • OP_LSHIFT, OP_RSHIFT - bitwise shifts.
  • OP_AND, OP_OR, OP_XOR, OP_INVERT - bitwise logic.
  • OP_CHECKMULTISIG - bare m-of-n multisig, standard and relayable.
  • OP_RETURN - provably unspendable. The original was bugged; this is fixed.
  • All six sighash types: ALL, NONE, SINGLE, with or without ANYONECANPAY.

Execution limits:
Code:
Max script size:      10,000 bytes
Max stack depth:      1,000 items
Max element size:     520 bytes
Max opcodes/script:   201
Max sigops/block:     20,000
Max multisig keys:    20

Evaluation model: Separated. scriptSig is push-only - it delivers data to the stack. scriptPubKey contains all logic. The scriptSig cannot influence control flow. Strict DER signatures, low-S enforcement, minimal push encoding. Scripts up to 10KB are standard and relayable.

Any well-formed script works: arithmetic puzzles, hashlocks, covenants via OP_CAT, timelocked payments with nLockTime, crowdfunding with SIGHASH_ANYONECANPAY, bare multisig with up to 16 keys.

---

Raw Transaction Toolkit

A full suite of RPC commands for building, signing, inspecting, and verifying arbitrary transactions:

  • createrawtransaction - construct a transaction from explicit UTXOs and outputs. Output keys can be addresses, OP_RETURN data, or raw hex scriptPubKey for custom contracts.
  • signrawtransaction - sign with wallet keys or explicit WIF keys. Supports all sighash types. Preserves partial signatures across multiple signers for multisig workflows.
  • buildscript - assemble a scriptPubKey from opcode names and hex data pushes.
  • setscriptsig - set an explicit scriptSig on a transaction input. The key tool for spending custom contracts.
  • getscriptsighash - compute the 32-byte sighash digest for an input. For offline and external signing.
  • verifyscriptpair - execute scriptSig + scriptPubKey against a real transaction and return the result with diagnostics.
  • decodescriptsig - decode a scriptSig in context, showing the role of each push element.
  • decoderawtransaction, decodescript, createmultisig, addmultisigaddress - inspection and multisig tooling.

Workflow: build a script, fund it with createrawtransaction, spend it with setscriptsig and sendrawtransaction. Offline cold-signing is supported - sign with explicit keys on an air-gapped machine, broadcast on the online node.

---

Native Privacy: Stealth ok-Addresses

On August 13, 2010, Satoshi described key blinding:

Quote
"What we need is a way to generate additional blinded variations of a public key. The blinded variations would have the same properties as the root public key, such that the private key could generate a signature for any one of them. Others could not tell if a blinded key is related to the root key, or other blinded keys from the same root key." - Satoshi Nakamoto, BitcoinTalk #356, August 13, 2010

He described it in detail. He never coded it. Bitok implements it.

How it works:

The receiver publishes a single stealth address (prefixed ok) that encodes two compressed public keys. Every sender independently derives a fresh one-time destination using ECDH with the receiver's scan key and spend key. The ephemeral public key is embedded in an OP_RETURN output (34 bytes on-chain). The receiver's wallet scans every transaction, derives the expected one-time key, and if it matches, computes the private key and imports the funds automatically.

  • Every payment to the same stealth address creates a different on-chain destination.
  • No outside observer can link two payments to the same person.
  • No interaction required - the receiver does not need to be online.
  • Deterministic change key derivation - change from stealth spends is recoverable from the SK secret alone.
  • No consensus changes - everything fits within the existing transaction format.

Backup and restore work through the same dumpprivkey / importprivkey commands as regular addresses. The combined SK export contains everything needed to recover both the stealth address and all derived change keys on any node via rescan.

RPC commands: getnewstealthaddress, liststealthaddresses, decodestealthaddress. sendtoaddress auto-detects ok-addresses and constructs the stealth transaction transparently.

---

Fee Policy

Bitcoin's original fee design was priority-based. Satoshi's intent was that coins held for a day move for free, and fees exist only to deter spam. Bitcoin Core replaced this with a pure fee market.

Bitok restores it:

Code:
priority = sum(input_value * confirmations) / tx_size

  • Coins held ~1 day at typical amounts qualify for free relay.
  • First 27KB of each block is reserved for high-priority free transactions.
  • Remaining block space is sorted by fee-per-byte.
  • When fees apply: 0.01 BITOK per KB.
  • Outputs below 0.01 BITOK (dust) always require a fee.

The wallet handles this automatically. If your coins qualify, they move for free. If not, the required fee is calculated and shown before sending.

---

CPU Mining

Satoshi wrote in 2009: "It's nice how anyone with just a CPU can compete fairly equally right now." That stopped being true within a year.

Bitok uses Yespower 1.0 (N=2048, r=32, pers="BitokPoW") - memory-hard, CPU-optimized, ASIC and GPU resistant. ~128KB memory per hash. SSE2, AVX, and AVX2 are auto-detected with no configuration required.

Code:
./bitokd -gen                    # mine on all cores
./bitokd -gen -genproclimit=4    # limit to 4 cores

In the GUI: Settings > Options > Generate Coins.

Pool operators: the node supports getblocktemplate (BIP 22) and getwork. Full Stratum-compatible pool integration is documented.

---

SPV / Lightweight Wallets

Section 8 of the Bitcoin whitepaper described simplified payment verification - lightweight clients that verify payments without downloading the full chain. The protocol is fully implemented:

  • Header sync - getheaders/headers, 2,000 headers per batch.
  • Bloom filters - filterload, filteradd, filterclear for transaction matching.
  • Filtered blocks - merkleblock messages with Merkle proofs for matched transactions.
  • Merkle proof RPC - gettxoutproof/verifytxoutproof for independent verification.
  • Transaction broadcast - sendrawtransaction for pre-signed transactions.

A lightweight wallet can verify payments trustlessly without a full node.

---

Security

Satoshi-era fixes (included from genesis):
  • Value overflow protection (184-billion coin bug)
  • Blockchain checkpoints at blocks 0, 6666, 14000, 16000
  • DoS limits on connection rate, message size, and message rate

Network hardening:
  • Time warp attack protection - timestamps validated at difficulty boundaries
  • DNS seed infrastructure - seed1/2/3.bitokd.run with hardcoded fallback peers
  • Anchor connections - 2 longest-lived peers saved and reconnected on restart (eclipse attack resistance)
  • Network group diversity - peers grouped by /16 subnet, capped at 2 outbound + 8 inbound per group (Sybil resistance)
  • External IP detection learned from peers via P2P, no HTTP dependency

Script hardening:
  • Strict DER signature validation
  • Low-S signature enforcement (anti-malleability)
  • SIGHASH_SINGLE out-of-range fix (prevents coin theft vector)
  • CHECKMULTISIG NULLDUMMY enforcement (anti-malleability)
  • OP_RETURN hard failure (original Bitcoin had a bug here)
  • Separated evaluation - scriptSig cannot manipulate scriptPubKey
  • Bounded execution - no CPU or memory exhaustion via scripts

---

Running

Extract and run. Peers are discovered via IRC bootstrap (irc.libera.chat #bitok) and DNS seeds - same mechanism early Bitcoin used.

Data directories:
  • Windows: %APPDATA%\Bitok\
  • Linux: ~/.bitokd/
  • macOS: ~/Library/Application Support/Bitok/

Code:
./bitokd                              # start a node
./bitokd getinfo                      # check status
./bitokd getnewaddress                # new address
./bitokd sendtoaddress <addr> <amount>
./bitokd getnewstealthaddress         # new stealth ok-address
./bitokd -gen -genproclimit=4         # start mining on 4 cores

---

Key Management

Code:
./bitokd dumpprivkey <address>            # export WIF or SK secret
./bitokd importprivkey <key> [label]      # import, triggers rescan

GUI: right-click any address in the address book to export. Import via File menu. Stealth address import runs two blockchain scan passes to recover all derived change keys.

---

Technical Documentation

Protocol:
SCRIPT_EXEC.md - Execution limits, separated evaluation, signature rules
SCRIPT_DEV.md - Full script developer guide: all opcodes, contract patterns, RPC toolkit
FEES.md - Priority-based fee policy
PRIVACY.md - Native stealth addresses (Satoshi's key blinding, implemented)
SPV_CLIENT.md - SPV lightweight client protocol
RAW_TRANSACTIONS.md - Raw transaction construction, multisig, custom scripts
SECURITY_FIXES.md - Security hardening details

Mining:
BITOKPOW.md - Yespower proof-of-work specification
SOLO_MINING.md - Solo mining with built-in miner or cpuminer-opt
POOL_INTEGRATION.md - Pool integration guide
MINING_OPTIMIZATIONS.md - CPU performance tuning

API & Building:
RPC_API.md - Complete JSON-RPC reference
BUILD_UNIX.md - Linux/BSD
BUILD_MACOS.md - macOS
BUILD_WINDOWS.md - Windows

---

License

MIT. Same as original Bitcoin.

---

Bitcoin v0.3.19, running as Satoshi designed it - with the parts he never had time to finish.
Tongpu
Member
**
Offline

Activity: 154
Merit: 10


View Profile
January 11, 2026, 12:46:31 AM
 #2



back to the future, haha Cool

elvisjedusor (OP)
Jr. Member
*
Offline

Activity: 74
Merit: 5


View Profile
January 11, 2026, 12:58:32 AM
Last edit: February 09, 2026, 08:03:42 AM by elvisjedusor
 #3


back to the future, haha Cool


Sometimes the future looks a lot like 2010, but with better hash functions.
Sparks60
Newbie
*
Online Online

Activity: 47
Merit: 0


View Profile
January 11, 2026, 02:17:45 AM
 #4

why is the blocks moving so fast, when i read its supposed to be 10 minute blocks ? some is like 30 seconds to find a blocks
elvisjedusor (OP)
Jr. Member
*
Offline

Activity: 74
Merit: 5


View Profile
January 11, 2026, 02:38:06 AM
 #5

why is the blocks moving so fast, when i read its supposed to be 10 minute blocks ? some is like 30 seconds to find a blocks

Network just started. Mining on genesis difficulty. It will auto-adjusts and blocks will normalize to ~10 minutes after few retargets.
Mynta
Newbie
*
Offline

Activity: 60
Merit: 0


View Profile WWW
January 11, 2026, 02:41:00 AM
 #6

why is the blocks moving so fast, when i read its supposed to be 10 minute blocks ? some is like 30 seconds to find a blocks

Mynta can help here.

If the retargeting occurs like bitcoin traditionally did, it should retarget after every ~2000 blocks or so. At 10 minute blocks this amounts to around 14 days, unless the dev's implemented early retargeting.
chn520
Newbie
*
Offline

Activity: 32
Merit: 0


View Profile
January 11, 2026, 03:16:13 AM
 #7

no peers
Mynta
Newbie
*
Offline

Activity: 60
Merit: 0


View Profile WWW
January 11, 2026, 03:49:33 AM
 #8

Mynta found none also.

You will need to connect to the irc server bitok used to bootstrap the network and decode the base64 IP's then add them manually.
chn520
Newbie
*
Offline

Activity: 32
Merit: 0


View Profile
January 11, 2026, 04:36:59 AM
 #9

Can I use cpuminer by rpc port?
Mynta
Newbie
*
Offline

Activity: 60
Merit: 0


View Profile WWW
January 11, 2026, 06:10:33 AM
 #10

Unfortunately because the RPC protocol was not updated this is highly unlikely. Mynta has been attempting to make a stratum bridge server for it, but its not looking good. Will report back with progress.
Mynta
Newbie
*
Offline

Activity: 60
Merit: 0


View Profile WWW
January 11, 2026, 07:07:11 AM
 #11

Mynta Now Supports Bitok (BITOK) — Custom Stratum for a Satoshi-Era Network

We’re glad to support Bitok (BITOK) and the direction this project has taken.

Bitok is not a re-imagining of Bitcoin — it’s a continuation of what Bitcoin actually was during Satoshi’s direct involvement. The v0.3.19 codebase, original rules, original behavior, original economics — preserved intentionally, with only the minimum changes required to operate securely on modern systems and prevent GPU/ASIC dominance.

Because of that legacy foundation, the RPC interface and networking behavior differ significantly from modern Bitcoin-derived chains. Standard pool software does not work reliably out of the box.

To support Bitok properly, we funded and deployed a custom stratum server built specifically for this network, designed to respect the original mechanics while allowing pooled mining for those who want reduced variance.

Pool Address:  
https://pool.a-zz.com
Download CPU Miner

Why pooled support exists  
Bitok is fully mineable solo — by design. That said:
• Some miners prefer steadier payouts over variance  
• Pools help smaller participants stay engaged as hashrate grows  
• Infrastructure should exist without redefining the network’s intent  

The pool exists to support Bitok, not change it.

Network observations  
Recent stats (see attached warning screenshots) show:
• Difficulty adjusting upward in response to real hashrate  
• Temporary block slowdowns as the 2016-block retarget reacts  
• Healthy behavior consistent with Bitcoin’s original difficulty model  

This is expected and confirms the network is behaving exactly as intended.

Mining roles  
Bitok: CPU-focused, memory-hard Yespower, accessible mining aligned with early Bitcoin philosophy  
Mynta: GPU-mined, ASIC-resistant, modern infrastructure-first blockchain  

Different goals. Different eras. Same respect for fairness.

Support  
If you need help connecting to the pool, have RPC quirks, or want clarification:
• Reply directly to this thread  
• Or send a DM  

You can also find Mynta in the Announcements section.

Quick Mynta note (for those curious)  
Mynta launches in approximately 4 days.

• Fair launch  
• No premine  
• ASIC-resistant  
• Built for long-term participation and infrastructure  

Mine Bitok with your CPU.  
Mine Mynta with your GPU.

Both are doing exactly what they set out to do.
Mynta
Newbie
*
Offline

Activity: 60
Merit: 0


View Profile WWW
January 11, 2026, 07:19:20 AM
 #12

no peers

You can find addnodes here:
https://pool.a-zz.com/explorer/peers?id=7
chn520
Newbie
*
Offline

Activity: 32
Merit: 0


View Profile
January 11, 2026, 08:56:38 AM
 #13

network hashrate   143MH 

 Shocked Shocked Shocked Shocked Shocked
Mynta
Newbie
*
Offline

Activity: 60
Merit: 0


View Profile WWW
January 11, 2026, 08:59:05 AM
 #14

network hashrate   143MH 

 Shocked Shocked Shocked Shocked Shocked

Mynta smells Nicehash...

The pool orphaned 3 blocks now because the other miner likely found the same blocks faster. At that speed they must be paying a fortune.
chn520
Newbie
*
Offline

Activity: 32
Merit: 0


View Profile
January 11, 2026, 09:06:44 AM
 #15

no yespower  nicehash
so large  hash,abnormal
Mynta
Newbie
*
Offline

Activity: 60
Merit: 0


View Profile WWW
January 11, 2026, 09:30:05 AM
 #16

no yespower  nicehash
so large  hash,abnormal


It would seem abnormal BUT blocks are still being generated and claimed - watch the wallet.
elvisjedusor (OP)
Jr. Member
*
Offline

Activity: 74
Merit: 5


View Profile
January 11, 2026, 09:33:54 AM
Last edit: February 09, 2026, 08:16:50 AM by elvisjedusor
 #17

no peers

Bitok 0.3.19.1 - fix wallet connection

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


Fix IRC peer discovery and network connectivity

Fix IRC channel formatting and response parsing

Add WHO command support for peer discovery

Improve address extraction and database integration

Add comprehensive logging for debugging

Fixed connection threshold

When you have fewer than 4 connections, retry addresses every 30 seconds instead of 10 minutes

Seed nodes are tried every 60 seconds if you have fewer than 4 connections

Connection loop runs faster (100ms vs 500ms) when bootstrapping

Windows wallet: Fixed process not terminating on close

P.s. Peer discovery uses IRC bootstrap, same as early Bitcoin.
If you see “no peers” on first run, update to 0.3.19.1 - IRC parsing and retry logic were fixed.
elvisjedusor (OP)
Jr. Member
*
Offline

Activity: 74
Merit: 5


View Profile
January 11, 2026, 09:57:18 AM
Last edit: January 12, 2026, 05:26:15 PM by elvisjedusor
 #18

2232066320e2c717a3cce26d87c0ce32ebc4187e4925a1a3837a815c1a7f7cf3  bitok-0.3.19.1-macos-arm64.tar.gz
934e468243a0bfef4aa3df58536d98abc82a7a75fa7336f06dcf8e3653d3a9db  bitok-0.3.19.1-macos-x86_64.tar.gz
ffe0dba6fd985795045c2d62c7bf699e2f37d7ef3c767e52d7984ca8aedd5857  Bitok-0.3.19.1-win64.zip
1388463feb1bd39bf6ee0b1f37dd4dffa309b58597c260a4e855b5b15f6b3fcb  Bitok-0.3.19.1-x86_64.AppImage
5e399a98897ad69ad183b4edf2680279a1b156319ca1a4e32e3da352b7488fec  bitokd-0.3.19.1-linux-x86_64.tar.gz
7a698cfe9bd568ce92443509e31920a97378abdbdb4a9947885d1d008a4ea51b  bitokd-0.3.19.1-macos-arm64.tar.gz
d1772492cf9183997d34e419658acc1090ff257d8a139651d56e3b83a7792469  bitokd-0.3.19.1-macos-x86_64.tar.gz
Sparks60
Newbie
*
Online Online

Activity: 47
Merit: 0


View Profile
January 11, 2026, 03:05:52 PM
 #19

do you have a discord?
EKLETTICK
Newbie
*
Offline

Activity: 21
Merit: 0


View Profile
January 11, 2026, 05:37:58 PM
Last edit: January 25, 2026, 02:01:28 PM by Welsh
 #20

Hi guys , if you want I can make a detailed discord server , just let me know!

I created some test logos
check the logos here https://imgur.com/a/XeTrwhg

Let me know if there is a logo that you like more
Pages: [1] 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 »  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!