PQ CRYPTA PLATFORM

๐Ÿ  Main

๐Ÿ“ฐ News

๐Ÿ‘ค Account

โŸจ QUANTUM ERROR PORTAL โŸฉ

Navigate the Error Dimensions

PQ Crypta Ledger

A record of who holds which keys, who vouches for whom, and which documents existed when: every entry signed with ML-DSA-87 (FIPS 204), in your browser for your own, and made final by four validators that agree with Tendermint BFT. It records attestations, not money: there is no coin.

Connecting…

The chain now

Height
–
Last block
–
Transactions
–
Accounts
–
Revoked
–
Consensus
–

Validators

Look something up

Latest blocks

HeightTimeTransactionsProposerSigned byHash

Your account

An account is an ML-DSA-87 key pair. It is made in this browser and kept here, sealed with a key the browser cannot export; it is never sent anywhere. Its address is the hash of its public key.

Bring a key from another device
Address
Next nonce
–
Identity
None claimed

Attest

The ledger records the document's SHA3-256 hash, your signature and the time, not the document. Anyone holding the same file can later prove it existed then, and that you vouched for it.

A name for your account, said by you: others see that this key claims it.

That your account holds another public key, for a purpose, until a date: so others can look it up by its hash and know it is yours.

You, as issuer, vouch that a subject holds a key for a period.

Withdraw one of your own records: it stays on the chain, marked revoked, by you, from this block on.

How it works

Accounts. An account is an ML-DSA-87 public key; its address is the SHA3-256 of the key. Each account numbers its transactions from 0, which orders them and stops any being replayed.

Transactions are encoded one way only (every field fixed in size or prefixed with its length) and signed with ML-DSA-87 under a context string naming what is signed, so a signature over a transaction can never pass as one over anything else. This page builds and signs them here; the validators check every signature again.

Blocks are proposed in turn by four validators, each on its own machine, and become final when more than two thirds of them have signed a precommit for the same block: Tendermint BFT. The chain cannot fork and does not stop while at most one of the four fails, in any way at all; a final block is never undone. Each block carries the signed precommits that made the one before it final, so anyone can check the whole chain.

Between validators everything travels over QUIC with a post-quantum key exchange (X25519MLKEM768), and each validator proves who it is with an ML-DSA-87 signature bound to the connection.

The API reads the validator on its own host and keeps an index for search: GET https://api.pqcrypta.com/ledger/status, /ledger/blocks, /ledger/attestations?digest=…, and live blocks as server-sent events at /ledger/events.