[ANN][LTA] Lattica — Post-Quantum Cryptocurrency | ML-DSA-44 | SHA3-256d GPU

[Pilatovich Kristian 2]

⬡ Lattica (LTA)
Post-quantum cryptocurrency. No premine. No ICO. Written from scratch.

Website · GitHub · Explorer · Telegram · Discord


What is Lattica?

Lattica is what Bitcoin would look like if designed today against quantum computers.

Same architecture — UTXO, Script, full-node validation, HD wallet, 21M cap, halving schedule. Different cryptography — every classical primitive replaced with NIST post-quantum standards. Not a fork. 232,000 lines of C++, built from the ground up by a solo developer.

Quantum computers running Shor's algorithm will break ECDSA. Every BTC sitting in a reused address or pending in mempool becomes vulnerable. Lattica removes that entire attack surface from genesis block zero.

Cryptography

Component	Bitcoin	Lattica
Signatures	ECDSA / Schnorr (broken by Shor)	ML-DSA-44 (FIPS 204)
P2P encryption	secp256k1 ECDH (broken by Shor)	ML-KEM-768 (FIPS 203)
Proof-of-Work	SHA-256d	SHA3-256d (Keccak, FIPS 202)
Address format	bech32 (bc1)	bech32 (lta1)

Every NIST standard finalized 2024. No experimental cryptography. No "we'll add it later."

Mainnet Status

Mainnet launched July 2026. Current stats:
- Block height: 12,400+
- Network hashrate: 400+ GH/s
- Nodes: 70+ across 30+ countries
- Mining pools: 3 independent (community-operated)
- GPU miners: CUDA + OpenCL (AMD/NVIDIA/Intel)
- Mobile wallet: Flutter, full validating node, syncs in under 1 minute
- Mined supply: 620,000+ LTA

No marketing budget. Every node, pool, and miner joined organically.

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: bech32 (lta1...)
Premine: none
Genesis: 3 January 2026

Why SHA3-256d instead of SHA-256d?

SHA-256 has known differential attacks up to 31 of 64 rounds. SHA3-256 (Keccak) has no equivalent cryptanalytic progress — fundamentally different sponge construction. For a chain that aims to survive decades, the margin matters.

Downloads

Latest release on GitHub: lattica-core/lattica/releases

Every release ships: GUI wallet (lattica-qt), node daemon (latticad), CLI tools, and GPU miner (lattica-miner). Linux and Windows. Verify against SHA256SUMS.

Quick Start

Code:

# Start a full node
./latticad -daemon

# Mine with your GPU
./lattica-miner --rpcuser=USER --rpcpassword=PASS

# Or connect to a community pool
# See Discord #mining for pool addresses

DNS seeds: seed.lattica.org / seed.lattica.uk / seed.lattica.us

What's Next

- Exchange listing in progress
- ResonanceNet — decentralized AI training protocol
- Continued network growth and tooling

Fair Launch Commitment

No premine. No ICO. No dev allocation. No masternodes. No VC. Genesis output is provably unspendable (OP_RETURN). The developer mines on the same terms as everyone else. Code is MIT licensed.


Built by a solo developer in South Korea. Post-quantum from genesis. Bring a GPU.

[Pilatovich Kristian 2]

Hey — I run Chainquiry, a searchable crypto project directory, and I’d like to invite your team to submit a free listing. 

It includes your official links, network, launch date and project information after editorial review:

https://chainquiry.com/list-your-project/

Thanks for reaching out! Just submitted the listing form on Chainquiry. Looking forward to the review.

[lightbit]

Hey — I run Chainquiry, a searchable crypto project directory, and I’d like to invite your team to submit a free listing. 

It includes your official links, network, launch date and project information after editorial review:

https://chainquiry.com/list-your-project/

Thanks for reaching out! Just submitted the listing form on Chainquiry. Looking forward to the review.

Lattica (LTA) is now listed on Chainquiry

Hello Lattica community 👋

Lattica (LTA) has now been added to the Chainquiry cryptocurrency project directory.

Lattica is a post-quantum, Proof-of-Work cryptocurrency built around the Bitcoin Core architecture. Its design replaces vulnerable legacy cryptography with post-quantum alternatives while retaining a familiar UTXO-based blockchain structure.

The Chainquiry profile covers:

• ML-DSA-44 post-quantum transaction signatures
• ML-KEM-768 encrypted peer-to-peer networking
• SHA3-256d GPU Proof-of-Work mining
• Fair launch with no premine, ICO or developer tax
• Wallet downloads, source code and community resources
• Supply, block reward, halving and network specifications

View the Lattica profile on Chainquiry:
https://chainquiry.com/projects/lattica/

Official website:
https://lattica.org/

This is an independent directory listing and does not represent an investment endorsement or guarantee from Chainquiry.

Corrections and properly sourced project updates are always welcome.

[Pilatovich Kristian 2]

.

[fibonacciopstan]

Lattica is an impressive project, especially considering it was written from scratch by a solo developer rather than forked from an existing chain. Implementing ML-DSA-44 signatures and ML-KEM-768 encrypted networking from genesis is a much cleaner approach than attempting a difficult post-quantum migration later.

One thing I would like to understand is how Lattica preserves its public project history outside the source code and blockchain transactions.

The announcement includes important long-term commitments: no premine, no developer allocation, no ICO, an unspendable genesis output, a fixed monetary policy and future plans such as exchange listings and ResonanceNet. However, websites, forum posts, GitHub pages and social media announcements can still be edited, removed or replaced over time.

Does Lattica have a public platform where its official announcements, commitments, roadmap updates, releases and major development decisions are published as permanent, timestamped records that cannot later be altered or deleted?

Please share a link to that platform if one already exists.

[lattica-core]

Lattica is an impressive project, especially considering it was written from scratch by a solo developer rather than forked from an existing chain. Implementing ML-DSA-44 signatures and ML-KEM-768 encrypted networking from genesis is a much cleaner approach than attempting a difficult post-quantum migration later.

One thing I would like to understand is how Lattica preserves its public project history outside the source code and blockchain transactions.

The announcement includes important long-term commitments: no premine, no developer allocation, no ICO, an unspendable genesis output, a fixed monetary policy and future plans such as exchange listings and ResonanceNet. However, websites, forum posts, GitHub pages and social media announcements can still be edited, removed or replaced over time.

Does Lattica have a public platform where its official announcements, commitments, roadmap updates, releases and major development decisions are published as permanent, timestamped records that cannot later be altered or deleted?

Please share a link to that platform if one already exists.

Good question. The most permanent record Lattica has is the chain itself — the genesis block embeds "Citi 03/Jan/2026 The trillion-dollar quantum security race is on" and every block since is immutable proof of the network's history.

For project commitments: the whitepaper is published at lattica.org and its hash can be anchored on-chain via OP_RETURN. GitHub commits are timestamped and signed. The Bitcointalk ANN thread itself is a public, timestamped record — I can't edit your post or lightbit's, and the original announcement is permanently visible.

I haven't set up a dedicated immutable announcement platform yet. If OPSTAN offers that kind of service, I'd be interested to hear more — anchoring project commitments on a PoW chain fits the philosophy.

[Kairo0001]

2026-07-25T15:10:34Z torcontrol thread start

2026-07-25T15:10:34Z Imported mempool transactions from file: 0 succeeded, 0 failed, 0 expired, 0 already there, O waiti

of for initial broadcast

2026-07-25T15:10:34Z initload thread exit

2026-07-25T15:10:34Z Bound to 127.0.0.1:9334

2026-07-25T15:10:34Z Bound to [::]:9333

2026-07-25T15:10:34Z Bound to 0.0.0.0:9333

2026-07-25T15:10:34Z Loaded 0 addresses from "anchors.dat"

2026-07-25T15:10:34Z 0 block-relay-only anchors will be tried for connections.

2026-07-25T15:10:34Z init message: Starting network threads...

2026-07-25T15:10:34Z net thread start

2026-07-25T15:10:34Z dnsseed thread start

2026-07-25T15:10:34Z addcon thread start

2026-07-25T15:10:34Z Loading addresses from DNS seed seed. lattica.us.

2026-07-25T15:10:34Z opencon thread start

2026-07-25T15:10:34Z init message: Done loading

2026-07-25T15:10:34Z msghand thread start

2026-07-25T15:10:34Z Loading addresses from DNS seed seed. lattica.uk.

2026-07-25T15:10:34Z Loading addresses from DNS seed seed. lattica.org.

