> For the complete documentation index, see [llms.txt](https://committees.docs.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://committees.docs.intersectmbo.org/groups-overview/technical-working-groups/hydra.md). # Layer 2 {% hint style="danger" %} **ARCHIVED** This page has been archived. It's content might be outdated. {% endhint %} {% hint style="info" %} The working group is currently being formed and a [dedicated git repository](https://github.com/cardano-scaling/wg-layer2) was chosen to form [charter](https://github.com/cardano-scaling/wg-layer2/blob/main/README.md#hydra-working-group) and processes. This document here is a copy / index of important sections from the charter. Now is the time to get involved if you want to align on Layer 2 technology, stay up-to-date on Cardano Layer 2 projects, or shape the future of Hydra concretely to make our [overall vision on Cardano scaling](https://cardano-scaling.org/#vision) come true. {% endhint %} ## Purpose / Goal > Why is this working group needed? * Break up silos and cross-pollinate projects across the broader domain of scaling Cardano transaction processing * Identify and scope *fundable features* and projects related to Layer 2 technology to be ratified by the community (e.g. through intersect) * Open discussion and governance of the [hydra](https://github.com/cardano-scaling/hydra) project roadmap ## Related committee [Intersect - Technical Steering Committee](https://committees.docs.intersectmbo.org/intersect-technical-steering-committee/) ## Working group lead * Sebastian Nagel (founding / interim) ## Working group members Any stakeholder or enthusiast is free to join this working group, whether working for an organisation in the ecosystem or not. New members must participate in one meeting and state their interest in joining the group. Members may not vote in the first meeting that they attend. ## Working group deliverables > What are we doing concretely? * Share progress and gather feedback on individual project deliveries * Discuss standards and [Cardano Improvement Proposals (CIPs)](https://github.com/cardano-foundation/CIPs) related to layer 2 * Prioritize and get feedback for individual project features (e.g. [Hydra features](https://github.com/cardano-scaling/hydra/issues?q=is%3Aissue%20state%3Aopen%20type%3AFeature)) * Chat about new layer 2 catalyst proposals and long term layer 2 projects, for example Midgard, zkFold, subbit, Cardano Lightning, μgraph, ... ## Collaboration channels * [`#wg-layer2`](https://discord.com/channels/1136727663583698984/1260242964513558548) on Intersect Discord [Invite link](https://discord.gg/cgesQH7xXC) * [`#ask-hydra`](https://discord.com/channels/826816523368005654/890903732462710836) on IOG Discord [Invite link](https://discord.com/invite/Qq5vNTg9PT) * [Git repository](https://github.com/cardano-scaling/wg-hydra) with charter and materials * [Hackmd team](https://hackmd.io/team/wg-layer2) for note taking, meeting notes persisted in repository though ## Working Group Meeting date and time * Bi-weekly using Google Meet, [Wednesday 12:00 UTC](https://meet.google.com/vnz-chhb-qxz) * Subscribe and join using [lu.ma calendar](https://lu.ma/cardano-scaling) If you read this far you might want to join us once we start the roadmap discussions? Signal interest on above's collaboration channels by dropping a message [on Discord](https://discord.gg/Qq5vNTg9PT), [on Twitter](https://x.com/ch1bo_), or by [opening an issue](https://github.com/cardano-scaling/wg-layer2/issues/new/choose). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://committees.docs.intersectmbo.org/groups-overview/technical-working-groups/hydra.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.