OpenZeppelin has put the first public pieces of its Daml development stack for Canton in front of the developer community. This early-stage development work gives builders a closer look at a privacy-preserving exchange, a lending protocol, cross-chain stablecoin payments and a confidential auction as reference architectures for future Canton applications.
A shared starting point
Building financial software on a new network can begin with the same hard questions every time: how should an asset move, how should settlement work, and where should privacy and permissions sit in the design? OpenZeppelin has made shared code and design material available for Canton builders to test, read and review.
The release includes a Daml contracts library implementing the CIP-112 token and settlement standard. CIP-112 is an approved standards-track evolution of CIP-56 that is designed to remain backward compatible with it. OpenZeppelin has also published designs showing how that tooling could support four common financial patterns: a privacy-preserving decentralized exchange, lending, cross-chain stablecoin payments and confidential auctions.
From public designs to future applications
The four published use cases are design documents, with implementation work beginning in a later milestone. The repository labels the software experimental, and OpenZeppelin says releases will undergo a full security audit after community feedback.
The announcement invites developers to test the repositories, read the designs and provide feedback. The public materials include specific designs for settlement, privacy, authority and interoperability questions that application teams would need to address.
Why it matters for Canton
OpenZeppelin’s repository describes the work as reference designs, experimental implementations and interoperability research for Canton applications. Its public release puts those materials in front of developers for testing and feedback.
It is a public invitation to review early development work. OpenZeppelin says implementation code begins in the next milestone and that releases will undergo a full security audit after community feedback.
The work is now public for testing and feedback; implementation remains a future milestone.
