Since our last report, we have been investigating the end result of the project in terms of how it fits into the platform. In the past month this involved developing the UI of the logic that we previously submitted. This draft UI is still under development, but is attached in the PDF with this form. 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/5 https://github.com/orgs/Profila/projects/4. ––

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/7 https://github.com/orgs/Profila/projects/3 –– After consultation with IOG in regards to all of our Atala Prism incorporating projects, we have received guidance that V2 of PRISM, once delivered, will be better equipped to provide our proposals with success. From this guidance we have decided to pause activity on the development and implementation of these proposals until the technology is ready. This includes this proposal, which facilitates the sharing of data between two sets of DIDs. We value the stability, scalability, and readiness that our proposal, if executed correctly, can offer the Cardano community. Due to this, we will reserve the allocated funds received to continue development with V2 of Prism once released. We are aware that this report does not show immediate progress, but with the release of ATALA PRISM V2 we will be able to progress with the project. This month we have had discussions with IOHK and are signing an NDA on updated scope of work. This document cannot be made public, but when work commences, all progress will be shown.

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/8 https://github.com/orgs/Profila/projects/3 –– After consultation with IOG in regards to all of our Atala Prism incorporating projects, we have received guidance that V2 of PRISM, once delivered, will be better equipped to provide our proposals with success. From this guidance we have decided to pause activity on the development and implementation of these proposals until the technology is ready. This includes this proposal, controlling data with Profila part 2 (integration of DID wrapper into mobile). We value the stability, scalability, and readiness that our proposal, if executed correctly, can offer the Cardano community. Due to this, we will reserve the allocated funds received to continue development with V2 of Prism once released. We are aware that this report does not show immediate progress, but with the release of ATALA PRISM V2 we will be able to progress with the project. This month we have had discussions with IOG on the scope of our requests based on the no too distant release of V2. We have also updated our RFW accordingly (linked)

Since the last report, we have been working on putting together the intractable database of the project, as well as the collection form. This database can be accessed using the username: 'profila' and password 'profila2022'. The link is attached in the next section. Attached is also a screenshot of the submission form created. This is just a screenshot as we do not yet want people to submit documents to the database.

Since the last report, our new team members have been working on the eventual implementation of the project despite the delays described below. These developments can be found in an internal RFC document, which is attached within this form and since our last report has reached phase 2. 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/1 https://github.com/orgs/Profila/projects/3. —– After consultation with IOG in regards to all of our Atala Prism incorporating projects, we have received guidance that V2 of PRISM, once delivered, will be better equipped to provide our proposals with success. From this guidance we have decided to pause activity on the development and implementation of these proposals until the technology is ready. This includes this proposal, registering and sign up through use of DID. We value the stability, scalability, and readiness that our proposal, if executed correctly, can offer the Cardano community. Due to this, we will reserve the allocated funds received to continue development with V2 of Prism once released.

Since the last report, we have been working on the user interface in how they will interact with the brand content. Screenshots of the UX progress are attached here. We are also still consulting advisors on the payoff logic of each brand interaction. 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/6 https://github.com/orgs/Profila/projects/5

Since the last report, our team have been working on the finalisation of the logic of gamification within the platform.This includes the logic around how we want to prevent the system being used merely to gain tokens. Attached is a list of unwanted behaviours we have deduced using game theory, as well as our preventative measures. As before, it is still under internal review. 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/4 https://github.com/orgs/Profila/projects/5

Since the last report, our team have been working on the development of the final POC of this feature. This work includes the logic of how a brand interacts with the content produced by the user. This logic is evidenced in the respective PDF attached. 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 https://github.com/orgs/Profila/projects/6. 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 and has been submitted previously. The next phase will be demonstrating the code with content attached (so the result is more clear) and integrating front and backend developments. This required considering both the consumer (demonstrated last month in the report) as well as the business perspective (this report)

Since the last report, we have been working on the payoff logic for how many tokens, or percentage of a token, that a user should earn per action taken on the platform. This draft document is attached in the form but is a draft as we are consulting advisors. 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/6 https://github.com/orgs/Profila/projects/5

