Bitcoin Forum
January 19, 2026, 06:21:37 PM *
News: Latest Bitcoin Core release: 30.2 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 [4] 5 6 »  All
  Print  
Author Topic: [ANN] LUMENYX - Bitcoin + Ethereum | PoW | CPU Mining | EVM | 21M | No Premine  (Read 668 times)
Cyboorg456
Newbie
*
Online Online

Activity: 23
Merit: 0


View Profile
January 18, 2026, 11:12:33 AM
 #61

This will never work. Developers are mining using multi-core technology while other miners receive no rewards. Their response was "Do it yourself." How ridiculous. Their goal is to take all the rewards. Once their bags are full, they'll update the version. This cryptocurrency is currently centralized, and never buy it in the future. A greedy, deceitful developer.
 Angry Angry Angry Angry Angry Angry Angry Angry Angry Angry
NEVER BELIEVE IT WAS A FAIR START. RIGHT NOW, ALL THE REWARDS ARE GOING TO THE PRIVILEGED. THEY WILL PROBABLY DISTRIBUTE IT TO WALLETS LATER AND UPDATE THE VERSION. BE CAREFUL, THEY WILL PRETEND TO HAVE SOLVED THE PROBLEM AFTER ACQUIRING ENOUGH COINS. Angry Angry Angry
Hashrateoptions
Newbie
*
Offline Offline

Activity: 82
Merit: 0


View Profile
January 18, 2026, 12:41:22 PM
 #62

This will never work. Developers are mining using multi-core technology while other miners receive no rewards. Their response was "Do it yourself." How ridiculous. Their goal is to take all the rewards. Once their bags are full, they'll update the version. This cryptocurrency is currently centralized, and never buy it in the future. A greedy, deceitful developer.
 Angry Angry Angry Angry Angry Angry Angry Angry Angry Angry
NEVER BELIEVE IT WAS A FAIR START. RIGHT NOW, ALL THE REWARDS ARE GOING TO THE PRIVILEGED. THEY WILL PROBABLY DISTRIBUTE IT TO WALLETS LATER AND UPDATE THE VERSION. BE CAREFUL, THEY WILL PRETEND TO HAVE SOLVED THE PROBLEM AFTER ACQUIRING ENOUGH COINS. Angry Angry Angry

You mean that You want to compare your 12 cores to people who mine with 120 ? Bad acting...
Cyboorg456
Newbie
*
Online Online

Activity: 23
Merit: 0


View Profile
January 18, 2026, 01:45:36 PM
 #63

This will never work. Developers are mining using multi-core technology while other miners receive no rewards. Their response was "Do it yourself." How ridiculous. Their goal is to take all the rewards. Once their bags are full, they'll update the version. This cryptocurrency is currently centralized, and never buy it in the future. A greedy, deceitful developer.
 Angry Angry Angry Angry Angry Angry Angry Angry Angry Angry
NEVER BELIEVE IT WAS A FAIR START. RIGHT NOW, ALL THE REWARDS ARE GOING TO THE PRIVILEGED. THEY WILL PROBABLY DISTRIBUTE IT TO WALLETS LATER AND UPDATE THE VERSION. BE CAREFUL, THEY WILL PRETEND TO HAVE SOLVED THE PROBLEM AFTER ACQUIRING ENOUGH COINS. Angry Angry Angry

You mean that You want to compare your 12 cores to people who mine with 120 ? Bad acting...
Never mind, buddy, even with live support, we spent over an hour on my end. Constant errors, errors... I still stand by what I said. This is currently unusable for the average miner. So, it's a complete failure.
Hashrateoptions
Newbie
*
Offline Offline

Activity: 82
Merit: 0


View Profile
January 18, 2026, 04:55:17 PM
 #64

This will never work. Developers are mining using multi-core technology while other miners receive no rewards. Their response was "Do it yourself." How ridiculous. Their goal is to take all the rewards. Once their bags are full, they'll update the version. This cryptocurrency is currently centralized, and never buy it in the future. A greedy, deceitful developer.
 Angry Angry Angry Angry Angry Angry Angry Angry Angry Angry
