Hurdles when managing ENS ABI records

I’ve not found any UIs or utilities to help manage ABI records.
Perhaps I didn’t dig enough?
Are there any?
If there aren’t any, does anyone know why ensjs doesn’t include support?

I added a number of ABI records for my project and I had to write a couple of scripts to help me along. These tasks seem rote. Surely others who’ve added ABI records have jumped through similar hoops? Standardizing this process would be a dream, of sorts.


ABIs haven’t seen widespread usage in ENS, so there isn’t yet a lot of tooling for them. If you’d like to build any, it would be warmly received!


I was looking over the content-hash library, as a possible starting point for ABI.
Should the ABI implementation focus on using CID, if the entries already define the data stored on chain?

The ABI spec defines several ways to encode the data. I don’t think CID is a good format - we need a structured format like JSON or CBOR.