JustaName - Quarterly Reports

Service Provider Program Reports
1

Q2 2025 - JustaName Service Provider Report

This quarter our team’s main focus was on core wallet infrastructure development: Development work focused on wallet service backend completion, smart contract wallet implementation, and infrastructure scaling to support platform growth.
We also worked on ENS standards development contributions, strategic partnerships to promote ENS adoption (see our initiative with SEAL), and preparing a more ambitious GTM roadmap for pushing ENS subnames to the market.

Core Product Development

Wallet Service Backend

Finalized beta version with complete architecture implementation. The backend now supports key wallet operations and provides the foundation for user-facing applications.

JustaName Account (Smart Contract Wallet)

Completed smart contract wallet implementation with multi-signature capabilities. Developed comprehensive unit testing framework to ensure code reliability. Full codebase is available at GitHub - JustaName-id/justanaccount · GitHub.

Multi-Owner Logic Implementation

Implemented wallet functionality that enables shared account management unlocking advanced features for the users.

Infrastructure Enhancements

  • Proxy Service: Built transaction broadcasting infrastructure and portfolio data APIs.
  • Records Endpoint: Made API performance improvements and added functionality for data retrieval and management
  • EKS Clusters: Completed infrastructure scaling upgrades to handle increased user load and ensure platform stability

Ecosystem Integration and Standards Development

SEAL Best Practices Initiative

Collaborated with ENS stakeholders to develop industry standards through the Security Alliance framework. Documentation and best practice guidelines available at Ens

ENS Improvement Proposals (ENSIP)

Worked on ENS Improvement Proposals with focus on root-context record development. Documentation is here: ensips/ensips/ensip-TBD-11.md at ensip-ideas · nxt3d/ensips · GitHub, with demo available at: https://root-context-demo.vercel.app/

Community Partnerships and Integrations

Business Development and Market Activities

Pilot Program Management

Provided ongoing technical support for Yodl, Peanut, and IPE City implementations.

Go-to-Market Strategy Development

Subnames Issuance:

We worked on our needs for more impactful business and technical content, to make developers onboarding easier to support business development discussions and partnership conversations, and generally improve our BD and Marketing capacities.

Wallet Products:
We also developed technical architecture documentation and market positioning narrative for identity-wallet services. We are now moving towards securing a solid pilot program to test validate our product for Q4.

Conference and Networking Activities

  • EthCC Attendance: We were able to leverage the event to reconnect or add some high quality, qualified organic leads to onboard onto ENS protocol.
  • ENS Cannes Lightning Talks: Delivered presentation on our JustaName current capabilities and vision (https://x.com/justaname_id/status/1940718918168985901)
  • letstalk.wtf Platform: Built ENS business card platform for EthCC networking to facilitate connections within the ecosystem (https://letstalk.wtf/)
7 Likes
ENS DAO Newsletter #91 — 07/15/25
Service Provider Program Watch
2

Q3 2025 - JustaName Service Provider Report

A) JAW.ID Proof of Concept:

This quarter’s priority was to deliver our Identity-Wallet proof of concept - JAW.ID - and start gathering feedback from industry experts and professionals to prepare our next phase: a self-service premium infra product enabling any brand to unlock onchain rails with ENS identity as the bedrock for onboarding their users.

  • We were able to build a true self-custody product and underlying infrastructure that keeps users in complete control of their assets. The wallet leverages passkey technology for authentication, ensuring private keys remain securely on users’ devices while delivering the seamless experience of modern web applications. This approach combines the security principles of Web3 with the intuitive user experience people expect, creating an identity-first wallet that works across multiple chains without compromising on decentralization or user sovereignty.Retry
  • We partnered with Ethereum Foundation backed (grants) Etherspot, leveraging their open source Account Abstraction infrastructure (bundlers and paymasters).
  • Our ‘Move Assets’ feature enables users to swap tokens across networks and protocols with unusual ease. Bridging is abstracted away completely.
  • We built partnerships with strong, promising industry players including Abstract Protocol and Relay to support our launch, powering our wallet intents (swaps, bridging, cross-chain swaps).
  • Our first contacts with major industry brands are going very well, we are discussing ecosystems integrations and partnerships with major EF related organizations, one of NY based major FinTech, and significant East Asian brands already. We are planning to open contacts with major American and Middle Eastern conglomerates where influential insiders have expressed real interest already.

B) JustaName Product Development

