AntiQua

Blythex

Found a bug? Missing a feature? From today there's a proper place for it.

BugHive is live: https://bugs.antiqua-blockchain.com

It's our own bug tracker – self-hosted, open to read for everyone, and wired to the same team that writes the code.

One space per part of AntiQua

Project	What belongs there
Core	NodeCore: consensus, P2P, mempool, mining, wallet logic
Windows Desktop	the desktop wallet
Windows CLI	command-line node and wallet
Linux	node and wallet on Linux
Android	the Android app
Forum	this forum and our own plugins

Inside each project you'll find Bugs, Features and Backlog – backlog meaning "accepted, but not scheduled yet". So you can see not only what's broken, but also what's planned.

How to report something useful

You need an account to write, and you sign in with Telegram – no password, no e-mail address.

A good report takes two minutes and saves hours:

What happened:
What I expected:
Steps to reproduce:
Version / platform:

Screenshots help – just make sure they don't show a recovery phrase, a private key or a balance you'd rather keep to yourself.

Search first. If your issue already exists, a comment with your details is worth more than a second report.

Security bugs: please, not in public

If you found something that could cost people money – consensus, signatures, wallet, node – do not post the details publicly, neither here nor in BugHive.

Report it through the Security category so we can fix it first
In BugHive, reports labelled security are removed from public lists on the server; the direct link and the comments return "not found". Only the team and the reporter can see them.
Responsible reports are what the Bug Bounty Fund (3,000,000 AQA) exists for – the details are in the tokenomics post

What's public

Reading is open to everyone, also without an account: projects, bugs, features, comments. Only writing needs a login. Keep that in mind when you attach logs – blur what shouldn't be public.

Staying up to date

Changes to BugHive itself are posted in the BugHive Changelog here in Development. Click the bell icon there and choose Watching if you want to follow along.

Go and try it: https://bugs.antiqua-blockchain.com – even a small report helps. Every bug that gets found before mainnet is one that never costs anyone a coin.

— Blythex

Blythex

Mining secures the chain. But a blockchain also needs nodes that pass things along – transactions, blocks, compact-block help. That work costs bandwidth and uptime, and on most chains it pays exactly nothing.

AntiQua pays for it. 4,000,000 AQA – 7.14 % of the total supply – belong to the Relay Reward Lottery, and the rules are enforced by consensus, not by a server we run.

How it works

Every block from height 5 onwards can pay 1.5 AQA to exactly one registered relay node. The payout is the second output of that block's coinbase, right next to the miner's reward – as public and verifiable as any other transaction.

Who wins is not decided by us and not by a queue:

All eligible candidates are sorted by their payout address
The winner's index is drawn from SHAKE-256 over the previous block's hash, with its own domain tag AQA/RELAY-LOTTERY-IDX/v1
Every node computes the same winner and rejects a block that pays someone else

If there is no eligible candidate, nobody gets a relay payout for that block – and the miner keeps the fees untouched.

How to register

Registration is an on-chain transaction, not a setting in a config file. It carries three things:


Bond	at least 0.5 AQA, locked in a dedicated output. The coin must already belong to your payout address, and coinbase coins need their 100 confirmations first
Proof-of-work	a RandomX (light) proof with its own domain `AQA/RELAY-REG-POW/v3`, over a block hash from the last 12 blocks. Difficulty scales with the number of candidates (target: 100)
Ownership proof	the transaction must spend a coin that belongs to the payout address, so nobody can register an address they don't control

In the desktop wallet that's the Node Rewards view; the CLI equivalent is relay register <payout address> after loading your wallet.

Not on Android. The Android build has no RandomX, so registration there fails by design. Use the desktop wallet or the CLI.

From registration to your first chance

Block H        registration is included
H + 6          activation_height – the candidate exists
H + 12         first block you can actually win (bias guard)
H + 1,440      registration expires (~10 days mainnet, ~2 days testnet)

After a win, your payout address has to sit out 144 blocks – about a day on mainnet – before it can win again. So a single node cannot collect block after block, and an expired registration simply drops out: the reward follows nodes that are actually online.

What it pays, and for how long


Reward per block	1.5 AQA from the relay budget
Total budget	4,000,000 AQA
First possible block	height 5
Duration	roughly 50 years on mainnet at 10-minute blocks
When the budget runs out	5 % of that block's fees go to the relay winner instead

