Open kantp opened 1 month ago
Team Lead (Main Contact Person):
Team Overview: What makes you best-suited to execute this project?
Our team consists of experienced TypeScript developers who have worked on various Web3 products in different ecosystems, including Ethereum, Cardano, and Mina. We always tend to raise the bar and adhere to the highest industry standards, writing type-safe, reusable and tested code. Our wallet, Pallad, is a manifestation of these principles.
@mina-js/provider
(reusable TypeScript interfaces and types for existing and future wallets) and @mina-js/connect
(Viem/Wagmi inspired client) to NPM.@mina-js/connect
, add test automation, and perform regression to ensure quality standards. We will reuse parts of our existing benchmark zkApp for our Web Connector implementation: https://palladians.github.io/mina-connector/.@mina-js/provider
- 2 weeks@mina-js/connect
developed and published to NPM - 3-4 weeks@mina-js/connect
deployed - 2 weeks@mina-js/provider
library work - $10000@mina-js/connect
library work - $40000Member 1:
Member 2:
Member 3:
Our team is Auro Wallet. A simple yet powerful Mina Protocol Wallet. Since the first day that Mina Mainnet went live, it has been operational. Right now, Auro Wallet is the most widely used and well-liked wallet on the Mina Protocol. There are nearly 100,000 installations. https://www.aurowallet.com.
Our team members have developed wallets and explorers in the past and have many years of blockchain experience.
Proposed Solution Description:
Our goal is that zkApp can be quickly connected to the Mina wallet, and it only needs to develop once to interact normally with the Mina wallet that supports the standard provider, and users can get good feedback during use.
We provided a lot of useful feedback on RPC-0008. We plan to communicate with more zkApp developers and other wallet developers based on RFC-0008 and the mina-provider currently used. Fully understand user needs to optimize and adjust the provider and related project content, so that zkApp can access the wallet more easily, so as to better implement the communication standard.
The mina-provider (TypeScript) currently used by Auro Wallet has been running healthily on the Mina Protocol for over 2 years with good documentation and sample demo code (TypeScript). We have been actively communicating with zkApp developers, accumulating valuable experience, and actively adjusting the provider to better meet the needs of developers on the premise of facilitating zkApp development and ensuring wallet security. We have currently implemented the main features of RFC-0008, and the above mentioned projects are open source.
We provide quick technical support services, and zkApp developers and users can communicate with us on Discord, Telegram, and GitHub in order to better access the wallet provider.
Step-by-Step Plan:
Critical Milestones:
mina-provider intergate to RFC-0008. Merge the existing mina-provider API with RFC-0008 optimization.
auro-wallet-extension Connect to the latest version mina-provider. Auro-wallet-extension develops the mina-provider core feature. When zkApp communicates with Auro Wallet, the corresponding content can be returned.
auro-wallet-extension develops test cases of mina-provider. Verify the robustness of auro-wallet-extension for provider functions to ensure secure and stable output.
Multi-wallet platform (wagmi/beacon on mina platform) and self-test case development. Access the mina-provider to provide a variety of wallet portals, and zkApp only needs to access the platform to adapt to the standard Mina-wallet. Support theme customization, black mode and other features.
test-zkApp use Multi-wallet platform and debugs with auro-wallet-extension. This step mainly simulates the process of zkApp interacting with mina wallet. As an example of the mina-provider and Multi-wallet platform, all the functions of the mina-provider are included.
Update the provider document to the latest. docs is the access document for the mina-provider, and zkApp developers can see all the content of the mina-provider API and important updates.
Support Requirements:
Grant Funding:
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?
RFP: Standard JavaScript Mina Wallet Provider API
Background
RFC-0008 describes a standard JavaScript API for Mina wallet providers, in order to ease third party integration with different wallets. The purpose of this RFP is to create a standard that covers what is described in RFC-0008, along with artefacts that ease adoption.
Objectives and Desired Artifacts
In order to have the standard be adopted, we desire the following artefacts:
Impact Measurement
Impact of this RFP will be measured by adoption. As listed above, we would like to see the standard implemented in at least one wallet as part of the work. Having good documentation, examples, and client-side utilities will be crucial for wide adoption.
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 [submission email/address]. 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.