[ANN][LTA] Lattica - Post-Quantum PoW | ML-DSA-44 | SHA3-256d GPU | Fair Launch

[lattica-core]

⬡ Lattica (LTA)
A post-quantum cryptocurrency built on the Bitcoin Core architecture
GitHub · lattica.org · Telegram

When a large enough quantum computer exists, Shor's algorithm breaks the ECDSA signatures that protect every Bitcoin and Ethereum coin. Lattica keeps Bitcoin Core's battle-tested design — UTXO ledger, Script, full-node validation, P2P network, HD wallet — and replaces the cryptography that won't survive:

• Quantum-resistant signatures — every coin is locked with ML-DSA-44 (CRYSTALS-Dilithium, NIST FIPS 204). No ECDSA, no secp256k1 anywhere in the tree.
• Quantum-resistant network — the encrypted v2 P2P transport uses ML-KEM-768 (CRYSTALS-Kyber, FIPS 203) key agreement, enabled by default. The wire is quantum-safe too, not just the coins.
• SHA-3 everywhere — consensus hashing is SHA3-256 (Keccak, FIPS 202), not double-SHA256.
• Simple, GPU-friendly proof-of-work — SHA3-256d over a standard 80-byte header with Bitcoin's 2016-block difficulty retarget. A portable OpenCL miner ships in-tree (NVIDIA / AMD / Intel).
• Fair launch — no premine, no ICO, no dev tax, no masternodes. The genesis output is provably unspendable (OP_RETURN). Every coin must be mined.

— Specifications —
Ticker: LTA
Algorithm: SHA3-256d (GPU, OpenCL)
Signatures: ML-DSA-44 (FIPS 204)
P2P encryption: ML-KEM-768 (FIPS 203)
Block time: 10 minutes (2016-block retarget)
Block reward: 50 LTA, halving every 210,000 blocks
Max supply: 21,000,000 LTA
Address format: native SegWit bech32 (lta1...)
Premine: none — fair launch
Genesis: 3 January 2026 — "Citi 03/Jan/2026 The trillion-dollar quantum security race is on"

— Downloads (v0.1.0) —

• Windows installer:
• Windows portable: lattica-0.1.0-win64.zip
• Linux x86_64: lattica-0.1.0-x86_64-linux-gnu.tar.gz
• Source + build docs: github.com/lattica-core/lattica

Every archive ships the GUI wallet (lattica-qt), node daemon (latticad), CLI, offline tools and the GPU miner (lattica-miner). Verify against SHA256SUMS.

— Run a node & mine —

Code:

# start a full node (Linux)
./latticad -daemon

# mine to the node with your GPU
./lattica-miner        # see the README for RPC flags

The network is bootstrapped by DNS seeds (seed.lattica.org / .uk / .us) with nodes in the US, UK and Asia.

Post-quantum from genesis. Fair launch. No premine.
Bring a GPU.

[scorpio18]

What's going on with the website ?? Did you forgot to create ?
And are you the same dev as the flowcoin flc or whatever symbol was ??

That "Block time: 10 minutes (2016-block retarget)" is bad, if someone with a big hash leave the chain, your chain will get stuck at high diff for 2016 blocks, you guys never learn.

[lattica-core]

Thanks for the questions.

Website — it's up now: https://lattica.org

Difficulty — fair point in general, and hit-and-run diff swings are exactly what
kill small coins. The reason 2016-block retarget is workable here specifically:
SHA3-256d has no rentable hashrate market and no idle ASIC farms — you can't spin
up a huge amount of SHA3-256d hash and dump it on the chain the way you can with
SHA-256/scrypt on NiceHash. So the "big miner joins then leaves" scenario is far
less likely than on a rentable algo. It's on the radar though — the retarget is
a one-file swap to a per-block DAA (ASERT/LWMA) if real hashrate volatility ever
shows up. I'd just rather not add timestamp-manipulation surface preemptively.