The budget is not created in one block like the ecosystem funds. It trickles out block by block, and every node tracks exactly how much has been emitted so far.

What protects the draw – and what doesn't

Honest engineering means naming the limits too.

What is protected:

The bond makes mass registration expensive, and the proof-of-work makes it slow
At most 5 registrations per block, and at most 32 waiting in the mempool
Activation delay and bias guard (6 + 6 blocks) stop last-minute registrations aimed at the very next draw
Cooldown of 144 blocks per payout address
Fail-closed validation: if a node cannot check the bond, the block is rejected. A coinbase paying the wrong winner, or paying the miner too much, is invalid

What is not fully solved, and we say so openly:

The draw uses the previous block's hash. A miner who is building that previous block can, in principle, grind it so that the next block favours their own node. This is a known, documented limitation of the current design, not an oversight. The bias guard does not remove it.

We consider that acceptable for now: the gain per block is 1.5 AQA, grinding costs real hashing, and the cooldown caps how often one address can benefit. If it ever becomes worthwhile, the seed can be hardened – and any such change would be announced in the Core Changelog first.

How to check it yourself

Block detail in the explorer shows the relay winner and whether the payout came from the budget or from the fee fallback
Coinbase breakdown of the block carries relay_lottery_sat and the winner address
In the desktop wallet: the Node Rewards view shows candidates, budget and your own status

Where it fits in

Who	Gets paid	From
Miners	block reward + all fees in the block	42,000,000 AQA over the halvings
Relay nodes	1.5 AQA per block	4,000,000 AQA, then 5 % of fees
Ecosystem funds	one-time, in blocks #1–#4	10,000,000 AQA

More: AntiQua Tokenomics · How Fees Work

Questions?

Wondering whether your VPS is enough, how long the registration proof-of-work takes, or what happens when your node goes offline? Ask below.

— Blythex

Blythex

BugHive update – 20 Sep 2026
Type: Feature
Action required: No

What's new – six project spaces, issue types, a real backlog and protected security reports
Details – below

Projects – every part of AntiQua now has its own space: Core, Windows Desktop, Windows CLI, Linux, Android and Forum.

Issue types – every entry is now a Bug, a Feature or a Task. You pick the type when you create it.

Backlog is a real status – "accepted, but not scheduled yet". Each project has three views: Bugs, Features and Backlog, plus All entries. The board shows Backlog as its own first column.

Security reports are protected – entries labelled security are removed from public lists on the server, and the direct link and comments return "not found". Only the team and the reporter can see them.

Login via Telegram – no password needed. Two-factor authentication is available in your profile settings.

Reading is public – bugs, features and projects can be read without an account. Only creating and commenting needs a login.

Take a look: https://bugs.antiqua-blockchain.com

Blythex

Hey everyone

This thread is the official changelog for BugHive, our own bug tracker at https://bugs.antiqua-blockchain.com. Whenever something changes there, it gets posted here as a new entry, newest at the bottom.

If you report bugs, request features or just want to follow how AntiQua is built, this is the one thread to keep an eye on.

What BugHive is

BugHive is where bugs, feature requests and planned work live – separate from the forum, so discussions stay here and tracked issues stay there.

Every project has its own space:

Project	What belongs there
Core	NodeCore: consensus, P2P, mempool, mining, wallet logic
Windows Desktop	the desktop wallet (GUI)
Windows CLI	command-line node and wallet
Linux	node and wallet on Linux
Android	the Android light wallet
Forum	this forum and our own plugins

Within a project you'll find Bugs, Features and Backlog – backlog meaning "accepted, but not scheduled yet".

What gets posted here

New features in BugHive itself – new views, filters, workflow changes
New projects added to the tracker
Security and access changes – who can see what
Maintenance – downtime, migrations, data cleanups
Process changes – how to report, what a status means

How every entry is structured

So you can tell at a glance whether something affects you, each entry follows the same format:

BugHive update – date
Type: Feature · Fix · Security · Maintenance
Action required: No / Yes – what you need to do

What's new – short summary
Details – the changes in full

Never miss an update

Click the bell icon on this topic and choose Watching. You'll get a notification every time a new entry is posted here.