We’ve shipped important product upgrades to JustaName:

  • Significant technical improvements to our product with Enterprise adoption of ENS in mind:
    • now enabling startups and enterprise to support broader technical requirements and build more flexible identity-centric user journeys.
    • Security and performance focused back-end improvements and infra refactoring.
  • Released admin-centric features to improve business users UX, again aimed at Enterprise and serious ventures (ie: reset passwords. Launched our Analytics features, as part of our admin dashboard upgrades).
  • Marketing and Messaging: New, improved landing page which had a quick impact in our ability to communicate ENS identity layer’s value proposal, and our capacities to nurture and convert account leads to using ENS protocol.

C) GTM of our ENS-centric products:

  • Our most significant win of the quarter in terms business development is our partnership and integration with Aurora to push ENS protocol as the identity layer in their fast growing ecosystem of dApps and Virtual Chains. Aurora is Near Protocol’s own EVM L2, and validates our thesis that ENS can grow even in major Alt L1s, some like Near initially aiming to compete with EVM ecosystems and Ethereum. We expect to launch an Aurora ENS ID very soon for their community and native wallet (Aurora Pass).
  • We will launch our first integration in Eastern Asia with CoinEasy, a leading regional blockchain community based in South Korea. They are well known as relentless crypto events organizers and are in multiple marketing partnerships with major blockchain industry brands that pay them to advertise to their communities. More to come soon from this partnership, with Aurora in the loop.
  • We are issuing subnames for Crescimiento, as part of their ‘hackathons and digital festival’ which will conclude at DevConnect. Crescimiento current hackathon is the largest ever organized in South America.
  • Kitchen Protocol, aiming to launch their Hyperliquid L2 within a month, has already purchased their domain (id.kitchen) and activated their ENS namespace on our platform. This use case again proves that ENS can reach ecosystems that have native name services (Hyperliquid does), and in many of them can simply take the leading identity layer position.
  • Business Cycles are quite slow, especially with larger accounts, which are our objectives. We expect significant account wins in the near future but these things take time since we are pushing brands towards a significant user-facing product and engineering decision with ENS protocol integration and subname issuance.

D) ENS Ecosystem Side Quests and Misc

We also supported ENS ecosystem with a few misc, but important side-quests:

  • We updated the ENS SEAL framework (a security initiative that coordinates blockchain security efforts across the industry), to properly cover ENSIP-19
  • We are contributing to an ENS x AI working group, helping to explore how AI agents can leverage decentralized identity and naming systems for autonomous interactions.
  • Assisted ENS Labs during the Ethereum 10 year anniversary initiative by creating a 3D video, which received strong engagement from the community.

E) Technical Details

JustaName

JAW.ID

  • Implement passkey server + npm passkey manager
  • Launch of the JAW.id Prototype, powered by the JustanAccount.sol
  • Complete redesign of JustanAccount.sol:
    • Multi-Owner Support: Allows multiple owners to control the account, with flexible owner management including addition and removal of owners. This essentially allows the account to be used with advanced functionalities such as Coinbase’s SpendPermissionManager.sol.
    • Flexible Owner Types: Supports both Ethereum addresses (20 bytes) and WebAuthn public keys (64 bytes), with architecture designed for future owner type expansion.
    • WebAuthn Signature Support: Full support for WebAuthn authentication. Owners can be registered as 64-byte public key coordinates (x, y) and authenticate using modern web authentication standards.
    • EIP-7702 Delegation: Can be used as a delegated implementation for existing EOA wallets, enhancing them with smart contract capabilities.
    • EIP-4337 Account Abstraction: Full compliance with account abstraction standards including UserOperation validation and EntryPoint integration.
    • ERC-7739 Compliant Signature Validation: Implements advanced signature validation with ERC-7739 nested EIP-712 support, preventing signature replay attacks across accounts while maintaining readable typed data for wallet UIs.
    • Signature Validation: Implements the isValidSignature function in compliance with EIP-1271 and ERC-7739, facilitating contract-based signature verification with replay protection.
    • Token Support: Built-in support for receiving ERC-721 and ERC-1155 tokens.
    • Namespaced Storage: Uses ERC-7201 standard for collision-resistant storage layout, ensuring safe delegation usage.