Since the last report, we have been working on validating the previously submitted database structure. Since then, we have validated the structure with our partner HSLU. We also held an in person meeting with HSLU, and partnered with Brussels University (signed) for internships to collect the documents we need as part of the database.

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/8 https://github.com/orgs/Profila/projects/3 –– After consultation with IOG in regards to all of our Atala Prism incorporating projects, we have received guidance that V2 of PRISM, once delivered, will be better equipped to provide our proposals with success. From this guidance we have decided to pause activity on the development and implementation of these proposals until the technology is ready. This includes this proposal, controlling data with Profila part 2 (integration of DID wrapper into mobile). We value the stability, scalability, and readiness that our proposal, if executed correctly, can offer the Cardano community. Due to this, we will reserve the allocated funds received to continue development with V2 of Prism once released. We are aware that this report does not show immediate progress, but with the release of ATALA PRISM V2 we will be able to progress with the project.

Since our last report, we have been investigating the end result of the project in terms of how it fits into the platform. In the past month this involved looking at how the user is affected and interacts with this project, which is business based. This logic and impact has been demonstrated in the attached document. 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/5 https://github.com/orgs/Profila/projects/4. –– The RFW document for this proposal has been updated to reflect business integration changes, however all notable developments are in the document attached.

Since the last report, our new team members have been working on the eventual implementation of the project despite the delays mentioned later in the section. These developments can be found in an internal RFC document, which is attached within this form. 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/1 https://github.com/orgs/Profila/projects/3. —– After consultation with IOG in regards to all of our Atala Prism incorporating projects, we have received guidance that V2 of PRISM, once delivered, will be better equipped to provide our proposals with success. From this guidance we have decided to pause activity on the development and implementation of these proposals until the technology is ready. This includes this proposal, registering and sign up through use of DID. We value the stability, scalability, and readiness that our proposal, if executed correctly, can offer the Cardano community. Due to this, we will reserve the allocated funds received to continue development with V2 of Prism once released.

Since the last report, our team have been working on the finalisation of the logic of gamification within the platform.This includes the logic around what features we want to gamify. This draft has been included in the attachment section and is currently under internal review. 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/4 https://github.com/orgs/Profila/projects/5

Since the last report, our team have been working on the development of the final POC of this feature. This work includes the UI of the front end, final version of the feature which is evidenced in the respective attachment. 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 https://github.com/orgs/Profila/projects/6. 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. The next phase will be demonstrating the code with content attached (so the result is more clear) and integrating front and backend developments

We have worked on the database structure of WP1, assigning and delegating out the initial preliminary workflow. We've attached this document in the latter half of the form. We are actively working on this document as well as continuing communications with HSLU on the timeline of project completion.

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. 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/7 https://github.com/orgs/Profila/projects/3 –– After consultation with IOG in regards to all of our Atala Prism incorporating projects, we have received guidance that V2 of PRISM, once delivered, will be better equipped to provide our proposals with success. From this guidance we have decided to pause activity on the development and implementation of these proposals until the technology is ready. This includes this proposal, controlling data via PRISM part 2 (integration of DID into data subscription between brands and users). We value the stability, scalability, and readiness that our proposal, if executed correctly, can offer the Cardano community. Due to this, we will reserve the allocated funds received to continue development with V2 of Prism once released.

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. 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/8 https://github.com/orgs/Profila/projects/3 –– After consultation with IOG in regards to all of our Atala Prism incorporating projects, we have received guidance that V2 of PRISM, once delivered, will be better equipped to provide our proposals with success. From this guidance we have decided to pause activity on the development and implementation of these proposals until the technology is ready. This includes this proposal, controlling data with Profila part 2 (integration of DID wrapper into mobile). We value the stability, scalability, and readiness that our proposal, if executed correctly, can offer the Cardano community. Due to this, we will reserve the allocated funds received to continue development with V2 of Prism once released.

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. . 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/6 https://github.com/orgs/Profila/projects/5 –– The RFW document will be updated in the coming month as we consult externally surrounding the gamification of the entire Profila platform and incentivising users to interact with brand content. The documentation surrounding gamification has been created and is being finalised

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. 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/5 https://github.com/orgs/Profila/projects/4. –– The RFW document for this proposal has been updated to reflect business integration changes.

As mentioned above, since the last report we have integrated an internal development team, consisting of two members. hese new team members have been evaluating our deliverables and doing research into any external products needed. 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/4 https://github.com/orgs/Profila/projects/5 –– The gamification documentation surrounding the platform has been written and is now being designed by our internal UX team

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 https://github.com/orgs/Profila/projects/6. 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. The next phase will be demonstrating the code with content attached (so the result is more clear) as aforementioned