Reporting safely

Never post exploit details for a security bug in public – not in BugHive, not in the forum. Report it through the Security category so the team can fix it first.
Reports labelled security in BugHive are hidden from public lists and links. Only the team and the reporter can see them.
Never share your recovery phrase, private keys or passwords in a bug report. Blur them in screenshots and log files.
Everything else in BugHive is publicly readable, also without an account. Keep that in mind when you attach logs.

Questions & discussion

To keep this changelog clean and easy to read, replies are closed here. Got a question or an idea? Open a new topic here in Development – we read everything.

Cheers,
Blythex

Blythex

What does it cost to send AQA? Who gets that money? And how does AntiQua stop spam without making everyone pay for it?

This post explains the AntiQua fee system exactly as it works in the node software today – no marketing numbers, just the rules the network enforces. Every number below was re-checked against the NodeCore source in September 2026.

TL;DR

A tiny base fee + your tip. Every transaction pays a small, fixed minimum of 100 satoshi per KiB – a typical post-quantum payment about 0.00001 AQA. On top, you choose a tip: a higher tip gets you confirmed faster.
Every fee goes to the miner. Nothing is burned, nothing goes to a hidden account.
More inputs cost more – because every input carries a large post-quantum signature.
Spam is stopped with work, not money: from the 6th pending transaction, your wallet has to solve a tiny proof-of-work.
Everything is exact: all amounts are whole satoshi – no rounding, no floating point.

What a fee actually is

On AntiQua, the fee isn't a separate field you can fake – it's simply what's left over:

fee = sum of inputs − sum of outputs

Everything you don't send to a recipient or back to yourself as change is the fee, calculated to the exact satoshi (1 AQA = 100,000,000 satoshi). The node checks that this amount covers everything the transaction requires – otherwise it's rejected.

The fee is also part of the transaction hash: if you change the fee, you get a new transaction ID. Nobody can alter it on the way.

Base fee + your tip

Your fee has two parts:

The base fee – a fixed minimum set by consensus: 100 satoshi (0.000001 AQA) per started KiB of transaction size. "Started" is literal: 9,194 bytes round up to 9 KiB. A typical post-quantum payment is around 9–10 KiB, so the base fee is roughly 900–1,000 satoshi – about 0.00001 AQA. It applies to every transaction from block 1 on.
The tip – whatever you add on top for the miner:

Low tip – still valid (even a tip of 0 is accepted, as long as the base fee is covered; the dust limit and spam protection still apply), but you may wait longer when blocks are busy
Higher tip – miners pick your transaction first

Fixed, not adjustable: the base fee depends only on the block height – no node, miner or admin can raise it on the fly or tune it to its own mempool. The consensus code allows a ceiling of 1,000× the minimum, but the active value is the minimum, and nothing in the node moves it. Changing it would require a network upgrade, announced in the Core Changelog first.

Real example from our testnet milestone: sending 10 AQA with a 0.01 AQA tip – the miner collected the fees on top of the block reward, the receiver got exactly 10 AQA. (See the milestone post) That payment was made before the base fee went live – today the wallet would add about 0.00001 AQA on top.

What your wallet suggests

You don't calculate any of this by hand. The wallet adds the base fee automatically (it comes out of your change) and offers three lanes:

Lane	What it does
Economy	No extra tip at all – just the base fee. Fine when you're not in a hurry.
Recommended	The median tip per KiB that the network is currently paying, never less than the base rate.
Next block	The 90th percentile of current tips, at least one step above Recommended.

When the wallet has seen no recent traffic – an empty or fresh mempool – it falls back to the base rate for Recommended and twice that for Next block.

These lanes are wallet policy, not consensus. Another wallet may suggest different numbers; the network only enforces the base fee.

What happened to the relay fee?

Older wallet builds showed a third field called relay fee, and our earlier testnet posts mention it. It no longer has any role. The node requires zero for relay: the amount a transaction must cover is base fee + tip (+ contract deployment fee), nothing else.

The name always caused the same misunderstanding, so to be clear: a relay fee never went to relay nodes. Relay nodes are paid only through the Relay Reward Lottery – 1.5 AQA per block from its own 4 million AQA budget, never out of your transaction.