8 Likes
ENS DAO Newsletter #98 — 10/21/25
3

Q4 2025 - JustaName Service Provider Report

A) JAW.ID (Identity-Smart Wallets) Beta Preparation (Mid-Q1 2026 Launch)

This quarter focused on hardening our infrastructure and completing the security foundations needed for JAW’s beta launch:

Security & Audit

  • Completed a security audit of JustanAccount.sol by Nethermind Security, validating our smart contract architecture for production readiness.
  • Developed JustaPermissionManager.sol, enabling programmable permissions that allow users to delegate specific, bounded capabilities to third parties (including AI agents) without exposing full account control.

JAW Mono Architecture

  • Shipped our monorepo architecture with a modular package structure:
    • @jaw.id/core: Base primitives for account abstraction, passkey management, and EIP-1193 provider integration. Includes full encryption layer for secure communication between dApps and keys-jaw-id in cross-platform mode. Supports two operational modes:
      • Cross-Platform: Passkey operations handled via the keys-jaw-id app, enabling universal accounts, re-usable across dApps.
      • App-Specific: Passkeys bound directly to the integrating application, enabling a higher level of control and customization.
    • @jaw.id/ui: Pre-built components for wallet interfaces
    • @jaw.id/wagmi: Wagmi Connector and react hooks for easy integration with existing wagmi-based dApps
    • keys-jaw-id app: Cross-platform passkey operations handler, enabling consistent authentication across web and mobile contexts
  • Early documentation available at docs.jaw.id

JAW Dashboard

  • Updated dashboard with Account Issuance Metrics and User Operations tracking, currently live on staging.

B) JustaName Product Development

  • Completed infrastructure refactoring into Terraform configurations for streamlined deployment and management
  • Major documentation overhaul for Core and React SDKs, with emphasis on the React SDK to lower integration barriers
  • Added ENSIP-19 support via new reverseResolve function in @justaname.id/sdk and useReverseResolve hook in @justaname.id/react

C) GTM and Business Development

We saw nice growth this quarter with an increase of 370% in issued subnames. With the overwhelming majority of these wallets active multiple times post inception.

We are proud of the success of Peanut’s who had a great launch at DevCon, as they went viral in Buenos Aires and won the startup worldcup at the event.

Generally we got to increase the quality and quantity of our BD pipeline, especially in eastern Asia where the reach of ENS is still limited.

Our goal is to bring easy ENS protocol implementations beyond Ethereum native audiences, and with new partnerships, to push the limits of what can be achieved with ENS identity to onboard internet users to decentralized applications.

Our priority is now the launch of JAW, our ENS identity native smart wallets infrastructure product. We believe that the best way to penetrate large ecosystems, and in turn to onboard (to ENS) brands and projects with substantial reach is to combine ENS identity to a ‘must-have’ features.

Moving forward, our strategy is to focus on a new value proposal and shifting to bundle ENS namespaces with critical infrastructure to offer great onchain UX to consumers.

We soft launched with a B2C implementation of our infra product with the JAW wallet that we already circulated in our network and the ENS DAO crowd, which gave us great feedback and solid validation.

