JustaName Architecture

JustaName Architecture

JustaName Architecture

The JustaName Architecture employs a microservices-driven design, comprising eight distinct services that communicate through a centralized event streaming system built on Kafka. At the forefront sits a Kong Gateway that routes external requests to the relevant microservices. Underpinned by Domain-Driven Design (DDD) principles and an event-driven approach, this framework ensures high scalability, fault tolerance, and maintainability. A robust testing pipeline further guarantees reliability and security across all services, complemented by a comprehensive monitoring stack that offers real-time performance insights. Backend operations run on AWS, while multiple frontends are deployed on Vercel for a seamless and globally accessible user experience.

JustaName Infrastructure

JustaName Infrastructure

JustaName Infrastructure

The JustaName Infrastructure is built within an AWS Virtual Private Cloud and leverages a Kubernetes cluster to orchestrate containerized services. It supports key bounded contexts for domain-specific logic and includes a self-managed Kafka for event streaming, along with the LGTM stack for monitoring and log aggregation. Data persistence is handled through Aurora PostgreSQL and Amazon S3, with container images stored in an Elastic Container Registry. External traffic is managed via an Application Load Balancer that routes requests through a Kong API Gateway, while integrated security services ensure controlled access and secret management across the platform.

To complement this enterprise-grade setup with decentralized transparency, we integrate OrbisDB on the Ceramic Network for publishing subname-related events, ensuring an open, tamper-resistant log of identity actions. This infrastructure was designed to ensure a secure, scalable, and highly available environment—while remaining aligned with the values of openness and verifiability that define Web3.

JustaName Multi-level SDKs

JustaName SDKs

JustaName SDKs

JustaName offers a tiered SDK structure that allows developers to pick the level of abstraction best suited for their needs. At the foundation, the Core SDK is optimized for backend use, providing low-level functionality to interact with the JustaName Infrastructure.

Building on top of this, the React SDK enables custom integrations for front-end applications, offering developer friendly hooks to integrate offchain issuance and ENS resolution/operations easily.

The JustWeb3 layer provides a fully plug-and-play solution, ideal for those looking to integrate ENS functionality rapidly without extensive customization.

Finally, an array of Plugins extends onchain profiles with specialized features, such as POAP displays, Talent Protocol Builder Score, EFP, XMTP-based messaging, and JustVerified allowing users to issue social verifications by leveraging ENS-specific Verifiable Credentials, making it easy to enrich the user experience while maintaining a modular, maintainable codebase.

JustVerified

JustVerified Design

JustVerified Design

JustVerified provides a way for users to generate verifiable credentials (VCs) that link their social accounts and identity proofs directly to their ENS names. Through a permissionless flow, users select a social platform (e.g., X, GitHub, Discord) within a front-end application equipped with the JustWeb3 + JustVerified plugin. After authenticating via the chosen social account, JustVerified invokes SIWENS (Sign In With ENS) to cryptographically bind the user’s social identity to their ENS domain. A verifiable credential is then created and can be appended to the user’s ENS records, allowing anyone to confirm social ownership and proof of personhood without requiring any centralized approval. This architecture ensures both trustlessness and transparency, enabling any third party to validate the authenticity of social claims tied to an ENS name.

SIWENS

SIWENS

SIWENS

SIWENS extends the Sign-In with Ethereum (SIWE) protocol by appending an ENS name to the signed message, effectively enabling the server to recognize the specific ENS used by the user. Much like selecting a Google account for different services, users can hold multiple ENS names and opt to sign in with a specific one for a given context. This decentralized authorization model not only preserves a familiar Web2-style login flow, but also when paired an infrustrucre like JustVerified, it can enable purely onchain identity validation and social credential checks, achieving an end-to-end trustless experience without relying on any centralized intermediary.