PacStac

Learn

PacStac Stewardship

ENS essentials

The Ethereum Name Service (ENS) maps human-readable names (for example, pacstac.eth) to resources such as wallet addresses, content hashes, and arbitrary text metadata. ENS data is stored on Ethereum as key/value pairs and resolved by smart-contract-aware DNS stubs. Because ENS names can expose text metadata, they are a natural companion to DNS TXT and /.well-known proofs.

Origins & history

2017

ENS launches on Ethereum mainnet

Ethereum Name Service (ENS) replaces hexadecimal addresses with human-readable names. Early ENS adoption focused on reverse resolution and wallet UX.

2020

ENS adds text records

ENS introduced arbitrary text records (such as `url`, `description`, and project-specific keys) so projects can publish metadata at the name level—similar to DNS TXT records.

2022‑2024

Cross-chain and L2 support

Bridges, CCIP-Read, and off-chain resolvers expanded ENS so data can live in traditional databases, IPFS, or custom APIs while still resolving via the ENS contract.

Publishing ENS text records

  1. 1. Choose the key. ENS clients let you add arbitrary keys (for example, pacstac or pacstac_url). Use a descriptive key so downstream consumers know how to parse the value.
  2. 2. Set the value. Store either your wallet public key, a PacStac attestation URL, or a JSON payload (if your resolver supports off-chain data).
  3. 3. Propagate. ENS changes finalize once the transaction is mined. Off-chain resolvers should return HTTP 200 responses with matching metadata.
  4. 4. Monitor. Use `ensjs`, Etherscan, or The Graph to confirm your text record is publicly visible. Schedule periodic checks similar to DNS TTL reviews.

Operational checklist

  • • Decide which chain (mainnet vs. L2) will host authoritative ENS data and document fallback resolvers.
  • • Track who controls the ENS name and how signer rotations will be handled.
  • • If you publish off-chain data via CCIP-Read, monitor the HTTP endpoint for uptime and TLS hygiene.
  • • Keep ENS text records in sync with DNS TXT and /.well-known proofs so users see consistent metadata.

PacStac roadmap

PacStac today verifies DNS TXT and /.well-known JSON proofs. ENS support is on the roadmap; when available, ENS text records will mirror PacStac payloads (wallet + verification metadata).

Until native ENS verification lands, you can store your PacStac attestation URL or checksum in an ENS text record so Web3 wallets surface the signal.

When exposing ENS proofs, reuse the same wallet public key you bind in PacStac to simplify revocation and auditing.

Resources