[ANN] Scorbits (SCO) — SHA-256 PoW — CPU Mining — Open Source

[Yousse]

SCORBITS (SCO)
SHA-256 Proof of Work — Independent Blockchain — Open Source
"Resistance of time as proof of trust"

What is Scorbits?

Scorbits (SCO) is an independent SHA-256 Proof of Work cryptocurrency. Fully open source, CPU-minable, and built without shortcuts. No ICO. No venture capital. No artificial pumps. The code is public, the blockchain is auditable, and anyone can participate — as a miner, a node operator, or a contributor.

Launch — Today

Scorbits is built from scratch. Every line of code, every parameter, every design decision was made with one goal: build something that lasts. There is no pre-mined advantage for insiders, no early access for investors, no hidden allocation. The blockchain launches today, and every participant starts from the same point — the first block is waiting to be mined. Not by us. By you.

There is no shortage of projects that chase attention and disappear within months. Scorbits is built for the opposite — a network designed to grow slowly, honestly, and to still be running in ten years. Its value will not come from hype. It will come from the people who choose to build it with us, block by block.

Technical Specifications

Parameter	Value
Algorithm	SHA-256 (Proof of Work)
Max supply	99,000,000 SCO
Block reward	11 SCO
Block time	~3 minutes
Halving interval	Every 840,000 blocks
Difficulty adjustment	Every 5 blocks
Transaction fee	0.1% to Treasury
Premine	11,000,000 SCO (11.1%) — development and infrastructure

Links

Website | Whitepaper EN | Whitepaper FR | GitHub


How to mine

Download the miner at scorbits.com/mine — available for Windows, Linux and macOS. No configuration needed, just enter your SCO address and start mining immediately.

SHA-256 ASIC miners can connect via any community Stratum pool compatible with the Scorbits network.


Roadmap

Stage	Objective	Status
Launch	Blockchain, CPU mining, explorer, wallet, community space	Completed
Phase 2	External nodes, P2P network, direct SCO purchase	In progress
Phase 3	First exchange listing	Planned
Phase 4	ASIC support, community Stratum pools	Planned

Scorbits (SCO) — SHA-256 Proof of Work — scorbits.com — info@scorbits.com

[Yousse]

[Development Update — Launch Day Report]

Scorbits launched yesterday. Here is a full transparent report of what happened and what was fixed.


Issue #1 — Miner sync
The CLI miner was not automatically switching to the next block when another miner found one first. Fixed: the miner now polls the server every 3 seconds and switches immediately.


Issue #2 — Difficulty not updating
Manual difficulty changes via the JSON file were not reflected in memory after restart. Fixed: a secure admin route now updates difficulty directly in memory without restarting the service.


Issue #3 — P2P validation flaw (critical)
A miner was submitting blocks through the P2P protocol with insufficient difficulty, bypassing the HTTP validation layer. The P2P node was not verifying difficulty at all. Fixed: the node now strictly validates that every block hash meets the current network difficulty before acceptance. Blocks that do not comply are rejected immediately and logged.


Issue #4 — Anti-spike bypass
The anti-spike relied on the miner's submitted timestamp instead of the server's real clock, allowing it to be bypassed. Fixed: the server now uses its own clock exclusively.
Current state


Network is stable. Difficulty is managed in real time. All attack vectors identified during launch have been patched. The full fix history is visible on GitHub.
We thank everyone who stayed through this rough start. This is what open source looks like — imperfect at launch, stronger every hour.
— Scorbits Team

[Yousse]

[Official Announcement — Scorbits Hard Fork Plan]




What is a Hard Fork?

A hard fork is a fundamental change to the blockchain protocol that is not backward compatible. All nodes and miners must upgrade to the new version at a specific block height. Blocks mined before the fork remain valid — only new blocks follow the new rules.

Why a Hard Fork is Necessary

The current Scorbits hash function uses a custom string-based SHA-256 format:
SHA256(index + timestamp + transactions + previousHash + nonce + minerAddress)
While functional and secure, this format is incompatible with standard ASIC firmware and the Stratum mining protocol used by professional hardware (Antminer, Whatsminer, etc.). These devices require the Bitcoin-standard 80-byte block header format:
SHA256d(version + previousHash + merkleRoot + timestamp + bits + nonce)
This incompatibility means that regardless of how many Stratum pools are created, no standard ASIC will ever be able to mine Scorbits in its current form. To unlock ASIC mining and full Stratum compatibility, a protocol-level change is required.

What Will Change After the Hard Fork

Hash function: custom string SHA-256 → standard SHA256d (double SHA-256 on 80-byte header)
Block header: adds version field, merkleRoot for transactions
Difficulty encoding: string-based zero prefix → standard compact bits format (like Bitcoin)
Stratum compatibility: full support for standard ASIC firmware
All existing parameters remain unchanged: 11 SCO reward, 840,000 block halving, 99M max supply, 3-minute target, 0.1% fees