On the dev question — Lattica stands on its own code. It's all open
(github.com/lattica-core/lattica), fair launch, no premine, genesis output is a
provably-unspendable OP_RETURN. Judge it on that. Happy to answer anything
technical.

GPU miner + full node are in the v0.1.0 release. Bring a card.

[yunta]

I'm experiencing a blockchain synchronization issue. My node syncs the headers, but the block height stays at 0, so I can't complete the sync. I'm not sure how to resolve it. Could you please help?

root@C.44587928:~/lattica-0.1.0/bin$ ./lattica-cli getchaintips
[
  {
    "height": 283,
    "hash": "c2fdf1cc17f8a59e69a3a5a0e373389c1fee4c0b64c8e6d1a59ffd279926bb79",
    "branchlen": 283,
    "status": "headers-only"
  },
  {
    "height": 0,
    "hash": "54d5b422f33460a0011a044dac5643245a721004cad674fa7ba3d7b3b56b6f0d",
    "branchlen": 0,
    "status": "active"
  }
]
root@C.44587928:~/lattica-0.1.0/bin$ ./lattica-cli getblockchaininfo
{
  "chain": "main",
  "blocks": 0,
  "headers": 283,
  "bestblockhash": "54d5b422f33460a0011a044dac5643245a721004cad674fa7ba3d7b3b56b6f0d",
  "bits": "1c01d41b",
  "target": "0000000001d41b00000000000000000000000000000000000000000000000000",
  "difficulty": 140.0005006884466,
  "time": 1767464118,
  "mediantime": 1767464118,
  "verificationprogress": 1,
  "initialblockdownload": true,
  "chainwork": "0000000000000000000000000000000000000000000000000000008c00acd0d5",
  "size_on_disk": 222,
  "pruned": false,
  "warnings": [
  ]
}


tail -200 ~/.lattica/debug.log

2026-07-12T09:24:01Z connect() to 127.0.0.1:9051 failed after wait: Connection refused (111)
2026-07-12T09:24:01Z [warning] tor: Error connecting to address 127.0.0.1:9051
2026-07-12T09:24:01Z [warning] tor: Initiating connection to Tor control port 127.0.0.1:9051 failed
2026-07-12T09:24:10Z Synchronizing blockheaders, height: 274 (~100.00%)
2026-07-12T09:24:39Z connect() to 127.0.0.1:9051 failed after wait: Connection refused (111)
2026-07-12T09:24:39Z [warning] tor: Error connecting to address 127.0.0.1:9051
2026-07-12T09:24:39Z [warning] tor: Initiating connection to Tor control port 127.0.0.1:9051 failed
2026-07-12T09:24:43Z Synchronizing blockheaders, height: 275 (~100.00%)
2026-07-12T09:25:37Z connect() to 127.0.0.1:9051 failed after wait: Connection refused (111)
2026-07-12T09:25:37Z [warning] tor: Error connecting to address 127.0.0.1:9051
2026-07-12T09:25:37Z [warning] tor: Initiating connection to Tor control port 127.0.0.1:9051 failed
2026-07-12T09:25:53Z Synchronizing blockheaders, height: 276 (~100.00%)
2026-07-12T09:26:17Z Synchronizing blockheaders, height: 277 (~100.00%)
2026-07-12T09:26:24Z Synchronizing blockheaders, height: 278 (~100.00%)
2026-07-12T09:26:27Z Synchronizing blockheaders, height: 279 (~100.00%)
2026-07-12T09:26:29Z Synchronizing blockheaders, height: 280 (~100.00%)
2026-07-12T09:26:32Z Synchronizing blockheaders, height: 281 (~100.00%)
2026-07-12T09:27:03Z connect() to 127.0.0.1:9051 failed after wait: Connection refused (111)
2026-07-12T09:27:03Z [warning] tor: Error connecting to address 127.0.0.1:9051
2026-07-12T09:27:03Z [warning] tor: Initiating connection to Tor control port 127.0.0.1:9051 failed
2026-07-12T09:27:07Z Synchronizing blockheaders, height: 282 (~100.00%)
2026-07-12T09:27:34Z Synchronizing blockheaders, height: 283 (~100.00%)
2026-07-12T09:29:13Z connect() to 127.0.0.1:9051 failed after wait: Connection refused (111)
2026-07-12T09:29:13Z [warning] tor: Error connecting to address 127.0.0.1:9051
2026-07-12T09:29:13Z [warning] tor: Initiating connection to Tor control port 127.0.0.1:9051 failed
2026-07-12T09:32:28Z connect() to 127.0.0.1:9051 failed after wait: Connection refused (111)
2026-07-12T09:32:28Z [warning] tor: Error connecting to address 127.0.0.1:9051
2026-07-12T09:32:28Z [warning] tor: Initiating connection to Tor control port 127.0.0.1:9051 failed



