feat: add ENSv2 BENS subgraph

[JOY (JOY)]

Summary

• add a DOS ENSv2 subgraph compatible with the official BENS schema
• index registry, registrar, resolver, ownership, expiry, and nested registry events
• render immutable Testnet manifests from a deployment record
• gate Docker publishing on subgraph tests and build validation

Validation

• 15 Matchstick mapping tests pass
• 6 manifest renderer tests pass
• graph codegen and build pass
• npm audit --omit=dev reports 0 vulnerabilities

Scope

The custom indexing adapter stays in DOS Names. DOScan consumes it by immutable commit and runs only official BENS, Graph Node, IPFS, and PostgreSQL images.

[gemini-code-assist]

Code Review

This pull request introduces a new subgraph adapter for the DOS Name Service (.dos), an ENSv2 fork on the DOS Chain compatible with Blockscout BENS. The review feedback highlights several key improvement opportunities: consistently using the namehash (node) as the ID for Registration entities to simplify lookup logic and prevent subdomain ID collisions; removing redundant Domain.load database reads in subregistry update handlers; cleaning up dead or redundant utility code (such as the custom byteArrayFromHex in favor of the built-in ByteArray.fromHexString); ensuring referential integrity by creating the Account entity for the empty address; and updating the test suite to reflect these entity ID changes.

[gemini-code-assist]

The Registration entity is created here using labelHash.toHexString() as its ID, whereas in userRegistry.ts it is created using node (the namehash). This inconsistency can lead to load failures and requires complex null checks on domain.labelhash when loading registrations. Furthermore, using labelHash as the ID can cause collisions if subdomains in different registries share the same label (e.g., test.dos and test.alice.dos). Consistently using node (the namehash) as the Registration ID everywhere solves these issues and simplifies the code.

Suggested change

	// Create Registration entity (id = labelHash hex)
	let registration = new Registration(labelHash.toHexString());
	// Create Registration entity (id = node namehash)
	let registration = new Registration(node);

[gemini-code-assist]

Since Registration ID is now consistently set to node (the namehash), we can load it directly using node without checking domain.labelhash.

  let registration = Registration.load(node);
  if (registration !== null) {
    registration.expiryDate = newExpiry;
    registration.save();
  }

[gemini-code-assist]

Since Registration ID is now consistently set to node (the namehash), we can load it directly using node without checking domain.labelhash.

  let registration = Registration.load(node);
  if (registration !== null) {
    registration.registrant = account.id;
    registration.save();
  }

[gemini-code-assist]

Since Registration ID is now consistently set to node (the namehash), we can load it directly using mapping.domain without checking domain.labelhash.

  let registration = Registration.load(mapping.domain);
  if (registration !== null) {
    registration.registrant = zeroAccount.id;
    registration.expiryDate = event.block.timestamp;
    registration.save();
  }

[gemini-code-assist]

Since Registration ID is now consistently set to node (the namehash), we can load it directly using node without checking domain.labelhash.

    // Update registration with cost
    let registration = Registration.load(node);
    if (registration !== null) {
      registration.labelName = label;
      registration.cost = cost;
      registration.save();
    }

[gemini-code-assist]

The custom byteArrayFromHex function is redundant because @graphprotocol/graph-ts provides a built-in, highly optimized ByteArray.fromHexString static method. We can remove this custom function entirely.

[gemini-code-assist]

We can define dosNode directly using the built-in ByteArray.fromHexString method instead of the custom byteArrayFromHex function.

var dosNode = ByteArray.fromHexString(DOS_NODE);

[gemini-code-assist]

In createOrLoadDomain, domain.owner is set to EMPTY_ADDRESS. However, the corresponding Account entity for EMPTY_ADDRESS is not created or loaded. This can lead to broken references or referential integrity issues when querying the domain's owner. Ensuring that the Account entity is created/loaded via createOrLoadAccount(EMPTY_ADDRESS) resolves this.

Suggested change

	export function createOrLoadDomain(node: string): Domain {
	let domain = Domain.load(node);
	if (domain == null) {
	domain = new Domain(node);
	domain.owner = EMPTY_ADDRESS;
	domain.isMigrated = true;
	domain.createdAt = BigInt.fromI32(0);
	domain.subdomainCount = 0;
	domain.storedOffchain = false;
	domain.resolvedWithWildcard = false;
	domain.save();
	}
	return domain;
	}
	export function createOrLoadDomain(node: string): Domain {
	let domain = Domain.load(node);
	if (domain == null) {
	domain = new Domain(node);
	let zeroAccount = createOrLoadAccount(EMPTY_ADDRESS);
	domain.owner = zeroAccount.id;
	domain.isMigrated = true;
	domain.createdAt = BigInt.fromI32(0);
	domain.subdomainCount = 0;
	domain.storedOffchain = false;
	domain.resolvedWithWildcard = false;
	domain.save();
	}
	return domain;
	}

[gemini-code-assist]

Since the Registration entity ID is now consistently set to node (the namehash, which is ALICE_DOS), we should assert on ALICE_DOS instead of LABEL_HASH.

Suggested change

	assert.fieldEquals("Registration", LABEL_HASH, "cost", "12");
	assert.fieldEquals("Registration", ALICE_DOS, "cost", "12");

[gemini-code-assist]

Since the Registration entity ID is now consistently set to node (the namehash, which is ALICE_DOS), we should assert on ALICE_DOS instead of LABEL_HASH.

Suggested change

	assert.fieldEquals("Registration", LABEL_HASH, "cost", "7");
	assert.fieldEquals("Registration", LABEL_HASH, "expiryDate", "2100000000");
	assert.fieldEquals("Registration", ALICE_DOS, "cost", "7");
	assert.fieldEquals("Registration", ALICE_DOS, "expiryDate", "2100000000");