Skip to content
Qlyphs

Quantus to NEAR

How it works
Your Qlyphs walletQuantusML-DSA-87
The safeQuantus · needs 2 of 3 keys
Three signerstwo must agree
The bridge contractNEAR · nobody holds its key
Your NEAR accountinside NEAR Intents

Your wallet signs the transfer with a post-quantum signature.

Every approval on this route is a post-quantum signature. Qlyphs runs all three signers, in one service: this shows 2-of-3 post-quantum authorization, not independent operators. Test networks only.

How it works

What does post-quantum mean?

Future quantum computers could break the keys most chains use today. ML-DSA (signatures) and ML-KEM (encryption) are the NIST standards built to resist them.

Who approves a transfer?

Your Qlyphs wallet signs it with ML-DSA-87. Then 2 of 3 signers approve it with ML-DSA-87, and a contract on NEAR checks their signatures before any QTC is created. No single key can create QTC.

What is encrypted?

A request for QTC is encrypted with ML-KEM-1024, so only the person asked can read it. Your receipts on NEAR are encrypted with a key from your backup, so only you can find your transfers. Amounts and accounts stay public.

How does QTC come back?

Each NEAR account has a single key, an ML-DSA-65 one, kept by this browser. It signs the withdrawal, and the 2-of-3 safe on Quantus releases your QTC, once.

Contracts on NEAR testnet
Their access keys
none: nobody can change them
Backup of this browser

Your NEAR accounts and their keys come from one backup kept in this browser. With it, any browser finds your QTC on NEAR again; without it, nobody can. Keep it secret.