Skip to content
Logo

Developer getting started

Integrations should use the supported networks and contract addresses distributed through official Hyndle channels. Do not enable transactions against an unverified address.

Read flow

An integration normally needs to:

  1. Normalize the user input with the canonical Hyndle naming package.
  2. Compute nameId with Keccak-256.
  3. Convert nameId to the deterministic ERC-721 token ID.
  4. Read owner and lifecycle state from HyndleNames.
  5. Read current-generation records from HyndleResolver.

Client setup

Hyndle's TypeScript applications use viem-compatible clients. The following shape is illustrative until an official SDK and deployed addresses are published:

import { createPublicClient, http } from 'viem'
import { base } from 'viem/chains'
 
const client = createPublicClient({
  chain: base,
  transport: http(process.env.BASE_RPC_URL),
})

Never expose a private RPC credential with a public frontend environment variable.

Next steps