As mentioned above, since the last report we have integrated an internal development team, consisting of two members. 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. 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/1 https://github.com/orgs/Profila/projects/3. —– After consultation with IOG in regards to all of our Atala Prism incorporating projects, we have received guidance that V2 of PRISM, once delivered, will be better equipped to provide our proposals with success. From this guidance we have decided to pause activity on the development and implementation of these proposals until the technology is ready. This includes this proposal, registering and sign up through use of DID. We value the stability, scalability, and readiness that our proposal, if executed correctly, can offer the Cardano community. Due to this, we will reserve the allocated funds received to continue development with V2 of Prism once released.

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/8 https://github.com/orgs/Profila/projects/3 –– After consultation with IOG in regards to all of our Atala Prism incorporating projects, we have received guidance that V2 of PRISM, once delivered, will be better equipped to provide our proposals with success. From this guidance we have decided to pause activity on the development and implementation of these proposals until the technology is ready. This includes this proposal, controlling data with Profila part 2 (integration of DID wrapper into mobile). We value the stability, scalability, and readiness that our proposal, if executed correctly, can offer the Cardano community. Due to this, we will reserve the allocated funds received to continue development with V2 of Prism once released.

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/7 https://github.com/orgs/Profila/projects/3 –– After consultation with IOG in regards to all of our Atala Prism incorporating projects, we have received guidance that V2 of PRISM, once delivered, will be better equipped to provide our proposals with success. From this guidance we have decided to pause activity on the development and implementation of these proposals until the technology is ready. This includes this proposal, controlling data via PRISM part 2 (integration of DID into data subscription between brands and users). We value the stability, scalability, and readiness that our proposal, if executed correctly, can offer the Cardano community. Due to this, we will reserve the allocated funds received to continue development with V2 of Prism once released.

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/1 https://github.com/orgs/Profila/projects/3. —–

After consultation with IOG in regards to all of our Atala Prism incorporating projects, we have received guidance that V2 of PRISM, once delivered, will be better equipped to provide our proposals with success.

From this guidance we have decided to pause activity on the development and implementation of these proposals until the technology is ready. This includes this proposal, registering and sign up through use of DID. We value the stability, scalability, and readiness that our proposal, if executed correctly, can offer the Cardano community. Due to this, we will reserve the allocated funds received to continue development with V2 of Prism once released.

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/6 https://github.com/orgs/Profila/projects/5 –– The RFW document will be updated in the coming month as we consult externally surrounding the gamification of the entire Profila platform and incentivising users to interact with brand content.

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 https://github.com/orgs/Profila/projects/6. 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. The next phase will be demonstrating the code with content attached (so the result is more clear)

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/4 https://github.com/orgs/Profila/projects/5 –– The RFW document will be updated in the coming month as we consult externally surrounding the gamification of the entire Profila platform, which includes the psychographic element of data input from users (building up their Profila via Category Quizzes)

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/5 https://github.com/orgs/Profila/projects/4. –– The RFW document for this proposal has been updated to reflect business integration changes.

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/6 https://github.com/orgs/Profila/projects/5

Internal discussions have been taking place regarding the implementation of our consumer shared 'moments', how most effectively to implement a first version, as well as how to efficiently use them for increased brand interaction.

–– 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. We have also direct contracted advisory services now from Mikko Kotila and blockchain advisory from Carlos Vargas.

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 We have been working directly with IOG PSG in respect to the viability of implementing PRISM and will continue to work with them on this project as well as have their involvement in our other PRISM related catalyst project. Some aspects of our integration of PRISM rely on the development of PRISM itself, which contributes to our project's extended length. Progress has specifically been made in the regard of this proposal in that use of MagicLink has been discussed and finalised as a solution to make user sign up more efficient as well as user-friendly.

–– 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 IOG PSG. We have also direct contracted advisory services now from Mikko Kotila and blockchain advisory from Carlos Vargas.

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/3 https://github.com/orgs/Profila/projects/6 –– 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 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/4 https://github.com/orgs/Profila/projects/5

We have been having internal discussions to develop out the gamification elements of our MVP as based on our catalyst proposal. –– 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. We have also direct contracted advisory services now from Mikko Kotila and blockchain advisory from Carlos Vargas.

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/5 https://github.com/orgs/Profila/projects/4

–– 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. We have also direct contracted advisory services now from Mikko Kotila and blockchain advisory from Carlos Vargas.

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/7 https://github.com/orgs/Profila/projects/3

