Skip to main content
Use the Offchain section of the Namespace App to create and manage gasless ENS subnames through the interface, Offchain Manager SDK, or API. Offchain subnames are application-managed records resolved through CCIP Read. They are not minted as NFTs and do not require a blockchain transaction for each creation or update.

​
What you can do

  • Configure a parent ENS name to use the Namespace Hybrid Resolver.
  • Create, update, and delete offchain subnames without code.
  • Manage address, text, and content hash records.
  • Generate API keys for server-side SDK or API integrations.
Offchain section of the Namespace App with subname and configuration tools

​
Before you begin

  • Connect the wallet that owns the parent ENS name.
  • Select the parent name you want to configure.
  • Use a CCIP Read-compatible ENS client when testing resolution.

​
Configure the resolver

The parent name must use the Namespace Hybrid Resolver before compatible ENS clients can resolve its offchain subnames.
1

Open the Offchain section

Visit app.namespace.ninja/offchain, connect the owner wallet, and select the parent ENS name.
2

Update the resolver

Find the resolver configuration, click Update, and confirm the transaction in your wallet. The app points the parent name to the Namespace Hybrid Resolver.Resolver configuration with the Update button in the Namespace App
3

Confirm resolution

After the transaction confirms, create a test subname and verify that its records resolve in a CCIP Read-compatible client.

​
Create and manage subnames

1

Open the Subnames tab

Select the configured parent ENS name, then open Subnames to view its issued names.Subnames tab for a selected parent ENS name
2

Create a subname

Enter the label you want to issue and add the required ENS records. You can store EVM and non-EVM addresses, text records, and a content hash.
3

Save and manage records

Save the subname, then use its record controls to update or remove data later. Offchain updates do not require a blockchain transaction.
Text record editor for an offchain subname
Address record editor for an offchain subname

​
Create an API key

You need an API key only when creating or managing offchain subnames from server-side SDK or API code. Keep the key out of client-side code and public repositories.

Generate an API key

Open the API Keys tab in the Namespace App.
Choose the key scope that matches your integration: Set an expiry date when you create the key. You can revoke or replace keys from the same screen. API key generation options in the Namespace App
New accounts have an issuance limit of 2,000 offchain subnames. Contact Namespace through the Builders group on Telegram before launch if your integration needs a different limit.

​
Next steps

Integrate offchain subnames

Create a subname, attach records, and query it with the Offchain Manager SDK.

Troubleshoot resolution

Diagnose resolver, API key, record, and client compatibility problems.