root@C.44587928:~/lattica-0.1.0/bin$ ./lattica-miner -address=lta1qu2cr23xfdrduzgfe2zkqshzqkckrukyx6zqqhf
GPU: NVIDIA GeForce RTX 2060
lattica-miner: chain=main gpu=NVIDIA GeForce RTX 2060 payout=lta1qu2cr23xfdrduzgfe2zkqshzqkckrukyx6zqqhf
getblocktemplate failed: RPC error for getblocktemplate: {"code":-9,"message":"Lattica is not connected!"}
retrying in 5s...

[lattica-core]

Your node has the headers but lost its peers (getblocktemplate says "not
connected" = 0 connections), so it has nothing to download block bodies from.
The chain itself is fine — the seeds are fully synced and serving blocks. You
just need a stable peer. Add the seed nodes explicitly:

  ./lattica-cli addnode 52.2.229.188 add
  ./lattica-cli addnode 51.24.93.148 add
  ./lattica-cli addnode 13.124.192.251 add

(or put them in ~/.lattica/lattica.conf as
  addnode=52.2.229.188
  addnode=51.24.93.148
  addnode=13.124.192.251
and restart latticad).

Then:
  ./lattica-cli getpeerinfo    # you should see the seeds connected
  ./lattica-cli getblockcount  # will climb from 0 up to the tip

Give it a minute to download the blocks. IMPORTANT: don't run the miner until
"blocks" has caught up to the network height — mining on top of block 0 would
build a fork off genesis that gets orphaned. Sync first, then mine.

(The "tor ... 127.0.0.1:9051 Connection refused" lines are harmless — you don't
have Tor running. Add listenonion=0 to silence them.)

[scorpio18]

Thanks for the questions.

Website — it's up now: https://lattica.org

Difficulty — fair point in general, and hit-and-run diff swings are exactly what
kill small coins. The reason 2016-block retarget is workable here specifically:
SHA3-256d has no rentable hashrate market and no idle ASIC farms — you can't spin
up a huge amount of SHA3-256d hash and dump it on the chain the way you can with
SHA-256/scrypt on NiceHash. So the "big miner joins then leaves" scenario is far
less likely than on a rentable algo. It's on the radar though — the retarget is
a one-file swap to a per-block DAA (ASERT/LWMA) if real hashrate volatility ever
shows up. I'd just rather not add timestamp-manipulation surface preemptively.

On the dev question — Lattica stands on its own code. It's all open
(github.com/lattica-core/lattica), fair launch, no premine, genesis output is a
provably-unspendable OP_RETURN. Judge it on that. Happy to answer anything
technical.

GPU miner + full node are in the v0.1.0 release. Bring a card.

"On the dev question — Lattica stands on its own code. It's all open
(github.com/lattica-core/lattica), fair launch, no premine, genesis output is a
provably-unspendable OP_RETURN. Judge it on that. Happy to answer anything
technical."

Next time you clone another coin, don't forget to rename the coin name everywhere in the code. I found references like `{'F','l','o','w','C','o','i','n',...}` still present.

I'm almost 100% sure you're the same developer behind FlowCoin (FLC). You posted multiple FlowCoin threads on Bitcointalk, and all of them ended up being deleted. Now it looks like you're trying again with Lattica.

[yunta]

ining block 721 (prev c8e65575b93a4cf7, target 0000000001d41b00)
mining block 722 (prev 4b3638f633a6d4fc, target 0000000001d41b00)
mining block 723 (prev ce45d467dc161f6e, target 0000000001d41b00)
mining block 724 (prev d2f8ae3027c90915, target 0000000001d41b00)


it is ok?  Where can I check my mining rewards and payout history?

[lattica-core]

ining block 721 (prev c8e65575b93a4cf7, target 0000000001d41b00)
mining block 722 (prev 4b3638f633a6d4fc, target 0000000001d41b00)
mining block 723 (prev ce45d467dc161f6e, target 0000000001d41b00)
mining block 724 (prev d2f8ae3027c90915, target 0000000001d41b00)


it is ok?  Where can I check my mining rewards and payout history?

Yep — that output means your miner is finding blocks, so you're good. 👍

Lattica is solo mining, so there's no separate "pool payout" — every block you mine pays its full reward straight to the address in your own wallet via the coinbase transaction. Your payout history is your wallet's receive history.

How to check:

GUI (lattica-qt): open the Transactions tab — each mined block shows up as a reward. Freshly mined coins are immature until 100 confirmations (~a couple hours), then they become spendable. The Overview tab splits your balance into Available and Immature.
CLI:

lattica-cli getbalances               # mine.trusted (spendable) + mine.immature
lattica-cli listtransactions "*" 50   # each reward, category "immature" / "generate"
If Immature is growing but Available is still 0, that's normal — just wait for the 100-conf maturity. If both stay 0 while mining, your blocks likely aren't being accepted — check lattica-cli getpeerinfo shows peers, and I'll help debug.

[yunta]

Is there any Discord channel?

[lattica-core]

Is there any Discord channel?

Just created: https://discord.gg/em2hSP5bFv

Also on Telegram: https://t.me/lattica_core

[lattica-core]

**Network Update — Day 2**

Lattica mainnet is running strong:

• Block height: 1,576+
• Network hashrate: 12.6 GH/s (SHA3-256d) and climbing
• 19 connected nodes
• 16 unique mining addresses
• 2 public pools live, 3rd operator joining soon
• Discord community active — first users setting up nodes on Windows

First difficulty retarget (block 2,016) coming within hours.

Fair launch, no premine, no ICO. First live mainnet running NIST ML-DSA-44 as the sole signature scheme.

Download: https://github.com/lattica-core
Discord: [https://discord.gg/ZBwDSQUh4]
Website: https://lattica.org

[lattica-core]

🟣 Grid · 1578 → 1629 (+51), 20 connections.
Hashrate: 10-block avg 12.6 · 120-block avg 15.0 GH/s (there was a spike to ~15, but the latest window has settled at 12.6) · Standard 140.
🆕 New node 86.233.28.105 — immediately synced (synced=1628, caught up quickly). 78.85.5.221 is still in IBD.
Top 2 frozen → ql6cq0z 41.8% → 40.5% (dropped below 41%). qxce2 surged +8 (105), qap7uum8 +11 (80), qu2cr23x +10.
No new miners (16 addresses).
A different trend: activity among small miners is rising (hashrate spiked to 15 GH/s), and the concentration of the top 1 is steadily decreasing — 40.5%. The network is becoming healthier.

[lattica-core]

.

[flowcoin5423]

**First public mining pool is live**

LedgeRock (multi-coin pool running BTC, BCH, DOGE + more) has added Lattica:
https://ledgerock.crypto-eire.com/#lattica

Solo mining, 1% fee, SHA3-256d, node fully synced.

Network stats at block 1,700+:
• Hashrate: ~12 GH/s and climbing
• 19 nodes connected
• First difficulty retarget approaching at block 2,016

Miners welcome — connect instructions on the pool page.
You can also solo mine with the built-in miner: lattica-cli generatetoaddress <nblocks> <address>