Labelhash is the keccak256 hash of the label (e.g. "nick" in the name "nick.eth"), which is different than applying NameHash.nameHashAsBytes() on the label.

Web3j likely doesn't have a helper function specific to labelhash, but it may have a keccak256 function which can be used in this example.

So NameHash.nameHash Function can be used for both full Name like nick.eth and just label like 'nickIt will give the correct result, thats why there is no ultitly function just for labels as user can use currentNameHash.nameHash` fucntion on label to get the labelHash.

This fuctions returns (Hash.sha3(result)) which is keccak256
Hope it makes sense, let me know if there is still any confusion

Hmmm I'm running a test script locally and NameHash.nameHashAsBytes('label') does not return the expected label hash. The expected value for label would be 0x1b036544434cea9770a413fd03e0fb240e1ccbd10a452f7dba85c8eca9ca3eda

I don't know Java well, but futzing around it looks like the code example will have to be a bit lower level like this:

public static String labelHash(String name) {
  // Get the label of the name (the part before the earliest '.')
  String[] parts = name.split("\\.");
  String label = parts[0];

  // Keccak256 hash the label and convert to hex string
  byte[] labelHash = Hash.sha3(label.getBytes(StandardCharsets.UTF_8));
  String labelHashString = Numeric.toHexString(labelHash);
  return labelHashString;
}

@gskril Thanks for pointing out this. I was able to reproduce it, and created a PR for labelHash fucntion - LFDT-web3j/web3j#2140

We will soon release new Web3j with this fix. Thanks

Looks like web3j also exposes NameHash.nameHash which returns a hex string directly, so no need to first get the bytes and convert it yourself