The IRCv3 Working Group is a group of IRC client and server software authors working to enhance, improve, maintain and standardize the current IRC protocol. It was created by atheme.org but now represents the interests of many parties.
Other stakeholders in the IRC protocol, such as IRC networks and IRC network operators are invited to participate. If you would like to discuss IRCv3 standardization efforts over IRC itself, you may find us at
Please also read our charter before participating.
The IRCv3 working group contains participants from the following organizations (and more):
To participate, contribute to our specifications and extensions registry on GitHub.
Right now the IRCv3 specification is distributed as a series of extension specifications to IRC protocol version 2.7, also known as RFC1459. To understand the basis of the IRC version 3 protocol, please read RFC1459 followed by the extension specifications. A unified specification draft is being worked on which will replace RFC1459 at a later date.
Each version of IRCv3 contains base extensions, which comprise the core functionality of the IRC version 3 client protocol, and optional extensions, which comprise the extended functionality of the protocol.
Current released version of IRC protocol is 3.1
Submit new extensions for consideration for 3.2!
The IRCv3 Working Group maintains a registry of “work-in-progress” extensions that have not yet been accepted as part of an IRC protocol version. IRC software vendors may provide additional extensions that have not yet been added to this registry. We recommend that extensions not in the registry use appropriate namespacing as described in the capability negotiation specification and in the message tags specification.
To submit an extension to the extension registry, please contact us via IRC for now (
irc.atheme.org #ircv3). Extension specifications should be submitted in Markdown format.
This software is compliant natively; other software may be compliant with extensions.