Community
The circle around the herald.
QERYX is young. Every channel on this page is real today — and what does not exist yet says so, plainly.
01 / THE CHANNELS THAT EXIST
Write to any of the four that exist.
Talk to the builders
A human reads every message — questions, ideas, and honest criticism all land in the same place.
support@qeryx.comBreak the crypto
Coordinated disclosure with a safe harbor, published in security.txt — the procedure.
support@qeryx.com — SECURITY in the subjectRead the research
Protocol specs, security analyses, and guides — dated, versioned, with a what-changed log per paper.
qeryx.com/research02 / THE ARTIFACT RAIL — FETCHABLE TODAY
Fetch every artifact and test us with it.
A messenger that asks for trust owes its skeptics the tools to test it. Every artifact below is real and fetchable today — and the one that is not yet says so in its own row, because a rail padded with dead links is a lie with navigation.
-
/.well-known/security.txt
RFC 9116
The disclosure contract in machine-readable form: contact, canonical URL, and the safe-harbor policy address.
-
/security/disclosure
Policy
Coordinated disclosure: 72-hour acknowledgment, 90-day window, the safe harbor in writing.
-
/security/bug-bounty
Scope
What we most want broken — clients, crypto-core, the relay surface, QLEAP, key transparency — and what is out of scope, stated.
-
/research/rss.xml
RSS 2.0
Every paper, versioned and dated from real changelogs; a version bump resurfaces it in your reader.
-
/trust/dossier
Evidence
The evaluation evidence in the Trust Center — the claims on this site anchor there, not to adjectives.
-
PGP / ML-DSA-87 contact keys
Not yet
Publish after the offline key ceremony completes. Until the fingerprints are real, none are shown — a contact key you cannot verify is worse than none.
03 / WHAT DOES NOT EXIST YET
Read the absences as closely as the features.
We list absences the way we list features — because a community page padded with dead links is a lie with navigation.
No social profiles yet.
Profiles publish here when the accounts exist. We ship no placeholder handles and buy no followers.
There is no QERYX forum today.
When a public forum or community space opens, it will be listed here — with its real address and nothing else.
04 / THE WORK
Help by trying to break it.
How can I contribute?
Study the published design and report where it bends: flaws to support@qeryx.com with SECURITY in the subject under the safe harbor, hard questions to the same address. The sharpest contribution to a security product is an honest attempt to break it.
Where do I follow development?
In /research: the papers, each dated and versioned, so you can see what changed and when.