In practice: if your wallet still shows the field, leave it at 0 and use the tip. The tip is strictly better anyway: both raise your fee rate equally, but only the tip counts as the tie-breaker when two transactions have the same score.

Footnote: once the lottery budget is used up (in roughly 50 years), 5 % of all fees in a block go to the lottery winner. That's a share of the block's total fees – not "the relay fee goes to relays".

Why more inputs cost more

Every coin you spend (an input) has to be signed – and post-quantum signatures are big, several kilobytes each. A transaction that gathers many small coins is heavy for every node on the network. So the required fee grows with the number of inputs:

Inputs	Fee factor
1	1.00×
2	1.05×
3	1.30×
4	1.60×
5 or more	2.00×

The factor applies to base fee and tip together, and it also lowers a transaction's priority in the mempool – it sits in the divisor of your fee rate, so a heavy transaction ranks below a light one paying the same absolute amount.

Practical tip: if your wallet has lots of tiny coins, consolidate them once in a quiet moment. At five inputs you are paying double the floor on every send.

Change that disappears into the tip

Sometimes a payment leaves a few hundred satoshi over. Your wallet will not hand that back as change, and that is deliberate:

Leftover below 1,000 satoshi always becomes extra tip. An output that small would be invalid anyway – see the dust limit.
Leftover up to 50,000 satoshi may optionally be folded into the tip instead of creating a new coin, to keep your wallet from filling up with crumbs that cost more to spend later than they are worth.
Anything larger comes back to you as a normal change output.

So if the fee on your receipt looks slightly higher than the lane you picked: that is your own leftover change, not a surcharge.

Who gets confirmed first

Miners sort waiting transactions by a simple score:

Fee per KiB – how much you pay relative to the size of your transaction
Divided by the input factor – heavy transactions rank lower
Contract deployments get a small boost (see below)

On a tie: the higher tip wins, then the older transaction, then the smaller hash. Completely deterministic – no favourites.

The mempool holds up to 50,000 transactions or 500 MiB, whichever comes first.

What if I pay too little?

Then the transaction never enters the mempool, and a transaction that is not in the mempool is never passed on to anyone. You get an error straight away – FEE_TOO_LOW if the amount misses the policy floor, FEE_INSUFFICIENT if it covers the floor but not everything the transaction owes.

There is no second, lower "minimum relay fee" hiding behind this one. What the floor says is what the network takes.

And no, a light node isn't a way around it. A transaction gossiped in from a light client runs through exactly the same check as any other – the light path only serialises the fee fields, it never applies a floor of its own.

Where the money goes

Every fee in a block goes to the miner who found it:

Miner reward = block reward (50 AQA, halving) + all fees in the block

Nothing is burned. Fees don't disappear, they pay the people securing the network.
Relay nodes are paid separately – through the Relay Reward Lottery, 1.5 AQA per block from its own 4 million budget, not by taking a cut of your fee. (Details in the tokenomics post)
In the far future – once the lottery budget is used up after roughly 50 years – 5 % of the block fees go to the relay winner, the rest stays with the miner.

Spam protection without making everyone pay

Making fees high enough to stop spam would make the network expensive for everyone. AntiQua keeps the base fee tiny and adds a separate limit instead:

1. Micro proof-of-work

Your first 5 pending transactions are completely normal.
From the 6th pending transaction (from the same sender), each one must carry a small proof-of-work – its hash needs 14 leading zero bits. For a normal user that's a blink; for someone trying to flood the network with thousands of transactions, it adds up fast.

2. A hard ceiling per sender

The same owner can have at most 25 unconfirmed transactions waiting at once. Number 26 is refused with QUOTA_EXCEEDED until some of them confirm.
That is the real admission limit, and it's the same number in the mempool and in the node's submit check. If you have read about 100, 200 or 1,000 anywhere: those numbers exist in older material but no code path enforces them.

Both are node policy, not consensus: they govern what a node accepts into its own mempool and passes on.

Plus the dust limit: outputs smaller than 0.00001 AQA are invalid, so nobody can clog the chain with worthless crumbs. How the dust limit works

Smart contract deployment fees

Deploying a smart contract adds a small, fixed deployment fee on top – depending on the template:

