Subject: [ANN][MNR] Emergency Difficulty Fix for Blockle Chain – Hard Fork @ Block 29000

Hello Blockle community,

We experienced an unexpected stall in block production at height 29000 due to a flaw in our original Bitcoin-style difficulty adjustment code. Here’s what happened and how we resolved it:
   1.   Issue Detected
   •   At block 29000, our 2016-block retarget algorithm encountered a division-by-zero error because the measured timespan dropped to zero.
   •   This prevented the creation of any further valid block templates, halting block production.
   2.   Immediate Action Taken
   •   We instructed all nodes to invalidate the bad block 29000 and roll back to 28999.
   •   Mining was briefly resumed, but the underlying algorithm remained broken.
   3.   Permanent Fix: Dark Gravity Wave v3
   •   We implemented Dark Gravity Wave (DGW) v3, a per-block retarget algorithm proven in fast-block networks, as a hard fork.
   •   DGW was activated at block 29000 to take over difficulty calculations and prevent future stalls.
   4.   Deployment & Update
   •   All full-node and mining-pool operators must upgrade to the new client before or at block 29000 to stay in consensus.
   •   New binaries and source code are available here: https://github.com/Blocklechain/blockle (branch main, tagged v1.0.1-dgw)
   •   Instructions for upgrading and rebuilding nodes can be found in the repo’s README.
   5.   What This Means for Users
   •   Your funds are safe. No past transactions or balances were altered. The hard fork only changes how difficulty is calculated going forward.
   •   Block production has resumed immediately under DGW, and blocks should now appear every ~15 seconds as intended.

We apologize for the inconvenience and thank everyone who helped diagnose and test the fix. Please upgrade your node at your earliest convenience and report any issues in this thread or on our Discord.

— Alexander Lehman, Founder & Lead Developer of Blockle

We’re excited to announce that Blockle (BLK) is officially listed on NonKYC!
You can now trade BLK/USDT and BLK/USDC pairs with zero KYC requirements.

Why this matters:
Blockle is a fast, SHA-256-based Proof-of-Work cryptocurrency with 15-second blocks and a focus on transparency, fairness, and decentralization from day one.

Links:
   •   Trade now: https://nonkyc.io
   •   Website: https://blockle.org
   •   Telegram: https://t.me/blockleofficial
   •   Explorer: https://explorer.blockle.org

This is just the beginning — more listings, tools, and integrations are on the way. Stay tuned!

[ANN] Blockle Paid for Exchange Listing – NonKYC Listing Confirmed!

We’re excited to announce that Blockle has officially paid the listing fee for a launch on NonKYC.io!

This means Blockle will soon be available for open trading on a decentralized-friendly exchange with no KYC requirements – making it easier for the community to access and trade BLK worldwide.

Why this matters:
   •   Easy access for all users without identity checks
   •   Supports our mission of keeping Blockle open, fast, and grassroots
   •   Expands visibility and liquidity for BLK

Stay tuned for the official live listing announcement – we’re one step closer to a thriving ecosystem.

Follow updates:
   •   Telegram: t.me/blockleofficial
   •   Explorer: https://explorer.blockle.org
   •   Website: https://blockle.org

Thank you to the miners, holders, and believers helping us build this from the ground up. Let’s go!

— Blockle Team

I’ll do another code review but this wasn’t me. I suggest checking if anyone has had similar problems with palladium’s code base since were forked from them. https://github.com/NotRin7/Palladium

We are a fork of palladium not sure what you’re talking about but I’m sorry to hear you lost exodus wallet funds wasn’t me tho

[ANN] Blockle v2 Relaunch – New Chain Live as of May 3, 2025!

Greetings everyone,

I’m excited to announce that **Blockle** has officially relaunched its blockchain! After careful development and testing, we’ve rolled out a brand-new network (“v2 fork”) with the following highlights:

[ul]

• Live Date: May 3, 2025 (fork at Block 30) 
  
• Block Time: 15 seconds 
  
• Difficulty Retarget: Every 120 blocks (~30 minutes) for smoother adjustments 
  
• Total Supply: 21 000 000 BLK 
  
• Premine: None – truly fair launch! 
  