NEVER BELIEVE IT WAS A FAIR START. RIGHT NOW, ALL THE REWARDS ARE GOING TO THE PRIVILEGED. THEY WILL PROBABLY DISTRIBUTE IT TO WALLETS LATER AND UPDATE THE VERSION. BE CAREFUL, THEY WILL PRETEND TO HAVE SOLVED THE PROBLEM AFTER ACQUIRING ENOUGH COINS. Angry Angry Angry

You mean that You want to compare your 12 cores to people who mine with 120 ? Bad acting...
Never mind, buddy, even with live support, we spent over an hour on my end. Constant errors, errors... I still stand by what I said. This is currently unusable for the average miner. So, it's a complete failure.
no it is not why claiming things like that becasue you can not sort it out on your side  Huh
pacca (OP)
Newbie
*
Offline Offline

Activity: 28
Merit: 0


View Profile
Today at 12:33:10 AM
Last edit: Today at 07:25:17 AM by pacca
 #65

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

⚠️ IMPORTANT UPDATE - Transparency Report + Community Decision

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

⛏️ MULTI-THREAD MINING IS NOW LIVE

We heard you. The binary and script have been updated.
Everyone can now mine with multiple CPU threads - fair for all.

How to update:
Code:
rm -rf ~/.lumenyx/lumenyx-node ~/lumenyx-setup.sh
curl -sL "https://api.github.com/repos/lumenyx-chain/lumenyx/contents/lumenyx-setup.sh" -H "Accept: application/vnd.github.v3.raw" -o lumenyx-setup.sh && chmod +x lumenyx-setup.sh && ./lumenyx-setup.sh

The script will ask how many threads you want to use.

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

⚠️ WE MADE A MISTAKE - Full Transparency

We declared in the README and announcement:
- "No premine"
- "100% distributed through mining"
- "Everyone starts equal"

This is not completely true. We found an error.

When compiling the genesis for mainnet launch, we forgot to remove a faucet allocation from an old version of the code. This faucet was meant for a validator bootstrap system that was never implemented.

The facts:
Code:
Address:  5EYCAe5jvNJx8PWVjCGPgVMm1RSs37G8jQxi4i22mztXxot4
Balance:  5,000 LUMENYX
Status:   PERMANENTLY LOCKED - No private key exists

This address is a PalletId - it's generated by code, not from a seed phrase.
Nobody can access these coins. Not us, not anyone. They are effectively burned forever.

But they exist in total supply. And we said "no premine".
That statement was incorrect. We apologize for this error.

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

📊 CURRENT STATE

Code:
Block:           #52,791
Total mined:     ~10,970 LUMENYX (by miners)
Locked faucet:   5,000 LUMENYX (inaccessible)
Total supply:    21,000,000 LUMENYX
Locked %:        0.024%

You can verify yourself on Polkadot.js Apps:
Developer → Chain State → system → account → paste the address above

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

🗳️ THE COMMUNITY DECIDES

We made the mistake. You decide how to fix it.

OPTION A - Continue current chain
- 5,000 LUMENYX stay burned forever (no one can ever use them)
- All mined coins are kept by miners
- Multi-thread mining available now for everyone
- Chain continues from block #52,791

OPTION B - Fresh restart
- New genesis with clean code (zero faucet)
- Multi-thread mining from block #0
- True "100% mining distribution" as originally promised
- Everyone loses currently mined coins

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

We're open to suggestions. Tell us what you think.

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

No excuses. Just honesty.
The chain belongs to the community. So does this decision.

- missed2009

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
unnamed0simple
Jr. Member
*
Offline Offline

Activity: 125
Merit: 1


View Profile
Today at 05:02:16 AM
 #66

We can't vote here. That's against the rules of the forum. I'd like you to consider a different method.
chn520
Newbie
*
Offline Offline

Activity: 22
Merit: 0


View Profile
Today at 06:05:06 AM
 #67

peer 0
pacca (OP)
Newbie
*
Offline Offline

Activity: 28
Merit: 0


View Profile
Today at 07:10:07 AM
 #68

