# · "Daml multi-party authorization — what tripped you up?" **URL:** \ **Category:** App Development\ **Created:** [September 22, 2026, 7:08pm UTC](https://forum.canton.network/t/daml-multi-party-authorization-what-tripped-you-up/9210 "2026-09-22T19:08:37Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![Bikko\_Chains](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.canton.network/bikko_chains/32/7816_2.png) [@Bikko\_Chains](https://forum.canton.network/u/Bikko_Chains)\ **Post date:** [October 2, 2026, 9:59am UTC](https://forum.canton.network/t/daml-multi-party-authorization-what-tripped-you-up/9210/5 "2026-10-02T09:59:03Z")
> [@Colin](#): > > There are definitely a few existing efforts to build reference implementations and/or canonical design patterns for different parts of the stack. Maybe worth a look, if you haven’t already. > Ex: [Proposal: OpenZeppelin Canton Ecosystem Stack by xdaluca · Pull Request #262 · canton-foundation/canton-dev-fund · GitHub](https://github.com/canton-foundation/canton-dev-fund/pull/262) > > Otherwise, I think the answers to these questions probably vary quite a bit between teams, especially where they begin to become/involve _business_ decisions. Thanks — that’s helpful, and we have looked at #262. Our view is that SettleFlow is complementary rather than overlapping: OpenZeppelin Canton Ecosystem Stack is about standardizing reusable contract foundations and canonical patterns, while SettleFlow is focused on the missing coordination layer for 3-party DvP workflows on top of existing primitives like CIP-56 and Daml Finance. We’re intentionally staying narrower so we can prove one concrete end-to-end workflow, rather than trying to define the whole stack. If you know of any teams working on reference implementations for settlement coordination specifically, I’d love to look at those too. --- _[View the full topic](https://forum.canton.network/t/daml-multi-party-authorization-what-tripped-you-up/9210)._