Do you foresee any problem with replacing the following template design… template Asset with owner : Party others : [Party] id : Text amt : Decimal -- : -- : -- a hundred other fields -- (some nested data structures) -- that the client wants "on the…

This sounds like a good design choice. It makes it explicit that the ledger is used to distribute opaque payloads and that distribution is governed by the fields that are not opaque. This also has precedent in systems like k8s where every object can carry annotations in their metadata that are not …

I’m not a fan of storing opaque blobs on the ledger. Store a reference (I like the idea of storing a hash of some canonical form as @Simon_Meier suggested). Blobs can’t partake in Daml’s authorization semantics or benefit from Daml’s type-safety, so why store them? As far as contract migrations g…

Sorry it has taken me so long to respond. In principle there is nothing wrong with this, and for very small json fragments this should work fine. As the json blob gets larger, you will start to run into operational issues. At some point the JSON blob will have to pass over the ledger API, if it …

Avoid contract upgrades with a JSON text field

App Development

WallaceKelly August 21, 2023, 7:02pm 2

One of our founders, who will remain anonymous (cc: @Shaul), pointed me at this related post.

Topic		Replies	Views
Will there be naming conflicts if I upgrade my contracts on Daml on Fabric (or any ledger)? App Development daml-on-fabric , upgrading	20	1050	March 26, 2021
Mapping Json values App Development	6	404	July 5, 2022
Daml Template Data conversion to JSON data App Development	5	1577	August 16, 2023
Can we use JSON API to fetch a large amount of contracts (e.g: 1M, 10M,..?)? App Development daml	2	242	March 23, 2022
Upgrade contracts, collect signs App Development upgrading	6	648	May 7, 2021

Avoid contract upgrades with a JSON text field

Related topics