Grow AtalaPrism: Holder connection requests

[GENERAL] Name and surname of main applicant

Ben Tairea

[GENERAL] Are you delivering this project as an individual or as an entity (whether formally incorporated or not)

Entity (Not Incorporated)

[GENERAL] Please specify how many months you expect your project to last (from 2-12 months)

3

[GENERAL] Please indicate if your proposal has been auto-translated into English from another language.

No

[GENERAL] Summarize your solution to the problem (200-character limit including spaces)

Upgrading the prism wallet to be able to initiate connection requests and automate credential interactions will new online experience and identity use cases 

[GENERAL] Does your project have any dependencies on other organizations, technical or otherwise?

No

[GENERAL] If YES, please describe what the dependency is and why you believe it is essential for your project’s delivery. If NO, please write “No dependencies.”

No dependencies

[GENERAL] Will your project’s output/s be fully open source?

Yes

[GENERAL] Please provide here more information on the open source status of your project outputs

LGPL-3.0-only

[SOLUTION] Please describe your proposed solution.

The objective of this project is to enhance the Prism Wallet Agent, enabling it to initiate connection requests with cloud agents. Additionally, the project aims to upgrade the cloud agents to auto-accept connections and respond to presentation requests. These additions will open up new use cases, particularly the seamless use of credentials online.

Scope:

1. Prism Wallet Agent Enhancement:

• Feature Addition: Connection Initiation
• Develop the functionality for the Prism Wallet Agent to initiate connection requests with cloud agents.

1. Cloud Agent Upgrade:

• Auto-Accept Connections:
• Upgrade the cloud agents to automatically accept incoming connection requests from Prism Wallet Agents.
• Presentation Request Handling:
• Enable cloud agents to respond to presentation requests from Prism Wallet Agents, facilitating the sharing of credentials in a secure and standardized manner.

1. Use Case Demonstration:

• Online Applications Integration:
• Update the ssb-atala-prism module to leverage new changes the wallet and cloud agents
• Update AtalaPrism PoC to utilise updated agent API's

1. Documentation:

• make updates to the documentation to include the changes

1. Testing and Quality Assurance:

• Update the testing suite to include feature changes to identify and address any issues.

1. Merge Pull Requests:

• Communicate with Atala Prism core team to have contributions merged and made available to all prism developers

The enhanced solution will offer a more versatile and user-centric identity management experience. 

[IMPACT] Please define the positive impact your project will have on the wider Cardano community.

Enabling more use cases within the Cardano ecosystem through the enhancements of the AtalaPrism project holds several key advantages and benefits for both developers and end-users. Here's an overview of how expanding the range of use cases contributes to the ecosystem:

1. Increased Adoption and Engagement:

• A broader range of use cases attracts a more diverse user base and developer community. This increased adoption not only strengthens the ecosystem but also encourages active engagement and participation from various stakeholders.

1. Economic Opportunities:

• The expansion of use cases can create new economic opportunities within the ecosystem. Developers and entrepreneurs can explore innovative applications, potentially leading to the creation of new services, products, and business models. This, in turn, contributes to the growth of the Cardano ecosystem's economic ecosystem.

1. Enhanced User Experience:

• Enabling a variety of use cases enhances the user experience by providing solutions that cater to different needs and preferences. Users benefit from a more tailored and personalized experience, fostering satisfaction and loyalty within the ecosystem.

1. Wider Developer Community Involvement:

• More use cases attract a diverse range of developers with expertise in various domains. This diversity in skills and perspectives can lead to more creative solutions, increased innovation, and a robust developer community actively contributing to the improvement and expansion of the Cardano ecosystem.

The successful delivery of the project will be measured by the success implementation of the updates within the teams tribalDIDs identity solution. 

[CAPABILITY & FEASIBILITY] What is your capability to deliver your project with high levels of trust and accountability? How do you intend to validate if your approach is feasible?

With a proven track record of five years working collaboratively, our team has demonstrated our commitment and competence in delivering successful projects, including the development and delivery of the Ahau application. Having delivered over $1.5 million in project funding in that time span, each endeavor required meticulous reporting, transparent communication, and the successful attainment of project objectives. Our collective experience showcases a consistent dedication to accountability and transparency, adapting to diverse communication methods and ensuring project success. This established cohesion, coupled with our expertise and track record, uniquely positions us as the ideal team to confidently and effectively deliver the proposed project.

