I kinda screwed up…

[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

[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.

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

You’re going to want to look into BFGminer, CGminer, or MultiMiner.

[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!

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

Thank you for starting that up. People volunteering and taking initiative to do things like this is what a Cryptocurrency project should be about, in my humble opinion. A strong community of volunteers who believe in what they’re doing is worth more than all the C-Suite executives in the world to me.