Since the last report, our team have been working on the development of the final POC of this feature. This work includes further UI drafts of the feature, as shown in the PDF attached. These alterations in UI reflect internal business discussions around consumer user case as well as scope prioritisation. Our developmental state of the proposal is still visible in our public Github repo here: https://github.com/Profila/Catalyst https://github.com/Profila/Catalyst/issues/3.

Since the last report, our team have been working on the development of the final POC of this feature. This work includes the UI drafts of the feature as internal discussions are still taking place to finalise minute details of implementation. This draft UI is found in the attached PDF. Our developmental state of the proposal is still visible in our public Github repo here: https://github.com/Profila/Catalyst https://github.com/Profila/Catalyst/issues/3.

As mentioned above, since the last report we have integrated an internal development team, consisting of two members. These new team members have been evaluating our deliverables and doing research into any external products needed. For this proposal, all that is left is to develop the front end for the community to see and interact with it. Our developmental state of the proposal is still visible in our public Github repo here: https://github.com/Profila/Catalyst https://github.com/Profila/Catalyst/issues/3 . In relation to this project, we have worked with partner Mlabs to deliver working and demonstrable code in relation to the minting of an NFT, which is an essential part of the project in sharing data between users and brands in an immutable way, as well as automating access to user data. The next phase will be demonstrating the code in a more concise way for non-technical community members (and closing out the report)

As mentioned above, since the last report we have integrated an internal development team, consisting of two members. These new team members have been adapting and learning to existing systems in the business, as well as evaluating all of our current Catalyst Proposal deliverables. Our developmental state of the proposal is still visible in our public Github repo here: https://github.com/Profila/Catalyst https://github.com/Profila/Catalyst/issues/3 . In relation to this project, we have worked with partner Mlabs to deliver working and demonstrable code in relation to the minting of an NFT, which is an essential part of the project in sharing data between users and brands in an immutable way, as well as automating access to user data. The next phase will be demonstrating the code in a more concise way for non-technical community members (and closing out the report)

We have made progress in two core aspects of this project. These are: development, and team organisation and workflow. — 1. Development Work — We continue to utilise our public repo (linked below) on Github wherein we have been adding RFW/RFC (Request for Work, Request for Comment) issues to display internal logic when approaching the development of features. This repo is also populated with UX designs so that a visual indication of the progress of our work is now visible. Additionally, via the projects tab we will be displaying respectively which RFWs apply to which feature to make our roadmap more transparent. The RFW that correlates to the development of this can be viewed in our GitHub repo. https://github.com/Profila/Catalyst https://github.com/Profila/Catalyst/issues/1 https://github.com/orgs/Profila/projects/3

A core part of our progress has been development work regarding the minting of NFTs within our own platform. Originally planning to use PlayerMint's smart contract, MLabs instead developed a new smart contract that is better suited to our needs. Remaining work now needs to be done regarding off-chain work. This Progress report is provided as evidence of progress in the next section (alongside the RFW in our public catalyst repo above).

. –– 2. Team Organisation and Workflow — As we continue to handover from our previous dev team, we are in the process of hiring an internal engineer for development projects. We are conducting interviews and aim to make a final decision soon. We have also signed an agreement with development house SteppeChange, pioneers in developing data and marketing tech solutions. This is in addition to our updated roadmap and delegation of development tasks among a select few other parties such as Virtido, PSG, UC3m, and Mlabs. This project specifically has utilised the consultancy of Mlabs. We have also direct contracted advisory services now from Mikko Kotila and blockchain advisory from Carlos Vargas.

We have made progress in all respects of this project. These include code development, team organisation and workflow, as well as community based commitments.

1. Development Work

We have now opened a public repo (linked below) on Github wherein we will be adding respective code for the project. We will also be adding RFW/RFC (Request for Work, Request for Comment) issues to display internal logic when approaching the development of features. Additionally, via the projects tab we will be displaying respectively which RFWs apply to which feature to make our roadmap more transparent.

A core part of our progress has been development work regarding the minting of NFTs within our own platform. Originally planning to use PlayerMint's smart contract, MLabs instead developed a new smart contract that is better suited to our needs. As mentioned above, this code can be viewed on our public Github repo, as well as the RFW that correlates to the development of this (this is the RFW that is attached above).

https://github.com/Profila/Catalyst https://github.com/Profila/Catalyst/issues/3 https://github.com/orgs/Profila/projects/6 https://github.com/Profila/Catalyst/tree/add-mint-contract

2. Team Organisation and Workflow

As we continue to handover from our previous dev team, we are in the process of hiring an internal engineer for development projects.

Additionally, in line with our updated roadmap we are now delegating and finalising development tasks among a select few parties. These include Virtido, PSG, UC3m, and Mlabs. This project specifically has utilised Mlabs for development thus far.

We have also direct contracted advisory services now from Mikko Kotila and blockchain advisory from Carlos Vargas.

3. Community based commitments

As a part of our progress update and new approach, we want to ensure that not only are the catalyst community updated and aware of our progress, but our entire community.

To do this, we are committed to hosting a Product Update stream / Twitter Space in August (date tbd) on one of our social media channels to inform our community of our progress to date on catalyst developments as well as overall platform decisions.

Mlabs has reviewed our initial proposal to integrate smart contract for the data subscription functionality where brands access people's data. After some sessions, we have decided that using NFTs instead of smart contracts will be better. We are now working on a formal spec to detail what this NFT process will look like, based on the parameters shows in the picture : - The user's information will be stored on your servers, but encrypted

• The user will use your service to mint an NFT
• The NFT's metadata will contain the password to unencrypt the data on the server
• The user will give the NFT to the business
• The business must pay the user as long as they hold the NFT
• When the time period of the authorization expires, the information on the server will be re-encrypted with a new password, rendering the old NFT void

Which was subsequently improved as follows: Nate Lane, [14/06/2022 17:27] Our new proposed approach is to give the company an NFT that authorizes them to access the information. Then when they try to access a user’s information, we are able to check their wallet to make sure that they own the access NFT

Nate Lane, [14/06/2022 17:29] So rather than having any information or metadata associated with the NFT, we simply check if the company owns the NFT, and give them the info if and only if they have that NFT

Partnership with Mlabs announced for assistance on the development of the smart contract

Parternship with Mlabs announced for assistance on the development of the smart contract

Profila has signed an engagement with Mlabs for the certain professional services and development services in relation to Profila’s Catalyst projects and ZEKE token governance. Mlabs will work with our development team and CTO on the smart contract development necessary for this fund 6 proposal

Working on partnership with Gimbalabs and Mlabs to help in the development of the smart contract for the data sharing feature of our app as explained in this proposal. Our development team is learning through Plutus Pioneer Program. We are making progress