I kinda screwed up…

[BitcoinII-Dev]

Obviously, I should’ve done a bit more research when selecting a name for my project. With the plethora of cryptos that exist today, I should’ve known a derivation of my chosen project name was already in use by somebody.

But… here’s the deal: I reset the clock, to the best of my ability. I took the BitcoinCore 0.27.0 code base, and built what I had named “BitcoinII”, or BC2.

What it is: A faithful recreation of the original launch of Satoshi’s Bitcoin. Target Difficulty 1. CPU mineable with minerd. No consensus rule changes. No deviation from the Bitcoin protocol itself. No gimmicks, no hacks, no BS.

What it isn’t: It is not associated with “Bitcoin2” or their developers in any way, shape, or form. No disrespect to them, I didn’t  even know they existed until about 10 minutes ago. It is not a fork of the Bitcoin blockchain. It is a new blockchain, with a new Genesis, but with identical features and performance.
 
Most all of the existing tooling that works with Bitcoin should work with BitcoinII, except for where pchMessageStart values or port changes would need to be implemented.

I just wanted to give people another shot at 2009, or at least be able to experience what it was like to CPU mine back then without having to have $10,000 Epyc CPUs to do it.

Every project has a “Make it” or “Break it” moment, and choosing not to rename my project may prove to be detrimental, but I’m past the point of no return. I’ve already pushed the source code and the pre-compiled static Windows and Linux Qt and CLI binaries to GitHub.

If this is of any interest to anyone, the GitHub repo is: https://github.com/BitcoinII-Dev/BitcoinII/tree/main

I would also like to add that there is 100% runtime separation of Bitcoin and BitcoinII. BitcoinII can be run simultaneously alongside a Bitcoin node on the same machine without network, data directory, or mempool cross contamination.

By all means, please check it out and critique the heck out of it… but spare me the hard times over the name, I’m already beating myself up over it.

Thanks for reading!

[Sparks60]

how to start mining from the qt wallet? what command to type in the Console cli?
what about a discord link?

[BitcoinII-Dev]

Sparks,

    BitcoinII is mineable with Pooler’s cpuminer/minerd, it is not mineable by simply issuing a command in the RPC console  or CLI like some projects are. You will need to configure BitcoinII’s bitcoinII.conf file first, then you will need to follow one of the links in the README.MD and select the software version applicable to your operating system, and follow Pooler’s easy setup instructions to mine BC2 to a BC2 address of your choosing. There is no built in miner inside BC2 with the exception of the Testnet/regtest miner.cpp and mini-miner.cpp, which aren’t functional for Mainnet mining, just as they’re not functional on Bitcoin Mainnet.

Conversely, if you have an old ASIC laying around, you can deploy one of those as well.

If you have any further trouble getting setup and mining, feel free to holler and I’ll try to walk you through it the best I can, although I’m not the best at explaining things.


I should’ve included some example configs in the repo, that was a lapse of judgement on my part, and I apologize.

Also, I do not have Discord… I’m kinda “Anti Social Media”… a bit too old for most of it.

[Sparks60]

thanks for the reply, but for some reason thought was cpu only, if asics can mine now, no need for me to even try, good luck tho

[BitcoinII-Dev]

Sparks:

What I mean is, Target Difficulty is currently 1. Same exact difficulty Bitcoin began with in 2009. CPUs can absolutely find valid blocks currently, I bootstrapped the network with a 2GHz Celeron. But I also didn’t prevent ASICs from being able to mine, because I couldn’t allow myself to make that kind of change to Satoshi’s original vision and still claim that it was identical to Bitcoin, just started over from a new Block #0 at Target Difficulty 1.

If you still want to give it a shot, I highly encourage it, as block rewards are currently 50 BC2. BitcoinII follows the exact same subsidy halving formula as Bitcoin.

If you’re willing to spin up a node and give it a shot, I would appreciate it. If you’re unable to find a Block within 24 hours, generate a BC2 address and let me know what it is and I’ll send you 50 BC2 for your time and effort.

[gameparadise007]

Yes, difficulty is still 1 and I am able to find blocks using my cpu.
For how long the difficulty will be 1?

[BitcoinII-Dev]

Gameparadise007,


     That’s a question I can’t answer with a definitive number, it depends solely on how much hashrate shows up, and when it shows up.

BitcoinII uses the exact same difficulty adjustment algorithm that Bitcoin does, so every 2016 blocks the timestamps of the previous 2016 blocks are evaluated, and the Target Difficulty is adjusted automatically.

If someone shows up with some serious hash power and spikes difficulty in the span of 2 retarget invervals, CPU mining could be a foregone conclusion in as little as 4,032 blocks.

But I can tell you this: Hash rate isn’t everything. Slower machines can and do find blocks in high target difficulty networks, that’s just how the hashing math works out sometimes.

And you miss 100% of the shots you don’t take.

[BitcoinII-Dev]

Yes, difficulty is still 1 and I am able to find blocks using my cpu.
For how long the difficulty will be 1?

Difficulty is currently at 3.79, with a network hash rate of 4937571453.939394.

And my Intel i5 machine just hit a valid block. Running minerd on a single CPU thread.