What Will NOT Change

All balances and wallet addresses remain valid
All SCO already mined remain in holders' wallets
The blockchain history (all blocks before the fork) remains intact and visible
The project name, ticker, supply, and economic model stay identical


Consequences for Current Miners

CPU miners using the current CLI must download the updated miner after the fork
The new miner will be available on scorbits.com/mine before the fork date
Mining after the fork with the old miner will result in rejected blocks
A transition period will be announced with clear instructions


Consequences for Node Operators

All nodes must upgrade to the new version before the fork block
Updated node binaries will be available on scorbits.com/mine
Nodes running the old version after the fork will be on a separate incompatible chain


Timeline
MilestoneTargetHard fork development4-6 weeksPublic testnet2 weeks of testingCommunity announcement2 weeks before forkFork blockBlock #10,000 (estimated)Updated miners and nodes available1 week before fork
Block #10,000 is estimated to be reached in approximately 5-6 weeks at the current block rate of ~3 minutes per block.

What This Means for the Community

The hard fork is not a sign of weakness — it is a sign of a project that listens, evolves, and builds seriously. Bitcoin itself has undergone multiple protocol changes. The difference between a project that survives and one that disappears is the willingness to make hard decisions for the long-term health of the network.
After the fork, Scorbits will be fully compatible with standard SHA-256 ASIC hardware. Any Antminer or compatible device will be able to connect via a Stratum pool and mine SCO. This opens the network to a much larger mining community and significantly increases network security.

What You Should Do Now

Continue mining normally — nothing changes until block #10,000
Keep your wallet address — it will remain valid after the fork
Follow official announcements on scorbits.com, Bitcointalk, and @Scorbits_SCO on Twitter
If you run a node, watch for the updated node release before the fork


Open Source
All hard fork development will be done publicly on GitHub (github.com/Scorbits/scorbits). The community is welcome to review, test, and contribute.

Scorbits (SCO) — Proof of Work — Resistance of time as proof of trust — 2026
scorbits.com | info@scorbits.com

[Yousse]

[ANN] Official Scorbits Mining Pool — Now Live

The official Scorbits (SCO) Stratum pool is now available to all miners.

-- Connection --
Stratum    : stratum+tcp://pool.scorbits.com:3333
Port       : 3333
Username   : YOUR_SCO_ADDRESS.worker_name
Password   : x

-- Details --
Pool fee   : 2%
Payout     : automatic every 12 hours
Minimum    : 1 SCO
Algorithm  : SHA-256 CPU mining
Stats      : scorbits.com/pool

-- How to mine --
1. Download the Scorbits miner from scorbits.com/mine
2. Run : scorbits-miner-windows.exe --address YOUR_SCO_ADDRESS --pool stratum+tcp://pool.scorbits.com:3333 --threads 4
3. Monitor your stats and balance at scorbits.com/pool

The pool is open to all CPU miners. Rewards are distributed proportionally based on shares submitted.

scorbits.com | info@scorbits.com | @Scorbits_SCO

[Bambalam]

a centralized web app with no peer to peer connectivity... This is not a cryptocurrency.

There is only one way to mine this: via their website and their pool. Local nodes cant connect, community contributions cannot be developed.

[Yousse]

Project Update — April 15, 2026

It has been 3 days since the announcement of Scorbits (SCO), and we want to be fully transparent with the community about what has happened since launch.

Within the first 48 hours, the network faced multiple coordinated attacks from malicious actors attempting to destabilize the blockchain and exploit early vulnerabilities. These included attempts to manipulate the chain, inject fraudulent transactions, and disrupt mining operations.

We identified and responded to each attack rapidly. Security patches were deployed in real time, the network was secured, and the chain integrity was preserved. No funds were permanently lost. Every incident was fully resolved.

Despite these challenges, our miners never stopped. The network kept running, blocks kept being mined, and the community stayed active. That resilience is exactly what Scorbits is built on.

On the technical side, we have released two native miners for the community:

- Go Miner — available for Windows, Linux and macOS
- C Miner — available for Windows and Linux (~80% faster than the Go miner)

Performance depends on your CPU and the number of threads you allocate.
Both support solo mining and pool mining via stratum+tcp://pool.scorbits.com:3333.
Download available at: https://scorbits.com/mine

Every decision we make is oriented toward one goal: a fully decentralized, secure, and tamper-proof network that stands the test of time. The attacks we faced only reinforced that commitment. We are not stopping.

More updates to come.

[Yousse]

a centralized web app with no peer to peer connectivity... This is not a cryptocurrency.

There is only one way to mine this: via their website and their pool. Local nodes cant connect, community contributions cannot be developed.

Thank you for the feedback, it is a fair point and deserves a straight answer.

