I recall reading about a proposed RFC a while back that utilized a hash of the account uri. Does anyone recall which RFC that was?
I've compiled a list of ACME RFCs below. If there are any omissions, let me know and I will edit this posting. I could not find any resource that listed them all – so I had to use the IETF site, search engines and this discourse. I am certain I missed some; I definitely missed the one with the account hash.
List of ACME RFCs
Implemented by LetsEncrypt
RFC 8555: Automatic Certificate Management Environment (ACME)
RFC 8657: Certification Authority Authorization (CAA) Record Extensions for Account URI and ACME Method Binding
RFC 8737: ACME TLS Application-Layer Protocol Negotiation (ALPN) Challenge Extension
draft-ietf-acme-ari-08: Automated Certificate Management Environment (ACME) Renewal Information (ARI) Extension
draft-aaron-acme-profiles-00: Automated Certificate Management Environment (ACME) Profiles Extension
Not Implemented / Unknown
RFC 8823: Extensions to Automatic Certificate Management Environment for End-User S/MIME Certificates
RFC 8823 - Extensions to Automatic Certificate Management Environment for End-User S/MIME Certificates
RFC 8738: ACME IP Identifier Validation Extension
RFC 9115: An ACME Profile for Generating Delegated Certificates
RFC 9444: Automated Certificate Management Environment (ACME) for Subdomains
RFC 9447: ACME Challenges Using an Authority Token
RFC 9448: TNAuthList Profile of ACME Authority Token Challenges