Thanks for pointing that out, @unnamed0simple - we weren't aware of that rule.
And honestly? This is the perfect example of why we can't do this alone.
We have a vision: make LUMENYX the most powerful community-built blockchain out there. Bitcoin's scarcity, Ethereum's power, built by real people.
But we're not geniuses. We're not a funded team. We're just people who started something.
Now we need YOU.
Developers. Self-taught coders. Dreamers. Tinkerers. People with crazy ideas. People who fix things. People who've been waiting for a project where their voice actually matters.
Want to build a voting system? Let's do it.
Have an idea for a feature? Let's hear it.
See something broken? Help us fix it.
Want to write docs, build tools, spread the word? Join us.
This isn't our project. It's everyone's project.
Let's build something legendary together.

missed2009
visibleplayer
Newbie
*
Offline Offline

Activity: 123
Merit: 0


View Profile
Today at 07:29:10 AM
 #69

If no restart then mine yourself
Hashrateoptions
Newbie
*
Offline Offline

Activity: 82
Merit: 0


View Profile
Today at 08:37:57 AM
 #70

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

⚠️ IMPORTANT UPDATE - Transparency Report + Community Decision

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

⛏️ MULTI-THREAD MINING IS NOW LIVE

We heard you. The binary and script have been updated.
Everyone can now mine with multiple CPU threads - fair for all.

How to update:
Code:
rm -rf ~/.lumenyx/lumenyx-node ~/lumenyx-setup.sh
curl -sL "https://api.github.com/repos/lumenyx-chain/lumenyx/contents/lumenyx-setup.sh" -H "Accept: application/vnd.github.v3.raw" -o lumenyx-setup.sh && chmod +x lumenyx-setup.sh && ./lumenyx-setup.sh

The script will ask how many threads you want to use.

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

⚠️ WE MADE A MISTAKE - Full Transparency

We declared in the README and announcement:
- "No premine"
- "100% distributed through mining"
- "Everyone starts equal"

This is not completely true. We found an error.

When compiling the genesis for mainnet launch, we forgot to remove a faucet allocation from an old version of the code. This faucet was meant for a validator bootstrap system that was never implemented.

The facts:
Code:
Address:  5EYCAe5jvNJx8PWVjCGPgVMm1RSs37G8jQxi4i22mztXxot4
Balance:  5,000 LUMENYX
Status:   PERMANENTLY LOCKED - No private key exists

This address is a PalletId - it's generated by code, not from a seed phrase.
Nobody can access these coins. Not us, not anyone. They are effectively burned forever.

But they exist in total supply. And we said "no premine".
That statement was incorrect. We apologize for this error.

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

📊 CURRENT STATE

Code:
Block:           #52,791
Total mined:     ~10,970 LUMENYX (by miners)
Locked faucet:   5,000 LUMENYX (inaccessible)
Total supply:    21,000,000 LUMENYX
Locked %:        0.024%

You can verify yourself on Polkadot.js Apps:
Developer → Chain State → system → account → paste the address above

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

🗳️ THE COMMUNITY DECIDES

We made the mistake. You decide how to fix it.

OPTION A - Continue current chain
- 5,000 LUMENYX stay burned forever (no one can ever use them)
- All mined coins are kept by miners
- Multi-thread mining available now for everyone
- Chain continues from block #52,791

OPTION B - Fresh restart
- New genesis with clean code (zero faucet)
- Multi-thread mining from block #0
- True "100% mining distribution" as originally promised
- Everyone loses currently mined coins

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

We're open to suggestions. Tell us what you think.

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

No excuses. Just honesty.
The chain belongs to the community. So does this decision.

- missed2009

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

I have put efforts and money to mine if you want to restart for those with no skills to cry later anyway I can agree but You should respect those who mined till now.
pacca (OP)
Newbie
*
Offline Offline

Activity: 28
Merit: 0


View Profile
Today at 08:51:10 AM
 #71

@Hashrateoptions
We respect everyone. That's exactly why we're asking.
You invested time and money. That matters. You're part of this community now - and that means something.
But here's the thing we need to think about together:
Mining alone doesn't make a chain valuable. A chain only has value when it's adopted, developed, built upon. When investors believe in it. When developers want to create on top of it. When people actually use it.
We can all mine thousands of tokens on a chain nobody cares about. Result? Tokens worth zero.
Or we can build something together - fix our mistakes, start clean, grow the right way. And maybe one day, those tokens we mine will actually mean something.
The question isn't "what do we lose today?"
The question is "what can we build tomorrow?"
We made an error. The README said "no premine" and that wasn't 100% true. We want to fix it properly - not because 5,000 locked tokens matter, but because trust matters. Integrity matters. Starting right matters.
If you want to help build this, you're welcome. If you have ideas, we're listening. This isn't our chain - it's everyone's chain.
We're not here to take. We're here to build.
What do you think? Continue or restart - we want to hear from everyone.

