This deliverable describes the exploitation strategies of the (industrial) partners as well as of the project as a whole. (T5.4)
This deliverable consolidates all the dissemination activities uptaken so far and presents a plan for further dissemination. (T5.1)
This deliverable outlines the initial strategy for communication and dissemination and all the required information on the elements on the website.
This document will contain the requirements for all the use cases. The main idea is to have separate requirements for each use case. Note that, there can be privacy issues that could be similar in the use cases. Such cases will lead to similar requirements too. These requirements will be grouped together. (T1.1)
This deliverable includes all the necessary descriptions on project design, template design for presentations, logo, online visual identity, design of posters etc. (T5.2)
This deliverable will present standard and new definitions and notions of privacyenhancing cryptographic primitives that are useful for distributed ledgers. (T2.2)
The quality assurance describes the standards, processes and procedures for the expected results of the project. (T6.2)
The project reference manual and tools outlines all the internal project delivery processes such as mailing lists, deliverable templates, presentation templates etc. (T6.1)
The state of the art in distributed ledgers is summarised focusing on the cryptographic aspects of the existing constructions. (T3.1)
The deliverable covers the architecture of protocols for secure ledger systems, such as authentication within the infrastructure, solutions for updating the ledger protocols, or results on consensus protocols. (T4.1)
This deliverable describes the impact of the research results as well as the preliminary implementations. (T6.2)
This deliverable presents the state of the art on privacy-enhancing cryptographic primitives that are useful for distributed ledgers. (T2.1)
As PRiVILEDGE is taking part in the Pilot on Open Research Data a first version of the DMP as an early deliverable will be provided within the first six months of the project. The purpose of the DMP is to provide an analysis of the main elements of the data management policy that will be used by the applications with regard to all the datasets that will be generated by the project. The DMP is not a fixed document, but evolves during the lifespan of the project. More developed versions of the plan can therefore be included as additional deliverables at later stages. According to the Guidelines on Data Management in Horizon 2020, the DMP should address data set reference and name, data set description, standards and metadata, data sharing and archiving and preservation (including storage and backup) on a dataset by dataset basis and should reflect the current status of reflection within the consortium about the data that will be produced.