
Overview
Cargo.toml all the way to a cohesive product surface that a non-technical user could plausibly open, understand, and use.
UX investigation
- Audit of competing wallets and DEXes (MetaMask, Phantom, Rabby, Uniswap, Jupiter) — cataloguing where first-time users drop off, which jargon is load-bearing vs. vestigial, and which "security" choices actually trade off against usability.
- Task-based user testing with non-crypto-native testers: "send 5 tokens to this address", "find out why this transaction failed", "recover your wallet on a new device." Every failure point fed back into the Xeris product language.
- Jargon triage: a written glossary that decides, per term, whether to keep it (because it's load-bearing), rename it (because a plain-language alternative exists), or hide it behind progressive disclosure. This document governs copy across all six products.
- A single design-system spec (
DESIGN_SYSTEM.md) that every product — web, extension, native mobile, Rust-rendered explorer — links back to, so the ecosystem feels like one product even though it spans six codebases and three languages.
The ecosystem
1. XerisCoin Testnet — the Layer 1
xrs-node) built on top of solana-sdk 2.0, with custom contract types, a Merkle-backed ledger, Ristretto255 Pedersen commitments and Schnorr zero-knowledge proofs for confidential state. The chain ships its own governance-ready validator set and a REST/RPC surface over warp + tokio. A full audit pass was run against the consensus and contract layers before any downstream product connected to it.
2. XerisDex — the decentralized exchange
3. Xeris Wallet — browser extension
@noble/ed25519 alongside @noble/post-quantum (CRYSTALS-Kyber and Dilithium) so that transaction signing and key exchange survive the arrival of cryptographically relevant quantum computers. BIP-39 seed handling, QR-based address sharing, and an injected window.xeris provider that any dApp in the ecosystem can pick up.
4. Xeris Wallet — Flutter mobile app
rust_pqc FFI bundle). Ships with a full internal design system document that defines the brand palette (Brand Blue #0019A5, Brand Vibrant #8FA3FF, Brand Navy #010414), the Inter / Plus Jakarta Sans type pairing, advanced order flows, l10n scaffolding, and store-ready assets plus a privacy policy.
5. XerisChat — onchain Snapchat
ContractType::XerisChatRegistry). Post-quantum key exchange via Kyber, signatures via Dilithium, with Ed25519 still handling the chain-level transaction layer.
6. XerisExplorer — the block explorer
Gallery




Key features
- Post-quantum cryptography everywhere it matters: Kyber for KEM, Dilithium for signatures, layered alongside battle-tested Ed25519 and Ristretto255 primitives.
- Shared design language: one palette, one type system, one motion vocabulary across web, extension, and native mobile — documented in a living design-system spec, not just Figma files.
- First-class confidential state: Pedersen commitments and Schnorr ZK proofs baked into the chain, not bolted on via L2.
- Private media layer (XIPFS): a swarm-key-gated IPFS network with a Rust pinning gateway so that "decentralized media" doesn't silently mean "public forever."
- End-to-end auditability: every user-facing product points back to XerisExplorer for verification.
Technologies used
- Chain / node: Rust, Tokio, Warp,
solana-sdk2.0,curve25519-dalek4.x,rs_merkle, SHA-2. - Cryptography:
@noble/post-quantum(Kyber, Dilithium),@noble/ed25519,@noble/hashes, BIP-39, Rust PQC FFI. - Web apps: Next.js 15 (App Router), React 19, Tailwind CSS 4, Framer Motion, Recharts, Reown AppKit, Solana Wallet Adapter.
- Browser extension: Vite, React 18, TypeScript, Zustand, Tailwind, Manifest V3 (Chrome + Firefox build pipelines).
- Mobile: Flutter, Dart, native iOS/Android, Rust FFI for PQC.
- Media layer: Kubo (go-ipfs) with a custom
swarm.key, Rust + axum signed-upload / pin service, systemd-deployed gateway nodes. - Design: Figma for specification, a written design-system markdown spec as the source of truth, Inter + Plus Jakarta Sans.
Challenges and learnings
- Crypto-library coherence:
solana-sdk 2.0pullscurve25519-dalek4.x internally. Mixing a second Scalar/Ristretto stack for Pedersen commitments had to match that major version exactly or the node wouldn't even link — a reminder that blockchain stacks leak dependency constraints upward into every consumer. - Post-quantum readiness without regressions: PQC signatures are large (Dilithium signatures dwarf Ed25519). Every byte on-chain has a cost, so the architecture signs transactions with Ed25519 and reserves Dilithium/Kyber for off-chain key exchange and messaging envelopes.
- One brand across six surfaces: shipping a Rust node and a Flutter app and a browser extension that all feel like the same product requires the design system to be explicit and written down. A Figma file alone was not enough — a markdown spec that each codebase links back to was.
- Private IPFS is a product problem, not a protocol problem: XIPFS taught me that the hard part of "decentralized media" isn't running a node, it's key-gating the swarm, signing uploads so the gateway can't be spammed, and making pin lifecycles match ephemeral-snap semantics.
- Scope discipline: six products, one person. Every feature had to justify itself against the question "does this move the ecosystem forward, or is it just a product I'd ship anyway?" — most of the cuts happened at that line.