• Consensus: SHA-256 Proof-of-Work 
  [/ul]
  
  

  ---

  
  Visit the official resources:
  
  [ul]
  
• GitHub Repository & Releases 
  
• Live Explorer 
  
• Pre-built Binaries 
  
• Website & Documentation 
  [/ul]
  
  

  ---

  
  ## Why Blockle?
  
  Blockle was designed to be the **slowest Fair Launch** in crypto, giving everyone an equal shot. With faster blocks (15 s) and a 30-minute retarget window, you’ll experience:
  
  [ul]
  
• Low orphan rates and predictable confirmations 
• Stable difficulty adjustments that resist hash-rate whipping 
• A truly decentralized, permissionless mining environment 
[/ul]

## Getting Started

1. **Download Binaries** (no build required): 
   `curl -L

https://github.com/Blocklechain/binaries/blockle-binaries.tar.gz -o blockle-binaries.tar.gz` 
   `tar -xzf blockle-binaries.tar.gz && cd blockle-binaries`

2. **Run a Node**: 
   `./blockled -daemon`

3. **Check Sync Status**: 
   `./blockle-cli getblockchaininfo`

4. **GUI Wallet**: 
   Launch `blockle-qt` from the same folder.

Your first 101 generated blocks will mature in ~25 minutes—mine them to an address of your choice:

