[ANN] Blockle (BLK) – SHA-256, 15-Second Blocks, 1 000 000 000 Supply, 20 000 00

[Blockle]

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
   •   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

[Drawesome]

Hello Blockle team (OP) and community,

Thanks for the announcement, the project looks interesting. I've been testing Blockle shortly after launch using the pre-compiled Windows wallet (version v1.3.0.0-g7ff64311...) available from the Blocklechain/Windows-Wallet GitHub repository, running on Windows 10 x64.

I wanted to share my initial experience, especially regarding attempts at CPU mining, in case it's helpful as feedback or for other users:

1. Sync and Network Status:
The wallet synced quickly to block 2, which matches the official explorer found at https://explorer.blockle.org/ . However, both my node and the explorer seem to indicate that the last block (block #2) was mined quite some time ago (over 17 hours at the time of my testing). My node successfully connects to peers (I had 2 active connections), and the debug.log file shows messages like 'Potential stale tip detected', indicating it's aware of the lack of new blocks.

2. CPU Mining Attempt (Console):
I attempted to mine using the CPU via the Debug Console within the blockle-qt.exe wallet:

• Generating a receiving address worked correctly after restarting the wallet.
• I encrypted the wallet for security.
• Executing

Code:

generatetoaddress 1 "my_blk1_address..."

while the wallet was locked returned

Code:

[ ]

immediately.

• I unlocked the wallet using
  Code:

  walletpassphrase

  (it returned
  Code:

  null

  , indicating success).
  
• Executing
  Code:

  generatetoaddress 1 "my_blk1_address..."

  again with the wallet unlocked also returned
  Code:

  [ ]

  immediately.
  
• Interestingly, checking the debug.log shows a
  Code:

  CreateNewBlock()

  entry matching the exact time of this second attempt[/b], suggesting the node does prepare the block template, but the RPC command fails or terminates before initiating the mining process.
  
• I tried the alternative command
  Code:

  setgenerate true 1

  , but it returned the error
  Code:

  Method not found (code -32601)

  , indicating this command has been removed in this version.
  
  
  Conclusion:
  Based on these tests, it appears that CPU mining using the built-in console commands (
  Code:

  generatetoaddress

  ,
  Code:

  setgenerate

  ) is not functioning correctly in the Windows v1.3.0 build.
  Code:

  generatetoaddress

  seems buggy (fails returning
  Code:

  [ ]

  even though the log shows
  Code:

  CreateNewBlock

  is executed), and
  Code:

  setgenerate

  no longer exists.
  
  Additionally, the observation that the main network seems stalled at block 2 for many hours is also worth noting.
  
  I hope this detailed information is helpful to the team and community. Is this a known issue with the Windows build or the
  Code:

  generatetoaddress

  command?
  
  Regards and best of luck with the Blockle project.

[Blockle]

Hello Blockle team (OP) and community,

Thanks for the announcement, the project looks interesting. I've been testing Blockle shortly after launch using the pre-compiled Windows wallet (version v1.3.0.0-g7ff64311...) available from the Blocklechain/Windows-Wallet GitHub repository, running on Windows 10 x64.

I wanted to share my initial experience, especially regarding attempts at CPU mining, in case it's helpful as feedback or for other users:

1. Sync and Network Status:
The wallet synced quickly to block 2, which matches the official explorer found at https://explorer.blockle.org/ . However, both my node and the explorer seem to indicate that the last block (block #2) was mined quite some time ago (over 17 hours at the time of my testing). My node successfully connects to peers (I had 2 active connections), and the debug.log file shows messages like 'Potential stale tip detected', indicating it's aware of the lack of new blocks.

2. CPU Mining Attempt (Console):
I attempted to mine using the CPU via the Debug Console within the blockle-qt.exe wallet:

• Generating a receiving address worked correctly after restarting the wallet.
• I encrypted the wallet for security.
• Executing

Code:

generatetoaddress 1 "my_blk1_address..."

while the wallet was locked returned

Code:

[ ]

immediately.

• I unlocked the wallet using
  Code:

  walletpassphrase

  (it returned
  Code:

  null

  , indicating success).
  
• Executing
  Code:

  generatetoaddress 1 "my_blk1_address..."

  again with the wallet unlocked also returned
  Code:

  [ ]

  immediately.
  
• Interestingly, checking the debug.log shows a
  Code:

  CreateNewBlock()

  entry matching the exact time of this second attempt[/b], suggesting the node does prepare the block template, but the RPC command fails or terminates before initiating the mining process.
  
