Hi folks,
I wanted to briefly note some early implementation experience related to
an Independent Submission Internet-Draft I published recently:
draft-jeftovic-x402-dns-discovery
https://datatracker.ietf.org/doc/draft-jeftovic-x402-dns-discovery/
The draft describes a simple DNS TXT-based discovery mechanism using:
_x402.<hostname>
to advertise HTTPS URLs for retrieving x402 payment manifests.
A few days ago I was informed by the team behind x402scan (which
operates discovery and indexing services for x402-enabled endpoints)
that they've incorporated the DNS-based discovery mechanism described in
this draft into their forthcoming spec and implementation, which they
were already developing (details here):
https://github.com/Merit-Systems/x402scan/pull/459
The DNS lookup will now appear alongside a proposed /.well-known/x402
mechanism.
In practice, their tooling will check for both:
* /.well-known/x402
* _x402 TXT record
(The ordering of these checks could be an interesting topic for discussion.)
I’m sharing this purely as an informational note to indicate early,
independent implementation convergence.
Feedback from DNSOP participants on the relevant aspects (TXT usage,
caching considerations, alternatives such as SVCB, etc.) would be very
welcome.
As a bit of context only: part of my motivation in exploring x402
discovery is the broader potential for agent-friendly micropayments on
the web, including possible implications for open source sustainability.
I’ve written up some related thoughts here for anyone interested:
https://easydns.com/blog/2026/01/10/can-x402-save-the-open-source-software-movement/
This is my first post to this list, so I hope I’ve followed the local
conventions.
regards,
- mark
--
Mark E. Jeftovic <[email protected]>
Co-founder & CEO easyDNS Technologies Inc.
+1-(416)-535-8672 ext 225
_______________________________________________
DNSOP mailing list -- [email protected]
To unsubscribe send an email to [email protected]
