Skip to content

ext protocols technically can't be rejected with nack

Quoting from the governance process:

  1. Protocols in the "ext" namespace are eligible for inclusion only if ACKed by at least 2 members.
  2. Protocols in the "ext" namespace must have at least one open-source client & one open-source server implementation to be eligible for inclusion.

This does not explicitly mention nack as a valid option, just that two members need to agree to adopt the protocol. Is this intentional or an oversight in the rules?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information