• I tried the alternative command
  Code:

  setgenerate true 1

  , but it returned the error
  Code:

  Method not found (code -32601)

  , indicating this command has been removed in this version.
  
  
  Conclusion:
  Based on these tests, it appears that CPU mining using the built-in console commands (
  Code:

  generatetoaddress

  ,
  Code:

  setgenerate

  ) is not functioning correctly in the Windows v1.3.0 build.
  Code:

  generatetoaddress

  seems buggy (fails returning
  Code:

  [ ]

  even though the log shows
  Code:

  CreateNewBlock

  is executed), and
  Code:

  setgenerate

  no longer exists.
  
  Additionally, the observation that the main network seems stalled at block 2 for many hours is also worth noting.
  
  I hope this detailed information is helpful to the team and community. Is this a known issue with the Windows build or the
  Code:

  generatetoaddress

  command?
  
  Regards and best of luck with the Blockle project.
  

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!

[Drawesome]

Wow, thank you so much for the  fast and clear explanation! That clears up everything perfectly.

This has actually been really insightful. I'll take this as an opportunity to learn more about mining (I'll try to get some bitaxe and spread the word within its active community).

Cheers!

[Blockle]

Wow, thank you so much for the  fast and clear explanation! That clears up everything perfectly.

This has actually been really insightful. I'll take this as an opportunity to learn more about mining (I'll try to get some bitaxe and spread the word within its active community).

Cheers!

No problem!

[prp-e]

Your project seems cool. Thanks for providing information here.
Just one question, do you have plans on getting listed? and what are specs needed for mining?

[13y85t]

https://i.ibb.co/gMfbD11D/bruh1.png
https://i.ibb.co/mr5dXL30/bruh2.png

there is something wrong here

[Blockle]

https://i.ibb.co/gMfbD11D/bruh1.png
https://i.ibb.co/mr5dXL30/bruh2.png

there is something wrong here

lol I see the irony

[Blockle]

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.

[r_victory]

When I read "BLK" I thought it was something related to Blackcoin   , although it no longer has the strength it once had. I would consider changing the ticker of your currency, as it could cause confusion for older investors.

In any case, good luck with your project!

[Blockle]

Blockle Mining Pool is Live!

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

[Blockle]

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

Code:

cd ~/blockle                  ;# your local source folder

Initialize if you haven’t already

git init
git remote add origin https://github.com/Blocklechain/blockle.git

git fetch origin
git reset --hard origin/main

Rebuild

cd src
make clean
./autogen.sh && ./configure && make -j$(nproc)

Replace your daemon

sudo systemctl stop blockled
sudo cp src/blockled /usr/local/bin/
sudo systemctl start blockled

Check your logs around block 30 for:

Code:

[DIGISHIELD] per‑block retarget active at height 30

⸻

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

[xichas]

Hi!

Started mining a few minutes ago and running windows wallet but seems to be stopped syncing headers at 0.6%.  Is there any aditional procedure after make windows wallet run?





Regards!

[Blockle]

Updated fork to block 19

[Blockle]

Hi!

Started mining a few minutes ago and running windows wallet but seems to be stopped syncing headers at 0.6%.  Is there any aditional procedure after make windows wallet run?





Regards!

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

[Blockle]

Hi!

Started mining a few minutes ago and running windows wallet but seems to be stopped syncing headers at 0.6%.  Is there any aditional procedure after make windows wallet run?





Regards!

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

New wallet is up!

[Blockle]

[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]

[Blockle]

[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
  
• Block Time: 15 seconds  
  
• Difficulty Retarget: Every 120 blocks (~30 minutes) for smoother adjustments  
  
• Total Supply: 1000 000 000 BLK  
  
• Premine: 20,000,000 – 2%
  
• 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

[buttah]

**MAJOR WARNING**

**This is a scam do not download anything from there github!!

THE MOTHERFUCK WHO CREATED THIS REPO TOOK ALL THE MONEY FROM MY EXODUS WALLET.
THIS IS S SCAM AND NEEDS TO BE BURRIED ALIVE!!!

and to the person who did it. Karma is real MF!! 


****SCAM ALERT***

[Blockle]

**MAJOR WARNING**

**This is a scam do not download anything from there github!!

THE MOTHERFUCK WHO CREATED THIS REPO TOOK ALL THE MONEY FROM MY EXODUS WALLET.
THIS IS S SCAM AND NEEDS TO BE BURRIED ALIVE!!!

and to the person who did it. Karma is real MF!! 


****SCAM ALERT***

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