Get zene for your App.

Try on Testnet

Add the SDK or point your Agent at agents.md

1. Add the SDK

<script src="https://cdn.jsdelivr.net/gh/zene-network/zene-sdk/dist/zene-sdk.js"></script>

2. Initialize + sign in

// Initialize once
Zene.init({ appName: 'My App' });

// Sign in on button click
const user = await Zene.signIn();
console.log(user.address);  // EVM wallet address

console.log(user.hash);     // On-chain identity hash

// Block access until signed in
Zene.init({ appName: 'My App', gate: true });

Zene.init(opts)       // Initialize SDK
Zene.signIn()         // Returns { address, hash, ... }
Zene.signOut()        // Clear session
Zene.getUser()        // Current user or null
Zene.isSignedIn()     // Boolean

Coming Soon — Self-hosted L1 Node

Run your own Zene node on the Avalanche L1. Full decentralization, zero trust in us.

# Pull and run the Zene node
docker run -d --name zene-node \
  -p 9650:9650 \
  zene/node:latest \
  --network=mainnet

Your app verifies identities directly against the chain. No API keys, no rate limits, no SaaS dependency.

How Zene Works

Zene is a decentralized identity layer on Avalanche. Two-factor auth (passkey + Google) that creates an on-chain EVM address. No MetaMask. No seed phrases. No centralized server sees your identity.

The Two-Factor Flow:

• Step 1: Passkey — WebAuthn biometric (Face ID / Touch ID). Creates a cryptographic credential on your device. Generates a deterministic salt unique to your passkey.
• Step 2: Google — OAuth sign-in confirms your social identity. Your Google ID is combined with the passkey salt and hashed client-side. Only the salted hash goes on-chain.
• Result — An EVM address linked to your identity, registered on-chain via ZeneRegistry on Avalanche. Two factors, one identity.

Trustless by Design:

• Decentralized Sign-In Page — The authentication page is hosted on Arweave/IPFS. The code is immutable and publicly auditable. You can verify it doesn't store or leak your data.
• Client-Side Hashing — Your Google ID never leaves your browser in plaintext. The passkey-derived salt + Google ID are hashed locally. The server only sees the resulting hash.
• Brute-Force Resistant — Without your passkey, the salt is unguessable. Without the salt, the on-chain hash reveals nothing about your Google identity.
• On-Chain Source of Truth — ZeneRegistry on Avalanche stores identity hashes. Any app can verify a user via a single RPC call. Zero trust in any server.

Why It Matters:

Traditional auth charges per user, controls your data, and requires trusting a server with your identity. Zene is free, decentralized, and verifiably trustless. Your identity is yours.

Implementation Phases

Zene launches in three phases, progressively adding features and decentralization.