Posts

Showing posts from February 24, 2019

Communes of the Seine-et-Marne department

Image
Communes of the Seine-et-Marne department From Wikipedia, the free encyclopedia Jump to navigation Jump to search The following is a list of the 510 communes of the Seine-et-Marne department of France. The communes cooperate in the following intercommunalities (as of 2017): Communauté d'agglomération Coulommiers Pays de Brie Communauté d'agglomération Grand Paris Sud Seine-Essonne-Sénart (partly) Communauté d'agglomération de Marne et Gondoire Communauté d'agglomération Melun Val de Seine Communauté d'agglomération Paris - Vallée de la Marne Communauté d'agglomération du Pays de Fontainebleau Communauté d'agglomération du Pays de Meaux Communauté d'agglomération Roissy Pays de France (partly) Val d'Europe Agglomération Communauté de communes de la Bassée - Montois Communauté de communes de la Brie des Rivières et Châteaux Communauté de communes La Brie Nangissienne Com

Is it possible to trigger a contract with a not prunable public trigger message?

Image
7 0 In the current state pruning is not implemented. Therefore an attached public trigger message should stay in the blockchain until pruning is enabled. When this is the case, will it be possible to make the trigger message unprunable? This could be useful for contract params validation. For example: If I trigger a contract with the following attached message: {"contract":"ExampleContract","params":{"veryImportantParameter":"42"}} I would like to make this message public (so everybody can validate that I've triggered the contract ExampleContract with the parameter veryImportantParameter and it's value 42 ) and not prunable (so that everybody can validate the message at any time in the future). Is this going to be possible?