AntiQua

Hey everyone

A forum is more than a place to post – for a project like AntiQua it has to be safe, private and usable for people from all over the world. Off-the-shelf plugins only got us part of the way there, so we built our own. This post walks you through every plugin we developed ourselves: why it exists and what it does for you.

Everything below runs on our own server. No tracking services, no third-party translation APIs, no data brokers.

---

1. Seed Protection

Why we built it
The number one way people lose crypto in communities is not a hack – it's a moment of panic. Someone's wallet won't sync, they ask for help and paste their recovery words into a post. Or a "support agent" sends a friendly DM asking for them. We wanted the forum itself to step in before that happens.

What it does

• Blocks recovery phrases in posts – topics, replies, edits and titles are checked before anything is saved. It understands our own post-quantum AIP-39 standard (24, 36 and 48 words, including checksum verification) as well as classic BIP-39 phrases, in all ten official wordlist languages.
• Blocks post-quantum private keys – ML-DSA and ML-KEM secret keys are recognised by their standardised size, whether pasted as hex or Base64. Transaction hashes and public keys are not affected.
• Protects your chats – without reading them. Before a chat message leaves your device, your own browser checks it and asks "Are you sure?" if it looks like a seed phrase or key. Nothing about this check is ever sent to our server. We do not scan, log or monitor private messages. Period.
• Scam warnings – if a message or post asks for your recovery phrase, pushes remote-access tools like AnyDesk, or promises to "double your coins", you'll see a warning right above it. This also runs only in your browser, and it speaks 12 languages.
• Impersonation protection – nobody can register or rename themselves to something that looks like a team member (think BIythex with a capital I, lookalike characters from other alphabets, or names like "Official Support").

Reminder: The AntiQua team will never ask for your recovery phrase, your private key or remote access to your computer. Anyone who does is a scammer.

---

2. Translate Button

Why we built it
Post-quantum security is a global topic, and good ideas shouldn't get lost because they were written in a different language. At the same time, we didn't want to ship your posts off to Google or DeepL.

What it does

• Every post has a translate button (next to Reply). One click translates the post – and the topic title for the first post – into your language. One more click shows the original again.
• Translation runs on LibreTranslate, self-hosted in its own container on our server. Your text never leaves AntiQua infrastructure.
• Supported languages: English, German, Spanish, French, Italian, Dutch, Polish, Portuguese, Russian, Turkish, Ukrainian and Chinese.
• Smart target language – your chosen forum language wins; if you never set one, your browser's language is used.
• Code stays code – code blocks, @mentions and links are left untouched, so commands and addresses are never "translated" into nonsense.
• Translations are cached, so popular posts load instantly for the next reader.

Honest note: this is machine translation. It's great for understanding a post, not for publishing a legal contract.

---

3. Legal Pages

Why we built it
A serious project needs a serious foundation. We wanted a legal notice, a privacy policy and community guidelines that describe what this forum actually does – not a generic template copied from somewhere.

What it does

• Adds the Legal notice, the Privacy policy and the Community guidelines – linked in the footer of every page.
• Every page is available in German and English with a one-click language toggle.
• The privacy policy documents the real data flows of this installation: self-hosted translation, local-only chat checks, what we store and for how long.
• You can withdraw your reCAPTCHA consent directly on the privacy page at any time.

---

4. Identicons

Why we built it
Rows of identical grey default avatars make it hard to tell who is who. We wanted every member to have a recognisable face from day one.

What it does

• Generates a unique, crisp 512 px identicon for every member who hasn't uploaded a picture.
• Your own uploads and your GitHub avatar are never overwritten – the identicon only fills the gap.

---

5. Emoji Packs

Why we built it
Emojis are half of how a community talks. We wanted full control over which packs are loaded and an easy way to add our own.

What it does

• Admins get a clear overview of every loaded emoji pack, including attribution and licence.
• Custom packs can be added simply by dropping images into a folder – no code required.
• Adds the emoji button to Quick Reply, so you don't have to open the full editor just to send a

