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/mainI 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.
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 keep 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/#BitcoinIIhttps://minorpool.com/#BitcoinII-Sand started a Telegram group:
https://t.me/+mc19GB_d5yo3Yjg5I'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
😂 Oh, you must be the budget Satoshi Nakamoto! Even your source code is garbage.
We checked the link to your "coin" that you proudly posted... and what did we find?
Recycled nonsense, a lazy fork, and not a single original idea. Looks like you changed one line and said, “I created a coin!”