missed2009
visibleplayer
Newbie
*
Offline Offline

Activity: 123
Merit: 0


View Profile
Today at 08:59:14 AM
 #72

I have put efforts and money to mine if you want to restart for those with no skills to cry later anyway I can agree but You should respect those who mined till now.
Mine yourself, create socials, list with your money then. Spent 50 cents for electricity ?
Cyboorg456
Newbie
*
Online Online

Activity: 23
Merit: 0


View Profile
Today at 09:00:42 AM
 #73

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

⚠️ IMPORTANT UPDATE - Transparency Report + Community Decision

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

⛏️ MULTI-THREAD MINING IS NOW LIVE

We heard you. The binary and script have been updated.
Everyone can now mine with multiple CPU threads - fair for all.

How to update:
Code:
rm -rf ~/.lumenyx/lumenyx-node ~/lumenyx-setup.sh
curl -sL "https://api.github.com/repos/lumenyx-chain/lumenyx/contents/lumenyx-setup.sh" -H "Accept: application/vnd.github.v3.raw" -o lumenyx-setup.sh && chmod +x lumenyx-setup.sh && ./lumenyx-setup.sh

The script will ask how many threads you want to use.

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

⚠️ WE MADE A MISTAKE - Full Transparency

We declared in the README and announcement:
- "No premine"
- "100% distributed through mining"
- "Everyone starts equal"

This is not completely true. We found an error.

When compiling the genesis for mainnet launch, we forgot to remove a faucet allocation from an old version of the code. This faucet was meant for a validator bootstrap system that was never implemented.

The facts:
Code:
Address:  5EYCAe5jvNJx8PWVjCGPgVMm1RSs37G8jQxi4i22mztXxot4
Balance:  5,000 LUMENYX
Status:   PERMANENTLY LOCKED - No private key exists

This address is a PalletId - it's generated by code, not from a seed phrase.
Nobody can access these coins. Not us, not anyone. They are effectively burned forever.

But they exist in total supply. And we said "no premine".
That statement was incorrect. We apologize for this error.

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

📊 CURRENT STATE

Code:
Block:           #52,791
Total mined:     ~10,970 LUMENYX (by miners)
Locked faucet:   5,000 LUMENYX (inaccessible)
Total supply:    21,000,000 LUMENYX
Locked %:        0.024%

You can verify yourself on Polkadot.js Apps:
Developer → Chain State → system → account → paste the address above

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

🗳️ THE COMMUNITY DECIDES

We made the mistake. You decide how to fix it.

OPTION A - Continue current chain
- 5,000 LUMENYX stay burned forever (no one can ever use them)
- All mined coins are kept by miners
- Multi-thread mining available now for everyone
- Chain continues from block #52,791

OPTION B - Fresh restart
- New genesis with clean code (zero faucet)
- Multi-thread mining from block #0
- True "100% mining distribution" as originally promised
- Everyone loses currently mined coins

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

We're open to suggestions. Tell us what you think.

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

No excuses. Just honesty.
The chain belongs to the community. So does this decision.