---

Also under the hood

Besides our own plugins, we maintain fixes for several community plugins we rely on – for example reCAPTCHA v3 support that only loads after you give consent, a cleaner admin view for two-factor authentication, and a fully translated mentions admin panel. Every change is version-controlled on our own Git server, so updates never silently undo them.

---

Our principles in one line

Self-hosted. Privacy first. Built for a global post-quantum community.

We'll keep posting updates like this here in Development. Replies are very welcome: bugs, ideas, wishes – let us hear them

Cheers,
Blythex

Thanks for the warm welcome! Excited to be part of the AntiQua community. Looking forward to following the project's progress and contributing where I can.

Hey, and welcome to AntiQua!

Whether you write code, run a miner, read NIST papers for fun, or simply believe that your money should stay yours – even in a world with quantum computers – you belong here.

This is the place to say hello. No question is too basic, no background too unusual. Everyone started somewhere.

---

Tell us about yourself

Just reply to this topic. If you're not sure what to write, copy this and fill in whatever you like – every line is optional:

Nickname:
Where I'm from:        (country or region is plenty)
How I found AntiQua:
What I'm into:         mining / running a node / development /
                       cryptography / economics / just curious
My background:         developer, miner, student, trader, ...
One thing I'd love to see in AntiQua:

Write in your own language if you prefer. Every post has a Translate button, so the rest of us can still read along.

---

Stay safe while you say hi

A few simple habits keep you and your coins protected:

• Never share your recovery phrase or private keys – not here, not in chats, not with "support". This forum blocks them automatically, but don't rely on that alone.
• Keep personal details to yourself. No real address, phone number or private e-mail needed – a nickname is perfect.
• Be careful with private messages. The team will never message you first asking for funds, keys, or "verification". Offers of airdrops, investments or "recovery services" in DMs are scams.
• Official news only comes from the Announcements category. If it's not there, it's not official.

---

Where to go next

You want to…	Go here
Understand what AntiQua is	Welcome to the AntiQua Community Forum
Learn why post-quantum matters	Why Post-Quantum? The Threat is Real
Get help with a problem	Support – start with How to Get Help Fast
Mine or run a node	Mining & Nodes
Talk code and protocol	Development · Technology
Discuss tokenomics	Economics & ICO
Report a vulnerability	Security

Please take a minute to read the forum rules – they're short, we promise.

---

I'll go first

I'm Blythex. I work on the AntiQua core and look after this forum and our Git. I read every introduction here – so say hi, tell us what brought you, and don't be shy about asking questions.

Glad you're here. Let's build something that lasts.

AntiQua has undergone two full external audit rounds:

NightShift Audit — 47 findings identified and remediated.
Draikoon Audit — 11 findings, all CRITICAL and HIGH resolved.

Production security decisions include: hard-abort on plaintext key handling, mempool RBF lockout, DNS eclipse fallback seeders, and mnemonic export PIN protection.

Bug bounty program incoming. Details to follow.

AntiQua ships with seven built-in smart contract templates, all tested (257/257 passing) :

• NFT
• Escrow
• Token
• Voting
• TimeLock
• RecurringPayment
• Vesting

Custom contracts beyond these templates are on the roadmap. Discussion welcome.

AntiQua spans three repositories:

NodeCore (C++) — The full node. P2P networking, UTXO model, mempool, smart contract VM, RandomX PoW, ACRP chat layer.

