Bitcoin Forum
June 13, 2026, 07:50:57 AM *
News: Latest Bitcoin Core release: 31.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: [ANN][BLOZ] Block Zero - Fair Launch CPU PoW chain, RandomX, Bitcoin Core based  (Read 135 times)
SODINNER (OP)
Newbie
*
Offline

Activity: 5
Merit: 0


View Profile
June 10, 2026, 06:28:59 PM
Last edit: June 11, 2026, 04:44:08 PM by SODINNER
 #1

Block Zero (BLOZ)
A live CPU-mineable RandomX proof-of-work chain built on modern Bitcoin Core code.

Mainnet status

Block Zero mainnet has been live since 2026-06-06 06:06:06 UTC.

BLOZ is an independent proof-of-work chain. It keeps the familiar Bitcoin-style UTXO model and modern Bitcoin Core foundation, but changes the mining layer to RandomX so normal CPUs can participate.

Launch principles

- No premine
- No presale
- No team allocation
- No ICO
- CPU-mineable RandomX proof-of-work
- Open-source node software

Project and community links

Website:
https://bloz.cc (edited, see reply #1 for more information)

Mainnet explorer:
https://explorer.bloz.cc (edited, see reply #1 for more information)

Mining pool:
https://pool.bloz.cc

Browser wallet generator:
https://wallet.bloz.cc

