NodeClient Logo
NodeClient BRAND & APPLICATION DOSSIER
Application & Brand Verification Portal

About NodeClient & NodeAuth

Comprehensive information regarding the NodeClient desktop application, the NodeAuth authentication protocol, technical architecture, and official verification URLs.

Official Application & Brand Verification URLs

Use these verified URLs when configuring OAuth consent screens or submitting developer portal reviews.

Application Home: https://nodeclient.app/

Brand Identity & Mission

NodeClient was conceived with a single guiding principle: Minecraft players should not have to compromise between raw graphical performance, modding flexibility, and uncompromising account security.

Traditional clients often bundle proprietary, closed-source obfuscated mods or route player credentials through third-party proxy authentication servers. NodeClient was designed from the ground up to take the opposite approach:

Decentralized Trust

Direct client-to-Microsoft authentication with NodeAuth. We operate no login proxies.

Open Mod Ecosystem

First-class compatibility with Fabric, Forge, NeoForge, Modrinth, and CurseForge.

Peak Hardware Efficiency

Sub-400ms startup times, optimized garbage collection flags, and minimal RAM footprint.

NodeAuth Technical Specification

NodeAuth is the cryptographic authentication subsystem embedded in NodeClient. It manages user authentication with the Microsoft Identity Platform to obtain valid session tokens for Minecraft Java Edition:

// Authentication protocol sequence:
1. OAuth 2.0 PKCE: Direct browser redirect to login.live.com/oauth20_authorize.srf
2. Xbox Live User Token: Direct POST request to user.auth.xboxlive.com/user/authenticate
3. XSTS Token Exchange: Direct POST request to xsts.auth.xboxlive.com/xsts/authorize
4. Minecraft Services: Exchange for bearer token at api.minecraftservices.com/authentication/login_with_xbox
5. Local Keyring Storage: Saved into local OS credential locker using native AES-256 GCM encryption.

NodeAuth guarantees that player credentials never traverse any server owned or controlled by NodeClient. Tokens remain strictly isolated to the user's local operating system.

Software Architecture & Components

NodeClient is architected in a modular decoupled design:

  • Launcher Core: Native compiled desktop client with minimal overhead, replacing sluggish legacy launchers.
  • Runtime Provisioner: Automatically detects the player's CPU architecture and downloads the optimal Temurin LTS Java Runtime (Java 8 for 1.8.9, Java 17 for 1.18+, Java 21 for 1.20.5+).
  • In-Game Client Engine: Built on top of the Fabric loader and modern LWJGL 3 bindings to eliminate frame drops and screen tearing.
  • Asset Cache: Smart delta updating ensures only modified game resources and mod jars are downloaded, conserving network bandwidth.

Developer & Community Contacts

Official Discord:
discord.gg/nodeclient
GitHub Organization:
github.com/nodeclient
Support & Verification Email:
support@nodeclient.app
Security & Privacy Desk:
privacy@nodeclient.app