[ANN] LUMENYX - Bitcoin + Ethereum | PoW | CPU Mining | EVM | 21M | No Premine

[Chrise5849]

Are we doing P2P trading yet?

[pacca]

🚨 MANDATORY UPDATE - v2.2.4 - UPGRADE NOW 🚨

The ASERT fix is ready. All miners MUST upgrade before block 75,000.

⏰ Time remaining: ~7-8 hours
📦 Current block: ~63,900
🎯 Fork block: 75,000

== YOUR TOKENS ARE SAFE ==

✅ All tokens you already mined STAY in your wallet
✅ Your wallet and private key are NOT affected
✅ You just need to restart with the new version

== HOW TO UPGRADE ==

1. Stop your miner:

Code:

pkill -9 lumenyx

2. Run the update:

Code:

curl -sL "https://raw.githubusercontent.com/lumenyx-chain/lumenyx/main/lumenyx-setup.sh" -o lumenyx-setup.sh && chmod +x lumenyx-setup.sh && ./lumenyx-setup.sh

3. When asked "Clean install?" → n
4. When asked "Update binary?" → y
5. Press 1 to start mining

== VERIFY ==

Code:

~/.lumenyx/lumenyx-node --version

Must show: lumenyx-node 2.2.4

== IMPORTANT ==

❌ If you don't upgrade before block 75,000 → you will fork off to a dead chain
✅ If you upgrade → you continue mining normally

—
missed2009

[Hashrateoptions]

🚨 MANDATORY UPDATE - v2.2.4 - UPGRADE NOW 🚨

The ASERT fix is ready. All miners MUST upgrade before block 75,000.

⏰ Time remaining: ~7-8 hours
📦 Current block: ~63,900
🎯 Fork block: 75,000

== YOUR TOKENS ARE SAFE ==

✅ All tokens you already mined STAY in your wallet
✅ Your wallet and private key are NOT affected
✅ You just need to restart with the new version

== HOW TO UPGRADE ==

1. Stop your miner:

Code:

pkill -9 lumenyx

2. Run the update:

Code:

curl -sL "https://raw.githubusercontent.com/lumenyx-chain/lumenyx/main/lumenyx-setup.sh" -o lumenyx-setup.sh && chmod +x lumenyx-setup.sh && ./lumenyx-setup.sh

3. When asked "Clean install?" → n
4. When asked "Update binary?" → y
5. Press 1 to start mining

== VERIFY ==

Code:

~/.lumenyx/lumenyx-node --version

Must show: lumenyx-node 2.2.4

== IMPORTANT ==

❌ If you don't upgrade before block 75,000 → you will fork off to a dead chain
✅ If you upgrade → you continue mining normally

—
missed2009

Your bootnode dont accept nwe connections

[pacca]

Bootnode is working - 24 peers connected, port 30333 open.

Please make sure you:
1. Updated to v2.2.4 (check: ~/.lumenyx/lumenyx-node --version)
2. Stopped old node before updating (pkill -9 lumenyx)
3. Your firewall allows port 30333

If still no peers, restart your node and wait 1-2 minutes.

[Hashrateoptions]

Bootnode is working - 24 peers connected, port 30333 open.

Please make sure you:
1. Updated to v2.2.4 (check: ~/.lumenyx/lumenyx-node --version)
2. Stopped old node before updating (pkill -9 lumenyx)
3. Your firewall allows port 30333

If still no peers, restart your node and wait 1-2 minutes.

No yesterday it works without a problem today I can not connect

[pacca]

⚠️ UPDATE - v2.2.4 Fork Cancelled ⚠️

The ASERT fix we released earlier today had a problem - it changed the genesis hash, which would have split the network.

What we did:
- Reverted to the original code
- Re-uploaded the correct binary (v2.2.4)
- No fork at block 75,000 anymore

What you should do:
- If you already updated today → run the setup script again to get the correct binary
- If you didn't update → you're fine, nothing to do

Code:

pkill -9 lumenyx
curl -sL "https://raw.githubusercontent.com/lumenyx-chain/lumenyx/main/lumenyx-setup.sh" -o lumenyx-setup.sh && chmod +x lumenyx-setup.sh && ./lumenyx-setup.sh

