Yeah, makes sense given 2018.03.12 Wildcard Certificate Encoding Issue. For myself, I’m more interested just in the ACMEv2 endpoint since the client I wrote doesn’t do dns validation (or ACMEv1). I wrote it on Feb. 21st, so it felt silly to support an already obsolete protocol.
On the other hand, I don’t want to commit changes using the production endpoint until there’s an announcement, so tonight I dream of an announcement of a non-wildcard v2 announcement in the morning. 