[RFW0001] Implementing metadata of DSR transactions on the Cardano blockchain

[ProfilaMitchell]

Table of Contents

• Housekeeping
• The Problem
• User Story
• Request Type A/B
• Owner
• Summary
• Is This Really Necessary?
• Motivation
• Named concepts
• Examples, Risks & Assumptions
• Success Metrics
• Conceptual Design
• Drawbacks
• Alternatives
• New Data
• Business Release Date

Housekeeping

Make sure to clearly understand Type-A and Type-B requests, and the relevant limitations. Failing to follow the guidelines pertaining to the two acceptable types of RFWs will automatically lead to disqualification of the RFW.

Take time to complete each section below with as much detail as is required to establish a comprehensive understanding about the underlying product specification.

ALL BELOW FIELDS ARE REQUIRED

The Problem

DSRs executed by Profila users are not currently lodged on blockchain

User Story

As a Profila user I want to have my DSR assertion recorded on the blockchain so that I have immutable proof of its execution

• High business severity - Having immutable proof of the DSR is a core part of the functionality of the base Profila platform
• High priority - Core functionality of the Profila platform

Request Type A/B

Type A

This RFW is an extension of the DSR Assertion feature
This RFW is an extension of the Individual DSR Management Panel
This RFW is an extension of the Brand DSR Response Panel

Owner

Michiel Van Roey

Summary

The implementation of writing metadata of DSR assertions from users onto the Cardano blockchain is being introduced. This RFW details the web3 details of the DSR process between brands and users.

Is This Really Necessary?

As a core feature of the Profila platform, allowing both brands and users to view executed DSRs on the blockchain in an immutable for is the "best way" to facilitate our discussed mission.

Motivation

By inserting the metadata of DSR assertions onto the blockchain, we provide both the user and brand with immutable proof that the right was asserted, as well as whether an action was taken or not to remedy the assertion.

The scope of this request:

• The details of what metadata is written onto the blockchain via smart contract

Named Concepts

N/A

Examples, Risks & Assumptions

1. Explain concretely what will manifest as a result of this RFW.

• Once a brand confirms on the platform that an action was taken with respect to a DSR assertion, the metadata of said DSR transaction will be written on the Cardano blockchain

2. Explain how is it different from what is already manifesting i.e. what we already have?

There is currently no blockchain record of DSRs executed using the Profila platform

3. Explain what Profila users/brands will experience as a result of this RFW. How will they feel as a result of it? How will they benefit as a result of it?

• Profila users will be able to obtain a PDF which contains a link to the blockchain view of the DSR metadata on the blockchain

• Brands will be able to verify the assertion on the Blockchain

4. If applicable, provide sample messages for any new messages the system will display as a result of this RFW.

N/A

5. Define what is out of scope in this request.

• The assertion of a DSR is out of scope of this request
• The Individual DSR Management panel is out of scope of this request
• The brand DSR Response panel is out of scope of this request

6. What are the data protection, privacy and security assumptions made for this request (example, should this be GDPR, HIPPA (healthcare), NIST compliant etc. - Speak to Michiel or Ipek!)

N/A

7. Explain how this user story will be supported (i.e customer support - if the user story fails technically, how will the user be supported).

Support Flow
If the DSR cannot be logged to the blockchain due to a technical fault, the Tech team should be notified so that they can resolve the issue.

Brand Logic

• There is text that lets the brand know that the DSR could not be written to the blockchain, but that the technical team will resolve the issue

Tech Support Logic

• Needs to resolve issue of why DSR not written to blockchain

8. Explain how this user story impacts revenue or billing (if applicable).

The transaction of writing the metadata to the blockchain incurs a cost

9. State any additional risks identified as a result of this user story.

N/A

Success Metrics

DSRs executed by users are recorded on the blockchain

Conceptual Design

The metadata entry takes place once the brand has confirmed in their Response Panel that they have taken the appropriate action.

The metadata entry to the blockchain should include:

• The brand name
• The user's full name
• The user's email address
• The DSR that was asserted by the user
• Confirmation text that confirm's the brand has taken the action
  • ""BRAND NAME" hereby confirms that appropriate measures have been taken to resolve this DSR assertion from "USER's FULL NAME""
• The date and time the DSR was initially asserted
• The date and time the DSR was confirmed as resolved

Drawbacks

For the brand to see the DSR in an easy manner (brand dashboard), they too must be using the Profila platform

Alternatives

New Data

The DSRs entry into the blockchain

Business release date

Delivery of the Brand DSR Response panel is requested by February 2023