Skip to main content
The addresses below are the production NEAR Auth deployment on NEAR mainnet. Use them when you configure an SDK or inspect on-chain activity in an explorer.
Mainnet access is gated. You must be whitelisted before your app can authenticate real users against this deployment. Apply for production access — or build against the open testnet contracts first, which need no sign-off.

​
Contract addresses

ContractAccount idDescription
NEAR Authfast-auth.nearThe entry-point contract. Verifies a JWT through a guard and requests an MPC signature.
JWT Guard Routerjwt.fast-auth.nearRegistry that routes a guard_id to the guard contract responsible for verifying the JWT.
Auth0 Guardauth0.jwt.fast-auth.nearGuard that RS256-verifies Auth0 JWTs and validates the iss, aud, and fatxn claims.
MPC signerv1.signerNEAR’s Multi-Party Computation network. Produces signatures from distributed key shares.
On mainnet, auth0.jwt.fast-auth.near is also the Auth0 signing audience — every JWT the guard verifies must list it in the aud claim. See the Auth0 concept for details.

​
Network information

SettingValue
NetworkNEAR Mainnet
Chain idmainnet
RPC endpointhttps://rpc.mainnet.near.org
Explorernearblocks.io
When you construct a client, point near-api-js at the mainnet RPC and pass the mainnet account ids:
main.ts
import { FastAuthClient } from "@fast-auth-near/browser-sdk";
import { JavascriptProvider } from "@fast-auth-near/javascript-provider";
import { connect } from "near-api-js";

const provider = new JavascriptProvider({
  network: "mainnet",
  clientId: "your-auth0-client-id",
});

const { connection } = await connect({
  networkId: "mainnet",
  nodeUrl: "https://rpc.mainnet.near.org",
});

const client = new FastAuthClient(provider, connection, {
  fastAuthContractId: "fast-auth.near",
  mpcContractId: "v1.signer",
});
The MPC signer derives each user’s key at the path {guard_id}#{sub}, so the same login always controls the same NEAR account across sessions.

​
Next steps

Apply for mainnet access

Get whitelisted to authenticate real users in production.

Testnet contracts

The open deployment for building and testing without approval.

Network configuration

RPC URLs, chain ids, and explorers side by side.