Fetches TXT records and displays them in a Linktree-style interface.

This repository provides comprehensive documentation for TXT record prefixes used with Handshake (HNS) TLDs. These prefixes facilitate standardized data interpretation, enabling clients to easily recognize and interact with on-chain and off-chain records.

Handshake TLDs empower individuals and organizations with total ownership and sovereign identity by providing immutable, censorship-resistant on-chain records. This ensures that your data is securely published without the risk of alteration or suppression by centralized entities.

TXT record prefixes standardize how information is structured and interpreted, making it easier for services and applications to extract the intended data seamlessly.

1. Navigate to your domain manager (e.g., Shakestation, Namebase, ...).

2. Add a new TXT record with the following configuration:

   • Type: TXT
   • Name: @
   • Value/Data: <prefix>:<value> (e.g., link:example.com)

3. After configuration, visit: https://hackbase.hns.bio (Replace "hackbase" with your actual TLD or desired domain name) or search for SLD's (ICANN/HNS) on the index page: https://hns.bio, you can share SLD's (ICANN/HNS) in this format https://hns.bio/sld.tld.

btc, ln, hns, eth, xmr, zec, bat, aave, ada, algo, apt, atom, avax, bch, bgb, bnb, chainlink, cro, dai, doge, dot, ena, etc, fil, gt, hbar, hype, icp, jup, kas, leo, ltc, mnt, near, okb, om, ondo, op, pepe, pi, pol, render, shib, sol, sui, tao, tia, ton, trx, uni, usdc, usde, usdt, vet, xlm, xrp

This is an experimental demo. It uses HNS nodes (by Eskimo and James) to fetch the TXT records. When an NS is set up, it will fetch only off-chain TXT records.. It works with Handshake HNS TLDs, HNS SLDs, HNS dSLDs, ENS domains and ICANN SLDs.

The primary goal of this demo is to establish a universal standard for TXT records and pave the way for APIs supporting wallets, socials, logins,...

No license, no limits. Free to use, abuse and improve this code however you see fit.

Headless Profile acts as a dynamic gateway to render Handshake TXT records, but you can also export your profile to host it natively on the InterPlanetary File System (IPFS) and link it directly to your .agent or Handshake domain.

If your domain is registered on HeadlessDomains.com (e.g., .agent, .chatbot), you can automate the entire IPFS pinning and DNS configuration process:

1. Start the Sync:
   • Look up your domain on headlessprofile.com.
   • Click the Export to IPFS ↗ button at the bottom of your profile.
   • Click Sync via Headless Domains.
2. Auto-Pinning & Pre-filling:
   • The application will automatically take a snapshot of your profile, convert images to absolute paths, and securely send it to the Headless Domains API to pin via Pinata.
   • You will be instantly redirected back to your Headless Domains dashboard where the new ipfs:<YOUR_CID> TXT record will be perfectly pre-filled and ready for you to confirm. (Note: This flow can also be triggered directly from the Headless Domains dashboard via the &auto_pin=true URL parameter!)

For domains registered elsewhere, or if you prefer to pin your files manually:

1. Download the Source Code:
   • Look up your domain on headlessprofile.com.
   • Click the Export to IPFS ↗ button at the bottom of your profile.
   • Select Download Source (.html). This generates a single, standalone HTML file containing your entire profile.
2. Upload to IPFS:
   • Create an account on a pinning service like Fleek or Pinata.
   • Upload the downloaded HTML file.
   • Copy the resulting IPFS CID (Content Identifier).
3. Link to your Domain:
   • Go to your domain manager (e.g., Namebase or Shakestation).
   • Add a new TXT record to your domain:
     • Name: @ (or leave blank)
     • Value: ipfs:<YOUR_CID>

Once the DNS propagates, resolving your Handshake domain natively will load your decentralized profile directly from IPFS!