To successfully deliver the project, we have an experienced team that possess a range of capabilities and experiences across various domains. Our fields of expertise include

1. Decentralized Identity (DID) and Verifiable Credentials:

• Expertise in designing, implementing, and managing decentralized identity systems, including the use of decentralized identifiers (DIDs) and verifiable credentials.

1. Security Proficiency:

• Strong background in cybersecurity and secure coding practices to establish robust security measures, safeguarding user data, and ensuring privacy.

1. Open-Source Development:

• Experience in leading or contributing to open-source projects, understanding the importance of transparency and collaboration in building trust within the community.

1. User-Centric Design:

• User experience (UX) and user interface (UI) design skills to create an intuitive and user-friendly interface, prioritizing the needs of the end-users.

1. Community Engagement:

• Past experience in managing and engaging with diverse communities, fostering open communication, and addressing concerns effectively.

1. Ethical Considerations:

• A commitment to ethical considerations in identity management, including a focus on user consent, data ownership, and minimizing biases.

1. Project Management Skills:

• Strong project management skills to ensure timely delivery, accountability, and effective communication with stakeholders.

By combining the team experience, expertise and already functional PoC developed in the tribalDIDs = indigenous data sovereignty project, the project team will continue to build trust through transparency, accountability, and a demonstrated commitment to user needs and security along with regular communication with the community throughout the development process.

[Project Milestones] What are the key milestones you need to achieve in order to complete your project successfully?

Objective: Run community design session(s)

Outputs: Delivery of SDK stakeholders design input sessions

Acceptance criteria:

1. The team have delivered multiple design sessions (Number depending on community interest and need).
2. Notes from sessions are available to public
3. Slide deck and video report

Objective: Define function specifications and proposed implementation plan

Outputs: Function specifications document including requirements and implementations

Acceptance criteria:

1. Approach has been shared with and approved by repo maintainers
2. Readme available in hosted on the repository
3. Slide deck and video report

Objective: Develop SDK initiate connection functionality

Outputs: New branch in SDK with proposed changes

Acceptance criteria:

1. Code available on the repo branch
2. Links, Slide deck and video report

Objective: Develop Agent auto-accept connection functionality

Outputs: New branch in agent with proposed changes

Acceptance criteria:

1. Code available on the repo branch
2. Links, Slide deck and video report

Objective: Get community feedback

Outputs: Delivery of SDK stakeholder group feedback session

Acceptance criteria:

1. The team have delivered multiple design sessions (Number depending on community interest and need).
2. Notes from sessions are available to public
3. Slide deck and video report

Objective: Develop tests for new functionality

Outputs: Developed testing suite

Acceptance criteria:

1. Code available on the repo
2. Tests passing when run
3. Slide deck and video report

xObjective: Demonstrate new functions within Ahau wallet application

Outputs:

1. Built application API to leverage SDK
2. Branch installed and running on the Ahau wallet application
3. Document installation and use

Acceptance criteria:

1. Any issues raised during the implementation phase have been responded too
2. Documentation can be found in repo
3. Repo available showing relevant code
4. Demonstration video of the feature in action
5. Slide deck and video report

Objective: Update code to meeting implementation requirements

Outputs: Respond to necessary changes for module implementation

Acceptance criteria:

1. Repo available showing relevant code
2. Demonstration video of the feature in action
3. Slide deck and video report

Objective: Merge code

Outputs: New branch has been merged into main SDK.

Acceptance criteria:

1. Repo available showing relevant code
2. Demonstration video of the feature in action
3. Slide deck and video report

Objective: Code is well documented

Outputs: Documentation for use and function found in repo

Acceptance criteria:

1. Repo available showing relevant code
2. Demonstration video of the feature in action
3. Slide deck and video report

Objective: Provide support for any related SDK issues

Outputs: Continue supporting module

Acceptance criteria:

1. Github issues responses logged in repo
2. Slide deck, links and video report

[RESOURCES] Who is in the project team and what are their roles?

For the past five years our team have been successfully building and delivering community designed technologies. Below are our team members that are leading this project

Ben Tairea:

As Product Owner of the project solution, Ben will play a pivotal role in driving the development and success of the project. Ben will be responisble for ensuring the product meets the needs of both the development team and the diverse communities it aims to serve.

Professional Experinence:

