Hyperledger projects use RocketChat to conduct ephemeral discussions; whereas, mailing lists are used to conduct larger discussions for which we want to maintain a history. To join our chat discussions, you will need a Linux Foundation ID to login to https://chat.hyperledger.org/.

• #ambassadors
  Used by the Technical Ambassadors to communicate amongst themselves and with others who are interested in having a technical ambassador speak at an event

• #architecture-wg
  Used by the Architecture Working Group to announce meeting updates and adhoc meetings

• #blockchain4good
  Used for discussions for the participants of the 2017 Dublin Blockchain for Good Hackathon held at Accenture The Dock

• #burrow
  Used by the Hyperledger Burrow project to discuss creating a permissioned smart contract machine based on the Ethereum Virtual Machine (EVM) specification

• #burrow-contributors
  Used for discussions by the contributors/maintainers of the Hyperledger Burrow project

• #caliper
  Used by the Hyperledger Caliper project for questions and ephemeral discussions

• #caliper-contributors
  Used by the Hyperledger Caliper project to discuss implementation details of the project

• #cello
  Used by the Hyperledger Cello project to discuss bringing an on-demand “as-a-service” deployment model to the blockchain ecosystem

• #ci-pipeline
  Used to discuss the Continuous Integration pipeline with respect to https://jenkins.hyperledger.org

• #composer
  Used for user discussions on the Hyperledger Composer project

• #composer-ci
  Used to discuss the Continuous Integration for the Hyperledger Composer project

• #composer-contributors
  Used for discussions by the contributors/maintainers of the Hyperledger Composer project

• #composer-quality
  Used for quality assurance and weekly verification test discussion for the Hyperledger Composer project

• #crypto-lib
  Used to discuss a shared crypto library across the different Hyperledger projects

• #deployment
  Used to discuss deploying any of the Hyperledger projects

• #fabric
  Used to discuss the Hyperledger Fabric project

• #fabric-ca
  Used to discuss the Certificate Authority of the Hyperledger Fabric project

• #fabric-chaincode-dev
  Used to discuss the chaincode development system or application chaincode

• #fabric-chaintool
  Used by the Chaintool project to discuss creating a utility to assist in various phases of Hyperledger Fabric chaincode development, such as compilation, test, packaging, and deployment

• #fabric-ci
  Used to discuss the Continuous Integration for Hyperledger Fabric

• #fabric-connect-a-cloud
  Used to discuss connecting Hyperledger Fabric across multiple hosted environments

• #fabric-crypto
  Used to discuss cryptography for Hyperledger Fabric

• #fabric-dev-env
  Used to discuss setting up and configuring the developer environment for Hyperledger Fabric

• #fabric-documentation
  Used to discuss the documentation for Hyperledger Fabric

• #fabric-evm
  Used to discuss the integration of the EVM with Hyperledger Fabric

• #fabric-gossip
  Used to discuss the gossip protocol used by Hyperledger Fabric

• #fabric-java-chaincode
  Used to discuss creating Java chaincode to use with Hyperledger Fabric

• #fabric-kubernetes
  Used to discuss support for Hyperledger Fabric on Kubernetes

• #fabric-ledger
  Used to discuss the technical aspects of the ledger used by Hyperledger Fabric

• #fabric-maintainers
  Used for discussion amongst or with the maintainers of Hyperledger Fabric

• #fabric-orderer
  Used for discussions regarding orderers and consensus protocols. Questions should be related to the ordering service code and its APIs (Broadcast/Deliver), configuration transactions, or the ordering service consensus plugins (Solo/Kafka/SBFT). See #fabric-orderer guidelines for more information.

• #fabric-orderer-dev
  Used for discussions by the contributors/maintainers of the Hyperledger Fabric's ordering service

• #fabric-peer-endorser-committer
  Used for technical discussions of both endorser and committer used by Hyperledger Fabric

• #fabric-playbacks
  Used to show developers the most current work on Hyperledger Fabric

• #fabric-pr-reviews
  Used to review pull requests for Hyperledger Fabric

• #fabric-quality
  Used to discuss testing of Hyperledger Fabric

• #fabric-questions
  Used to ask questions about Hyperledger Fabric

• #fabric-release
  Used for Hyperledger Fabric release-related questions, surveys, feedback, inquiries, requests, along with discussions of all sorts around: priorities, planning, schedule, milestones, and, of course, announcements

• #fabric-samples
  Used to discuss the fabric-samples repository

• #fabric-scrum
  Used to hold the Scrum meetings for Hyperledger Fabric

