Intent: The purpose of this RFP is to extend the wallet provider API for Mina wallets to enable attestations beyond the current features, focusing on composable privacy and secure proof storage, as outlined in the original RFC.
The original RFC introduces an extension to the wallet provider API for Mina wallets, focusing on enabling attestations beyond the current features of attesting to knowledge of private keys. The proposal aims to expand this feature to allow wallets to attest to a broader range of private data, such as credentials. Composable privacy is a central concept, offering users and developers discretion in selecting which data remains private and which becomes public, ensuring that sensitive data is not exposed to the browser context.
Objectives and Desired Artifacts
This RFP seeks to implement the extended wallet provider API, focusing on:
Standardized Attestation Construction API: Allow users to attest to any data.
Attestation Composition API: Enable users to compose local and remote proofs.
Nullifier and Expiration Support for Proofs: Integrate nullifier mechanisms to prevent proof reuse.
Secure Proof Storage: Ensure proofs are stored securely and are tamper-proof.
Example Implementations: Provide example implementations demonstrating the API usage.
Impact Measurement
The impact of the RFP will be assessed based on:
API Usability: Ease of use and integration of the extended API for developers.
Security and Privacy: Effectiveness of composable privacy and secure proof storage.
Community Adoption: Adoption rate of the extended API by Mina wallet developers and zkApp developers.
Compliance with Specifications: Adherence to the requirements and specifications outlined in the original RFC.
Application Instructions
To apply for this RFP, applicants are required to:
1. Thoroughly review all listed requirements and deliverables to ensure a complete understanding of the RFP's scope and objectives.
2. Complete the application form provided at [link to form], including all requested information and any preliminary ideas or proposals.
3. Submit their detailed proposal in the specified format to submissions@mina.foundation. Proposals should be structured and clear, with an emphasis on how the applicant intends to achieve the RFP's objectives.
4. Engage with the Mina community through the designated discussion channels, sharing initial ideas and seeking feedback to refine the proposal before submission.
Applicants are encouraged to ask questions and seek clarifications as needed to fully comprehend the expectations and objectives of this RFP.
**Submission Form Template**
**Application Form**
Ensure that all information provided is accurate and complete to best represent your proposal.
**Contact Information**
**Team Lead (Main Contact Person):**
- Name:
- Position/Role:
- Email:
- GitHub Username:
- Telegram/Discord Handle:
- Mina Recipient Address (for potential funding):
**Team Members:**
- Member 1:
- Name:
- Role:
- Relevant Experience/Previous Work (with links):
- (Add more members as needed)
**Team Overview:**
What makes you best-suited to execute this project?
[Provide a comprehensive answer]
**Proposed Solution**
- Proposed Solution Description:
- Please describe your proposed solution based on the requirements and core features outlined in the RFP:
- [Provide a detailed explanation]
**Execution Plan**
- Step-by-Step Plan:
- Please outline your step-by-step plan to execute this project, including expected deadlines for each piece of work:
- [Provide a timeline with milestones]
- Critical Milestones:
- Please define the critical milestones that should be used to determine whether you’ve executed on this proposal:
- [List and explain the milestones]
**Additional Support and Funding**
- Support Requirements:
- Please list any additional support your team would require to execute this project (financial, technical, etc.):
- [Specify the support needed]
- Grant Funding:
- [Explain your financial needs and conditions]
**Community Engagement**
- Engagement with Mina Community:
- How have you engaged with the Mina community to refine your proposal before submission?
- How does your experience with Mina and the community increase the likelihood of success?
- [Describe the engagement]
Please ensure that you have reviewed all listed requirements, deliverables, and the provided resources to ensure a complete understanding of the RFP's scope and objectives.
RFP: Private Credential Standard
Background
The original RFC introduces an extension to the wallet provider API for Mina wallets, focusing on enabling attestations beyond the current features of attesting to knowledge of private keys. The proposal aims to expand this feature to allow wallets to attest to a broader range of private data, such as credentials. Composable privacy is a central concept, offering users and developers discretion in selecting which data remains private and which becomes public, ensuring that sensitive data is not exposed to the browser context.
Objectives and Desired Artifacts
This RFP seeks to implement the extended wallet provider API, focusing on:
Impact Measurement
The impact of the RFP will be assessed based on:
Application Instructions
To apply for this RFP, applicants are required to: 1. Thoroughly review all listed requirements and deliverables to ensure a complete understanding of the RFP's scope and objectives. 2. Complete the application form provided at [link to form], including all requested information and any preliminary ideas or proposals. 3. Submit their detailed proposal in the specified format to submissions@mina.foundation. Proposals should be structured and clear, with an emphasis on how the applicant intends to achieve the RFP's objectives. 4. Engage with the Mina community through the designated discussion channels, sharing initial ideas and seeking feedback to refine the proposal before submission. Applicants are encouraged to ask questions and seek clarifications as needed to fully comprehend the expectations and objectives of this RFP. **Submission Form Template** **Application Form** Ensure that all information provided is accurate and complete to best represent your proposal. **Contact Information** **Team Lead (Main Contact Person):** - Name: - Position/Role: - Email: - GitHub Username: - Telegram/Discord Handle: - Mina Recipient Address (for potential funding): **Team Members:** - Member 1: - Name: - Role: - Relevant Experience/Previous Work (with links): - (Add more members as needed) **Team Overview:** What makes you best-suited to execute this project? [Provide a comprehensive answer] **Proposed Solution** - Proposed Solution Description: - Please describe your proposed solution based on the requirements and core features outlined in the RFP: - [Provide a detailed explanation] **Execution Plan** - Step-by-Step Plan: - Please outline your step-by-step plan to execute this project, including expected deadlines for each piece of work: - [Provide a timeline with milestones] - Critical Milestones: - Please define the critical milestones that should be used to determine whether you’ve executed on this proposal: - [List and explain the milestones] **Additional Support and Funding** - Support Requirements: - Please list any additional support your team would require to execute this project (financial, technical, etc.): - [Specify the support needed] - Grant Funding: - [Explain your financial needs and conditions] **Community Engagement** - Engagement with Mina Community: - How have you engaged with the Mina community to refine your proposal before submission? - How does your experience with Mina and the community increase the likelihood of success? - [Describe the engagement] Please ensure that you have reviewed all listed requirements, deliverables, and the provided resources to ensure a complete understanding of the RFP's scope and objectives.