“KingPepe” …. Your “chain” has burned down around you. Twice. 50% or better of your code is busted. Miners got ripped off and burned hash power for nothing. You front loaded the chain not once, but twice with instamines.


You thought just because it compiled successfully, that it was ready to ship, and you shipped it out without even testing it thoroughly.


You’re a grifter… and not even a smooth one.


GTFOH.

Apologies for the delay. Here’s a link to the more “Official” launch announcement:
https://bitcointalk.org/index.php?topic=5548676.0

“Note: No promises. No bullshit. No roadmap. It's just for fun. Mine it or ignore it. Ya you win big 🐸📈, or you learn a damn good lesson.”


It was right there in the very first post.

After the past 36 or so hours of watching BitcoinII be put in the crosshairs of solo and pool miners, and ran by a few volunteer node operators, I feel like it's time to
make an "Official Announcement":


BitcoinII's mainnnet is LIVE.

From my first BitcoinTalk post:


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!




Below is the README.MD from the Github repo:

A brief message from BrokenMachine:

In this repository resides the source code, Official Linux x86_64 and Windows x86_64 Release Binaries for BitcoinII, a new PoW (Proof of Work) cryptocurrency built purely on the founding first principles of Satoshi Nakamoto's original Bitcoin protocol, and the various network enhancements (Bitcoin Improvement Protocols) that have been established by the Bitcoin Core Developers over the previous 16 years.

The following facets of the BitcoinII network remain identical to Bitcoin:

-PoW Algorithm: SHA256

-Maximum Supply: 21,000,000 BC2.

-Smallest Unit: 0.00000001 BC2, or 1 Sat2, or 1 "Satooshi".

-Proof of Work Difficulty Retargeting: Every 2016 blocks, or ~2 weeks.

-Block Subsidy Halving: Every 210,000 blocks, or ~4 years.

-Initial Block Reward Subsidy: 50 BC2.

-B.I.Ps (Bitcoin Improvement Proposals): BIP34, BIP65, BIP66, CSV, and SegWit are all Activated and "buried".

-Taproot Deployment has a minimum activation height of 300, and times out at 12:00, January 9th, 2030 UTC.

The B.I.Ps that are currently Activated and "buried" were done so due to reasons related to security, ease of use, functionality, and familiarity for Node Operators, Miners, and Users alike. Taproot was not buried due to the requirement of additional code that would need to be implemented, and it is of my opinion that the Community should decide on whether or not it should be fully implemented and "buried" in the future.

The following facets of the BitcoinII network are different from Bitcoin:

-Genesis Block: This is not a "hard" nor "soft" fork in any traditional sense. The Node and Wallet software is forked from Bitcoin Core 0.27.0 source code, but BitcoinII is not a fork from the existing Bitcoin network itself.

-Network PoW Difficulty: Restarted at Difficulty 1. BitcoinII is currently well within the realm of being mineable with standard consumer grade CPUs. I recommend using Pooler's "cpuminer", also known as "minerd".

-Pooler's CPU mining software can be found here: For the source code you can compile yourself: https://github.com/pooler/cpuminer For pre-compiled, ready to run binaries: https://sourceforge.net/projects/cpuminer/

-Network Ports: BitcoinII operates on different network ports than Bitcoin, to facilitate the operation of Bitcoin and BitcoinII node operation on the same machine. BitcoinII uses ports 8338, 18338, 38338, 18448, and whichever RPC and Onion ports the user configures, if they use those features.

-RPC Ports: Configurable via bitcoinII.conf to avoid confusion and contamination with Bitcoin.

-pchMessageStart values: These are changed so that Bitcoin and BitcoinII nodes can never communicate with each other, thus avoiding any potential blockchain or mempool contamination.

-Binary name: BitcoinII binaries are named "bitcoinIId", "bitcoinII-cli", "bitcoinII-qt", etc. so as to facilitate the operation of Bitcoin and BitcoinII nodes on the same machine.

-Default Data Directories: Again, these are changed slightly to facilitate operation of both Bitcoin and BitcoinII nodes on the same machines.

Most all software written to interact with Bitcoin should also work with BitcoinII, given the software is made aware of the minor differences in Ports and pchMessageStart values where applicable.