Like I said, you miss 100% of the shots you don’t take.

[chn520]

HTTP request failed: Failed to connect to 127.0.0.1 port 8337: Connection refused
[2025-07-02 10:46:10] json_rpc_call failed, retry after 30 seconds

[BitcoinII-Dev]

HTTP request failed: Failed to connect to 127.0.0.1 port 8337: Connection refused
[2025-07-02 10:46:10] json_rpc_call failed, retry after 30 seconds

How is your node’s config file setup? Are you configured for rpcport=8337 ?

[chn520]

HTTP request failed: Failed to connect to 127.0.0.1 port 8337: Connection refused
[2025-07-02 10:46:10] json_rpc_call failed, retry after 30 seconds

How is your node’s config file setup? Are you configured for rpcport=8337 ?

listen=1
server=1
daemon=1
rpcuser=abc
rpcpassword=123
rpcport=8337

[BitcoinII-Dev]

Try 8333 and let me know if that resolves the issue.

I use 8333 on one machine, 8332 on another machine with no issues.

If you’re using the GUI client, be sure to click “Settings”, “Options”, and then “Enable RPC Server”.

“daemon=1” is if you’re using bitcoinIId launched from an ms-dos terminal or Linux terminal and want it to run unseen in the background.

[chn520]

Try 8333 and let me know if that resolves the issue.

I use 8333 on one machine, 8332 on another machine with no issues.

If you’re using the GUI client, be sure to click “Settings”, “Options”, and then “Enable RPC Server”.

“daemon=1” is if you’re using bitcoinIId launched from an ms-dos terminal or Linux terminal and want it to run unseen in the background.

Cpu mine  ok.

Can we mine with  gpu?

[BitcoinII-Dev]

You can mine it with anything that has historically been used to mine Bitcoin. CPU, GPU, ASIC, etc.

As long as the mining software that’s in control of your mining setup can pull block templates via RPC from the node, and supports your mining hardware, you’re good to go.

[SaltyPirate]

Try 8333 and let me know if that resolves the issue.

I use 8333 on one machine, 8332 on another machine with no issues.

If you’re using the GUI client, be sure to click “Settings”, “Options”, and then “Enable RPC Server”.

“daemon=1” is if you’re using bitcoinIId launched from an ms-dos terminal or Linux terminal and want it to run unseen in the background.

I installed the Win 64 qt wallet but not sure how to connect an asic to mine. stratum? port?

[oen23tow]

Don't give up, you can continue with this project, start all your old machines, dig this coin, I will buy this coin, I am prepared to buy the coins in your hands for $100 each, dig them, don't save face for me.

[btc1092828733]

Don't give up, you can continue with this project, start all your old machines, dig this coin, I will buy this coin, I am prepared to buy the coins in your hands for $100 each, dig them, don't save face for me.

I dug them out, do you want to buy them for $100 each?

[Domajor]

web ?
explorer ?
discord ?
telegram ?

pool is active and working smoothly for now

[Grizzlymining1975]

Don't give up, you can continue with this project, start all your old machines, dig this coin, I will buy this coin, I am prepared to buy the coins in your hands for $100 each, dig them, don't save face for me.

ready to sell for $1

[btc1092828733]

Obviously, I should’ve done a bit more research when selecting a name for my project. With the plethora of cryptos that exist today, I should’ve known a derivation of my chosen project name was already in use by somebody.

But… here’s the deal: I reset the clock, to the best of my ability. I took the BitcoinCore 0.27.0 code base, and built what I had named “BitcoinII”, or BC2.

What it is: A faithful recreation of the original launch of Satoshi’s Bitcoin. Target Difficulty 1. CPU mineable with minerd. No consensus rule changes. No deviation from the Bitcoin protocol itself. No gimmicks, no hacks, no BS.

What it isn’t: It is not associated with “Bitcoin2” or their developers in any way, shape, or form. No disrespect to them, I didn’t  even know they existed until about 10 minutes ago. It is not a fork of the Bitcoin blockchain. It is a new blockchain, with a new Genesis, but with identical features and performance.
 
Most all of the existing tooling that works with Bitcoin should work with BitcoinII, except for where pchMessageStart values or port changes would need to be implemented.

I just wanted to give people another shot at 2009, or at least be able to experience what it was like to CPU mine back then without having to have $10,000 Epyc CPUs to do it.

Every project has a “Make it” or “Break it” moment, and choosing not to rename my project may prove to be detrimental, but I’m past the point of no return. I’ve already pushed the source code and the pre-compiled static Windows and Linux Qt and CLI binaries to GitHub.

If this is of any interest to anyone, the GitHub repo is: https://github.com/BitcoinII-Dev/BitcoinII/tree/main

I would also like to add that there is 100% runtime separation of Bitcoin and BitcoinII. BitcoinII can be run simultaneously alongside a Bitcoin node on the same machine without network, data directory, or mempool cross contamination.

By all means, please check it out and critique the heck out of it… but spare me the hard times over the name, I’m already beating myself up over it.

Thanks for reading!

Welcome to join the BitcoinII group https://t.me/+ut1vGP4VjH01MDYx