[ANN] LUMENYX - 21M Supply, ZK-SNARKs Privacy, No Team

[pacca]

LUMENYX

I've been working on a new electronic cash system that runs without central control.

Launched December 25, 2025.

PROPERTIES
- 21,000,000 fixed supply
- 3 second block time
- ZK-SNARKs privacy (optional)
- EVM compatible
- Permissionless validation

DISTRIBUTION
- No ICO, no presale, no VC
- No team allocation, no foundation
- No premine
- 100% via mining

EMISSION
- Phase 0: 2.4 LUMENYX/block
- Phase 1: 0.3 LUMENYX/block
- Phase 2: 0.25 LUMENYX/block (halving every ~4 years)

Early validators take the highest risk. Same principle as Bitcoin's early blocks.

CURRENT STATE
- Network operational
- Validator faucet active (2 free LUMENYX to start)

EXIT PLAN
When enough validators join, I disappear. Excess above 5% burned.

GitHub: https://github.com/lumenyx-chain/lumenyx

"Banks ended up in the headlines. Today control over digital money sits in a few hands: founders, large holders, intermediaries and those who write the rules."

No website. No social media. No company.
Just code and consensus.

This chain belongs to no one. It's yours now.

Use at your own risk.

- missed2009

[visibleplayer]

Last time you said you've found this coin on github 

[pacca]

Yes, that was me too. I initially posted as someone who "found" the project, but that felt dishonest.

This is the real announcement. I'm the creator. No more hiding.

The code is open, the chain is running, anyone can verify.

- missed2009

[MiningCoinsPool]

Not a great start.. and you're caught lying again 

[visibleplayer]

The code is open, the chain is running, anyone can verify.

- missed2009

Good good

[pacca]

I wasn't "caught" - I admitted it voluntarily. The first post was removed, so I decided to post honestly this time.

There's nothing to hide here. No ICO, no presale, no tokens to sell. Just open source code.

You can verify everything on-chain. Or don't. Your choice.

- missed2009

[Fascior2000]

and how do you mine that thing?

Error: Service(Network(The same bootnode (`/ip4/89.147.111.102/tcp/30333`) is registered with two different peer ids: `12D3KooWAe7PepkGKEzYMZWRZv5VmHuPdgoo1tuWSEoZnAWYrFEp` and `12D3KooWSnyAJBQoKRQL3SWgYu5LKqEsAYfN5JWtzoc2NKgGb5ZJ`))
root@PC:/home/lol/lumenyx#

[mandown]

what is problem ?

Essential task `basic-block-import-worker` failed. Shutting down service.
Error: Service(Network(The same bootnode (`/ip4/89.147.111.102/tcp/30333`) is registered with two different peer ids: `12D3KooWAe7PepkGKEzYMZWRZv5VmHuPdgoo1tuWSEoZnAWYrFEp` and `12D3KooWSnyAJBQoKRQL3SWgYu5LKqEsAYfN5JWtzoc2NKgGb5ZJ`))

[Fascior2000]

Step 4: Set Session Keys
Using Polkadot.js Apps:

Call session.setKeys(keys, proof) with your AURA + GRANDPA public keys
Costs ~0.001 LUMENYX (paid from faucet claim)

cant get throught this point

[pacca]

@Fascior2000 @mandown

Chain spec was updated today. Delete your local copy and re-clone:

rm -rf lumenyx
git clone https://github.com/lumenyx-chain/lumenyx
cd lumenyx
cargo build --release
./target/release/lumenyx-node --chain mainnet-spec.json --validator

@Fascior2000 for setKeys:

Added a new script. After your node syncs, run:

pip install substrate-interface
python3 scripts/set_keys.py

Enter your 12-word phrase when prompted.

- missed2009

[mandown]

How can I tell if the validator is actively running? Is there a block explorer available? and faucet not working

[pacca]

@mandown

**1. CHECK IF YOUR NODE IS RUNNING**

journalctl -u lumenyx -n 20 --no-pager

If you see "Imported block" or "Prepared block" = working.

**2. BLOCK EXPLORER (Polkadot.js Apps)**

