ENS-KIT/1Draft

Text Record Extension Spec

A proposed convention for driving frontend UI directly from ENS text records. Compatible with any ENS name — no custom resolver required. Updates are instant, gasless, and require no redeployment.

Reference implementation: dinamic.eth · ens-dynamic-kit

Media

KeyFormat
avatar
URL or ipfs://
ipfs://Qm...
icon
URL or ipfs:// (SVG/PNG)
ipfs://Qm...
video
URL or ipfs://
https://...
banner
URL or ipfs://
ipfs://Qm...
gallery
Comma-separated URLs
ipfs://Qm...,ipfs://Qm...
card_bg
URL or ipfs://
ipfs://Qm...
media
URL or ipfs:// (img/video)
ipfs://Qm...
media_desc
Text
My latest project

Actions

KeyFormat
pfp_button
Label|URL or URL
Hire me|https://cal.com/me
pfp_button_2
Label|URL or URL
Portfolio|https://...
url
URL
https://mysite.com
tip
ETH address
0x123...
donate
ETH address
0x123...
cal
Calendly / Cal.com URL
https://cal.com/me

Integrations

KeyFormat
com.twitter
Handle or full URL
@handle
com.github
Username
myuser
discord
Handle or invite URL
user#1234
telegram
Handle
@handle
email
Email address
me@example.com
rss
Feed URL
https://blog.me/rss.xml

Appearance

KeyFormat
theme
dark / light / gradient:<color>
gradient:purple
layout
minimal / full / grid
minimal
badge
Short string
Available for work

Conventions

  • Keys follow existing ENSIP-5 conventions where they exist (com.twitter, com.github, avatar, url, email).
  • New keys use lowercase with underscores (pfp_button, pfp_button_2).
  • Multi-value fields use | as separator — label first, URL second.
  • All URL fields accept ipfs:// as well as https://.
  • Unknown keys are silently ignored — spec is forwards compatible.