xeteLog inRegister

Trust

Proof, not promises.

Security you can prove — live programs on mainnet, verifiable for yourself.

Most platforms ask for your trust. xete is built so you never have to extend it — every guarantee below is enforced by cryptography and written to a permanent, immutable record. You can verify all of it without our permission.

What's actually running

Relay

Forwards sealed messages and resolves identities — and nothing more. It never sees what's inside what it carries.

Settlement

A public, immutable program records identity, delivery, and payment. Open source and reproducible — verifiable down to the byte.

Watcher

Observes the record for settlements and tells the parties. It witnesses what happened; it moves nothing itself.

Client

Your client. Keys are created here and encryption happens here — and neither ever leaves your device.

How it holds — tap to read

Encrypted
end to end
Non-
custodial
Permanent
& auditable
Verifiable,
not asserted

An honest threat model

Holds against
  • The network that carries your traffic
  • The server — and whoever operates it
  • A fully compromised or seized server
  • A subpoena or legal demand served to xete
  • An insider with access to our systems
Cannot protect against
  • A compromised endpoint — malware or a keylogger on your own device
  • Misplaced keys — they're yours alone to hold, which is the point; the vault is built to keep exactly that from happening
  • Traffic-pattern analysis — when and how often you communicate, even when the contents stay sealed

Verify the contract yourself

verify-settlement.sh
# 1 — pull the live program straight off the public ledger
$ solana program dump GPCsJ6kvrQ61wDG8bpP8315ge7AHfmsUHdxTD7LQ6CoJ onchain.so

# 2 — rebuild from source and hash both binaries
$ git clone github.com/xetenet/xete-tab
$ sha256sum onchain.so target/deploy/*.so

# 3 — compare the two hashes. they match, or the build isn't reproducible.
#     don't take it on faith — run it yourself.

Built for regulated environments

Data minimization

Message contents are nulled on a fixed schedule; only cryptographic proof of what occurred remains. Less retained data is less to govern, breach, or disclose.

Self-sovereign deployment

Run it fully managed, or host the entire stack inside your own perimeter. Your keys, your infrastructure, your jurisdiction.

No custodial liability

xete never holds your keys or your funds. There is no honeypot on our side — and nothing we could be compelled to hand over.

Responsible disclosure

A published security.txt and a coordinated-disclosure process, so vulnerabilities reach us through the front door.

Talk to us Verify on GitHub › Read the source. Reproduce the build. Then let's talk about your deployment.
How it worksAboutHelpSource