We have been working directly with IOG PSG in respect to the viability of implementing PRISM and will continue to work with them on this project as well as have their involvement in our other PRISM related catalyst project. Some aspects of our integration of PRISM rely on the development of PRISM itself, which contributes to our project's extended length. –– 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 IOG PSG. We have also direct contracted advisory services now from Mikko Kotila and blockchain advisory from Carlos Vargas.

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/8 https://github.com/orgs/Profila/projects/3

We have been working directly with IOG PSG in respect to the viability of implementing PRISM and will continue to work with them on this project as well as have their involvement in our other PRISM related catalyst project. Some aspects of our integration of PRISM rely on the development of PRISM itself, which contributes to our project's extended length. Additionally, as we have had internal discussions regarding launching our platform as web based for the MVP, these developments take direct precedence in terms of resource allocation. –– 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 IOG PSG. We have also direct contracted advisory services now from Mikko Kotila and blockchain advisory from Carlos Vargas.

We have made progress in all aspects of this project. These include 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. We are still in the process of delegating the development of this project to one of the teams we are working with, laid out below. As mentioned above, the RFW that correlates to the development of this can be viewed in our GitHub repo (this is the RFW that is attached above). Note that this RFW is not complete as we finalise design and implementation internally, hence the lack of complete detail for now.

https://github.com/Profila/Catalyst https://github.com/Profila/Catalyst/issues/6

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 the consultancy of IOG PSG. 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.

We have made progress in all aspects of this project. These include 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. We are still in the process of delegating the development of this project to one of the teams we are working with, laid out below. As mentioned above, the RFW that correlates to the development of this can be viewed in our GitHub repo (this is the RFW that is attached above). Note that this RFW is not complete as we finalise design and implementation internally.

https://github.com/Profila/Catalyst https://github.com/Profila/Catalyst/issues/8

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 the consultancy of IOG PSG as it pertains to the implementation of Atala PRISM. 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.

We have made progress in all aspects of this project. These include 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. We are still in the process of delegating the development of this project to one of the teams we are working with, laid out below. As mentioned above, the RFW that correlates to the development of this can be viewed in our GitHub repo (this is the RFW that is attached above). Note that this RFW is not complete as we finalise design and implementation internally.

https://github.com/Profila/Catalyst https://github.com/Profila/Catalyst/issues/7

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 the consultancy of IOG PSG. 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.

We have made progress in all aspects of this project. These include 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. We are still in the process of delegating the development of this project to one of the teams we are working with, laid out below. As mentioned above, the RFW that correlates to the development of this can be viewed in our GitHub repo (this is the RFW that is attached above). Note that this RFW is not complete as we finalise design and implementation internally.

https://github.com/Profila/Catalyst https://github.com/Profila/Catalyst/issues/5

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 the consultancy of IOG PSG. 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.

We have made progress in all aspects of this project. These include 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. We have been working directly with IOG PSG in respect to the viability of implementing PRISM and will continue to work with them on this project as well as have their involvement in our other PRISM related catalyst project.

As mentioned above, the RFW that correlates to the development of this can be viewed in our GitHub repo(this is the RFW that is attached above).

https://github.com/Profila/Catalyst https://github.com/Profila/Catalyst/issues/1 https://github.com/orgs/Profila/projects/3

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 the consultancy of IOG PSG. 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.

We have made progress in all aspects of this project. These include 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. We are still in the process of delegating the development of the smart contract layer of this project to one of the teams we are working with, laid out below. As mentioned above, the RFW that correlates to the development of this can be viewed in our GitHub repo(this is the RFW that is attached above).

https://github.com/Profila/Catalyst https://github.com/Profila/Catalyst/issues/4 https://github.com/orgs/Profila/projects/5

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. 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.

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 for allowance of a core Profila feature called Moments. 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/2 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.

Working with playermint and Mlabs on advancing this project. Kick-off call passed, we all have our tasks. ZEKE character came back from designed and is attached als JPG. This will be the visual NFT mascot

IOG high level requirement document almost final (confidential so I cannot disclose the content). This contains the development and implementation of Atala prism as per this proposal.

IOG high level requirement document almost final (confidential so I cannot disclose the content). This contains the development and implementation of Atala prism as per this proposal.

High level requirement document scoped (first page attached) with IOG professional services team which includes the lay-out of the PRISM implementation under this project is as good as ready. Document is confidential so I couldn't include it entirely.

This is a follow up project from our fund 7 proposal, which foresees to integrate our own Cardano-native token called "Zero Knowledge Token" or ZEKE into the profila platform. More information about our token can be found on https://profila.com/token. We have hired Christian Zupeuc and his gamification development company to help us with workshops on how the token economics of this gamification use case look like. We had the first workshops already since the report of last month.

