JAW.id is now in beta 🎉

🧑‍💻 ENS Development
1

We’ve built smart account infrastructure on top of JustaName, and it’s live.

JAW.id gives every user a passkey-secured smart account with a human-readable ENS name, gasless transactions, batch operations, and programmable permissions; all through a single SDK integration.

ENS adoption in B2B audiences has historically been constrained by its positioning as an optional feature: feedback is very positive, but rarely prioritized or implemented in practice.

With JAW we wanted to address this by embedding ENS identity natively into smart account infrastructure, eliminating the need for a separate integration and making subname issuance a automatic outcome of user onboarding.

Today, as stablecoin adoption draws brands and platforms onto onchain rails at scale, JAW is aiming to make ENS the default identity layer for the next generation of internet consumers.

What this means for ENS:

Subname issuance is built directly into onboarding. When a user creates a passkey account, they automatically receive a username.yourapp.eth subname, gaslessly. There’s no separate ENS integration step for developers, the identity issuance is part of the onchain account creation.

The JAW SDK resolves and reverse-resolves ENS names everywhere an address would normally appear: decoded calldata, recipient fields, account displays, contract interactions… The goal is to remove hex addresses from the user experience entirely.

With gasless transactions and paymaster flows already in the stack, JAW.id is well positioned for ENSv2 when it rolls out. Users won’t need to hold ETH anymore for onchain name operations.

Our supported chains so far are: Ethereum, Base, OP Mainnet, Arbitrum One, Linea, Avalanche, Binance Smart Chain, and Celo; with testnets available for all major networks.

JAW.id’s features:

  • One-tap onboarding: users sign up with Face ID, fingerprint, or device PIN → No seed phrases, no extensions, no app downloads.

  • True self-custody: passkey private keys live in the user’s device secure enclave.

  • Pay gas in stablecoins: apps can sponsor gas entirely, or let users pay in stablecoins.

  • Atomic batch transactions: multiple operations in a single user approval.

  • Recurring payments: built on ERC-7715 permissions, the users will approve a payment schedule once. The app charges within approved limits.

  • Portable or app-native: CrossPlatform mode (one account across apps) or AppSpecific mode (app-scoped accounts).

JAW.id also supports AI agent delegation through ERC-7715 programmable permissions. A user can create a smart account and grant an AI agent a constrained permission: which contracts it can call, how much it can spend, when the permission expires. The agent operates as a delegated signer within those boundaries. The account enforces the rules onchain, and the user can revoke them at any time. No seed phrases are shared with agents, no unlimited access: it’s fully auditable onchain.

It is also optimized for AI-assisted development. Our docs are structured for LLMs, and we provide a dedicated skill for AI coding agents: npx skills add JustaName-id/jaw-skills

Or you can point your AI assistant to our LLM-friendly docs.

:double_exclamation_mark: We’d love to get your feedback: what’s working, what’s missing, what you’d want to see next. Join the Telegram Group: JAW.id Community :double_exclamation_mark:

Useful Links:

12 Likes
2

This is institutional-grade infrastructure with ENS at its core — and it solves a real pain point: how do you onboard mainstream users into self-custodial crypto without destroying the UX?

  • Smart account SDK — passkey-authenticated, no seed phrases, biometric login (Face ID/fingerprint)
  • ENS identity baked in at account creation
  • USDC for gas — users never need ETH
  • Programmable permissions — users can authorize AI agents or third parties with defined spending limits

The neobank GTM is exactly where this should land. Institutional demand for self-custodial accounts is real — compliance teams want identity, product teams want UX parity with web2.

JAW.ID addresses both without sacrificing custody.

One thought: ENS DAO delegates likely have direct relationships in institutional finance and fintech conferences. It would be worth connecting the JAW.ID team with those delegates — getting in front of neobank product and BD teams is a conversation the broader ENS ecosystem has a stake in.

Happy to facilitate if useful.

3 Likes
3

JAW.id update: the CLI is live

Following up on our initial post: we’ve shipped @jaw.id/cli, a command-line interface for interacting with JAW smart accounts from the terminal.

What it does

The CLI brings the full JAW smart account stack to the terminal. It’s built around the same passkey-first security model as the rest of JAW: no private keys are stored anywhere on disk. Signing happens through a WebSocket relay to a browser tab where users authenticate with their passkeys, with all messages encrypted end-to-end (ECDH P-256 + AES-256-GCM). The relay is a blind pipe, it never sees the data.

Getting started

npm install -g @jaw.id/cli
jaw config set apiKey=YOUR_KEY defaultChain=8453
jaw rpc call wallet_connect

MCP server

The CLI ships with a built-in MCP server, which means AI coding agents can interact with JAW smart accounts natively through any MCP-compatible client. There’s also a dedicated skill for AI assistants:

npx skills add JustaName-id/jaw-skills

The jaw-cli skill gives agents full context over the CLI’s command surface: the AI constructs and executes operations, while the user retains final approval through their passkey: a fingerprint or Face ID tap.

Full docs at docs.jaw.id/cli. The relay server is open-source and self-hostable if you need infrastructure control: jaw-relay.

We’d love to hear what you think, what’s working, what’s missing, what you’d want to see next.

4 Likes
ENS DAO Newsletter #108 — 3/15/2026