```bash
ADDR=$(./blockle-cli getnewaddress)
./blockle-cli generatetoaddress 101 $ADDR

[size=150]Blockle (BLK) v2 Relaunch – Chain Rebuild & Hard-Fork on May 3, 2025[/size]

Greetings Blockle Community,

After extensive testing and feedback, we are pleased to announce a complete rebuild of the Blockle blockchain (v2), scheduled to activate on **May 3, 2025**. This re-launch will usher in improved security, a streamlined difficulty adjustment, and our long-awaited DigiShield-style retarget at block 30.

-------------------------------------------------------------------------------

[size=120]⏰ Hard-Fork Activation[/size]
• **Date:** Saturday, May 3, 2025 
• **Block:** 30 (v2 genesis will reset, old chain will be deprecated) 

-------------------------------------------------------------------------------

[size=120]🎯 Why v2?[/size]
• **Full Chain Rebuild** – Resolve accumulated inconsistencies and support our new consensus tweaks 
• **Dynamic Difficulty** – DigiShield-inspired smoothing for more stable block times 
• **Future-Proof** – Simplified parameters ready for upcoming features (segwit, version bits) 

-------------------------------------------------------------------------------

[size=120]⚙️ Upgrade Instructions[/size]

• Download the v2.0 binaries from GitHub: 
     https://github.com/Blocklechain/blockle/releases
  
  
• Stop your node/wallet before May 3 
  
• Replace your executables with the new v2 ones 
  
• Clear your data directory (or re-index) to start from the new genesis 
  
• Launch the v2 node and let it sync from block 0 (fast sync recommended) 
  

-------------------------------------------------------------------------------

[size=120]📚 Resources[/size]

•   Official website: https://blockle.org 
  
•   Whitepaper & spec: blockle.org/whitepaper.html 
  
•   Explorer (v2 soon): explorer.blockle.org 
  
•   Public Pool: stratum+tcp://pool.blockle.org:3333 
•   GitHub repo: github.com/Blocklechain/blockle 
  

-------------------------------------------------------------------------------

[size=120]🙌 Thank You & Support[/size] 
We appreciate everyone who’s tested v2 on testnet and provided feedback. Please report any issues on our GitHub Issues page or join our Discord for real-time support:

[uid=discord]https://discord.gg/blockle[/uid] 

Together, let’s make Blockle the most robust¹ fair-launch coin of 2025!

— The Blockle Core Developers 
[small]¹ Robustness guaranteed by DigiShield retarget, clean state, and active community oversight.[/small]

New wallet is up!

Heya I need to compile and upload the new wallet please give me a few hours the fork just happened

Updated fork to block 19

[ANN] Blockle v1.1 “DigiShield Fork” Live at Block 30 – GitHub Upgrade Instructions

Hello everyone!

We’re pleased to announce Blockle v1.1, which activates a per‑block difficulty retarget (DigiShield) at block 30. This dramatically smooths out block times and keeps us at our 15 s target even as miners join or leave.

⸻

Key Changes

[]

Fork Height: 30 – At block 30 all nodes switch from the legacy 2016‑block retarget to per‑block DigiShield.
[]Averaging Window: 60 blocks (~15 min)
[]Max Adjustment: ±30% per block
[]Target Spacing: 15 s
[/list]

Why DigiShield?

[]Faster reaction to hashpower swings (minutes, not days)
[]Smoother difficulty curve under ASICs

• Closer adherence to 15 s block time

⸻

Upgrade via GitHub
Simply pull the latest code, rebuild, and restart—no manual edits required.


Check your logs around block 30 for:

⸻

If you encounter any issues, please open an issue on GitHub or post below. Thank you to everyone who tested on testnet and submitted feedback!

Happy mining,
— The Blockle Dev Team

We’re happy to announce our new Blockle pool:

• Stratum: stratum+tcp://pool.blockle.org:3333
• Web UI: https://pool.blockle.org/
• Fee: 1.5%

Features include PPLNS & SOLO, VarDiff, HTTPS-secured UI/API, and full JSON API for custom dashboards.

To start mining, point your miner to:

stratum+tcp://pool.blockle.org:3333 
Username: YourBlockleAddress 
Password: x 

Visit the Web UI for live stats and block history: pool.blockle.org

Happy mining!
— The Blockle Team

Heads-Up for Blockle Pool Setups: Don’t Use Native SegWit (blk1…) Addresses Directly

Blockle wallets today default to giving you a native SegWit Bech32 address (e.g.

blk1q3g8gd7y9k09ew0fxe59ht0ayye73cqjn7ahvxe

). Unfortunately, many pool back-ends (block-notify scripts, payment processors, Stratum implementations) still only recognize “wrapped” P2SH-SegWit addresses.

⸻

The problem
   •   Native SegWit (blk1…) may be seen as “invalid address” by your pool software
   •   Payouts silently fail or RPC calls error out
   •   Web UI address validation rejects your wallet

The quick fix
   1.   Generate a P2SH-SegWit address in your Blockle wallet

blockle-cli getnewaddress "" "p2sh-segwit"

That will give you an address starting with “3…” (or whatever your P2SH prefix is).

   2.   Use that P2SH-SegWit address in your pool config
In your serverconfig.php or config.json, set:

$config['payout_address'] = '3YourP2SHSegWitAddressHere';

instead of the blk1… address.

   3.   Test it via RPC before restarting your pool:

blockle-cli validateaddress 3YourP2SHSegWitAddressHere

Ensure it returns "isvalid": true.

   4.   Restart your pool services so they pick up the new address.

⸻

Why this matters
   •   P2SH-SegWit gives you the lower fees of SegWit (transactions still spend to a SegWit output)
   •   Keeps compatibility with existing pool daemons and notify scripts
   •   No need to patch dozens of Node.js, PHP or C scripts to support Bech32 yet

Once your pool is running smoothly with the P2SH-SegWit address, you can plan a full SegWit-capable upgrade later. But in the meantime, this simple switch will avoid the “invalid address” and payout errors that trip up most Blockle pool operators.

lol I see the irony

No problem!

Hi there, thanks for the very detailed write-up and for helping us shake out these edge cases! A few things to clarify:

⸻

1) Why no new mainnet blocks?

Right now the only miners on mainnet are whoever runs external hashing hardware or pools—you won’t see your single-CPU attempts actually find a block at real-world difficulty (it’s astronomically unlikely). Until someone spins up a pool or runs enough hashpower, the chain will “stall” at block 2. That’s expected for a brand-new PoW network.

⸻

2) The console RPCs on Windows v1.3.0
   •   setgenerate was removed upstream in Bitcoin Core v0.21 (and we inherited that change).
   •   generatetoaddress on our mainnet build effectively becomes a no-op (it returns [] immediately) because block-on-demand is only enabled in RegTest mode. The fact that you see CreateNewBlock() in the log simply means the node built a template—it didn’t actually spin up a real hashing loop or solve the PoW.

TL;DR:
   •   On mainnet/testnet you must use an external miner (or pool) speaking the getblocktemplate / submitblock RPCs.
   •   On regtest, generatetoaddress N <addr> still works instantly (because difficulty is trivial).

⸻

3) How to CPU mine on mainnet/testnet
   1.   Point a miner (e.g. cgminer, cpuminer-opt, etc.) at your node’s RPC port:

miner --url http://rpcuser:rpcpass@127.0.0.1:9332 --user rpcuser --pass rpcpass 


   2.   The miner will internally call getblocktemplate, do the work, then call submitblock when it finds a solution.

If you just want to experiment locally, you can start your node in regtest mode:

blockled -regtest
blockle-cli -regtest generatetoaddress 10 <your-regtest-address>

That will mine 10 blocks instantly.

⸻

Bottom line: what you saw in v1.3 on Windows is working as upstream-designed—there is no built-in CPU miner on mainnet, and generatetoaddress only really “mines” in regtest mode. I hope that clears things up, and thanks again for testing!

https://blockle.org

Welcome to the Blockle launch announcement! Blockle is a new SHA-256 coin derived from Bitcoin Core, customized for ultra-fast confirmations, a transparent emission schedule, and miner-friendly Proof-of-Work.

⸻

🌟 Key Features
   •   SHA-256 Security – Battle-tested PoW algorithm shared with Bitcoin.
   •   15 Second Blocks – Lightning-fast block times for near-instant confirmations.
   •   Per-Block Retarget – Difficulty adjusts on every block to follow hash-rate swings in real time.
   •   20 000 000 Premine – One-time allocation to bootstrap ecosystem development.
   •   1000 BLK Block Reward – Initial subsidy of 1000 BLK per block, smoothly decaying via halvings.
   •   Fixed Supply – 1 000 000 000 BLK maximum, halving every 500 000 blocks (~90 days).

⸻

📊 Network Parameters

Property   Value
Algorithm   SHA-256
Block Time   15 seconds
Difficulty Retarget   Every block
Premine   20 000 000 BLK (2 % of max supply)
Initial Block Reward   1000 BLK
Halving Interval   500 000 blocks (~90 days)
Total Supply Cap   1 000 000 000 BLK
Genesis Timestamp   2025-04-29 00:00 UTC
Genesis Hash   000001a4be420fc42744d0ea40b4b90ae07d14379ee98acc0836952d0818a865
Merkle Root   e98678b8040e9c4e9dc9af078ef864e26681d8d52f9cdba2a48ea3eca0477d07
Message Start   0xb1 0x0c 0x4b 0x1e
P2P Port   15151
RPC Port   15150
Seed Node   144.126.133.21:15151
Address Prefixes   P2PKH: 55 (“L…”), P2SH: 5 (“3…”), WIF: 128
Bech32 HRP   blk



⸻

🛠 Getting Started

# Clone & build
git clone https://github.com/Blocklechain/blockle.git
cd blockle
./autogen.sh
./configure --with-gui=qt5 --disable-tests --disable-bench
make -j$(nproc)

# Launch daemon
blockled -daemon
blockle-cli getblockchaininfo

# Generate an address
blockle-cli getnewaddress

# (Regtest) Mine 1 block
blockle-cli -regtest generate 1



⸻

🚀 Roadmap

Q2 2025   Q3 2025   Q4 2025 & Beyond
• Mainnet launch   • Official block explorer   • Mobile/light client releases
• Core GUI & CLI v1.0   • Mining pool integrations   • Lightning-network R&D
• Community mining event   • Merchant payment plugins   • Hardware-wallet support



⸻

🤝 Join the Community
   •   GitHub: https://github.com/Blocklechain/blockle
   •   Docs: https://docs.blockle.org
   •   Telegram: https://t.me/blockleofficial

Blockle is a fair-launch project with a one-time 20 000 000 premine for development, and 1000 BLK per block thereafter. Difficulty retargets every block for maximum responsiveness. With 15 second blocks and a predictable emission, Blockle is engineered for real-world use and genuine Proof-of-Work security.

Welcome aboard — let’s build a faster, fairer SHA-256 future!

— Alexander Lehman & the Blockle Core Team