The P2P layer exists and is functional. Nodes communicate over TCP and the CLI miner operates fully independently from the website in both solo and pool mode. The source code is open on GitHub.

However, you are correct that external P2P connectivity is currently restricted. Port 3000 is closed to the public while we stabilize the network. We launched 3 days ago and spent the first 48 hours dealing with coordinated attacks targeting the chain. Opening the P2P port to the public before the network was hardened would have been irresponsible.

This is an early stage project. Full decentralization, open node connectivity, and community contributions are on the roadmap and will be progressively opened as the network matures and proves its stability.

We are not claiming this is finished. We are building it in the open and being transparent about where we are.

[Bambalam]

a centralized web app with no peer to peer connectivity... This is not a cryptocurrency.

There is only one way to mine this: via their website and their pool. Local nodes cant connect, community contributions cannot be developed.

Thank you for the feedback, it is a fair point and deserves a straight answer.

The P2P layer exists and is functional. Nodes communicate over TCP and the CLI miner operates fully independently from the website in both solo and pool mode. The source code is open on GitHub.

However, you are correct that external P2P connectivity is currently restricted. Port 3000 is closed to the public while we stabilize the network. We launched 3 days ago and spent the first 48 hours dealing with coordinated attacks targeting the chain. Opening the P2P port to the public before the network was hardened would have been irresponsible.

This is an early stage project. Full decentralization, open node connectivity, and community contributions are on the roadmap and will be progressively opened as the network matures and proves its stability.

We are not claiming this is finished. We are building it in the open and being transparent about where we are.

And your saying your on mainnet? These are testnet things man. You dont want to interrupt real miners if you are actively developing on mainnet and changing things that effect consensus. Stuff gets messy real fast, but i get that your using this project to learn about blockchain. If you would like some help or guidance, feel free to reach out in DM or join the Fairchain discord.

[Yousse]

a centralized web app with no peer to peer connectivity... This is not a cryptocurrency.

There is only one way to mine this: via their website and their pool. Local nodes cant connect, community contributions cannot be developed.

Thank you for the feedback, it is a fair point and deserves a straight answer.

The P2P layer exists and is functional. Nodes communicate over TCP and the CLI miner operates fully independently from the website in both solo and pool mode. The source code is open on GitHub.

However, you are correct that external P2P connectivity is currently restricted. Port 3000 is closed to the public while we stabilize the network. We launched 3 days ago and spent the first 48 hours dealing with coordinated attacks targeting the chain. Opening the P2P port to the public before the network was hardened would have been irresponsible.

This is an early stage project. Full decentralization, open node connectivity, and community contributions are on the roadmap and will be progressively opened as the network matures and proves its stability.

We are not claiming this is finished. We are building it in the open and being transparent about where we are.

And your saying your on mainnet? These are testnet things man. You dont want to interrupt real miners if you are actively developing on mainnet and changing things that effect consensus. Stuff gets messy real fast, but i get that your using this project to learn about blockchain. If you would like some help or guidance, feel free to reach out in DM or join the Fairchain discord.

This is mainnet. The changes made in the first 48 hours were emergency security patches in response to coordinated attacks targeting the chain — not experimental development. Patching under attack is a reality every network faces at launch.

The other adjustments reflect the natural instability of a brand new project built without funding, without backing, and without connections in the crypto space. No VC, no launchpad, no insider support. That means fast adaptation, hands-on support, and making decisions in real time to keep the network alive and give the community room to grow.

We have not lost sight of the goal — full decentralization, open node connectivity, and a network that stands on its own. We are just being honest about where we are on that path.

Your point on consensus stability is valid and appreciated.

[Yousse]

Scorbits Miner v2.0 — Multi-threading fully optimized

We have just deployed a major update to the official Scorbits miner.

The previous version had a concurrency issue in the mining loop — all goroutines were competing for the same memory allocations on every single hash, causing Go's garbage collector to trigger frequent stop-the-world pauses that froze all threads simultaneously. The more threads you ran, the worse the scaling got.

What changed in v2.0 :

- Hash input is now pre-computed outside the hot loop. Only the nonce changes per iteration, eliminating redundant string allocations on every hash.
- Timestamp is cached and refreshed every 1024 iterations instead of being called on every single hash.
- Stop-check is batched every 1024 iterations instead of hitting a live channel on every hash.
- Raw byte target comparison replaces hex string encoding on every hash — hex encoding now only happens on a successful find.

The result is near-linear scaling with thread count. On a 4-core machine, 4 threads now deliver close to 4x the hashrate of a single thread. The bottleneck is now your hardware, not the code.

For multi-socket servers (dual EPYC etc.), the recommended approach is to run one miner instance per NUMA node pinned with numactl to avoid inter-socket memory traffic.

Download the new binaries (Windows / Linux / macOS) at scorbits.com/mine

Feedback and benchmark results are welcome.