Regarding hashrate, it should be noted that today's modern machines have vastly superior hashrates compared to the equipment from the era in which Satoshi Nakamoto developed the first Bitcoin node software. Since BitcoinII begins life at the same Target Difficulty as Satoshi Nakamoto started the Bitcoin network with, it is recommended that miners exercise restraint when devoting hashpower to mining BitcoinII. Doing so may encourage faster mining adoption by the inexeperienced, and help keep energy consumption low network-wide as BitcoinII's Difficulty Retargeting mechanism begins to adjust Target Difficulty. Much consideration was given to the idea of whether or not to adjust the Retargeting mechanism due to this fact, but I decided against it as I felt it would stray too far from Satoshi's vision and design, so the end result is that the Retargeting mechanism was left as Satoshi designed it. Perhaps we can learn from the previous 16 years and adjust our Mining Operations accordingly.

Roadmap: That is not for I alone to determine, that is for YOU, the Community to determine. The hope and intent is that BitcoinII grows to become something of value and purpose to a large Community of Node Operators, Volunteers, Miners, and users. My intent was for not for BitcoinII to compete with, nor attempt to replace Bitcoin, but to become a "Sister Chain" that would appeal to "Maxis" and "Newcomers" alike, and to provide a chain built on the security principles and technology that has proven itself for the past 16 years. By all means, I encourage people to continue to support Bitcoin, Bitcoin Core, Bitcoin Knots, and their respective developers. BitcoinII is offered as an accompaniment to their efforts. While Bitcoin(BTC) continues to be a long term investment vehicle used by many, perhaps BitcoinII(BC2) can provide an instrument to be used more freely for day-to-day purchases, by implementing the same proven and familiar technology implemented by Bitcoin(BTC) that millions around the world have grown to understand and trust.

Final Words: All documentation related to the system requirements, compilation, installation, configuration, and usage of Bitcoin Core 0.27.0 apply directly to BitcoinII, with the exceptions of the above mentioned differences (port changes, etc). There has been no large "Pre-Release" mining take place. Blocks have been mined by two machines to establish the blockchain, activate B.I.Ps, test network transactions, etc. I hate a "Rug Pull" as much as anyone.

Until more nodes come online and the dnsseed server populates, use the command "addnode bitcoinII.ddns.net:8338 add" in BitcoinII-qt's RPC console to connect to the network, or simply add it in the bitcoinii.conf config file.

The BitcoinII project needs volunteers: Node Operators, DNS Seed Server Operators, Miners, etc. If you would like to volunteer to help with any of these needs, reach out to BrokenMachine on BitcoinII's subreddit r/BitcoinII, BrokenMachine's username is u/BitcoinII.

Satoshi Nakamoto is often credited with saying, in regards to Bitcoin: "It might make sense to get some in case it catches on."

Many people wish they could or would have been mining Bitcoin since 2009. Absent a working a time machine, this is the best chance at a second chance that I can provide to them.

    BrokenMachine

The Packages in this release have been signed with the Private Key for the Coinbase Address that mined BitcoinII's Block #1, and can be verified using "verifymessage" via the CLI or RPC Console.

Block 1 Coinbase Address: 1gaUkKnNzFmARU4JW49AEqNFV5EbWURqR

BitcoinII-0.27.0-Source.tar.gz: 2ac77bafbdc7bab3598fb06e8323f0095b1297c917f79cbd87a5bfc6c3907ce7

BitcoinII-0.27.0-Source.zip: 3fe8d6befd27c1802e1ecea5fe2ecf04c763120f2301622b6ba62e84569c99b6

BitcoinII-0.27.0-CLI-Linux-x86_64.tar.gz: f9081fbe1f33ce1053d561f9b004ffcec15abb111fb4877b68f4f0f389983796

BitcoinII-0.27.0-Qt-Linux-x86_64.tar.gz: c80b4445ab3959e0c1da271023fbc339b98cf55ae44a1af1d2fb733ad3f27d04

BitcoinII-0.27.0-CLI-Windows64.zip: 2846b55c04f7fab1e6490d090755df7a136b31f4f2b4f6894a6125c7ba84bdb4

BitcoinII-0.27.0-Qt-Windows64.zip: 408b566cb307f0d30e601dfb14e2acf85180834afa49ff232ceadb9de0fa87f1

BitcoinII-0.27.0-Source.tar.gz Sha256Sum Signature:

IC1A+hj6BSTtEEt/qaqcVYvp1nT+R0OfC0RoyBE1s55/dd8C1ZnXAjUb2aezPhnGIG4Wr9maKHf/WSAM79XhZ8A=

BitcoinII-0.27.0-Source.zip Sha256Sum Signature:

H1sBTnANAMGc2AwqUHcv4X3wlbnZWpIdeJFN5+w9U1V8N43zcvkQ2ADkIbBXB9x1VNzAPS9TtvAzuY7YQrLvHB0=

BitcoinII-0.27.0-CLI-Linux-x86_64.tar.gz:

HzPw8b4EjiBH+Bx+9Jx+CbhMBfU6gVMnRJPLL/hHbru0AH42gyqMVL13v8j4+oiVmHj3l6P660cJMFdjmRnjp34=

BitcoinII-0.27.0-Qt-Linux-x86_64.tar.gz:

INZuoQe5kh1G11rhT7LfpMpmmYEqmu27vsvODVwa7GHbR5vYSOBlXrYY4brrwHA1vaVEHHjec4s/DWh8fMnenHQ=

BitcoinII-0.27.0-CLI-Windows64.zip:

IB0B/i3xeyenTxG6DQMD98S0b1Uo2aL04g/ELLJb+zoRO+RE+6VnolZkKcuni4BwXEOwDRQ+YSiJAezc+xFbGtc=

BitcoinII-0.27.0-Qt-Windows64.zip:

H0rokVaSRGk3VVPYjuD5pxlK6xm4oC9ilQJI6JhRcdA/Aho4HYdUzL0AdsL8t05+bRjEnBim0x/1d/1lzaDurs4=



I keeep my head mostly in source code, and not so much Social Media. I am not a good "Front Man" when it comes to "shilling" or "promoting" anything, but I
wanted to do the best I could for people looking for a "Second Chance", and feel the need to make a more "Official Announcement" so that people will become aware of it.

As far as the code goes, like anything with Cryptocurrency: "Don't Trust, Verify."

Since my first post on BitcoinTalk, someone in the community has spun up a PPLNS pool and a Solo pool:
https://minorpool.com/#BitcoinII
https://minorpool.com/#BitcoinII-S

and started a Telegram group:
https://t.me/+mc19GB_d5yo3Yjg5

I'm not "perpetually online", so to speak, but I will make it a point to visit this post every evening for a couple hours to answer any questions I possibly can.

I intended for this to be a "Community Project", where the ultimate outcome of the Network and the Coin's value is decided by the ones who are willing to run nodes,
mine blocks, and establish a market for BitcoinII.

I hope that you all enjoy it, and that it becomes of use to you

                                                                         -BrokenMachine

I just wanted to drop in and give a quick 24 hour update since my first post here. In the last 24 hours:


Someone created a Telegram chat.
Someone spun up PLNS and Solo Mining pools.
Estimated network hash rate came within 1-2 Terahashes of breaking 1Petahash.
Miners appeared to conduct Block reward UTXO consolidations
Pool operators conducted Payout transactions.

And BitcoinII, by every estimation I can make from what I can see, took it all in stride just as it should. The Difficulty Retarget Mechanism, Mempool, etc all seem to be functioning perfectly by my estimation.

If anyone who has tried it has encountered any errors, please… by all means, let me know so I can get started with diagnosing and fixing them.

Thank you all for what has been one of the most exciting 24 hours in my 40 years of existence on this planet!

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.

I haven’t had the time to take any of that on yet, my focus has been solely the node/wallet software and getting the blockchain up and running. If someone would like to take any one of those projects on, I sure won’t turn down the help!

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

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.

It was a heck of a thing to sit and watch the hashrate climb as you all started mining in the last couple hours.

It’s one thing to bootstrap a network from Block #0 with 3 machines and not have any issues, but it’s much more rewarding to see that BitcoinII could indeed survive a healthy increase in mining pressure without falling apart at the seams.

There’s only so much stress testing I can do with my limited access to hardware.

I’ve stressed over this for months trying to be sure that everything was exactly right, or that at least I didn’t massively screw up somewhere, and those of you who put it to the test have helped put my mind at ease.

Sincerely, Thank You!

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

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

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.

Gameparadise007,


     That’s a question I can’t answe 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.

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.

Sparks,

    BitcoinII is mineable with Pooler’s cpuminer/minerd, it is not mineable by simply issuing a command in the RPC console 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.

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!