# Should we maintain a daml 'base' or 'prelude-next' library?

**URL:** <https://forum.canton.network/t/should-we-maintain-a-daml-base-or-prelude-next-library/1576>\
**Category:** Outreach\
**Tags:** daml, daml-sdk\
**Created:** [November 4, 2020, 10:15am UTC](https://forum.canton.network/t/should-we-maintain-a-daml-base-or-prelude-next-library/1576 "2020-11-04T10:15:42Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![Martin\_Huschenbett](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.canton.network/martin_huschenbett/32/372_2.png) [@Martin\_Huschenbett](https://forum.canton.network/u/Martin_Huschenbett)\
**Post date:** [November 5, 2020, 6:47pm UTC](https://forum.canton.network/t/should-we-maintain-a-daml-base-or-prelude-next-library/1576/9 "2020-11-05T18:47:49Z")

</div>

> [@Luciano](#):
>
> Does this mean that any contracts (on-ledger) using this library would need to be ‘upgraded’ if we release a new version of the library, even if we haven’t changed the data types we’re using?

@Luciano I assume you’re asking whether your existing active contracts need to be upgraded when you want them to use the new version of your library. Please correct me if I misunderstood your question.

The answer is an emphatic “Yes, that’s exactly what it means” and I would argue that’s exactly what you want in a DAML-like smart contract setting. If it wasn’t like this, you could change the potential consequences of a contract _after_ its signatories have agreed to it by virtue of changing a function in your library, which then changes the behavior of the underlying template. However, that is at odds with one of the fundamental principles of DAML: If you sign a contract, you authorize all its potential consequences, which might make you a signatory of further contracts without your explicit signature being required.

Does that make sense and does it answer your question?

---

_[View the full topic](https://forum.canton.network/t/should-we-maintain-a-daml-base-or-prelude-next-library/1576)._