• Proven experience as the Product Owner with Ahau since 2017
• Strong familiarity with AtalaPrism and Cardano as the core contributor to the ssb-atalaprism module
• Strong understanding of decentralized identity concepts, verifiable credentials, and related technologies, serving as chair of Digital Identity NZ 2019-23 and Member of the Identity Product Advisory Group for New Zealand Government (current)
• Clear understanding of user base and product vision as Earth Defenders Toolkit Community Steward since 2022

Key Responsibilities:

• Develop and communicate a clear product vision aligned with the goals of the project.
• Curate and manage the product backlog, ensuring it reflects project priorities.
• Champion user-centric design principles, working closely with UI/UX designers to implement feedback and improve usability.
• Collaborate with QA teams to establish and maintain quality standards, participating in testing processes.
• Develop and maintain comprehensive project plans, defining tasks, timelines, and dependencies.
• Track project timelines, identifying and addressing potential delays, and ensuring the timely delivery of milestones.
• Facilitate clear communication between project stakeholders, ensuring everyone is informed about project progress and changes.
• Work closely with the project's financial team to manage and monitor the budget, ensuring resources are allocated efficiently.

Engie Matene:

Is our community liaison for the project leading our co-development approach between between the product development team and the communities we aim to serve. Engie will be responsable for developing an engaged communities user base, fostering collaboration, addressing concerns, and ensuring a positive and inclusive experience.

Personal experience:

• Strong understanding of community registrations as lead research and community engagement for TribalDID's = Indigenous soveriengty project since Nov 22
• Secretary for Te Riingi Marae (Marae Trustee)
• Strong technical understanding and community product development working as a community software developer since 2017

Key Responsibilities:

• Actively engage with potential user communities to build strong relationships.
• Gather and synthesize user feedback, ensuring the community's voice is heard and considered in project development.
• Address community concerns, inquiries, and issues promptly, working closely with the development team to find resolutions.
• Act as the bridge between development teams, community stakeholders, and other relevant parties.
• Be an advocate for the community within the development team, ensuring their needs and perspectives are considered in decision-making processes.

Mix Irving:

As the senior developer for the project Mix is a key player in the design, development, and implementation of our decentralized identity solution on the Cardano blockchain. His expertise will drive technical excellence, innovation, and the successful delivery of a robust and scalable open-source product.

Personal Experience:

• Core developer for Loomio governance tool
• Key contributor to Dark Crystal v1
• Core developer and community organiser of Scuttlebutt
• Lead developer for Āhau
• Founder of commons.garden
• a new project working to build a stronger p2p commons, sharing learning, fostering collaborations

Key Responsibilities:

• Provide technical leadership within the development team, guiding the implementation of decentralized identity solutions.
• Lead blockchain development efforts, particularly on the Cardano and AtalaPrism platform, ensuring secure and efficient integration
• Enforce coding standards and best practices to maintain high-quality, maintainable, and efficient code.
• Implement robust security measures, including encryption and secure key management, to ensure the integrity of the decentralized identity system.

[BUDGET & COSTS] Please provide a cost breakdown of the proposed work and resources.

Development Team (75% - ₳56,063):

• Salaries and compensation for developers, and technical team members.
• Software development tools and licenses.

Feature design (10% - ₳7,475):

• Compensation for solution architecture services, development team and stakeholder input costs

Project management (7% - ₳5,232):

• Compensation for project management resource responsible for reporting and communications

Documentation (5% - ₳3,738)

• Technical writers for creating comprehensive documentation.

Contingency (3% - ₳2,242):

• A reserve fund for unexpected expenses or scope changes.

The budget will be regularly revisited throughout the duration of the project with shared responsibility between the project leads to ensure that funds are allocated optimally and to accommodate any emerging needs or changes in scope. Additionally, maintaining a detailed and transparent record of expenditures will aid in effective budget management throughout the project lifecycle.

[VALUE FOR MONEY] How does the cost of the project represent value for money for the Cardano ecosystem?

The project budget has been based on converted industry average salary rates for Aotearoa, NZ, where our project team in based:

Average salary: Technical lead

Average salary: Project manager

Average salary: Solution architect

Considering the teams considerable expertise in this particular field and current contracting rates the Cardano ecosystem is getting significant value for money for this project.

[IMPORTANT NOTE] The Applicant agrees to Fund Rules and also that data in the submission form and other data provided by the project team during the course of the project will be publicly available.

I Accept