Desktop Wallet (C# WPF) — Full-featured Windows wallet with transaction history, smart contract interaction, and encrypted ACRP messaging.

Android Wallet (Kotlin) — Mobile node + wallet. Runs a full AntiQua node on your phone.

All three are developed simultaneously. No forks. Every line written from scratch.

Bitcoin uses BIP-39 mnemonics backed by secp256k1 keys — fundamentally incompatible with post-quantum cryptography. AntiQua implements AIP-39, a custom mnemonic standard designed around ML-DSA-87 key material.

Your seed phrase on AntiQua is quantum-resistant from word one.

Almost every blockchain in use today secures your coins with elliptic-curve signatures (ECDSA or EdDSA). They are fast, compact and safe against every computer we have today. Against a large quantum computer running Shor's algorithm, they are not safe at all.

AntiQua was designed from day one on the assumption that this threat is not hypothetical – it's a matter of when. Here is what that means in practice.

---

What a quantum computer actually breaks

Not everything in a blockchain is equally at risk. The real problem is signatures, not hashing:

Building block	Used for	Quantum attack	Impact
ECDSA / EdDSA	Signing transactions	Shor's algorithm	Broken – the private key can be computed from the public key
RSA, ECDH	Encryption, key exchange	Shor's algorithm	Broken
SHA-256, SHA-3	Hashing, addresses, mining	Grover's algorithm	Weakened – effective security roughly halved (256 → ~128 bit), still considered safe
AES-256	Symmetric encryption	Grover's algorithm	Weakened the same way, still considered safe

In plain words: whoever controls a large enough quantum computer can derive your private key from your public key – and sign transactions as if they were you.

---

Why "not yet" is not a good excuse

1. Public keys live on-chain forever.
On most blockchains, your public key becomes visible the moment you spend from an address – and it stays in the chain history permanently. Every coin behind an exposed public key is a target the day a capable quantum computer exists. That includes millions of coins already sitting in such addresses today.

2. Migrating a live blockchain takes years.
Switching the signature scheme of an existing network needs consensus, new wallets, exchange support – and every single holder moving their funds. Coins whose owners lost their keys or stopped paying attention can never be moved to safety.

3. The standards are already here.
In August 2024, NIST published the first post-quantum standards: FIPS 203 (ML-KEM) and FIPS 204 (ML-DSA). NIST's transition plan proposes to deprecate quantum-vulnerable algorithms like RSA and elliptic-curve cryptography after 2030 and disallow them after 2035. The rest of the industry is starting its migration now.

4. Attackers can wait.
"Harvest now, decrypt later" is not science fiction: data and public keys collected today can be attacked the day the hardware is ready.

---

How AntiQua handles it

AntiQua doesn't bolt post-quantum cryptography onto an old design. It is the design:

Layer	AntiQua uses	Standard
Signatures	ML-DSA-87	FIPS 204 · NIST security category 5
Key encapsulation	ML-KEM-1024	FIPS 203 · NIST security category 5
Hashing	SHAKE-256	FIPS 202 (SHA-3 family)
Seed phrases	AIP-39	our own post-quantum mnemonic standard
Proof of Work	RandomX	CPU-friendly, ASIC-resistant mining

NIST security category 5 is the highest level NIST defines: breaking it must be at least as hard as brute-forcing a key for AES-256.

And because post-quantum signatures are there from the genesis block, there is no legacy signature scheme to migrate away from – no future hard fork just to become quantum-safe.

---

The honest part: where the cost is – and how we contain it

Post-quantum security isn't free. The keys and signatures are much larger than what Bitcoin or Ethereum use:

	Public key	Signature
ECDSA (secp256k1)	33 bytes	~72 bytes
ML-DSA-87	2,592 bytes	4,627 bytes
AntiQua combined key (ML-DSA-87 + ML-KEM-1024)	4,160 bytes	–

A naive design would store all of that forever, on every node. AntiQua doesn't. Signatures are expensive once – on the wire and when a block is first accepted. After that, the network works with hashes, compact commits and checkpoints.

Verify once, then commit compact

When a block is connected, every transaction is verified in full – including its ML-DSA signature. What gets written to the ledger afterwards is a compact record: the 32-byte transaction hash, inputs, outputs and amounts – without signature and public key. The Merkle root and the block header hash bind that record to the verified original. Full and light nodes therefore store the proof of validation, not the proof itself.

Commitments instead of bodies in gossip

Block announcements carry transaction commitments – again 32 bytes per transaction. The full block with all signatures only goes to a subset of verifying nodes, or to whoever explicitly requests it.

Checkpoints instead of re-checking history

• UTXO snapshots every 5,000 blocks record the state hash, total coin supply and UTXO root. A starting node syncs from the latest snapshot – checking proof of work, Merkle roots and transaction hashes – instead of re-verifying every historical signature.
• Finality checkpoints every 100 blocks are signed by miners and confirmed by a quorum. Once a height is finalized, reorganisations before it are locked. That's a handful of large signatures for finality – not millions of transaction signatures on disk.

Why this stays secure

The check always happens before anything is discarded: a compact record is only valid because the full transaction was accepted first. Archive nodes keep the complete bodies, so anyone who needs the original – for an initial sync or a wallet – can fetch it and verify it again against the committed hash.

In short: post-quantum signatures cost bandwidth and CPU once. Storage stays lean. And even if it didn't: storage gets cheaper every year – a stolen private key never gets un-stolen.

---

Let's talk

Questions, doubts, counter-arguments? That's exactly what this category is for. Happy to go deep on any part of the stack – ask away

Want more? Read how AIP-39 keeps your seed phrase quantum-resistant, or check our Security Audit History.

— Blythex

As of March 31, 2026, the AntiQua testnet went live with four simultaneous nodes syncing correctly across Hetzner, home node, and two Android devices.

The full stack is operational:

• NodeCore (C++)
• Desktop Wallet (C# WPF)
• Android Wallet (Kotlin)
• ACRP encrypted chat layer on port 20557

Stay tuned.

Welcome to the official AntiQua community forum

This is the home base for everyone building, running or simply curious about AntiQua – a blockchain designed from the ground up for the post-quantum era. Whether you're a developer, a miner, a cryptography nerd or just found us today: you're in the right place.

---

AntiQua at a glance

Cryptography	NIST Level 5 – ML-DSA-87 signatures, ML-KEM-1024 key exchange, SHAKE-256 hashing
Consensus	RandomX Proof of Work
Supply	56,000,000 AQA – hard cap, 75 % mined + 7 % node rewards
Launch	Fair launch · clean genesis block · no VC allocation · funds multi-sig or vested
Codebase	Built from scratch – no forks, no shortcuts
Status	Testnet live since March 31, 2026

---

New here? Start reading

1. Why Post-Quantum? The Threat is Real – why today's blockchains are at risk and what AntiQua does differently
2. AIP-39 – Our Post-Quantum Mnemonic Standard – how your seed phrase stays quantum-resistant
3. AntiQua Testnet is Live – where the network stands today
4. Repository Overview – NodeCore, Desktop Wallet and Android Wallet
5. Tokenomics – the 56M AQA supply, the Relay Reward Lottery, the four funds and the rules that bind them
6. Security Audit History – our external audits and what came out of them

---

Find your way around

• Announcements – official news from the core team
• Technology – post-quantum cryptography, consensus and protocol internals
• Development – NodeCore, wallets, code and bug reports · follow the NodeCore Changelog
• Mining & Nodes – running a node and mining AQA with RandomX
• Support – stuck? Read How to Get Help Fast, then ask away
• Economics & ICO – tokenomics, supply and distribution
• Security – audits, hardening and responsible disclosure
• Community – introductions and everything else

---

Your first steps

• Say hello in Introduce Yourself – tell us who you are and what brought you here
• Watch the NodeCore Changelog (bell icon → Watching) to get notified about every core update
• Write in your own language – every post has a translate button next to Reply
• Have a quick look at our Community guidelines – short and to the point

---

Stay safe: The AntiQua team will never ask for your recovery phrase, your private keys or remote access to your computer. Anyone who does is a scammer – please report them.

---

We're building AntiQua in the open, and this forum is where it happens. Ask questions, challenge our decisions, report bugs, share ideas – we read everything.

Glad to have you here.

— Blythex, Lead Developer