• #fabric-sdk
  Used for discussions on Hyperledger Fabric SDK agnostic of programming language

• #fabric-sdk-go
  Used for discussions of Hyperledger Fabric's Go SDK

• #fabric-sdk-java
  Used for discussions of Hyperledger Fabric's Java SDK

• #fabric-sdk-node
  Used for discussions of Hyperledger Fabric's Node SDK

• #fabric-sdk-py
  Used for discussions of Hyperledger Fabric's Python SDK

• #general
  Used for generic discussions relating to blockchain or Hyperledger in general – Discussions here should not be specific to a particular project

• #github-taskforce
  Used to discuss the potential migration from Gerrit to Github

• #hackfest
  Used for discussions during the Hyperledger Hackfests

• #healthcare-wg
  Used by the Healthcare Working Group to announce meeting updates and adhoc meetings

• #hyperledger-bot
  Used by those interesting in contributing to the Hyperledger Hubot that runs on Rocket.Chat (see also https://github.com/hyperledger/hyperledger-rocket-chat-hubot)

• #hyperledger-explorer
  Used by the Hyperledger Explorer project to collaborate on creating a blockchain UI for all Hyperledger blockchain framework projects

• #identity-wg
  Used by the Identity Working Group to announce meeting updates and adhoc meetings

• #indy
  Used to discuss the Hyperledger Indy project

• #indy-agent
  Used to discuss Hyperledger Indy's Agent (p2p endpoints of the network)

• #indy-node
  Used to discuss Hyperledger Indy's validator and observer nodes

• #indy-pr-review
  Used to review pull requests for Hyperledger Indy

• #indy-sdk
  Used for discussions on Hyperledger Indy's SDK

• #infra-support
  Used for discussions related to Infrastructure Support provided by The Linux Foundation for Hyperledger projects

• #iroha
  Used to discuss the Hyperledger Iroha project

• #iroha-smartcontracts
  Used for technical discussions related to Hyperledger Iroha smart contracts

• #japanese
  Used for discussion amongst Japanese community developers (Hyperledger に関する日本語での議論)

• #jenkins-robot
  Used by Jenkins to notify success/failure of CI pipelines (Not currently used)

• #jira
  Used to discuss setting up Jira for new projects

• #jira-notifications
  Used by Jira to notify about new bugs (Not currently used)

• #jobs
  Used for posting Hyperledger-specific job openings

• #labs
  Used for Hyperledger Labs as a place to communicate

• #learning-materials-development-wg
  Used by the Learning Materials Development Working Group to announce meeting updates and adhoc meetings

• #marketing
  Used by the Hyperledger marketing team

• #meetup
  Used by Hyperledger meetup.com organizers to share best practices and material

• #performance-and-scale-wg
  Used by the Performance and Scale Working Group to announce meeting updates and adhoc meetings

• #portuguese
  Used for discussion amongst Portuguese community developers (Canal para comunicação de membros da comunidade Hyperledger em língua portuguesa)

• #quilt
  Used for discussions regarding Hyperledger Quilt

• #requirements-wg
  Used by the Requirements Working Group to announce meeting updates and adhoc meetings

• #rocketchat-chat
  Used to discuss issues with Rocket.Chat

• #russia
  Used for discussion amongst Russian community developers

• #sawtooth
  This is the main channel for asking Sawtooth application and deployment questions.

• #sawtooth-consensus-dev
  Discuss development of consensus algorithms and interfaces for Sawtooth.

• #sawtooth-core-dev
  Discuss internal development of the Sawtooth platform (as opposed to transaction family or smart contract development).

• #sawtooth-infra
  Used to discuss the Continuous Integration for Hyperledger Sawtooth and other infrastructure systems.

• #sawtooth-next-directory
  Discuss development and use of the role based access control sub-project called Next Directory.

• #sawtooth-pr-reviews
  Used to review pull requests for Hyperledger Sawtooth

• #sawtooth-sabre
  Used for discussions on the Sawtooth web assembly smart contract engine (Sabre)

• #sawtooth-seth
  Used for discussions on the integration of Hyperledger Sawtooth and Hyperledger Burrow (SETH - Sawtooth Ethereum)

• #sawtooth-release
  Used for release planning and management

• #tsc
  Used by the Hyperledger Technical Steering Committee to announce meeting updates and adhoc meetings

• #twg-china
  Used by the Technical Working Group China to announce meeting updates, adhoc meetings, and other discussions

• #whitepaper-wg
  Used by the Whitepaper WG to announce meeting updates and adhoc meetings