Considerations for TruBudget 2.0

[mayrmartin]

We are planing for TruBudget 2.0. In this context, we aim to solve a GDPR related issue when storing documents via on-chain storage. At the moment - depending on the system configuration - data is either stored on the off-chain or on the on-chain storage. When storing on-chain documents can not be deleted in the future and documents get shared with all nodes in the network. To address this problem, we will discontinue the on-chain storage option. This means existing files will not be further stored on the chain but rather on the storage service.

This - obviously - will cause some breaking changes. To allow a smooth transition from TruBudget 1. x to 2. x, we will provide a migration script. When developing this migration script, some considerations to take into account:

• Where to read/write the data from/to? API/Blockchain?
  • We will read data from the Blockchain and use the API to write the data on the new chain
• Documents
  • Documents stored off-chain should be stored on storage service
  • Documents stored on-chain should be stored on storage service
  • What happens with secrets related to documents?
• User
  • Can be migrated 1:1
• Chain encryption
  • Data on a new chain should be encrypted if the old chain was encrypted
• Timestamps
  • should migrated events have the original timestamp? or shouldn't there be an additional timestamp for not migrated events?