- missed2009

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
If this cryptocurrency has a community-based promise, and there's also an option like a relaunch, then my recommendation would be this:
A Fair Mining Model for Lumenyx: Community Power or Server Power?
Lumenyx was launched with a clear promise:
to build a decentralized, CPU-friendly network where everyone can participate.
However, the current mining structure is moving in the opposite direction.
Today:
.High-core cloud servers are dominating block production.
.Individual users are leaving because they can no longer earn rewards.
.Network security is becoming dependent on server capacity instead of real community participation.
.This trend risks turning Lumenyx into a centralized, hardware-driven system controlled by a few powerful actors.
The Core Issue
In CPU-based Proof-of-Work systems:
.Performance scales directly with the number of CPU threads.
.This gives cloud servers an overwhelming advantage over regular home computers.
.Difficulty adjusts only to raw computing power, not to real user participation.
.The result is simple:
.The more cores you have, the more rewards you get.
.This is not fair, and it discourages true decentralization.
Why This Matters
This imbalance leads to:
Declining participation
→ Smaller miners leave the network.
Centralized reward distribution
→ A few powerful servers receive most of the rewards.
Weaker network resilience
The centralized structure will hinder investor acquisitions.
→ Instead of thousands of independent nodes, the network relies on a handful of strong machines.
This model is neither sustainable nor aligned with Lumenyx’s decentralized vision.

 Path Toward Fair CPU Mining
1. Introduce a Thread / Core Limit per Node
Each validator node should be restricted to a maximum number of CPU threads.
This would:
Prevent rented servers from overwhelming the network
Restore competitive balance for individual participants
Encourage wider and healthier decentralization
By determining difficulty levels based on participation rate, this rewards not only the power of the hardware but also the power of the community.

The Vision
The future of Lumenyx should be built on:
Community power, not server power.
A truly decentralized network is one where everyone has a fair chance to participate and earn.
If mining continues to reward only the strongest hardware:
Lumenyx will evolve into a server competition.
But if fairness is prioritized:
Lumenyx can become a global, community-driven network with real decentralization at its core.

visibleplayer
Newbie
*
Offline Offline

Activity: 123
Merit: 0


View Profile
Today at 09:14:06 AM
 #74

I can't see the coins at this address. Could someone check using a browser? I'd at least like to know if I'm mining anything.

5GHhBpDDJyThzRzm3aP1HXpmbvYawgW1wXhbk8bPxdB89eEh
  Wallet:   5GHhBpDD...B89eEh
  Balance:  offline LUMENYX
  Block:    #offline
  Status:   ● MINING
  Peers:    0
12.4771 LUMENYX
And mine was around 14 coins
Even before difficulty up that high we get 40 to 50 blocks each in 2-3 hours of mining with block time 2.5 sec using 1 thread. Imagine that, someone already cheated from the start even without that guy  Grin
pacca (OP)
Newbie
*
Offline Offline

Activity: 28
Merit: 0


View Profile
Today at 09:24:20 AM
 #75

@visibleplayer
Your proposal is thoughtful and we appreciate the time you put into it. The concern is real: big servers dominating, small miners leaving, centralization creeping in.
But here's the technical reality we had to face:
Why "max threads per node" doesn't work:
If we limit each node to 8 threads, someone with 128 cores just runs 16 nodes instead of 1. Same hashpower, same rewards, just more processes. This is called a Sybil attack.
In a permissionless system, "one node = one miner" is not verifiable. Anyone can create N identities at almost zero cost. The reason PoW is Sybil-resistant in the first place is because influence scales with a scarce resource (hashpower/energy), not with the number of identities.
If you try to make it scale with "number of miners" instead, you need to limit identities somehow. And without identity verification (KYC), you hit a wall. We want to stay permissionless - no KYC, no registration, no gatekeepers.
What RX-LX already does:
Our algorithm is a RandomX fork specifically designed to be ASIC-resistant. This levels the playing field against specialized hardware. But it can't prevent someone with more budget from running more CPUs. That's the nature of PoW.
The hard truth:
In pure Proof of Work, "more hardware = more rewards" is not a bug - it's the foundation of security. It's what makes PoW Sybil-resistant. We can't remove it without breaking the system.
The real solution: Mining Pool
The chain is young. We just launched. What small miners really need is not a protocol change - it's a mining pool.
A pool allows everyone to mine together and share rewards. There are different models we could explore:

Proportional - rewards based on contribution
PPLNS (Pay Per Last N Shares) - favors consistent miners
Other fair models - we're open to discuss what works best for small miners

If someone in the community wants to help build pool infrastructure for LUMENYX, we fully support it. This is how Bitcoin solved the same problem. This is how decentralization actually works in practice.
We're open to ideas. We're open to contributors. The chain belongs to everyone - so does the solution.

missed2009
Hashrateoptions
Newbie
*
Offline Offline

