The QRL Ecosystem Index is a community-maintained directory of projects, tools, services, and resources across QRL 1.x and QRL 2.0. Its goal is to make the ecosystem easier to explore by collecting project information in one structured, searchable place.
Each listing is stored as YAML in the public repository and validated against schema v6. Artifact type, use-case categories, primary capabilities, available platforms, QRL support and deployments, lifecycle, provenance, and links are recorded as independent facts. This makes changes reviewable and keeps classification from implying maturity or trust.
What gets listed
Listings may include protocols, user-facing applications, infrastructure, developer tooling, and community resources. A project does not need to be complete, but it should have enough public information for others to understand what it is, who maintains it, its QRL relationship, and the generations or environments it supports.
The project directory covers both QRL generations. Builder guidance, Getting Started, and Ideas currently focus on QRL 2.0 and are labelled accordingly.
This index is informational. Inclusion does not mean endorsement by QRL, the QRL Foundation, or the maintainers of this repository.
Analytics and privacy
If you choose to allow analytics, the site uses Google Analytics to understand page visits, scrolling, and links to listed projects. Analytics is not loaded before you make that choice, and you can change it using Analytics settings in the footer. The site also respects a browser’s Do Not Track signal.
How projects are organized
Each project has an artifact type:
- protocol - On-chain or protocol-level logic with a documented deployment
- application - User-facing software such as wallets, explorers, or interfaces
- infrastructure - Services, nodes, APIs, indexers, or other network-supporting systems
- tooling - SDKs, libraries, templates, testing tools, or developer utilities
- resource - Community spaces, educational resources, news, research, or ecosystem information
Type is independent from use-case classification. Every project has one primary category, up to two secondary categories, one to four controlled capabilities, and a separate list of applicable platforms. Projects also record their QRL relationship, support, and any concrete deployments separately.
Lifecycle and trust
Maturity (prototype, beta, stable, or deprecated) and availability (live, limited, paused, offline, or archived) are separate. Network environment is not a maturity label.
Publisher, maintainer, repository, license, security-review, and evidence records provide context without creating an endorsement. Evidence and ownership checks do not produce public trust labels in the initial schema v6 release. The moderation and takedown policy explains reporting and safety responses.
Homepage spotlight
The homepage spotlight is not editorially selected. It rotates weekly among projects that are marked stable and live and include at least one gallery screenshot. Eligible listings are ordered by their stable project ID before the weekly selection is calculated. Appearance in the spotlight is not a ranking, endorsement, audit, or affiliation.
Submitting updates
Project data is managed through GitHub. To add a new project or update an existing one, open a pull request in the qrl-ecosystem-index repository. See CONTRIBUTING.md for the submission format, validation rules, and branding guidance.