We will be in Beta with JAW.ID’s B2B SDK before mid Q1-2026. Our goal is to be able to use this platform to distribute ENS in new ecosystems, beyond Web3 audiences, targeting TradFi and Fintech brands along Telecom operators and large retailers.

5 Likes
ENS DAO Newsletter #104 — 1/15/26
4

Q1 2026 - JustaName Service Provider Report

A) JAW.id — Beta Launch & Product Releases

Q1 was the quarter JAW shipped. After a Q4 focused entirely on security and architecture foundations, we moved from prototype to production across every layer of the stack.

JAW.id Beta Launch

JAW.id launched publicly in early March as an identity-first smart account infrastructure. The core value proposition: programmable smart accounts with passkey-based self-custody, ENS-native identity, and onchain permissions, integrated by builders in two lines of code.

Key capabilities shipped at launch:

  • Passkey self-custody: No seed phrases, no custodians. Private key material lives in the device’s secure enclave. The account is non-custodial with no provider dependency.
  • ENS-native onboarding: Every account issued at onboarding receives an ENS subname gaslessly via JustaName. Users get a human-readable identity (e.g. alice.yourapp.eth) from day one, portable across the ENS ecosystem.
  • Onchain programmable permissions (via JustaPermissionManager.sol): Structured grants at the account level; specific spender addresses, expiry windows, contract and function selector whitelists, and spend caps. The account enforces the rules, not the application.
  • Stablecoin gas payments: Users pay transaction fees in USDT/USDC with no native token required.
  • AI agent delegation: Agents operate within scoped, revocable permissions enforced onchain. Spending limits and contract whitelists apply regardless of agent behavior.
  • Atomic batching: Multiple operations settle in a single transaction.
  • wagmi connector: Drop-in for existing wagmi-based apps. Existing hooks work unchanged.
  • Two integration modes: Cross-platform (reusable accounts across apps via keys.jaw.id) and app-specific (passkey bound to the integrating application).

Multi-chain from day one: 18+ chains supported so far (Supported Networks – JAW.id Documentation)

Infrastructure partners at launch: Pimlico and Etherspot for bundler and paymaster services; dRPC for RPC infrastructure. JAW self-hosts Skandha bundlers for configuration flexibility and chain deployment speed.

Open ecosystem:

Launch announcement: https://x.com/_JAW_ID/status/2029253810573439061?s=20

JAW CLI: @jaw.id/cli

Shipped alongside the beta launch: a command-line interface that brings the full JAW smart account stack to the terminal, designed for developers and AI coding agents.

Architecture highlights:

  • No keys on disk: Signing happens via a WebSocket relay to a browser tab where the user authenticates with their passkey. The relay is a blind pipe; messages are encrypted end-to-end (ECDH P-256 + AES-256-GCM) and the relay never sees the data.
  • Built-in MCP server: AI coding agents interact with JAW smart accounts natively through any MCP-compatible client (including Claude Code).
  • jaw-skills: A dedicated skill for AI assistants, npx skills add JustaName-id/jaw-skills, giving agents full context over the CLI’s command surface: wallet calls, permission management, account operations.
  • Self-hostable relay: jaw-relay is open-source for teams that need full infrastructure control.

The CLI positions JAW as the first smart account infrastructure natively integrated into the AI development workflow.

Cli launch announcement: https://x.com/_JAW_ID/status/2032139650848948551?s=20

JAW v0.2.0: EIP-7702 Support

Released in late March. v0.2.0 adds the ability to upgrade existing EOAs to JAW smart accounts while preserving the original wallet address; no asset migration, no new identity.

The entire upgrade is triggered by a single flag: { eip7702: true }. JAW handles authorization signing, owner registration, and delegation automatically on the first UserOperation. Compatible with Privy, Turnkey, raw private keys, and any Viem account.

This is a meaningful unlock for teams with existing user bases: smart account features (batching, gas sponsorship, permissions) become available to existing wallets without asking users to move anything.

Full guide: docs.jaw.id/guides/eip7702-upgrade
Announcement: https://x.com/_JAW_ID/status/2037557268804251873?s=20