Activity: 82
Merit: 0


View Profile
Today at 09:26:05 AM
 #76

@visibleplayer
Your proposal is thoughtful and we appreciate the time you put into it. The concern is real: big servers dominating, small miners leaving, centralization creeping in.
But here's the technical reality we had to face:
Why "max threads per node" doesn't work:
If we limit each node to 8 threads, someone with 128 cores just runs 16 nodes instead of 1. Same hashpower, same rewards, just more processes. This is called a Sybil attack.
In a permissionless system, "one node = one miner" is not verifiable. Anyone can create N identities at almost zero cost. The reason PoW is Sybil-resistant in the first place is because influence scales with a scarce resource (hashpower/energy), not with the number of identities.
If you try to make it scale with "number of miners" instead, you need to limit identities somehow. And without identity verification (KYC), you hit a wall. We want to stay permissionless - no KYC, no registration, no gatekeepers.
What RX-LX already does:
Our algorithm is a RandomX fork specifically designed to be ASIC-resistant. This levels the playing field against specialized hardware. But it can't prevent someone with more budget from running more CPUs. That's the nature of PoW.
The hard truth:
In pure Proof of Work, "more hardware = more rewards" is not a bug - it's the foundation of security. It's what makes PoW Sybil-resistant. We can't remove it without breaking the system.
The real solution: Mining Pool
The chain is young. We just launched. What small miners really need is not a protocol change - it's a mining pool.
A pool allows everyone to mine together and share rewards. There are different models we could explore:

Proportional - rewards based on contribution
PPLNS (Pay Per Last N Shares) - favors consistent miners
Other fair models - we're open to discuss what works best for small miners

If someone in the community wants to help build pool infrastructure for LUMENYX, we fully support it. This is how Bitcoin solved the same problem. This is how decentralization actually works in practice.
We're open to ideas. We're open to contributors. The chain belongs to everyone - so does the solution.

missed2009

If I can suggest :
1. Restart
2. No premine
3. Block time 10 minutes which can reduce database storage.
4. Block reward 50 coins from start which make same amount of coins in circulation over time.
visibleplayer
Newbie
*
Offline Offline

Activity: 123
Merit: 0


View Profile
Today at 09:33:05 AM
 #77

You have to add function to choose amount of mining threads. We all understand what someone will create miner one day and make pool. But locking threads from the start is not fair at all
Cyboorg456
Newbie
*
Online Online

Activity: 23
Merit: 0


View Profile
Today at 09:33:20 AM
 #78

I can't see the coins at this address. Could someone check using a browser? I'd at least like to know if I'm mining anything.

5GHhBpDDJyThzRzm3aP1HXpmbvYawgW1wXhbk8bPxdB89eEh
  Wallet:   5GHhBpDD...B89eEh
  Balance:  offline LUMENYX
  Block:    #offline
  Status:   ● MINING
  Peers:    0
12.4771 LUMENYX
And mine was around 14 coins
Even before difficulty up that high we get 40 to 50 blocks each in 2-3 hours of mining with block time 2.5 sec using 1 thread. Imagine that, someone already cheated from the start even without that guy  Grin

The fair and sustainable approach is to enforce a one-CPU-per-node model. Otherwise, from the very first day, the network can be taken over by a single actor with access to hundreds or even thousands of CPU cores. For example, if someone connects a 1,600-core server, they don’t just increase their own rewards — they effectively suffocate the network and eliminate the earning opportunities of everyone else. At that point, the project stops being a community blockchain and becomes the chain of whoever owns the biggest machine.

In the beginning, when everyone was mining with a single CPU, rewards were distributed naturally and fairly. The network’s hash power was growing organically through real participation. That is what a community-built blockchain should look like.

However, once a few high-core miners joined, they started capturing most of the rewards. This pushed regular participants out of the system. When people stopped earning, they shut down their nodes, and the network gradually shifted from being powered by many individuals to being controlled by a few powerful servers.

As a result, Lumenyx now faces the risk of turning into a hardware-dominated network rather than a truly decentralized, community-driven blockchain. If the goal is to build a chain where everyone can contribute and benefit, the system must be designed in a way that prevents large server owners from monopolizing the network.
Hashrateoptions
Newbie
*
Offline Offline