2026-07-25T15:10:34Z 0 addresses found from DNS seeds

2026-07-25T15:10:34Z dnsseed thread exit

2026-07-25T15:10:36Z connect() to 127.0.0.1:9051 failed after wait: No connection could be made because the target machi

me actively refused it. (10061)

2026-07-25T15:10:36Z [warning] tor: Error connecting to address 127.0.0.1:9051

2026-07-25T15:10:36Z [warning] tor: Initiating connection to Tor control port 127.0.0.1:9051 failed

2026-07-25T15:10:39Z connect() to 127.0.0.1:9051 failed after wait: No connection could be made because the target machi

me actively refused it. (10061)

2026-07-25T15:10:39Z [warning] tor: Error connecting to address 127.0.0.1:9051

2026-07-25T15:10:39Z [warning] tor: Initiating connection to Tor control port 127.0.0.1:9051 failed

2026-07-25T15:10:43Z connect() to 127.0.0.1:9051 failed after wait: No connection could be made because the target machi

ne actively refused it. (10061)

2026-07-25T15:10:43Z [warning] tor: Error connecting to address 127.0.0.1:9051

2026-07-25T15:10:43Z [warning] tor: Initiating connection to Tor control port 127.0.0.1:9051 failed

2026-07-25T15:10:47Z connect() to 127.0.0.1:9051 failed after wait: No connection could be made because the target machi

me actively refused it. (10061)

2026-07-25T15:10:47Z [warning] tor: Error connecting to address 127.0.0.1:9051

2026-07-25T15:10:47Z [warning] tor: Initiating connection to Tor control port 127.0.0.1:9051 failed

2026-07-25T15:10:52Z connect() to 127.0.0.1:9051 failed after wait: No connection could be made because the target machi

me actively refused it. (10061)

2026-07-25T15:10:52Z [warning] tor: Error connecting to address 127.0.0.1:9051

2026-07-25T15:10:52Z [warning] tor: Initiating connection to Tor control port 127.0.0.1:9051 failed

2026-07-25T15:10:59Z connect() to 127.0.0.1:9051 failed after wait: No connection could be made because the target machi

me actively refused it. (10061)

2026-07-25T15:10:59Z [warning] tor: Error connecting to address 127.0.0.1:9051

2026-07-25T15:10:59Z [warning] tor: Initiating connection to Tor control port 127.0.0.1:9051 failed

2026-07-25T15:11:09Z connect() to 127.0.0.1:9051 failed after wait: No connection could be made because the target machi

me actively refused it. (10061)

2026-07-25T15:11:09Z [warning] tor: Initiating connection to Tor control port 127.0.0.1:9051 failed

2026-07-25T15:11:09Z [warning] tor: Error connecting to address 127.0.0.1:9051

---------------------------------------------------------------------------------------

# 1 · start a full node
./latticad -daemon

why can't it connect? I am running it on Windows 10

[cryptomaxsun]

No connection, no nodes.

[lattica-core]

No connection, no nodes.

The v0.1.3 release included a transport layer fix but the DNS seed nodes needed to be restarted with the updated binary. They were still running v0.1.2, which caused a version mismatch — new nodes couldn't complete the handshake with the old seeds.

The seed nodes have been updated now. Please restart your node and it should find peers within a few minutes. Make sure port 9333 is not blocked by your firewall.

Sorry for the inconvenience — this was my oversight in the rollout, not a problem on your end.

[cryptomaxsun]

Thanks for the reply!
I was able to launch the miner.
How can I find out the hashrate rx 480 4gb?

[lattica-core]

Thanks for the reply!
I was able to launch the miner.
How can I find out the hashrate rx 480 4gb?

lattica-miner -benchmark — measures the card and exits, no node needed:


GPU: <your card>
SHA3-256d hashrate: 1378.271 MH/s  (1.3783 GH/s)
That is the output on an RTX 5090 for reference. An RX 480 will land far below it — it is a 2016 Polaris card, so expect somewhere in the low hundreds of MH/s.

If you have more than one GPU, pick it with -device=<n> (default is 0):


lattica-miner -benchmark -device=1
While actually mining, the miner does not print a running hashrate — it only reports when it finds a block. So run -benchmark once to learn your card's speed, then mine with -address=.... Your effective share of the network is that number against the chain's total hashrate, which lattica-cli getmininginfo shows.