Skip to content

Commit

Permalink
Update PolarisWallet.md
Browse files Browse the repository at this point in the history 
Updates
  • Loading branch information
@MontechStudiosINC
MontechStudiosINC authored Oct 25, 2024
1 parent 16dd045 commit fc450e7
Showing 1 changed file with 46 additions and 54 deletions.
100 changes: 46 additions & 54 deletions applications/PolarisWallet.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,7 @@

- Polaris Wallet is a custodial wallet integrated with Polkadot’s Asset Hub, designed for non-crypto-native users. It facilitates seamless interactions with multiple parachains, offering functionalities such as yield farming, lending, borrowing, staking, and restaking across the Polkadot ecosystem.
- Key Features
Custodial Wallet: O
Asset Hub Integration: Support for DOT, USDC, USDT, and other compatible assets.
Parachain Interactions: Participate in DeFi services like yield farming, staking, and borrowing.
Snowbridge Integration: Bridging assets from Ethereum (USDC, USDT) to Polkadot.
Expand All @@ -33,7 +34,7 @@ We expect the teams to already have a solid idea about your project's expected f
- Asset Hub Integration:
Enable deposits and management of DOT and native stablecoins.
Provide seamless access to all parachains linked to Polkadot’s Asset Hub.
Actively searching for 3rd party custodial wallet provider within Polkadot ecosystem
Actively searching for 3rd party custodial provider within Polkadot ecosystem
https://wiki.polkadot.network/docs/general/dune-analytics/interlay-dashboards
- Snowbridge Integration:
Accept Ethereum-based assets and automate the bridging process to Polkadot.
Expand Down Expand Up @@ -71,7 +72,12 @@ Help us locate your project in the Polkadot/Substrate/Kusama landscape and what
Fiat-to-Crypto On-Ramp: It simplifies the conversion of fiat to crypto (e.g., USD to DOT or USDT) by integrating trusted payment processors for seamless transactions.
Security & Compliance: Polaris ensures that users' assets are securely managed and complies with necessary regulations across jurisdictions.
- How did you identify these needs? Please provide evidence in the form of (scientific) articles, forum discussions, case studies, or raw data.
-
- Our identification of user needs for Polaris Wallet was driven primarily by direct feedback from potential users gathered through various channels. Notably, discussions on platforms like Reddit have been instrumental. For example, in threads on the Polkadot subreddit, many participants have highlighted difficulties with the complexity and accessibility of existing cryptocurrency solutions, particularly for those unfamiliar with blockchain technologies. These discussions underscore a significant demand for a more intuitive and user-friendly interface that can cater to non-crypto-natives. Our objective with Polaris is to address these pain points by simplifying interactions within the Polkadot ecosystem, thereby enhancing user acquisition and retention, and reducing the steep learning curve associated with cryptocurrency transactions. [Reddit discussion on Polkadot needs.](https://www.reddit.com/r/Polkadot/comments/192wu6e/as_a_big_believer_in_dot_give_me_your_best_pitch/)
Compared to other Layer 1s Polkadot is among the lowest in TVL and Average Daily Address'
https://www.grayscale.com/research/reports/layer-1-blockchains-a-tale-of-user-owned-cities-part-ii-of-ii

We know that creating a user friendly custodial design will attract more users to the Polkadot Ecosystem

- Are there any other projects similar to yours in the Substrate / Polkadot / Kusama ecosystem?
- Yes, there are a few similar projects:
Subwallet: A browser extension wallet for managing Polkadot and Kusama assets. However, Subwallet focuses more on non-custodial services, whereas Polaris provides a custodial wallet for non-crypto-native users.
Expand All @@ -96,7 +102,6 @@ Help us locate your project in the Polkadot/Substrate/Kusama landscape and what
UI/UX Designer: 1 UIUX designer
Frontend Developers: 2
Backend/Rust Developers: 2
QA Engineer: 1
Support Staff: Post-launch support and maintenance team

### Contact
Expand Down Expand Up @@ -141,43 +146,45 @@ If you've already started implementing your project or it is part of a larger re
### Overview

- **Total Estimated Duration:** Duration of the whole project - 6 Months
- **Full-Time Equivalent (FTE):** 6 FTE
- **Full-Time Equivalent (FTE):** 5 FTE
- **Total Costs:** Requested amount in USD for the whole project is 90,000 USD
- **DOT %:** Percentage of Total Costs to be paid in (vested) DOT (50%)

### Milestone 1 — Research & Planning
### Milestone 1 — Design & Prototyping

- **Estimated duration:** 1 month
- **FTE:** 3
- **Costs:** 16,250 USD
- **Costs:** 20,000 USD

> :exclamation: **The default deliverables 0a-0d below are mandatory for all milestones**, and deliverable 0e at least for the last one.
| Number | Deliverable | Specification |
| -----: | ----------- | ------------- |
| **0a.** | License | Apache 2.0. See the [delivery guidelines](https://grants.web3.foundation/docs/Support%20Docs/milestone-deliverables-guidelines#license) for details. |
| **0b.** | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how a user can (for example) spin up one of our Substrate nodes and send test transactions, which will show how the new functionality works. See the [delivery guidelines](https://grants.web3.foundation/docs/Support%20Docs/milestone-deliverables-guidelines#documentation) for details. |
| **0c.** | Testing and Testing Guide | Core functions will be fully covered by comprehensive unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. See the [delivery guidelines](https://grants.web3.foundation/docs/Support%20Docs/milestone-deliverables-guidelines#testing-guide) for details. |
| **0a.** | License | Apache 2.0. |
| **0b.** | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how a user can (for example) spin up one of our Substrate nodes and send test transactions, which will show how the new functionality works.|
| **0c.** | Testing and Testing Guide | Core functions will be fully covered by comprehensive unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests.|
| **0d.** | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. |
| **0e** |We will provide an article summarizing the innovations introduced during the development of Polaris Wallet. This article will be published on Medium.
| **1.a** |Final list of parachains and DeFi services to integrate.
| **1.b** |Architecture and technical approach defined.
| **0e** |We will provide an article summarizing the innovations introduced during the development of Polaris Wallet. This article will be published on Medium.| Wireframes and design prototypes will cover key user interactions, including wallet management, asset transfers, and parachain interactions.|
| **1.a** |Complete wireframes and design prototypes for the user interface, covering all key user interactions (wallet management, asset transfers, parachain interactions).
| **1.b** |Detailed user flow diagrams mapping key user journeys, such as onboarding, wallet creation (custodial and non-custodial), asset transfers, and DeFi service interactions| Diagrams will outline the core user journeys such as wallet creation, asset transfers, and DeFi service interactions, for both custodial and non-custodial users.|
| **1.c** |UI/UX design for interacting with parachain DeFi services (e.g., staking, yield farming, borrowing, and lending). Wireframes should reflect the ease of access to multiple services across parachains.| UX design will focus on making interactions with DeFi services, including staking, yield farming, and borrowing, intuitive and accessible.|


### Milestone 2 — Design & Prototyping
### Milestone 2 — Development

- **Estimated Duration:** 1 month
- **FTE:** 5
- **Costs:** 20,000 USD

| Number | Deliverable | Specification |
| -----: | ----------- | ------------- |
| **0a.** | License | Apache 2.0. See the [delivery guidelines](https://grants.web3.foundation/docs/Support%20Docs/milestone-deliverables-guidelines#license) for details. |
| **0b.** | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how a user can (for example) spin up one of our Substrate nodes and send test transactions, which will show how the new functionality works. See the [delivery guidelines](https://grants.web3.foundation/docs/Support%20Docs/milestone-deliverables-guidelines#documentation) for details. |
| **0c.** | Testing and Testing Guide | Core functions will be fully covered by comprehensive unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. See the [delivery guidelines](https://grants.web3.foundation/docs/Support%20Docs/milestone-deliverables-guidelines#testing-guide) for details. |
| **0d.** | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. |
| **0e** |Complete UI wireframes and design prototypes.
| **1.a** |Feedback incorporated. https://www.figma.com/design/MCHgoPbuSiweOuxucSHmyV/Polaris-Wallet?node-id=0-1
| **0a.** | License | Apache 2.0. |
| **0b.** | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how a user can (for example) spin up one of our Substrate nodes and send test transactions, which will show how the new functionality works.|
| **0c.** | Testing and Testing Guide | Core functions will be fully covered by comprehensive unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests.|
| **0d.** | Initial integration of Asset Hub with support for managing DOT and stablecoins (USDC, USDT), enabling users to view balances and initiate basic transactions.|
| **0e** | Initial development of Snowbridge integration for asset bridging between Ethereum and Polkadot. The core framework for bridging assets (e.g., USDC, USDT) is set up, with initial transfer testing
| **1.a** |Development of APIs and SDKs enabling interactions with parachains. Key functionalities such as staking, yield farming, and borrowing services are partially developed, but not yet fully functional.



### Milestone 3 — Development (Midpoint)
Expand All @@ -188,65 +195,50 @@ If you've already started implementing your project or it is part of a larger re

| Number | Deliverable | Specification |
| -----: | ----------- | ------------- |
| **0a.** | License | Apache 2.0. See the [delivery guidelines](https://grants.web3.foundation/docs/Support%20Docs/milestone-deliverables-guidelines#license) for details. |
| **0b.** | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how a user can (for example) spin up one of our Substrate nodes and send test transactions, which will show how the new functionality works. See the [delivery guidelines](https://grants.web3.foundation/docs/Support%20Docs/milestone-deliverables-guidelines#documentation) for details. |
| **0c.** | Testing and Testing Guide | Core functions will be fully covered by comprehensive unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. See the [delivery guidelines](https://grants.web3.foundation/docs/Support%20Docs/milestone-deliverables-guidelines#testing-guide) for details. |
| **0a.** | License | Apache 2.0. |
| **0b.** | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how a user can (for example) spin up one of our Substrate nodes and send test transactions, which will show how the new functionality works.|
| **0c.** | Testing and Testing Guide | Core functions will be fully covered by comprehensive unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests.|
| **0d.** | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. |
| **0e** | We will integrate the ability to manage DOT and stablecoins on Polkadot's Asset Hub, providing full support for deposits, transfers, and withdrawals. https://wiki.polkadot.network/docs/general/dune-analytics/assethub-dashboards
| **1.a** | Integrate Snowbridge to enable seamless bridging of assets from Ethereum (e.g., USDC, USDT) to Polkadot’s network. https://docs.snowbridge.network/architecture/components
| **1.b** | Enable users to engage with DeFi services like yield farming, staking, lending, and borrowing across multiple Polkadot parachains. https://wiki.polkadot.network/docs/general/dune-analytics/interlay-dashboards
| **1.a** | Full implementation of both custodial and non-custodial wallet authentication. Custodial users can securely access and manage assets, while non-custodial users maintain full control of their private keys.
| **1.b** | Complete integration of Asset Hub for managing DOT and stablecoins (USDC, USDT), with full functionality for deposits, transfers, and withdrawals.
| **1.c** | Full implementation of Snowbridge integration, enabling seamless asset transfers between Ethereum and Polkadot. All bridge operations, including asset locking, minting, and burning, are functional. https://docs.snowbridge.network/architecture/components
| **1.d** | Full development of interactions with parachain DeFi services (staking, yield farming, lending, and borrowing). Users can fully interact with multiple parachains to manage and grow their assets


### Milestone 4 — Development (Completion)

- **Estimated Duration:** 1 month
- **FTE:** 5
- **Costs:** 16,250 USD
- **Costs:** 20,000 USD

| Number | Deliverable | Specification |
| -----: | ----------- | ------------- |
| **0a.** | License | Apache 2.0. See the [delivery guidelines](https://grants.web3.foundation/docs/Support%20Docs/milestone-deliverables-guidelines#license) for details. |
| **0b.** | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how a user can (for example) spin up one of our Substrate nodes and send test transactions, which will show how the new functionality works. See the [delivery guidelines](https://grants.web3.foundation/docs/Support%20Docs/milestone-deliverables-guidelines#documentation) for details. |
| **0c.** | Testing and Testing Guide | Core functions will be fully covered by comprehensive unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. See the [delivery guidelines](https://grants.web3.foundation/docs/Support%20Docs/milestone-deliverables-guidelines#testing-guide) for details. |
| **0a.** | License | Apache 2.0. |
| **0b.** | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how a user can (for example) spin up one of our Substrate nodes and send test transactions, which will show how the new functionality works.|
| **0c.** | Testing and Testing Guide | Core functions will be fully covered by comprehensive unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests.|
| **0d.** | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. |
| **0e** | Implement custodial authentication for users, allowing secure and easy access to their Polaris Wallet accounts.
| **1.a** | Implement non-custodial authentication for advanced users who prefer to maintain full control of their keys and assets.
| **1.b** | Develop a fiat-to-crypto conversion feature, enabling users to convert fiat currencies (e.g., USD, EUR) into supported crypto assets directly into their custodial wallet. https://www.moonpay.com/buy/dot
| **1.b** | Develop a fiat-to-crypto conversion feature, enabling users to convert fiat currencies (e.g., USD, EUR) into supported crypto assets directly into their custodial wallet. https://www.moonpay.com/buy/dot |
| **1.c** | Implement real-time exchange rates to provide users with accurate and transparent conversion rates when converting fiat to crypto.
| **1.d** | Comprehensive documentation I | We will provide comprehensive documentation for developers - on how to start the application and different functions overview (Via GitHub pages) |
| **1.e** | Comprehensive documentation II | We will provide comprehensive documentation for users - on how to create a Polkadot wallet, how to use the application, and a basic application overview (Via Github pages) |


### Milestone 5 — Testing & QA

- **Estimated Duration:** 1 month
- **FTE:** 5
- **Costs:** 10,000 USD
| **1.d** | Partner with 3rd Party Custody solution provider

| Number | Deliverable | Specification |
| -----: | ----------- | ------------- |
| **0a.** | License | Apache 2.0. See the [delivery guidelines](https://grants.web3.foundation/docs/Support%20Docs/milestone-deliverables-guidelines#license) for details. |
| **0b.** | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how a user can (for example) spin up one of our Substrate nodes and send test transactions, which will show how the new functionality works. See the [delivery guidelines](https://grants.web3.foundation/docs/Support%20Docs/milestone-deliverables-guidelines#documentation) for details. |
| **0c.** | Testing and Testing Guide | Core functions will be fully covered by comprehensive unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. See the [delivery guidelines](https://grants.web3.foundation/docs/Support%20Docs/milestone-deliverables-guidelines#testing-guide) for details. |
| **0d.** | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone.
| **0e** | Conduct comprehensive unit and integration tests to ensure all functionalities work as intended across various platforms.
| **1.a** | Complete UAT to ensure that the wallet provides a smooth and user-friendly experience for non-crypto-native users.



- ### Milestone 6 — Deployment & Launch
- ### Milestone 5 — Deployment & Launch

- **Estimated Duration:** 2
- **FTE:** 4
- **Costs:** 7,500 USD
- **Costs:** 10,000 USD

| Number | Deliverable | Specification |
| -----: | ----------- | ------------- |
| **0a.** | License | Apache 2.0. See the [delivery guidelines](https://grants.web3.foundation/docs/Support%20Docs/milestone-deliverables-guidelines#license) for details. |
| **0b.** | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how a user can (for example) spin up one of our Substrate nodes and send test transactions, which will show how the new functionality works. See the [delivery guidelines](https://grants.web3.foundation/docs/Support%20Docs/milestone-deliverables-guidelines#documentation) for details. |
| **0c.** | Testing and Testing Guide | Core functions will be fully covered by comprehensive unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. See the [delivery guidelines](https://grants.web3.foundation/docs/Support%20Docs/milestone-deliverables-guidelines#testing-guide) for details. |
| **0a.** | License | Apache 2.0. |
| **0b.** | Documentation | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how a user can (for example) spin up one of our Substrate nodes and send test transactions, which will show how the new functionality works.|
| **0c.** | Testing and Testing Guide | Core functions will be fully covered by comprehensive unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests.|
| **0d.** | Docker | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. |
| **0e** | Establish Plan for ongoing maintenance
| **0e** | Maintenance Plan | Plan for ongoing maintenance and support post-launch. |



## Future Plans
Expand Down

0 comments on commit fc450e7

Please sign in to comment.