B) JustaName Product Development

  • ENSv2 resolution support: Shipped ENSv2 resolution support across the full JustaName stack; the resolution system, records endpoint, @justaname.id/sdk (core), and @justaname.id/react.
    Announcement: https://x.com/justaname_id/status/2036392333730599300?s=20
  • ENSIP-19 support: reverseResolve in @justaname.id/sdk and useReverseResolve in @justaname.id/react stable and integrated across JAW’s flows.
  • Interoperable Addresses (ERC-7828): Resolved across the Records API, Core SDK, and React SDK (vitalik.eth@ethereum, vitalik.eth@eth, vitalik.eth@eip155:1). JAW inherits this natively; the UI surfaces the interop format wherever ENS names appear. Announcement: https://x.com/_jaw_id/status/2045140366890881465?s=46
  • ENS subname volume: ENS domains under management doubled following JAW’s beta launch, with every new JAW account representing a net-new ENS subname issued programmatically at onboarding.

C) Business & GTM

Q1 was built around two parallel tracks: shipping JAW and preparing the field for our GTM phase. That meant building an ecosystem partnerships pipeline, opening a pilots pipeline, and gathering early product feedback from ICPs, all before the formal launch.

Conferences

We attended four events across the quarter:

  • WebSummit Doha
  • Consensus Hong Kong
  • Lausanne EPFL Blockchain Week
  • EthCC Cannes

WebSummit in early February was a deliberate stop on the way to Hong Kong. The audience skewed toward traditional economy players, and the current stablecoin adoption tailwind opened conversations that would have been harder to have a year ago. Two meaningful channels opened: Ooredoo, an international telecom operator, and Transfero, known for stablecoin issuance in Brazil.

The winner and runner-up of the EPFL Blockchain Week hackathon both built using JAW, the first external validation of the stack under competitive conditions.

Consensus Hong Kong extended the BD pipeline into Asia. The industry is more active there than in Western markets, and we see real opportunity in geographic diversification for ENS, which remains underrepresented in Asian markets relative to its Western footprint. A key target account at the event was Animoca Brands, and we were able to initiate that relationship.

Ecosystem Content

Alongside the product work, we published two long-form pieces to build narrative ahead of the launch:

  • From Seed Phrases to Smart Accounts: traces the evolution from EOA self-custody through KMS-based embedded wallets to passkey-based smart accounts; explains why the real frontier is the permission layer, not key management.
  • The Account Layer for a World with Agents: lays out the architectural reasoning behind JAW: hardware-bound custody, structured onchain permissions, and ENS as portable identity infrastructure, and why the three compound rather than stack independently.

GTM Status

JAW.id launched mid-March. On the institutional side, we’re in active deployment with a multi-subsidiary client targeting cross-border stablecoin transfers via JAW in headless mode, the first corporate treasury use case in the pipeline, and the profile of customer we’re building toward.

On the JustaName side, we made a deliberate tradeoff this quarter: standalone subname issuance BD has a ceiling, and we’ve hit it. The JAW bundle removes that ceiling, ENS namespaces packaged with smart account capabilities give our B2B audience a reason to move that a subname pitch alone never could.

Early data supports this thesis:

  • Subname issuance grew approximately 10% quarter-over-quarter on its own trajectory
  • ENS domains under management jumped 70% in the three weeks following JAW’s beta launch
  • Every new JAW account issues a net-new ENS subname at onboarding, programmatically

The 70% jump is the clearest signal we have that ENS namespaces see significantly more adoption velocity when bundled with the smart account layer. This validates GTM thesis in practice.

Looking ahead to Q2: EthCC Cannes closed with a strong pipeline. With just over a month since JAW’s launch, we’re already seeing a quality of inbound interest and partnership conversations that we hadn’t experienced before, a direct signal that shipping the full stack changed the conversation. The priority for Q2 is converting that pipeline into the first cohort of institutional integrations.

9 Likes