We recently hired Christian Zupeuc and his game development company to help us with the gamification aspect of this proposal (see attached their workshop offers which we took). We have since last reporting had the first session.

This project will build further on the initial metadata privacy ledger project that was funded under project catalyst fund 5. Watch our reporting video on the townhall - https://www.youtube.com/watch?v=GqT9TYwsPW0. We also just finalized our project closeout report and are now fully ready to take on the development of this follow up project.

Atala Prism team of IOG and Professional services team (under Carlos Vargas) are working with the Profila development and research team (partnering with the university of Madrid), to implement Atala Prism as DID in Profila's zero knowledge advertising strategy (explained in our initial research paper - available here https://docsend.com/view/s8fdq9h32ghm78yk)

This project will build further on the initial metadata privacy ledger project that was funded under project catalyst fund 5. Watch our reporting video on the townhall - https://www.youtube.com/watch?v=GqT9TYwsPW0

This is a follow up project from our fund 7 proposal, which foresees to integrate our own Cardano-native token called "Zero Knowledge Token" or ZEKE into the profila platform. More information about our token can be found on https://profila.com/token

This project will build further on the initial metadata privacy ledger project that was funded under project catalyst fund 5. Watch our reporting video on the townhall - https://www.youtube.com/watch?v=GqT9TYwsPW0 - we only have to send the reporting form (3 pages) and then the project can be closed out

Atala Prism team of IOG and Professional services team (under Carlos Vargas) are working with the Profila development and research team (partnering with the university of Madrid), to implement Atala Prism as DID in Profila's zero knowledge advertising strategy (explained in our initial research paper - available here https://docsend.com/view/s8fdq9h32ghm78yk)

Our first NFT project with Revuto (partner company) has been launched, whereby Revuto token owners who hold our NFT can get additional tokens when they connect to companies on Profila that are also companies in the Revuto app (e.g. Netflix), + they get a multiplier on the upcoming Profila ISPO.

In addition, we are working with our development partner Mlabs and our NFT partner playermint to integrate the Playermint NFT minting smart contract into our app for delivery of this funded proposal. More about our playermint partnership via this press release - https://cardanofeed.com/profila-announces-partnership-with-playermint-66333.html

ZEKE token sale in being organized in parallel - https://profila.com/token

Currently negotiating a professional relationship with IOG/Atala team to work on this proposal + collaboration with Mlabs setup to aid in development efforts

Partnership with playermint announced to use Playermint NFT minting smart contract + Mlabs partnership to integrate Playermint SC into the app

ZEKE token sale in being organized in parallel - https://profila.com/token

Towards the realization of our decentralized marketing platform, Profila will integrate with IOG through ATALA PRISM for its identity management system component. In addition to identity management, cardano blockchain will be used to build an Ad ecosystem. Profila is scoping a collaboration with IOG's professional services team, of which the development of this fund 6 proposal forms a part.

ZEKE token has been minted - https://explorer.cardano.org/en/transaction?id=bc9fb4d250a8bb739713c8df09296036e57e1b957c762fba4648c12eb9a8075e

Designers are working on additional app screens to include the gamification and token earning in the app.

Negotiations with wallet providers to integrate a Cardano native wallet in the app.

Profila is proud to announce a partnership with PlayerMint - a project on Cardano building a play-to-earn layer and launchpad that integrates with existing games like Fortnite and Rocket League. The PlayerMint layer lets gamers earn the PlayerMint token (PMX) through their gameplay performance, enabling them to use it in a Marketplace to purchase virtual creations (NFTs).

Profila and Playermint will collaborate on multiple projects that relate to NFTs, starting with the implementation of Profila’s Catalyst Fund 6 proposal ‘NFT for customer feedback/content’, where people using the Profila app can share content with brands in the form of NFTs, thereby allowing brands to reuse artistic and unique customer-created videos about their products, while at the same time remunerating the original creator.

Working on partnership with Playermint and NFTMaker to help in the development of the NFT feature in our app as explained in this proposal. We are making progress

Cardano-native token was created. App feature that integrates token is ready. Now working on wallet functions and payouts.

Working on partnership with IOG professional services team (under Carlos Vargas) to help in the development of Atala Prism our app as explained in this proposal. Our development team is learning through Atala Prism Pioneer Program. We are making progress