@bernhard Any ideas on this please? Given there isn’t an identifier to uniquely identify a single Command in a CommandsSubmission batch, as per this discussion.
Is there a way the ledger’s automatic deduplication mechanism could be manually implemented? One approach we were looking at was using a single contract that stores the requestIds (commandIds) that have been successfully executed over the last week (assuming we were looking for a 1 week deduplication period)? The issue with this of course would be the contract would contain a List or Set of a few million values - I’m guessing that would exceed some sort of max contract payload size limitations or gRPC message size limits?