Proposal has been updated: #91 - FEP-0ea0: Update proposal - fediverse/fep - Codeberg.org
I decided to keep type: Link requirement. “Duck typing” approach could make sense in certain situations, but when working with AS objects I prefer to match by type first (because this results in cleaner code when the number of variants is large); other implementations I’m familiar with seem to do that as well. If there’s a use case for payment link where a different type is really necessary, I’ll re-consider this.
Mastodon’s legacy identity proofs had type, name, signatureAlgorithm and signatureValue properties. FEP-c390 identity proofs have type, subject, alsoKnownAs and proof properties.