Proposal: Iris Wallet Polkadot - Open Source cross-browser fully featured wallet
Hi 👋
I’m Francis Luz CEO at B58 Finance, and first of all its being a pleasure to be able to bring our blockchain knowledge to the Polkadot ecosystem.
We’ve been building a Wallet for the Cardano Blockchain, and then we got invited to this new challenge to develop Iris Wallet on top of Polkadot.
The Proposal
Iris Wallet will be a fully featured cross-browser extension wallet, built natively on Polkadot and Open-Source.
Our mission is the bring the user experience to the next level, which increases the adoption and makes it easy for non-crypto users to get on board.
For more details about features, B58 Team and Milestones please read our full proposal:
📄 - Full Proposal
We’re here for an open discussion asking for feedback and interesting features that we might not be covering at moment.
Let’s build it together and looking forward to your feedback.
B58 Finance - Decentralized digital future.
Thanks,
B58 Team
Comments (2)
The more wallets we have, the better! I love it!
Good structure of the proposal btw :P haha
As for the content, I would like to provide the following feedback and questions (by your favor):
Nice looking extension! Do you have plans to have "full-screen" version of the extension (like Talisman or Metamask have)?
These are Treasury funded wallets, however, users have more options nowadays when it comes to browser extensions, specifically I think it is worth mentioning:
I would recommend taking a look at least at SubWallet to understand the upcoming value of Iris Wallet and how it can shine compared to others (e.g. Talisman & SubWallet)
I would suggest also dedicate at least on the design lvl support for Ethereum-based accounts in order to be compatible with EVM-based/comptable parachains (Moonriver/Moonbeam, Shiden/Astar), and it will also help to support upcoming EVM-bridge features (e.g. on Acala/Karura DApps I'm pretty sure there will be an option to connect both Acala/Karura & Ethereum account in order to do the bridging transactions)
How exactly that would be implemented? Like fetching the data from Polkadot/DotMarketCap/other twitter account or...?
If that's defined now, what would you use for the Transaction history data source (IMHO well working solutions are Subscan / SubQuery / Subsquid)? In novawallet.io we have developed & maintaining data sources for all Polkadot ecosystem networks to fetch operations history for all Polkadot assets, I would be happy to help on the introduction side to those!
With cross-chain transfers available for some networks (and the list is expanding on weekly basis), I would recommend to think about the UX/UI and architecture design for cross-chain transfers as well
Will there be an option to select validators manually? How exactly "automatic selection of validators" will work? For example, we have implemented "Recommended validators" in novawallet.io in a way that basically Nova Wallet is fetching all elected validators in current era, and applying filters & sorting on them (sort by profits, remove oversubscribed, limit 2 per 1 identity, remove slashed, include only those who has an identity with at least 1 contact)
I would recommend to call that "Polkadot JS Extension protocol" integration since in Web3 there are multiple protocols for DApps (Tether, Metamask, etc). I suppose in the future Iris Wallet would need to support Metamask protocol in addition to Polkadot JS Extension protocol so that Iris Wallet will cover all available DApps in the ecosystem (that's what we are developing for Nova Wallet DApp browser at this moment)
Do you have any companies to consider now for Iris Wallet audit? I think it would be great to have a Kusama/Polkadot bounty to fund ecosystem apps for security audits
Transak, MoonPay & Ramp are great choices for integrating onramp to the app! Couldn't find any info about Banksa, do they support Polkadot & Kusama tokens?
In my understanding, you need JS engineers (usually referred to as Frontend engineers) to build an extension-based app, or are you planning to have some middleware/backend? In this case, how the architecture is going to look like in terms of components responsibilities — what is stored on the side of the browser extension, how networking is divided between the extension and the backend/middleware, etc?
Overall, feel free to ask for any help & questions on how to build the apps in the Polkadot ecosystem! We are mostly focused on mobile app development, but we have 2+ years of experience in building client apps for Substrate, so would be happy to help
And once again — I'm excited and wish you luck with your proposal!
Hey Anton,
We appreciate your time and contribution to our proposal, and we couldn't agree more about having more wallets, the ecosystem will just grow.
Yes, we’re going to work on a full-screen mode
Section updated with specific treasury funded wallets that have browser extension versions. And thanks for the other references will be looking at them.
Make sense, we’ll be considering it in futures iterations of our wallet, the main focus at moment will the core. We will structure our solution in such a way it can be extended with web3.js integration later.
News Exactly as you said, we’ll be fetching data from verified accounts, like you mention Polkadot/DotMarketCap/Web3 Foundation.
We will be using SubQuery for now but we love to know about your solution.
Thanks for pointing that out.
And we also included a new section for Transaction view history in the proposal.
Thanks for highlighting it, we have some discussion about it with Parity but, will in future phases as well. The first version will be considered only the same chain transactions but this very important feature to have.
Yes, you’ll be able to select it manually, tbh we were thinking about doing similar to what you’re doing just getting the TOP 1 validator at the moment as extra.
Suggestion taken ;)
We don’t have a specific one yet, but Parity will recommend one once we get to this point.
About the bounty, after you mention it here, we went back to the Parity team, we’ll set up some brainstorming sessions to write this proposal. But first, we need to get our proposal through.
It was a typo the correct name is “Banxa” and is an Australian provider that only supports DOT.
You’re correct, for building an extension we need mainly JS skills, so today the wallet we’re building is using Typescript and for backend APIs we use Rust. Pretty much 3 of us are fluent in it. But think in expanding team the main role will be Frontend focus for sure.
Regarding the architecture, we’ll divide it into Client(“Frontend”), and API(“Backend”) with a mix of Substrate-api-sidecar recommended by the Parity team.
About data storage, pretty much user settings, account public data similar to PolkadotJS and some cached data from API.
Once again thanks a lot, we’d love to keep in touch and collaborate. As you guys have a lot of experience will be probably bothering every now and then ;) Also very excited about being part of the community.
2.6 Submit Code to Audit
We would be happy to help you draft a proposal for a bounty that handles auditing processes for teams developing projects with treasury funds: we would need to specify the scope of work, the teams we want to work with and who the curators will be. Also, application process would be required. I think the most difficult part is to find a audit team that has the bandwidth to do so.
Thanks for the support, we've spoken with the Parity team, and they will help us with the Bounty too. First, we need to get this proposal through and then we can start the Bounty proposal. Definitely find the audit team will be a hard one, let's see Parity has some recommendations.