GitHub Repository - Core:
SODINNER/blockzero-core (edited, original repo by "Rexemre", see reply #1 for more information)

GitHub Repository - Docs:
SODINNER/blockzero-docs (edited, original repo by "Rexemre", see reply #1 for more information)

GitHub Repository - Ops / Mining Scripts:
SODINNER/blockzero-ops (edited, original repo by "Rexemre", see reply #1 for more information)

GitHub Repository - Wallet:
SODINNER/blockzero-core/releases (edited, original repo by "Rexemre", see reply #1 for more information)

Discord:
https://discord.gg/z7vaB4ate (edited, see reply #1 for more information)

Community infrastructure

The bloz.cc community stack is live:

- public full node
- mining pool
- explorer
- browser wallet generator
- Linux/macOS/Windows mining setup (one-liner)
- direct on-chain pool payouts

The goal is to make the first mining experience simple:

0. Go to https://pool.bloz.cc
1. Generate a `bz1q...` address.
2. Copy the one-line miner command for your OS.
3. Watch your worker show up on the pool dashboard.

Trying to make the experience user-friendly.

Mining

Algorithm:
rx/blockzero

Mine solo, use the community pool, or create and share your own pool. Every contribution that expands the ecosystem is welcome.

Chain parameters

Coin: Block Zero
Ticker: BLOZ
Consensus base: Bitcoin Core v31 based independent chain
Proof-of-work: RandomX
Block time: 10 minutes
Difficulty retarget: 72 blocks
Initial block reward: 50 BLOZ
Halving interval: 210,000 blocks
Max supply: 21,000,000 BLOZ
Smallest unit: 1e-8 BLOZ
Mainnet address prefix: bz
Mainnet P2P port: 8210

Why RandomX?

The point of Block Zero is not to compete with industrial ASIC mining. It is to bring back a small-chain mining experience where a normal CPU can participate. RandomX is designed for general-purpose CPUs and makes the launch more accessible to hobby miners.

Run a node

Mining is important, but long-running full nodes are what make the network easier to discover, verify, and join.

Block Zero currently has two public mainnet seed nodes:

Community (https://bloz.cc) seed:
13.140.142.65:8210

WARNING: "Official" (https://bloz.org) seed:
217.160.46.61:8210
(edited, see reply #1 for more information)

If you run a node, please add both nodes to your config:

addnode=13.140.142.65:8210 (independent community)
addnode=217.160.46.61:8210 ("official", see reply #1 for more information)

If possible, keep port 8210 open so other peers can connect to you. More reachable nodes means better peer discovery, faster sync, more independent verification, and less reliance on any single server.

If you start a public node, post it in this thread so other users can add it and the network can grow.

Get involved

Independent node operators, miners, solo miners, pool operators, explorers, documentation, scripts, wallet tools, testing, and mirrors are welcome.

If you run your own pool, explorer, node, or mining setup, share it in this thread so others can verify it and join.

Thread purpose

This thread can be used for mainnet updates, releases, mining questions, pool announcements, node information, explorer mirrors, setup notes, and community infrastructure.

Block Zero is live. Mine it, run a node, verify the chain, build tools, and help make the network easier to join.
SODINNER (OP)
Newbie
*
Offline

Activity: 5
Merit: 0


View Profile
June 10, 2026, 06:36:00 PM
Last edit: June 11, 2026, 04:38:55 PM by SODINNER
 #2

Update: Independent BLOZ infrastructure (pool / explorer / wallet) + a note on project governance

A quick update for everyone following Block Zero here. I've been running my own infrastructure for BLOZ since the early testnet, and I'm continuing it independently:

- Mining pool:   https://pool.bloz.cc  - own Stratum pool
- Block explorer: https://explorer.bloz.cc
- Web wallet (client-side, keys never leave your browser): https://wallet.bloz.cc/
- Independent community Discord: https://discord.gg/z7vaB4ate

All of it unofficial, clearly labeled as third-party.

Why I'm raising this openly:

I've put time, hashrate, VPS, domains and development into this coin from the start - collaboratively, with bug reports and improvement suggestions. Unfortunately the cooperation with the creator has reached a point where I have to fairly warn newcomers about what to expect from this project:

- Consensus changes with no warning. An update was rolled out from one moment to the next that altered the chain and invalidated already-mined blocks - no announcement, no coordination with the miners who contributed the hashrate.

- Bridge fee for wBLOZ from 0% to 3.9% overnight. No prior notice. On a "fair launch" chain that's a breach of trust.

- Centralized control on a supposedly decentralized coin. Independent pools, wallets and services aren't treated as a contribution to decentralization but as competition. Anyone building their own infrastructure gets lumped in near "scam" territory and removed from the official Discord.

- "Open source" on demand. I was personally told the landing-page template was open source, "do whatever you want." Later it was retroactively declared closed - please change it.

I'm explicitly NOT saying BLOZ is a scam. The chain runs, I mine it, I keep building on it. But a single maintainer who changes consensus and fees without notice and blocks every independent contribution is exactly the central risk you should keep your eyes open for in a project like this. Decentralization means more than a coin ticker - it means no single person can rewrite the rules overnight.

I have the reasons to assume, I was treated as competition despite of my willing to help and contribute to the project, this is why I had promoted this project here in the first place.

Anyone who wants to mine along or explore the chain independently is welcome on pool.bloz.cc / explorer.bloz.cc and in the Discord. Questions, criticism, bug reports - happy to take them directly.
I am happy for any advertising if it directly serves the purpose of extending the infrastructure and eco-system of BLOZ. Anyone who loves building and contribute is welcome.
gall00tech
Newbie
*
Offline

Activity: 29
Merit: 0


View Profile
June 10, 2026, 06:53:46 PM
 #3

linux wallet show as bitcoin? Huh Huh
Laheeboo
Jr. Member
*
Offline

Activity: 87
Merit: 4


View Profile
June 11, 2026, 02:27:28 AM
 #4

I respect how on the explorer what you mine is highlighted so you are upfront about everything. giving it a try for sure!
SODINNER (OP)
Newbie
*
Offline

Activity: 5
Merit: 0


View Profile
June 12, 2026, 01:00:44 PM
 #5

In my previous reply I documented Rexemre's habit of pushing consensus changes with no warning - segwit activation height moved under our feet, the bridge fee jumped from 0 % to 3.9 % overnight, independent contributors removed from official channels as "competition".

Today (2026-06-12) the next chapter landed. Four commits. A consensus-enforced "Development & Growth Fund" that diverts up to 20 % of every block subsidy to a single hardcoded address. No ANN here. No BIP. No vote.

Activation: block 1500. Current tip: 1232. ~268 blocks left.

THE COMMITS -- https[Suspicious link removed]mre/blockzero-core/commits/main
  3cc757f9  Add Development & Growth Fund: 10% consensus minimum from block 1500
  0027227f  Dev fund: raise consensus minimum to 10 %
  6d200179  Test fixes
  82655df0  Merge devfund (10 % min, 20 % default, block 1500)

THE RULE
  From block 1500, every coinbase MUST send ≥ 10 % of the block subsidy to bz1qmv7lyweytwy807f6yq78zfvhh5ye5y2y0x2gfl, or the block is rejected with `bad-cb-devfund`. Default miner setting is 20 % -- twice the minimum. Unmodified upgraded nodes donate the full 20 %.

THE ADDRESS -- verify yourself: https://explorer.bloz.cc/address/bz1qmv7lyweytwy807f6yq78zfvhh5ye5y2y0x2gfl
  - Zero on-chain history. No prior tx. No anchor of prior custody.
  - Hardcoded as hex literal in consensus (0014db3df23b245b8877f93a203c712597bd099a1144).
  - Single ECDSA key. No multi-sig. No timelock. No governance. No revocation path. Unaccountable on misuse.

THE CAPTURE
  50 BLOZ subsidy × ~144 blocks/day:
  - 20 % default:  ~1,440 BLOZ/day → ~43,000 BLOZ/month
  - 10 % minimum:    ~720 BLOZ/day → ~21,500 BLOZ/month
  Until the next halving (block 210,000), at 20 % default, this one address would receive on the order of 2.1 million BLOZ.

This is exactly the pattern I called out in my previous reply. A coin marketed as "no premine / no presale / no team allocation" is, few days after mainnet, being silently retro-fitted with a single-key 20 % block tax - pushed at a speed that makes review impossible and on a timeline that makes opt-out impossible.

WHAT I AM DOING
  The repos at github.com/SODINNER/blockzero-core have NOT picked up the devfund commits and will not. They are pinned at 711a458e (the last consensus-relevant Rexemre commit, segwit fix to block 413) - which IS the consensus our mainnet currently runs on. Anyone who wants to keep mining the chain we actually launched should build from there.

  - Repo: https://github.com/SODINNER/blockzero-core
  - Pool that will not enforce the devfund rule: https://pool.bloz.cc
  - Explorer following the unchanged chain: https://explorer.bloz.cc

  At block 1500 the chain splits. The pool, explorer, public seed node and web wallet under bloz.cc stay on the original consensus. The Rexemre branch becomes the "Rexemre-tax" fork - whoever upgrades follows it. We don't.

WHAT YOU SHOULD DO
  - If you hold BLOZ: understand that "the project" no longer means one chain after block 1500. Pick which side you're on before exchanges/bridges do.
  - If you solo-mine: do NOT pull from Rexemre/blockzero-core after commit 711a458e (2026-06-07) without reading every diff. Pull from SODINNER/blockzero-core or pin your own fork at 711a458e.
  - If you mine on a pool: ask the operator which side they will be on at block 1500. pool.bloz.cc has answered: original consensus, no devfund.

I had hoped my previous reply would be the last one I had to write on this pattern. It isn't.

— SODINNER, operator of bloz.cc (pool, explorer, public node, web wallet, telegram bot)
gall00tech
Newbie
*
Offline

Activity: 29
Merit: 0


View Profile
June 12, 2026, 06:27:21 PM
Last edit: June 12, 2026, 07:37:47 PM by gall00tech
 #6

Def DEV is shady AF,  i saw how he was promoting the other guys pool on the discord then he says he doest not know him, then why post  his pool on the ann in the launch.

The no premine was bs,  he was mining since the day one than annouce it  days later... so no premine right?
SODINNER (OP)
Newbie
*
Offline

Activity: 5
Merit: 0


View Profile
June 12, 2026, 10:33:24 PM
Last edit: June 12, 2026, 11:12:11 PM by SODINNER
 #7

I was there in the Discord channel from very early on, so I want to explain the story from MY perspective.

I am not saying everything was bad from the start, and I also do not want to blame him for every single thing. At the beginning, the project actually looked pretty good to me.

I found the GitHub repository while I was looking for new coins where I could contribute very early and maybe get a leading position. Yes, that is selfish, but let’s be honest, everyone would love to be at the beginning of Bitcoin in 2009. That was exactly the kind of feeling BlockZero was promising.

There was a testnet, it worked, the mainnet launched at the promised time, and I was prepared. I had tested mining on testnet, I caught the mainnet start, and technically the repo and landing page were public. So at least from that side, it was not completely hidden. People had a chance to find it if they were looking.

My early involvement

In the beginning, everything was friendly.

I joined the Discord, talked a bit, contributed some ideas and started working on a pool. There was no public pool at that time. He told me he was working on his own pool too, which is totally fine.

I rented a VPS, hosted a public node and later bought the .cc domain. The creator had the .org domain.

I also asked him about the landing page and if I could host it. His answer was basically that it is open-source and everybody can do whatever he wants with it.

There were also discussions about a Bitcointalk announcement because that would bring more people in. He allowed me to do it. I prepared things, proposed independent nodes, DNS seeders, multiple contributors, more transparency and more decentralization away from one person.

I also proposed creating a Telegram community. He allowed that too, but luckily I never had the time to actually do it.

The pool

Yes, I promoted my pool a bit. I am not going to pretend I did not.

Was it selfish? Sure, in some way. I wanted the pool to grow, and I wanted to be early. But again, that was the whole point of the coin. It was marketed with this “be early like Bitcoin 2009” feeling.

At that time there was no other pool. I answered people’s questions in Discord, helped with mining issues and fixed bugs on the pool.

There was one case where a miner did not receive around 18 BLOZ because of a pool bug. I sent him 25 BLOZ as compensation and as a sorry, then fixed the bug quickly. So I was not there to scam people or steal from miners.

The first real red flag, SegWit and bech32

The first direct contact with the dev happened because of the SegWit problem.

We were all using bech32 addresses because that was what the guides recommended. But nobody had really tested normal transactions before, only mining.

When I wanted to send the missing coins to the miner, I noticed that it did not work. The Bitcoin fork still had the original Bitcoin SegWit activation height in the code, around block 481824. So in practice, the coins on bech32 addresses were not normally spendable with SegWit rules until that height.

This was a huge issue.

I contacted him and explained the problem. The chain was still very young, somewhere around block 400, so I wanted to solve it before the network got bigger.

At first I tried setting SegWitHeight to 0 because I thought that would be the cleanest solution. But that was wrong, because it invalidated the existing chain. The existing blocks were mined without the required SegWit data, so making SegWit active from block 0 made those old blocks invalid.

I noticed that quickly and then proposed a future activation instead. My suggestion was block 500.

That would have kept the existing chain valid and still given everyone a short window to update before SegWit became active. It was not some magic no-risk solution, because consensus changes always need coordination, but it would have been much cleaner than activating it retroactively or almost immediately.

When I started testing, he told me very clearly not to do anything myself because my pool had a lot of hashpower and I could fork the coin. That was fair in principle, and exactly why I contacted him instead of just pushing my own fix. But the tone was already a bit panic and angry.

Still, I stopped and let him work on it.

Then I saw commits. First it looked like he set activation to 0, which would have broken the whole existing chain. Then he changed it again, I believe to around block 413. He mined the activating block himself, but there was no proper announcement to everyone.

No clear “guys, there is a critical consensus issue, please update before block X”.

No proper coordination.

No public explanation of what happened and why everyone had to update.

He just later asked if everyone was on the latest rc9 version or something like that.

That is not how you handle a consensus-related issue, especially if you want people to trust the chain.

The bridge and wrapped coin

After that, the bridge and wrapped coin topic came up.

This was also not transparent enough in my opinion. We discussed whether it should be added to the Bitcointalk ANN, but I decided not to include it yet because I wanted him to work it out properly first.

At that point I was still trying to help. I wanted to mirror things, keep the project alive and make sure it does not depend only on one person.

Kind of funny, because later it became exactly that problem.

Where things started to change

Some time before the escalation, he publicly wrote in Discord something like:

“Be aware of risk of other websites, they have no affiliation with bloz.org, they can contain malware etc.”

I was basically the only one with such websites at that time.

I had talked with him, contributed, hosted a node, worked on a pool, discussed the ANN and asked for permission before doing things. And suddenly there was a public warning that made me look like some scammer.

Then he wrote me privately, in summary:

“I am worried about confusion with the landing page, so I will take the website away from open-source, please change your design.”

Okay, fine. I did not like it, but I could understand the concern about confusion.

Around that time I had also posted some updates about the pool. Bug fixes, improvements, payout fixes and stuff like that. I posted some of it in the mining thread and also some things in general.

So yes, I did mention the pool before. I am not going to pretend I never did. But it was not like I was spamming the Discord all day.

The important part is the timeline and the context.

There were pool-related posts in different threads before he ever warned me. One of them was in general, one was in the mining thread. Those were before the warning.

After that, he messaged me because of a pool post in general and told me to stop promoting my pool.

I said okay, no problem, I will not do it anymore.

After that warning, someone asked in the mining thread about the patched xmrig and solo mining. I answered that for solo mining you do not need xmrig, because there is a command through the full node. I told him he can look it up on GitHub and on the landing, and that the links are already in Discord.

There was no pool link in that answer.

I did not tell him to use my pool.

I did not even mention my pool in that reply.

It was just a normal answer to a mining question.

Then he sent me another screenshot from the mining thread and treated it like a last warning.

That is the part I could not understand.

Yes, there was an older pool-related message visible above in that screenshot. But that message was from before his warning.

My actual message after the warning was only about solo mining and full-node mining. No pool promotion, no pool link, nothing like that.

So either he meant my latest answer, which was clearly not pool promotion, or he meant the older pool message visible above, which makes no sense because it was before he warned me.

That is why the “multiple advertisement warnings” thing felt dishonest to me.

Warn me once, fine. Tell me you do not want pool promotion anymore, fine. I can accept that.

But do not warn me, I say okay, then answer a normal mining question without even mentioning my pool, and still treat it like a “last warning”.

The disclaimers got worse

After that I saw more disclaimers about other domains and no affiliation with the BLOZ team or project.

In one message he did not even write it generally, he specifically mentioned the .cc TLD. That was obviously my domain.

As far as I checked, there were no other similar landing pages except mine. And mine existed because I had asked him before and he had given consent while the landing was still open-source.

The disclaimers were also not neutral. They talked about malware, unfair pool payouts and similar things.

That is not just “be careful, check what you use”.

That makes someone look like a scammer.

And at that point it felt very clear to me that I was no longer seen as a contributor, but as competition.

The ban

So I wrote him and asked what his problem is. I asked if he wants to do everything alone, why he is making these accusations and why he is acting like this.

Then he banned me from the Discord.

Just like that.

After that he sent me a message that looked very ChatGPT generated. It was something like “I assume you are out of the project, but this is not about control, this is about transparency, no source code...” and so on.

Some of his points are not completely wrong. For example, yes, I could have open-sourced more parts faster. Fair enough.

But he could have just said that normally.

Also, he talks about pool transparency, but I do not see his pool being open-source either.

He also used the advertisement thing again, but again, he warned me one time and then retroactively used older messages from before the warning as “multiple warnings”.

That is just not honest.

He said I could join again if I want to, but honestly, after getting banned and then receiving some generated corporate-style message instead of a real answer, no thanks.

What happened after

And then things got even worse.

The bridge fee was raised to 3.9 percent.

The landing page was removed from the public repos after it was previously open-source and after I was told everybody could do whatever they want with it.

Then he implemented a dev fund of 20 percent, with a minimum of 10 percent of every block from block 1500.

For me, that is too much. Way too much.

You cannot sell a project with this early Bitcoin 2009 feeling, no premine, community, fair start, decentralization, and then suddenly add 10 to 20 percent of every block to a dev fund.

I am not giving away 10 to 20 percent of each block to one dev like that. For me this is where it crosses the line.

Why I am out

So this is why I am out.

I do not know how the fork will go. I do not know if anyone will stay with this version, if it has a future, or if the community even wants to continue this work.

I personally like the coin idea. I like RandomX. I saw potential in it.

But not with this kind of control, not with this communication, and not with this dev fund.

I learned a lot while working on this project. I hope I explained the story as clearly and honestly as I can. Maybe the order of a few small things is not perfect because a lot happened in Discord and I no longer have access to the channel, but the important part is accurate from my perspective.

I am frustrated because I really wanted this to become something good.

But I do not want to waste time on a pump and dump or just another shitcoin fork. If I continue with something, I want it to solve real problems, have some technical innovation, be transparent and actually be useful.

I will watch the project for a few more days and then decide if it makes sense to continue this work in some form, or if it is better to focus on building a proper coin from scratch.

Everyone can choose his side. I will not continue commenting on every action from the original dev.

Thanks folks.

P.S. Yes, I also used ChatGPT for formatting help, however I asked to keep the style and fix gramatics.

P.S.S. Actually I was writing this to answer to this message, as it was the trigger for this:
Def DEV is shady AF,  i saw how he was promoting the other guys pool on the discord then he says he doest not know him, then why post  his pool on the ann in the launch.

The no premine was bs,  he was mining since the day one than annouce it  days later... so no premine right?

I am not sure what exactly is meaned by the pool in the ann in the launch, as I didn't catch the moment, as far I know there was not a single link of mine in the announcements, not as mirror, not as something else or additional resources.
I was promoting in some way my pool, yeah, providing updates with the fixed bugs and improvements, answering questions how to mine etc.
If you mean that by promoting, then it was probably just me. If something else, then sorry, had not enough context to answer.

I just wanted to state, yeah, the DEV is shady, but not because of the premine thing. I mean you couldn't do really much wrong at the beginning. I mean yeah, you could test if the transactions even work, but this is nothing that should be critized. We were enough people there and nobody checked that properly, not even in testnet.

Let's not blame everything just for the reason of it.
There are things to critize, but focus on the real ones.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!