Current status:
- Network is stable
- Mining continues normally 
- The 25s clamp bug still exists but doesn't affect normal operation
- We will work on a proper fix that doesn't change genesis

Sorry for the confusion. This is why we test things.

—
missed2009

[pacca]

🔧 ASERT FIX COMPLETED ✅ - RELEASE COMING SOON 🔧

== FIX READY ==
The ASERT fix has been completed and tested. The genesis hash problem is solved.

== CURRENT STATUS ==
- Network is running normally
- Mining continues as usual
- The slowdown bug could still appear but the chain will unstick on its own

== COMING SOON ==
We will release the new version with the fix. Details and fork height will be announced when ready.

== YOUR TOKENS ARE SAFE ==
✅ All mined tokens stay in your wallet
✅ Same chain, same history, no reset

Stay tuned for release announcement.

— missed2009

[weesdr]

Chain stuck again

[pacca]

🚨 MANDATORY UPDATE - v2.2.5 - UPGRADE NOW 🚨
The ASERT fix is ready. All miners MUST upgrade before block 125,000.
📦 Current block: ~124,220
🎯 Fork block: 125,000
⏰ Chain is slow due to bug - blocks will arrive gradually until the fork
== YOUR TOKENS ARE SAFE ==
✅ All tokens you already mined STAY in your wallet
✅ Your wallet and private key are NOT affected
✅ Same genesis hash (0xd3b7...7676) - verified
✅ You just need to restart with the new version
== HOW TO UPGRADE ==

Stop your miner:

Code:

pkill -9 lumenyx

Run the update:

Code:

curl -sL "https://raw.githubusercontent.com/lumenyx-chain/lumenyx/main/lumenyx-setup.sh" -o lumenyx-setup.sh && chmod +x lumenyx-setup.sh && ./lumenyx-setup.sh

When asked "Clean install?" → n
When asked "Update binary?" → y
Press 1 to start mining

== VERIFY ==

Code:

~/.lumenyx/lumenyx-node --version

Must show: lumenyx-node 2.2.5
== IMPORTANT ==
❌ If you don't upgrade before block 125,000 → you will fork off to a dead chain
✅ If you upgrade → you continue mining normally
—
missed2009

[pacca]

📋 CLEAN INSTALL PROCEDURE (if you have sync issues)
If your node is not syncing correctly or showing wrong block target, do a clean install:
== STEP 1: BACKUP YOUR SEED PHRASE ==
⚠️ Make sure you have your 12-word seed phrase saved! You will need it to restore your wallet.
Your tokens are on the blockchain, not on your computer. The seed phrase is the only way to recover them.
== STEP 2: STOP AND REMOVE EVERYTHING ==

Code:

pkill -9 lumenyx
rm -rf ~/.local/share/lumenyx-node
rm -rf ~/.lumenyx
rm -f ~/lumenyx-setup.sh

== STEP 3: FRESH INSTALL ==

Code:

curl -sL "https://raw.githubusercontent.com/lumenyx-chain/lumenyx/main/lumenyx-setup.sh" -o lumenyx-setup.sh && chmod +x lumenyx-setup.sh && ./lumenyx-setup.sh

== STEP 4: RESTORE WALLET ==
When asked "Do you have an existing seed phrase?" → y
Enter your 12-word seed phrase to restore your wallet.
== STEP 5: VERIFY BOOTNODE CONNECTION ==
Your node should connect to the official bootnode:

Code:

/ip4/207.180.204.4/tcp/30333/p2p/12D3KooWHRMGZLj8LSuwFYAXUoKCKSwcuQuhaVjfLJRGjL9F7Hp8

Check connection:

Code:

curl -s -H "Content-Type: application/json" -d '{"id":1, "jsonrpc":"2.0", "method":"system_peers"}' http://127.0.0.1:9944 | grep -o "12D3KooWHRMGZLj8LSuwFYAXUoKCKSwcuQuhaVjfLJRGjL9F7Hp8"

