We route ciphertext we can't read.
Encryption is the headline here, not the fine print. The mediator forwards JWE ciphertext it cannot decrypt, its own identity resolves on-chain, and delivery can require a verified credential — cryptographic proof standing in for a compliance badge we haven't earned.
Four claims, each one checkable.
No throughput or uptime figure here doubles as a security story. These are the mechanisms, with what they look like on the wire.
Encrypted in transit (JWE)
The relay routes ciphertext it cannot read. There is no plaintext access, no message-body storage, no content column in our console. Zero-knowledge to the mediator.
{"protected": {"alg": "ECDH-ES+A256KW","enc": "A256GCM","typ": "application/didcomm-encrypted+json"},"recipients": [{ "header": { "kid": "did:solidus:z6Mk…#key-1" } }],"iv": "9f2Ka7XrT2mYbGd4NsLuP0oQ","ciphertext": "8Jk2p9WsE4…(sealed)…QzT4Yb3xVe5W","tag": "wQtU0S1caK5JzYxV2"}
Chain-anchored mediator identity
A mediator's did:solidus is anchored on chain, so an agent resolves the real endpoint cryptographically instead of trusting an off-chain registry — phishing-resistant discovery no off-chain registry offers. This mediator's own DID is published once it is anchored.
Example values — this mediator has not published an anchored DID yet.
Credential-gated delivery
Require a verified credential to accept mediation or delivery, checked against verify.solidus.network. Selective-disclosure (BBS+) supported.
Per-DID rate limiting
Message-flooding protection. Per-DID limits and burst controls keep one abuser from drowning a recipient's queue.
No SOC 2, ISO 27001, or audit badge below — none has been earned yet. The signals above are real and checkable today.
A mediator identity you can check yourself.
Not an analyst logo — a did:solidus document resolved from the chain at a specific, citable block.
This mediator's did:solidus is published here once it is anchored on chain. Until then there is nothing to show, and an example DID in this position would read as the real one.
When it appears, resolve it yourself: POST solidus_didResolve to rpc.solidus.network. A DID you cannot check is not a trust signal.
Read the protocol. Verify the identity.
The docs cover the full DIDComm v2 sequence; the mediator DID above is checkable on-chain today.