Activity: 82
Merit: 0


View Profile
Today at 09:37:16 AM
 #79

I can't see the coins at this address. Could someone check using a browser? I'd at least like to know if I'm mining anything.

5GHhBpDDJyThzRzm3aP1HXpmbvYawgW1wXhbk8bPxdB89eEh
  Wallet:   5GHhBpDD...B89eEh
  Balance:  offline LUMENYX
  Block:    #offline
  Status:   ● MINING
  Peers:    0
12.4771 LUMENYX
And mine was around 14 coins
Even before difficulty up that high we get 40 to 50 blocks each in 2-3 hours of mining with block time 2.5 sec using 1 thread. Imagine that, someone already cheated from the start even without that guy  Grin

The fair and sustainable approach is to enforce a one-CPU-per-node model. Otherwise, from the very first day, the network can be taken over by a single actor with access to hundreds or even thousands of CPU cores. For example, if someone connects a 1,600-core server, they don’t just increase their own rewards — they effectively suffocate the network and eliminate the earning opportunities of everyone else. At that point, the project stops being a community blockchain and becomes the chain of whoever owns the biggest machine.

In the beginning, when everyone was mining with a single CPU, rewards were distributed naturally and fairly. The network’s hash power was growing organically through real participation. That is what a community-built blockchain should look like.

However, once a few high-core miners joined, they started capturing most of the rewards. This pushed regular participants out of the system. When people stopped earning, they shut down their nodes, and the network gradually shifted from being powered by many individuals to being controlled by a few powerful servers.

As a result, Lumenyx now faces the risk of turning into a hardware-dominated network rather than a truly decentralized, community-driven blockchain. If the goal is to build a chain where everyone can contribute and benefit, the system must be designed in a way that prevents large server owners from monopolizing the network.

This is how the pow works bigger players always mine more and better go mine bitcoin and complain there you can not mine becasue someone use ASICS what an nonsense.
pacca (OP)
Newbie
*
Offline Offline

Activity: 28
Merit: 0


View Profile
Today at 09:38:58 AM
 #80

Some quick updates and clarifications:
@visibleplayer
Multi-thread mining is already live! You can choose how many threads to use. Just update your script:
rm -rf ~/.lumenyx/lumenyx-node ~/lumenyx-setup.sh
curl -sL "https://api.github.com/repos/lumenyx-chain/lumenyx/contents/lumenyx-setup.sh" -H "Accept: application/vnd.github.v3.raw" -o lumenyx-setup.sh && chmod +x lumenyx-setup.sh && ./lumenyx-setup.sh
The script will ask how many threads you want. This has been available since the last update.

@Hashrateoptions
Thanks for the suggestion. Let's look at the numbers:
10 minute blocks vs 2.5 second blocks - same coins over time, but very different user experience.
About storage - we checked our nodes:

Current chain: 859MB for ~65,000 blocks
Growth: ~450MB/day (~14GB/month)
Our VPS has 50GB disk = months of space
Pruning is supported for nodes that need to save space

The 4GB you see includes OS, logs, cache - not just chain data. The actual chain is small.
2.5 second blocks = fast confirmations. That's a feature, not a bug. Bitcoin is slow. We don't want to be slow.
But we hear you on the restart question. That decision belongs to the community.

@Cyboorg456
We understand your frustration. But we explained the technical reality:
"One-CPU-per-node" is not enforceable in a permissionless system. If we limit to 1 CPU per node, someone with 100 CPUs just runs 100 nodes. Same result. This is called a Sybil attack.
The only way to enforce "one person = one node" is KYC (identity verification). We don't want that. No registration, no gatekeepers, no permission needed.
This is not us being unfair. This is how all PoW systems work. Bitcoin has the same "problem" - more ASICs = more rewards. That's the nature of Proof of Work.
The real solution for small miners is a mining pool - everyone contributes, everyone earns proportionally. If someone wants to build one, we support it.

The restart question is still open. We made a mistake with the 5,000 locked tokens. We admitted it. The community decides what happens next.
We're not here to defend ourselves. We're here to build something together.

missed2009
Pages: « 1 2 3 [4] 5 6 »  All
  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!