If it shows the bootnode ID → you are connected correctly ✅
—
missed2009

[roy-aron09]

📋 CLEAN INSTALL PROCEDURE (if you have sync issues)
If your node is not syncing correctly or showing wrong block target, do a clean install:
== STEP 1: BACKUP YOUR SEED PHRASE ==
⚠️ Make sure you have your 12-word seed phrase saved! You will need it to restore your wallet.
Your tokens are on the blockchain, not on your computer. The seed phrase is the only way to recover them.
== STEP 2: STOP AND REMOVE EVERYTHING ==

Code:

pkill -9 lumenyx
rm -rf ~/.local/share/lumenyx-node
rm -rf ~/.lumenyx
rm -f ~/lumenyx-setup.sh

== STEP 3: FRESH INSTALL ==

Code:

curl -sL "https://raw.githubusercontent.com/lumenyx-chain/lumenyx/main/lumenyx-setup.sh" -o lumenyx-setup.sh && chmod +x lumenyx-setup.sh && ./lumenyx-setup.sh

== STEP 4: RESTORE WALLET ==
When asked "Do you have an existing seed phrase?" → y
Enter your 12-word seed phrase to restore your wallet.
== STEP 5: VERIFY BOOTNODE CONNECTION ==
Your node should connect to the official bootnode:

Code:

/ip4/207.180.204.4/tcp/30333/p2p/12D3KooWHRMGZLj8LSuwFYAXUoKCKSwcuQuhaVjfLJRGjL9F7Hp8

Check connection:

Code:

curl -s -H "Content-Type: application/json" -d '{"id":1, "jsonrpc":"2.0", "method":"system_peers"}' http://127.0.0.1:9944 | grep -o "12D3KooWHRMGZLj8LSuwFYAXUoKCKSwcuQuhaVjfLJRGjL9F7Hp8"

If it shows the bootnode ID → you are connected correctly ✅
—
missed2009

strange, after the first installation there were now 3 peers, after changing the number of threads and restarting the peers became 0,
can you share the peers? Is it possible to register several peers in bootnod.conf? Does it work on Ubuntu in WSL?

[weesdr]

No issues here running on wsl. Try force closing the node and restart it again.

[pacca]

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

✅ HARD FORK COMPLETE — CHAIN STABLE

Block 125,000 reached. ASERT difficulty fix active.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

📊 CURRENT STATUS

Block Height	#132,000+
Block Time	~2.5 seconds ✅
Network	Stable ✅
Version Required	v2.2.5

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🔧 WHAT WE FIXED (Last 2 Weeks)

✅ ASERT difficulty bug → fixed → deployed
✅ Archive node 24/7 with public RPC
✅ P2Pool support added
✅ Pruning options for lighter nodes
✅ Peers issue → clean install procedure (#170)
✅ WSL/Ubuntu confirmed working (#172)
✅ Every bug reported → fixed

No excuses. No promises. Just fixes pushed to main.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

⛏️ FOR MINERS

Keep mining. The chain runs.

If you have sync issues: clean install procedure in post #170.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🏗️ FOR BUILDERS

The README has been updated.

RPC	http://207.180.204.4:9944
Chain ID	7777
EVM	Full Solidity compatibility

Solidity works. MetaMask works. Hardhat works. Foundry works.
Deploy in minutes.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

📁 RESOURCES

GitHub: https://github.com/lumenyx-chain/lumenyx
Why LUMENYX: https://github.com/lumenyx-chain/lumenyx/blob/main/docs/WHY_LUMENYX.md

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

If you have an idea that no one lets you build elsewhere — now you have a place.

No faucet. No airdrop. Mine or buy.
No Discord. No Telegram. No website.
Just code.

If you're not the one, maybe you know someone who is.
Send them the repo.

If you are the one — stop reading. Build.

- missed2009

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

[subdev]

Premine.

Genesis Block #1: January 26, 2026 at 17:28:33 UTC
ANN at 19:55:07 PM



premine 2.5h + hours at least.

Who knows how long ports was closed.
No genesis timestamp proving you did not premined blocks before everyone join.

You may fool the newbie but you do not fool tech people.