Template	Base deployment fee
Escrow	0.0001 AQA
Time-Lock	0.00015 AQA
Token · NFT · Vesting	0.0002 AQA
Voting	0.00025 AQA
Recurring payment	0.0003 AQA

The deployment fee can rise up to 5× when the chain is busy – calculated only from on-chain data (block timing and number of contracts), so every node arrives at exactly the same number. Deployments also get a 15–25 % priority boost in the mempool, so contracts don't get stuck. Calling a contract later costs a normal transaction fee.

The rules in one place

Fee = inputs − outputs, exact to the satoshi, part of the transaction hash
Base fee 100 sat per KiB (consensus, from block 1) + your tip. There is no relay fee any more – the node requires zero for relay
More inputs → higher fee factor and lower priority; the factor hits base fee and tip together
Leftover change below 1,000 satoshi always becomes tip
100 % of fees to the miner, nothing burned – relays are paid by the lottery
Micro proof-of-work from the 6th pending transaction; at most 25 unconfirmed per sender
Contract deployments: small fixed fee by template, up to 5× under load

Questions?

Wondering what fee to set, or how this compares to Bitcoin or Ethereum? Ask below – happy to explain.

— Blythex

Blythex

How many AQA will ever exist? Who gets them – and how can you check that we keep our word?

This post lays out the AntiQua tokenomics in plain language: the total supply, how new coins are created, how the Relay Reward Lottery pays node operators, what the four ecosystem funds are for, and the rules that bind them. Everything here is enforced by the node software or verifiable on-chain – you shouldn't have to trust us, you should be able to check.

The big picture

Total supply: 56,000,000 AQA – a hard cap, enforced by consensus. The node rejects anything that would exceed it.

Allocation	Amount	Share
Mining rewards	42,000,000 AQA	75.00 %
Relay Reward Lottery	4,000,000 AQA	7.14 %
Charity Fund	4,000,000 AQA	7.14 %
Bug Bounty Fund	3,000,000 AQA	5.36 %
Dev Fund	1,500,000 AQA	2.68 %
Server & Infrastructure Fund	1,500,000 AQA	2.68 %

More than 82 % of all coins go to the people who run the network – 75 % to miners, another 7 % to relay nodes. There is no allocation for VCs. The remaining ~18 % keeps the project secure, running and useful to the world.

Mining: 42 million AQA, earned block by block

Starting reward: 50 AQA per block
Halving: every 420,000 blocks – the first one at block height 420,005
Target block time on mainnet: 10 minutes → a halving roughly every 8 years, twice as long as Bitcoin
Reward floor: the reward never drops below 0.1 AQA – miners always get paid, until the hard cap is reached

Era	Reward per block	Coins in this era	Share of mining supply
1	50 AQA	~21,000,000	50 %
2	25 AQA	~10,500,000	25 %
3	12.5 AQA	~5,250,000	12.5 %
4	6.25 AQA	~2,625,000	6.25 %
…	halving continues down to 0.1 AQA	…	…

On testnet, blocks come every 2 minutes, so everything there runs five times faster – the 8-year figure applies to mainnet.

Relay Reward Lottery – 4,000,000 AQA

Miners aren't the only ones keeping AntiQua alive. Nodes that relay transactions and blocks do essential work too – so they get their own reward.

How it works:

Register your node with a small bond of 0.5 AQA. A registration stays valid for 1,440 blocks (about 10 days on mainnet) and becomes active after 6 blocks.
Every block from height 5 on pays 1.5 AQA to one registered relay node – as a second output of the block's coinbase, right next to the miner's reward.
Fair rotation: a winner has to sit out for 144 blocks (about a day on mainnet) before winning again, and built-in guards prevent anyone from flooding or biasing the draw.
Long-lasting: at 1.5 AQA per block, the 4 million budget lasts around 50 years on mainnet. After that, relays keep earning 5 % of the block fees.

Every lottery payout is part of a block – public and verifiable like any other transaction. The full rules – bond, registration, cooldown and the guards against gaming – are in Relay Reward Lottery. Running a full node? Relay lottery participation is switched on by default in the node config.

How the funds are created: in the open, one block each

The genesis block stays clean: it only contains the genesis message and the normal 50 AQA block reward. No fund money is hidden in it.

Right after genesis, the four ecosystem funds are created in four separate, dedicated blocks. In each of them, the block's coinbase is the fund – nothing else:

Block #0   Genesis           genesis message + 50 AQA mining reward
Block #1   Bug Bounty Fund   3,000,000 AQA
Block #2   Charity Fund      4,000,000 AQA
Block #3   Dev Fund          1,500,000 AQA
Block #4   Server Fund       1,500,000 AQA
Block #5+  mining            50 AQA per block + 1.5 AQA relay lottery

After block #4 the funds are closed for good – there are no further fund blocks, ever. Apart from these four one-time blocks, new AQA can only be created by mining and the relay lottery. No hidden mint, no admin key that prints coins.

The four funds – and the rules that bind them

Bug Bounty Fund – 3,000,000 AQA · Multi-sig 2-of-3

A post-quantum blockchain has to be battle-tested. This fund pays security researchers who find and responsibly report vulnerabilities, and finances professional security audits.

Severity	Guideline reward
Critical	up to 300,000 AQA
High	30,000 – 100,000 AQA
Medium	5,000 – 30,000 AQA

Available on demand – no vesting, because a critical bug can't wait for the next quarter. Every payout needs 2 of 3 signatures.

Charity Fund – 4,000,000 AQA · Multi-sig 2-of-3

Our way of giving back. The community votes on where the money goes, with a focus on environment, education and open source.

Locked in an on-chain vesting contract: 250,000 AQA per quarter, 16 quarters, 4 years – starting with the fund block at mainnet launch
Quarterly community vote on the recipients
Every release needs 2 of 3 signatures

Dev Fund – 1,500,000 AQA · Single-sig, vested

Building a blockchain from scratch costs years of work and real money – servers, tools, audits. This fund recognises the initial development and keeps full-time development going.

The full 1.5 million goes into an on-chain vesting contract
Released linearly over 4 years – no big dump possible

Server & Infrastructure Fund – 1,500,000 AQA · Single-sig, vested

A network needs infrastructure: DNS seeders, archive and full nodes around the world, backups and redundancy.

250,000 AQA available right away to get the infrastructure running
The remaining 1,250,000 AQA released linearly over 5 years

Enforced by the node software: the fund blocks are only created if Bug Bounty and Charity point to multi-sig addresses and Dev and Server to single-sig addresses – anything else is rejected. The vesting contracts use the VESTING template built into NodeCore.

How the fund keys are protected

Cold storage – fund wallets are created and signed on offline machines that never touch the internet
Separated backups – recovery phrases are stored on paper in several physically separate locations
Public announcements of large transfers – before they happen
Quarterly transparency reports here in the forum: balance of every fund, every payout with amount, purpose and transaction hash, charity votes, current mining reward and how much of the relay budget has been paid out

Verify it yourself

Once mainnet is live, anyone can check with a node or the block explorer:

Block #0 – clean genesis, 50 AQA
Blocks #1–#4 – exactly 3M / 4M / 1.5M / 1.5M AQA to the four fund addresses
Every block from #5 – 50 AQA mining reward (halving) + 1.5 AQA relay output
Fund addresses – every balance and every outgoing transaction

Fund addresses & explorer links – coming soon.
The official mainnet addresses of all four funds will be published after the key ceremony, together with links to the AntiQua block explorer, so you can check every balance and every transaction yourself. We'll add them to this post and announce them in Announcements. Until then: any "fund address" you see anywhere else is not official.

The fine print


Smallest unit	1 AQA = 100,000,000 satoshi
Dust limit	0.00001 AQA – smaller outputs are invalid
Coinbase maturity	mined coins become spendable after 100 blocks
Consensus math	all amounts are integers in satoshi – no floating-point rounding anywhere

Your turn

Questions, doubts, ideas? This is exactly the place for them – good tokenomics survive tough questions. Ask below.

— Blythex

Blythex

