A community-maintained collection of Substrate runtime modules (pallets) for building blockchain applications.
ORML (Open Runtime Module Library) is a collection of reusable runtime modules (pallets) for the Substrate blockchain framework. It provides pre-built components like token systems, auction mechanisms, oracle feeds, and cross-chain messaging tools, enabling developers to build custom blockchains faster and with greater reliability.
Blockchain developers and teams building parachains or standalone blockchains using the Substrate framework, particularly those in the Polkadot and Kusama ecosystems.
Developers choose ORML to avoid reinventing common blockchain components, leveraging community-audited, production-tested modules that ensure interoperability and reduce development time and risk.
Substrate Open Runtime Module Library
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
ORML modules are used by major projects like Acala and Moonbeam, as listed in the README, indicating they have undergone real-world testing and audits.
Includes essential pallets for tokens, auctions, oracles, and XCM support, reducing the need to build from scratch, as detailed in the runtime modules overview.
Provides specific modules like xcm-support and xtokens that facilitate cross-chain token transfers, a key feature for Polkadot ecosystem interoperability.
Listed as used by over 30 projects including Astar and Parallel Finance, demonstrating reliability in live networks and community trust.
The asset-registry pallet is noted to have Acala-specific elements in the README, making it less suitable for other teams without modification.
Requires copying Cargo.dev.toml to Cargo.toml for local development, adding an extra step and potential for configuration errors, as mentioned in the development section.
Only points to a workshop example for usage, lacking comprehensive tutorials or detailed API documentation, which can slow onboarding for newcomers.
Tightly coupled with Substrate's FRAME, so breaking changes in Substrate could require updates to ORML, introducing maintenance overhead and versioning issues.