Browsers block insecure WebSocket by default. Use Firefox with this fix:

1. Open Firefox (Chrome won't work)
2. Type in address bar: about:config
3. Click "Accept the Risk and Continue"
4. In search box type: network.websocket.allowInsecureFromHTTPS
5. You will see it set to "false"
6. Click the arrows icon on the right to change it to "true"
7. Close Firefox completely and reopen it
8. Go to: https://polkadot.js.org/apps/?rpc=ws://89.147.111.102:9944
9. Wait a few seconds - you'll see "LUMENYX Mainnet" in top left

Now you can see blocks, validators, balances, everything.

**3. BECOME A VALIDATOR - COMPLETE STEPS**

Step 1 - Clone and build:
git clone https://github.com/lumenyx-chain/lumenyx
cd lumenyx
cargo build --release

Step 2 - Start your node and let it sync:
./target/release/lumenyx-node --chain mainnet-spec.json --validator --name "your-name" --bootnodes /ip4/89.147.111.102/tcp/30333/p2p/12D3KooWSnyAJBQoKRQL3SWgYu5LKqEsAYfN5JWtzoc2NKgGb5ZJ

KEEP THIS TERMINAL OPEN! The node must stay running.
Wait until you see "Imported #12xxx" - your node is synced.

Step 3 - Claim faucet (2 free LUMENYX):
Open a NEW terminal window and run:
pip install substrate-interface base58
cd lumenyx
python3 scripts/claim_faucet.py

IMPORTANT: This creates a NEW account with 2 LUMENYX.
SAVE THE 12-WORD SEED PHRASE IT SHOWS YOU!

Step 4 - Set session keys (same terminal as Step 3):
python3 scripts/set_keys.py

When it asks for seed phrase, enter THE SEED PHRASE FROM STEP 3 (the faucet account).

Done! After ~10 minutes you'll be in the validator set and start producing blocks.

**4. VERIFY EVERYTHING WORKS**

python3 << 'EOF'
from substrateinterface import SubstrateInterface
substrate = SubstrateInterface(url="ws://89.147.111.102:9944")
block = substrate.get_block_number(None)
validators = substrate.query("Session", "Validators")
print(f"Block: #{block}")
print(f"Validators: {len(validators.value)}")
for v in validators.value:
    print(f"  - {v}")
EOF

Current status: Block #12,000+, 2 validators active, faucet has 5000 LUMENYX.

Questions? Ask here.

- missed2009

[pacca]

@mandown
Faucet fixed.
The genesis had funds at a wrong address (generated from old code). Since the chain is immutable - no sudo, no admin keys - we couldn't modify it.
Solution: Transferred 5000 LUMENYX from our validator node to the correct faucet pallet address.
You can verify on-chain:

Faucet address: 5EYCAe5jvNJx8PWVjCGPgVMm1RSs37G8jQxi4i22mztXxot4
Balance: ~5000 LUMENYX

cd lumenyx
git pull
python3 scripts/claim_faucet.py

This is what "no admin keys" means - even the creator can't change the rules. We had to use our own coins to fix it.

missed2009

[pacca]

[UPDATE] LUMENYX - Network Restart

We identified an issue with GRANDPA finalization. Some validators joined but didn't configure GRANDPA correctly, which blocks finalization for everyone.

Since LUMENYX has no admin keys and no governance (by design, like Bitcoin), we cannot fix the running chain.

The network is still in early phase. Better to restart now with correct code.

What's improved:
- Automatic validator setup (impossible to misconfigure)
- Auto-removal of inactive validators (network self-heals)
- Same tokenomics (21M supply, fair launch, no premine)

The old chain will be shut down. New chain will be live soon.

Will post here when ready.

- missed2009

[pacca]

[UPDATE] LUMENYX  - LIVE NOW

The chain is yours now.

**WHAT CHANGED**

Removed GRANDPA finality.

GRANDPA requires 2/3 of validators to agree. If they go offline = chain stops. Central point of failure.

Now pure AURA with probabilistic finality:
- Chain NEVER stops. Even if 90% of validators disappear.
- No voting committee. No coordinator. No bottleneck.
- More decentralized than before.
- After 6 blocks (~18 seconds) = practically final.

Same model Bitcoin used for 16 years. Simple. Unstoppable.

**STATUS**
- Block: #1,400+
- Block time: 3.0 seconds 
- Validators: 2 active
- Faucet: 4,994 LUMENYX available

**BECOME A VALIDATOR (3 Steps)**

Step 1 - Build and run:

git clone https://github.com/lumenyx-chain/lumenyx
cd lumenyx
cargo build --release

./target/release/lumenyx-node \
  --chain mainnet \
  --validator \
  --name "your-name" \
  --rpc-cors=all \
  --rpc-methods=unsafe \
  --bootnodes /ip4/89.147.111.102/tcp/30333/p2p/12D3KooWFvS5t55gVhjtzP4egiWMZKtjdPDQg9HxCkXDXNmeH2V1

Wait for "Idle (1 peers)" = synced.

Step 2 - New terminal:

pip install substrate-interface
cd lumenyx
python3 scripts/become_validator.py

Does everything: generates account, claims 2 free LUMENYX, registers you as validator.

SAVE YOUR SEED PHRASE.

Step 3 - Wait ~10 minutes. You'll see:

🎁 Prepared block for proposing at 1234

You're mining.

**BLOCK EXPLORER**

Firefox only (Chrome blocks WebSocket):
1. about:config → network.websocket.allowInsecureFromHTTPS → true
2. Restart Firefox
3. https://polkadot.js.org/apps/?rpc=ws://89.147.111.102:9944

**IGNORE OLD POSTS**

Posts #10, #12, #13 reference old chain. Use instructions above.

GitHub: https://github.com/lumenyx-chain/lumenyx

No website. No Discord. No company.
Just code.

The chain belongs to no one. It's yours now.

- missed2009

[subdev]

[UPDATE] LUMENYX  - LIVE NOW

The chain is yours now.

**WHAT CHANGED**

Removed GRANDPA finality.

GRANDPA requires 2/3 of validators to agree. If they go offline = chain stops. Central point of failure.

Now pure AURA with probabilistic finality:
- Chain NEVER stops. Even if 90% of validators disappear.
- No voting committee. No coordinator. No bottleneck.
- More decentralized than before.
- After 6 blocks (~18 seconds) = practically final.

Same model Bitcoin used for 16 years. Simple. Unstoppable.

**STATUS**
- Block: #1,400+
- Block time: 3.0 seconds  
- Validators: 2 active
- Faucet: 4,994 LUMENYX available

**BECOME A VALIDATOR (3 Steps)**

Step 1 - Build and run:

git clone https://github.com/lumenyx-chain/lumenyx
cd lumenyx
cargo build --release

./target/release/lumenyx-node \
  --chain mainnet \
  --validator \
  --name "your-name" \
  --rpc-cors=all \
  --rpc-methods=unsafe \
  --bootnodes /ip4/89.147.111.102/tcp/30333/p2p/12D3KooWFvS5t55gVhjtzP4egiWMZKtjdPDQg9HxCkXDXNmeH2V1

Wait for "Idle (1 peers)" = synced.

Step 2 - New terminal:

pip install substrate-interface
cd lumenyx
python3 scripts/become_validator.py

Does everything: generates account, claims 2 free LUMENYX, registers you as validator.

SAVE YOUR SEED PHRASE.

Step 3 - Wait ~10 minutes. You'll see:

🎁 Prepared block for proposing at 1234

You're mining.

**BLOCK EXPLORER**

Firefox only (Chrome blocks WebSocket):
1. about:config → network.websocket.allowInsecureFromHTTPS → true
2. Restart Firefox
3. https://polkadot.js.org/apps/?rpc=ws://89.147.111.102:9944

**IGNORE OLD POSTS**

Posts #10, #12, #13 reference old chain. Use instructions above.

GitHub: https://github.com/lumenyx-chain/lumenyx

No website. No Discord. No company.
Just code.

The chain belongs to no one. It's yours now.

- missed2009

Block: #1,400+
3sec * Block: #1,400. it is huge premine
means that you premined huge portion and therefore your stack will be dominating in block reward(producing) for years and years in current PoS system where validators need stake and then more stake then more hashpower to find block reward.

you post polkadot js with a ws connection and not wss that is not accessible on polkadot js because it is ssl(polkadot.js) that not capable to speak with a ws(no ssl connection)

so no one even able to verify how much you premine here.

With only ~2 validators active, the early issuance is highly concentrated (likely in the hands of whoever was running validators from the start). In a validator/stake-based model, that’s effectively a premine in practice: early block rewards become stake, stake becomes validator power, and validator power compounds into more rewards for a long time.

Also, the verification path you posted is not acceptable for any users: (so people need to run fork of polkadot.js on the localhost to ly access that ws RPC url you share)

You’re linking Polkadot.js (served over HTTPS) to an insecure ws:// RPC. Most browsers block HTTPS → WS “mixed content”, so people can’t even verify balances/supply without changing hidden browser settings. If users can’t easily inspect chain state, they can’t verify distribution.

[pacca]

@subdev

Two separate points:

**1. "Premine"**

There was no premine. At block #0:
- Faucet pool: 5,000 LUMENYX (for new validators)
- Everything else: 0

Block #1,400 = 1,400 blocks mined since genesis. At 2.4 LUMENYX/block = ~3,400 LUMENYX total. That's 0.016% of 21M supply.

Anyone who joins now earns the same 2.4 LUMENYX/block. The emission schedule is identical for everyone.

Also: LUMENYX uses round-robin selection. Every validator gets equal turns, regardless of balance. More coins ≠ more blocks. This is not stake-weighted PoS.

**2. "ws not accessible"**

Firefox fix explained in post #15:
- about:config → network.websocket.allowInsecureFromHTTPS → true

Or verify without browser:

pip install substrate-interface
python3 -c "from substrateinterface import SubstrateInterface; s=SubstrateInterface(url='ws://89.147.111.102:9944'); print(s.query('Balances','TotalIssuance').value/10**12)"

Or run your own node.

Don't trust. Verify.

- missed2009

[mandown]

2026-01-03 09:44:28 📦 Highest known block at #0
2026-01-03 09:44:28 〽️ Prometheus exporter started at 127.0.0.1:9615
2026-01-03 09:44:28 Running JSON-RPC server: addr=127.0.0.1:9944,[::1]:9944
2026-01-03 09:44:28 🔍 Discovered new external address for our node: /ip4/46.1.230.47/tcp/30333/p2p/12D3KooWPhvhvTzn3tFBuZ565SRwkcAUvABQbVy2rVu99qxQj7t3
2026-01-03 09:44:28 Bootnode with peer id `12D3KooWFvS5t55gVhjtzP4egiWMZKtjdPDQg9HxCkXDXNmeH2V1` is on a different chain (our genesis: 0xb03f…b0ab theirs: 0x1345…35e8)
2026-01-03 09:44:33 💤 \x1b[37m\x1b[1mIdle\x1b[0m (\x1b[37m\x1b[1m0\x1b[0m peers), best: #\x1b[37m\x1b[1m0\x1b[0m (0xb03f…b0ab), finalized #\x1b[37m\x1b[1m0\x1b[0m (0xb03f…b0ab), ⬇ \x1b[32m0.6kiB/s\x1b[0m ⬆ \x1b[31m0.7kiB/s\x1b[0m
2026-01-03 09:44:33 Bootnode with peer id `12D3KooWFvS5t55gVhjtzP4egiWMZKtjdPDQg9HxCkXDXNmeH2V1` is on a different chain (our genesis: 0xb03f…b0ab theirs: 0x1345…35e8)
2026-01-03 09:44:33 Report 12D3KooWFvS5t55gVhjtzP4egiWMZKtjdPDQg9HxCkXDXNmeH2V1: -2147483648 to -2147483648. Reason: Genesis mismatch. Banned, disconnecting.
2026-01-03 09:44:38 💤 \x1b[37m\x1b[1mIdle\x1b[0m (\x1b[37m\x1b[1m0\x1b[0m peers), best: #\x1b[37m\x1b[1m0\x1b[0m (0xb03f…b0ab), finalized #\x1b[37m\x1b[1m0\x1b[0m (0xb03f…b0ab), ⬇ \x1b[32m0.1kiB/s\x1b[0m ⬆ \x1b[31m0.1kiB/s\x1b[0m
2026-01-03 09:44:43 💤 \x1b[37m\x1b[1mIdle\x1b[0m (\x1b[37m\x1b[1m0\x1b[0m peers), best: #\x1b[37m\x1b[1m0\x1b[0m (0xb03f…b0ab), finalized #\x1b[37m\x1b[1m0\x1b[0m (0xb03f…b0ab), ⬇ \x1b[32m39 B/s\x1b[0m ⬆ \x1b[31m9 B/s\x1b[0m
2026-01-03 09:44:48 💤 \x1b[37m\x1b[1mIdle\x1b[0m (\x1b[37m\x1b[1m0\x1b[0m peers), best: #\x1b[37m\x1b[1m0\x1b[0m (0xb03f…b0ab), finalized #\x1b[37m\x1b[1m0\x1b[0m (0xb03f…b0ab), ⬇ \x1b[32m0.1kiB/s\x1b[0m ⬆ \x1b[31m0.1kiB/s\x1b[0m
2026-01-03 09:44:53 💤 \x1b[37m\x1b[1mIdle\x1b[0m (\x1b[37m\x1b[1m0\x1b[0m peers), best: #\x1b[37m\x1b[1m0\x1b[0m (0xb03f…b0ab), finalized #\x1b[37m\x1b[1m0\x1b[0m (0xb03f…b0ab), ⬇ \x1b[32m9 B/s\x1b[0m ⬆ \x1b[31m39 B/s\x1b[0

what is problem.

[pacca]

@mandown

You have old chain data. Delete it and restart:

rm -rf ~/.local/share/lumenyx-node

Then use --chain mainnet (not mainnet-spec.json):

./target/release/lumenyx-node \
  --chain mainnet \
  --validator \
  --name "your-name" \
  --rpc-cors=all \
  --rpc-methods=unsafe \
  --bootnodes /ip4/89.147.111.102/tcp/30333/p2p/12D3KooWFvS5t55gVhjtzP4egiWMZKtjdPDQg9HxCkXDXNmeH2V1

After sync: python3 scripts/become_validator.py

- missed2009

[mandown]

@mandown

You have old chain data. Delete it and restart:

rm -rf ~/.local/share/lumenyx-node

Then use --chain mainnet (not mainnet-spec.json):

./target/release/lumenyx-node \
  --chain mainnet \
  --validator \
  --name "your-name" \
  --rpc-cors=all \
  --rpc-methods=unsafe \
  --bootnodes /ip4/89.147.111.102/tcp/30333/p2p/12D3KooWFvS5t55gVhjtzP4egiWMZKtjdPDQg9HxCkXDXNmeH2V1

After sync: python3 scripts/become_validator.py

- missed2009

(base) mandown@test:~/lumenyx$ rm -rf ~/.local/share/lumenyx-node
(base) mandown@test:~/lumenyx$ rm -rf ~/.local/share/lumenyx-node
(base) mandown@test:~/lumenyx$ ./target/release/lumenyx-node \
  --chain mainnet \
  --validator \
  --name "your-name" \
  --rpc-cors=all \
  --rpc-methods=unsafe \
  --bootnodes /ip4/89.147.111.102/tcp/30333/p2p/12D3KooWFvS5t55gVhjtzP4egiWMZKtjdPDQg9HxCkXDXNmeH2V1
WARNING: No public address specified, validator node may not be reachable.
                                Consider setting `--public-addr` to the public IP address of this node.
                                This will become a hard requirement in future versions.
Error: NetworkKeyNotFound("/home/mandown/.local/share/lumenyx-node/chains/lumenyx_mainnet/network/secret_ed25519")
(base) mandown@test:~/lumenyx$

idont understand problem where?