NodeCore – Testnet milestone – 18 Sep 2026
Type: Network milestone · Fix
Action required: No for users – testnet node operators: run the current NodeCore build (older builds can't read multi-sig transactions on the wire)

What's new – first post-quantum payment and first 2-of-2 multi-sig spend confirmed on the public testnet
Details – below

Single-sig spend – 10 AQA sent with an ML-DSA-87 signature, confirmed in block #112
Multi-sig wallet – 2-of-2 wallet funded, block #127
Multi-sig spend – two independent ML-DSA-87 signatures verified (2/2), confirmed in block #130 and accepted by the archive node

Fixes

Multi-sig builder set the fee after computing the transaction hash → hash mismatch. Fee is now set first.
P2P serializer dropped the multi-sig fields (required signatures, signer keys, signatures) → receiving nodes computed a different hash. Hashing, mempool and network now share one serialization path.
New regression test: truncated transaction inputs are rejected, full ones round-trip.

Sizes – single-sig tx ~9.4 KB · 2-of-2 multi-sig tx ~15 KB · block with multi-sig spend 27.5 KB

Full write-up with all transaction and block hashes: Testnet Milestones: First Post-Quantum Payments and 2-of-2 Multi-Sig Confirmed On-Chain

Blythex

September 18 was a big day for AntiQua.

In less than two hours, our public testnet crossed three milestones – every transaction signed with ML-DSA-87 (Dilithium), the NIST post-quantum signature standard, mined into real blocks and accepted by our public archive node.

TL;DR

First post-quantum payment confirmed on-chain
First 2-of-2 multi-signature wallet funded
First multi-sig spend – two independent post-quantum signatures, verified and confirmed

First single-signature spend

18 Sep 2026, 16:06 CEST

A simple payment of 10 AQA from a mining payout address to a fresh AIP-39 wallet (our 24/36/48-word recovery standard), with a 0.01 AQA tip and a 0.001 AQA relay fee.

Path: wallet send → signed transaction → mempool → mined → confirmed by the archive node
Transaction size: ~9.4 KB (post-quantum signatures are big – more on that below)
Confirmed in block #112
Receiver balance after confirmation: 10.000000 AQA

tx     9e353fb5ba5c1af53ec726946a4ef41a93c3152bc652a89148b8281f4388600a
block  #112  ea98a8b5bf5ca0288d277f96300bd841ad5fd06ada2c51c4e41cef8ee947ef9b

Multi-sig wallet funded

18 Sep 2026, 16:46 CEST

We created a 2-of-2 multi-signature wallet on testnet – funds can only move when both key holders sign – and sent 10 AQA into it.

tx     2d4df3e35cabbd89ef3da8b4fb4f56a31f375e1761a34ad169f464156f88d60e
block  #127  831935a282b0a417baedefd68b097ad5a9aade33a64e619e047a7ddb3f3f3320

First multi-sig spend

18 Sep 2026, 18:04 CEST – the big one.

Two signers each loaded their own wallet, built one transaction together and signed it independently with their own ML-DSA-87 keys. The node checked both signatures before accepting it:

verify_multisig_input [SUCCESS]: enough signatures present (2/2 required)

The spend went into the mempool, was mined into block #130, broadcast to the network and accepted by the archive node.

tx     d57ab29312337aa64958f84fefcfc6141487e666eb09cfcb0529706e08d1544f
block  #130  ccb98b6b6438dff6e76492d624e777d454c7d18262e136109638bffc242180a7

And the numbers add up to the last decimal:

Wallet	Balance	Math
Receiver	15.000000 AQA	10 (milestone 1) + 5
Multi-sig	4.989000 AQA	10 − 5 − 0.01 tip − 0.001 fee

For the developers among you, this is the whole flow in our node CLI:

walletload <signer-1>
walletload <signer-2>
mscreate 2 testnet
mstx ms 2 <receiver> 5 0.01 0.001
mssign last 0 0
mssign last 0 1
mine 1

What we had to fix to get there

Multi-sig didn't work on the first try – the archive node rejected our transactions with a hash mismatch. We tracked it down to two independent bugs:

Fee set after hashing. The multi-sig builder calculated the transaction hash first and set the fee afterwards – so the hash no longer matched the transaction body. Now the fee is set first, then the hash is computed.
Multi-sig fields lost on the wire. The network serializer only sent the basic input fields and silently dropped the multi-sig data (required signatures, signer keys and signatures). The receiving node filled in defaults and computed a different hash. You can see it in the numbers: the transaction packet grew from 656 bytes (broken) to 15,232 bytes (complete), and the block from 12,888 to 27,464 bytes.

The fix: hashing, the mempool and the network now use one single serialization path, so they can never disagree again. A dedicated regression test makes sure the truncated format is rejected and the full format round-trips cleanly.

Why these sizes matter

A post-quantum signature is much larger than a classic Bitcoin signature – that's the price of security against quantum computers. One single-sig payment is ~9.4 KB, a 2-of-2 multi-sig transaction ~15 KB.

This is exactly why AntiQua was designed from day one with compact commits and checkpoints to keep the chain lean over time. If you missed it, read Why Post-Quantum? The Threat is Real.

What this does not prove yet

We'd rather be honest than hype. These milestones were done with the node CLI on testnet. Still ahead:

Multi-sig in the desktop wallet (GUI)
Multi-sig in the Android light wallet against the live chain
Larger setups like 2-of-3 or 3-of-5
Compact block relay (currently switched off)
Mainnet – of course

We'll keep posting progress in the Core Changelog.

Questions about the transactions, multi-sig or post-quantum signatures? Ask below – we're happy to go into the details.

— Blythex

Blythex

Welcome to Support

Something not working? You're in the right place. This category is for wallet, account and transaction problems – and nobody here expects you to be an expert. The community and the team read every topic.

To get help fast, please take two minutes and read this first.

Rule number one: never share your recovery phrase

Never post your recovery phrase (seed phrase) or private keys – not in a topic, not in a chat, not "just to check". Anyone who has them can empty your wallet.

The AntiQua team will never ask for them, and will never ask for remote access to your computer. If someone does, it's a scam – please report them to the team.

This forum actively protects you: posts containing a recovery phrase or a private key are blocked automatically, and chats show you a warning before anything is sent.

How to ask a good question

1. One problem, one topic. Please open a new topic for your question instead of replying to someone else's – it keeps answers clear for both of you.

2. Use a clear title.
"Help!!!"
"Desktop wallet stuck at 'Synchronizing' after update"

3. Tell us the basics. Copy this into your topic and fill it in:

Wallet / app:     Desktop / Android / other
Version:          e.g. 1.2.0
Operating system: e.g. Windows 11, Android 14
What happened:
What I expected:
Steps to reproduce:
Error message:

4. Add a screenshot of the error if you can – often it says more than a long description. Double-check it doesn't show a recovery phrase or private key.

5. Logs help – but check them first. Before pasting a log file, take a quick look for anything private. Wallet addresses and transaction IDs are public and fine to share.

Is this the right category?

Wallet, account or transaction problem → right here in Support
Running a node or mining → Mining & Nodes
You found a bug in the code → Development
You found a security vulnerability → please do not post details publicly. Send a private message to a team member instead, so we can fix it before anyone can exploit it.

Write in your own language

You don't have to write in English. Every post has a translate button next to Reply – others can read your question in their language, and you can read the answers in yours.

Found the solution?

Please post what fixed it before you move on – even if you solved it yourself. The next person with the same problem will thank you.

Cheers,
Blythex

Blythex

Hey everyone

This thread is the official changelog for the AntiQua core – NodeCore, the node software that runs the AntiQua network. Whenever we ship something worth knowing about, it gets posted here as a new entry, newest at the bottom.

If you run a node, test the network or simply want to follow how the protocol evolves, this is the one thread to keep an eye on.

What gets posted here

Releases – new NodeCore versions and what changed
Security & hardening – fixes and improvements to cryptography, consensus and validation
Performance & networking – sync, P2P, mempool and resource usage
Breaking changes – anything node operators have to act on, always clearly marked
Network milestones – testnet resets, upgrades and other events that affect the whole network

How every update is structured

So you can tell at a glance whether something affects you, each entry follows the same format:

NodeCore vX.Y.Z – date
Type: Release · Hotfix · Security
Action required: No / Yes – what you need to do

What's new – short summary
Details – changes, fixes, notes for node operators

Never miss an update

Click the bell icon on this topic and choose Watching. You'll get a notification every time a new core update is posted here.

Questions & discussion

To keep this changelog clean and easy to read, replies are closed here. Got questions, found a bug or want to discuss a change? Just open a new topic here in Development – we read everything.

Stay safe: Only trust release information from official AntiQua channels. The team will never send you node or wallet files via private message, and will never ask for your recovery phrase or private keys.

Cheers,
Blythex