​

Registering a Resource

​

What on-chain registration gives you

• Ownership. The transaction sender becomes the owner of the resource ID and is the only party able to revoke or elevate it.
• Discoverability. Aliases like alice.eth resolve directly to a resource ID without needing the original .nota file in hand.
• Verifiability. The proof hash anchors the canonical .nota file content on-chain; any tampering produces a different hash.
• Revocation. A single transaction flips is_revoked = true, a signal wallets and explorers can treat as terminal.

​

Prerequisites

• A deployed Notareum instance with configured contract addresses (see Contract Addresses).
• An Ethereum account with enough native gas (ETH on mainnet, testnet ETH on Sepolia) to send one transaction.
• Optional: enough NOTA to pay the alias fee if you want a human-readable alias.
• A signed .nota file (see Your First .nota File).

​

The flow

​

Step 1: Derive the resource ID locally

import { ResourceType } from "@notareum/sdk";

const resourceId = ntm.registry.computeResourceId(
  ResourceType.ADDRESS,
  1n,
  await signer.getAddress()
);
console.log("Resource ID will be:", resourceId);

​

Step 2: Compute the proof hash

import { keccak256, toUtf8Bytes } from "ethers";

const wire = signed.serialize();
const proofHash = keccak256(toUtf8Bytes(wire));

​

Step 3: Claim an alias (optional)

import { Contract } from "ethers";

const fee = await ntm.fee.getAliasFee();
const nota = new Contract(
  contracts.notaToken,
  ["function approve(address,uint256) returns (bool)"],
  signer
);
await (await nota.approve(contracts.notaRegistry, fee)).wait();

​

Step 4: Send the transaction

const txHash = await ntm.registry.registerResource(
  ResourceType.ADDRESS,
  1n,
  await signer.getAddress(),
  proofHash,
  "alice.eth"
);
console.log("Registered:", txHash);

​

Step 5: Verify from any wallet

const id = await ntm.registry.resolveAlias("alice.eth");
const info = await ntm.registry.getResource(id);
console.log(info.owner, info.proofHash, info.verificationLevel);

​

Common pitfalls

• Reverts with AliasAlreadyTaken. Someone else already owns that alias. Choose another or bid on a release in the future (governance-configurable).
• Reverts with InvalidResourceType. Governance has not added this type ID yet. Use one of the six initial types or sponsor a proposal.
• Wrong proof hash. Always hash the canonical serialization (serialize()), not the file as you pretty-printed it.

​

Next step