[ANN] Bitcoin 09 (09C) | CPU PoW | No Premine | Fair Launch

[tradi3]

Bitcoin 09 (09C)

The coin that you can mine like it's 2009.

I made Bitcoin 09 because I wanted to bring back the part of Bitcoin most of us missed: mining on a normal computer when the coins were worth nothing.

Bitcoin 09 keeps Bitcoin's economics and changes one thing: the proof of work. It uses Argon2id instead of SHA-256 so CPUs can mine it.

Basic specs

Code:

Name: Bitcoin 09
Ticker: 09C
Algorithm: Argon2id, 64 MiB memory cost
Block target: 10 minutes
Difficulty retarget: 2016 blocks
Max supply: 21,000,000
Block reward: 50 09C
Halving: every 210,000 blocks
Premine: none
Allocation: none
Genesis reward: burned / unspendable
Model: UTXO
Signatures: Ed25519
Block size: 1 MB

Genesis

Code:

ba685f741a04ddad03d37500ff354ce3887e64dd9cb6154ae236952792e90c3f

Genesis message:

Code:

the coin that you can mine like it's 2009

Source and releases

Code:

https://github.com/krutftw/bitcoin09
https://github.com/krutftw/bitcoin09/releases/tag/v0.1.2

Seed node

Code:

82.22.32.82:9009

The seed is built into v0.1.2, so you can just run:

Code:

btc09 node -mine

Or from source:

Code:

git clone https://github.com/krutftw/bitcoin09
cd bitcoin09
go build ./cmd/btc09
./btc09 node -mine

Notes

09C has no price. It may never have one. There is no premine, no allocation, no ICO, no airdrop and no reserved dev wallet. Every spendable coin starts from public mining after genesis.

I launched it, so I will answer technical questions here.

[weesdr]

Peer 82.22.32.82 timed out while mining

[tradi3]

Thanks for the heads up.

The node could mine a stale local block, then fail to catch up cleanly from the seed because block sync was requesting the wrong next height and sending too much at once.

Fixed in v0.1.7:
- bounded block sync
- fork catch-up fixed
- peers sending invalid old-fork blocks are disconnected
- seed send queues are no longer backing up

Latest release:
https://github.com/krutftw/bitcoin09/releases/tag/v0.1.7

If your node is stuck or timing out, stop it, download v0.1.7, then run:

btc09 node -mine

My node caught up from height 177 to 251 after the fix, so this should resolve it.

[longdi]

I set up a mining pool:
https://bitcoin09.tutuit.xyz

[tradi3]

Thanks, added the pool link to my notes.

Quick network update:

Latest release is now v0.1.9:
https://github.com/krutftw/bitcoin09/releases/latest

Explorer:
http://82.22.32.82:8009

Seed:
82.22.32.82:9009

If you mined on an early build, please upgrade. Older clients can get stuck on stale forks from before the sync and retarget fixes.

The seed and explorer are live right now, with the network around height 367 and 13 peers when I checked.

[weesdr]

How to run node without mining?

I also noticed that the balance in the node is slow in showing up the balance. In my case, it took several minutes for the balance to show in node, while explorer is already showing the balance

[tradi3]

Run it without mining by leaving off `-mine`:

btc09 node

Mining only starts when you add `-mine`.

On the balance delay: the wallet does not read from the public explorer. It calculates balance from your own local synced chain. So if your node is still catching up, the public explorer can show the balance first.

That was slower than it should be in v0.1.9, so I pushed v0.1.10. Fresh sync now uses larger bounded block batches, and the node logs balance changes as soon as the local chain sees them instead of only waiting for the regular status heartbeat.

Latest release:
https://github.com/krutftw/bitcoin09/releases/latest

If the coins are mined block rewards, they still need 100 blocks before they are spendable.

[tradi3]

Quick update:

v0.1.11 is out:
https://github.com/krutftw/bitcoin09/releases/tag/v0.1.11

Changes:
- Explorer now has supply endpoints:
  http://82.22.32.82:8009/api/supply
  http://82.22.32.82:8009/api/circulating_supply
- Circulating supply excludes the burned genesis reward.
- Normal chain extension has a faster path, so node/explorer startup is less wasteful.
- Added a quickstart:
  https://github.com/krutftw/bitcoin09/blob/master/QUICKSTART.md
- Added a simple early markets note:
  https://krutftw.github.io/bitcoin09/markets.html

When checked just now, the explorer was at height 2734 with 20 peers, and the public pool showed height 2742 with 9 connected miners.

There is still no official 09C price. If people trade it this early, it is just community OTC between a buyer and seller.

[BoozyTalking]

Where to get gpu miner? Coz people mine with GPU on tutuit pool.

[tradi3]

No official 09C GPU miner right now.
The tutuit pool uses NTMminer for pool mining, but for Bitcoin 09 the -a btc09 backend is CPU. NTMminer is a multi-algo miner, and it has GPU support for some other coins/algos, so that part can be confusing.

Current command is still:
NTMminer -a btc09 -o hk.tutuit.xyz:8344 -u YOUR_09C_ADDRESS
The pool hashrate/miner list only shows connected payout addresses and hashrate. It does not mean there is an official GPU miner for 09C.

[BoozyTalking]

Stats from pool:
Pool Hashrate - 24.65 KH/s
Workers: 12

What CPU can mine ~2KH/s on argon2id algo?
scam.

[weesdr]

Stats from pool:
Pool Hashrate - 24.65 KH/s
Workers: 12

What CPU can mine ~2KH/s on argon2id algo?
scam.

You never mine in pool before? 12 miners. Each miner can use the same worker. So 2kh/s can be multiple CPU rigs, not just one

[tradi3]

Stats from pool:
Pool Hashrate - 24.65 KH/s
Workers: 12

What CPU can mine ~2KH/s on argon2id algo?
scam.

You are reading the pool number wrong. The pool “workers/miners” number is not guaranteed to be 12 physical CPUs. It is pool-side connected payout addresses/workers. One 09C address can be used by multiple rigs, and NTMminer also supports worker names. So 24.65 KH/s / 12 does not mean one CPU is doing 2 KH/s. For btc09, the current public NTMminer docs list Bitcoin 09 as Argon2id 64MiB, CPU-only. NTMminer has CUDA/GPU support for other algorithms, but not for the btc09 backend.