Tech Fleet’s open source cross-chain wallet built for Kadena

Caption: Tech Fleet wants to bridge the gap between web2 and web 3 for UX, Product, and Development talent.

The vision

First release

For the purposes of this article we’ll call this “Wallet Dapp” until the team names it.

Future versions

In the future, Wallet Dapp could make it easy for a person to send tokens from ERC20 to and from KDA blockchain directly in the dapp, to and from any blockchain with an RPC connection ability that Kadena has bridged to, or bridging through pre-defined options in the app for users (think Anyswap). Other features like fiat onramp services could also be voted on in the future. Tech Fleet Community DAO could vote for Wallet Dapp DAO and create a governance token for it, allowing it to operate as a DAO on its own in the future (think Metamask DAO). Any theoretical fees that Wallet Dapp would collect would go to the Tech Fleet Community DAO treasury and distributed as voted upon.

Features

Disclaimer: the designs you see here are not final, and will change as the team explores the problem space and designs. Think of them as concepts to be fleshed out in detail, and changed when it makes sense, through Tech Fleet’s Agile User-Centered Design process.

Token wallet for Kadena, Ethereum, BSC, Polygon, and more

Since this dapp is copied from the Metamask code, it will have a similar baseline ability to hold tokens across many blockchains. The main difference between Metamask and Wallet Dapp is that Wallet Dapp is custom built to solve user problems on the Kadena blockchain. Wallet Dapp will be able to create secure “Kadena K accounts” and hold any token on Kadena. And just like Metamask it will also be able to create wallet accounts and hold any token on Ethereum, Binance Smart Chain, Polygon, and any other blockchain we make available for the dapp. We’ll make it easy for you to send cross-blockchain in the future (but not for MVP).

Send tokens on Kadena from any chain all at once

One hurdle for newcomers of Kadena is understanding the concept of the “multiple chain” architecture, and how to interact with dapps across all Kadena chains. Blockchains like Ethereum have one chain, and sending from one wallet to the next is straightforward enough. Go to Kadena and you add multiple dimensions to sending tokens. Kadena’s architecture exists on 20 separate chains (each its own blockchain) and more in the future. Dapps on the Kadena ecosystem are deployed on specific chains, requiring users to send Kadena to their own wallet on multiple different chains before they can start using Kadena dapps (each wallet can exist on chains 0 to 19 today). A big part of the user experience for Kadena today is sending funds chain-by-chain. For instance, if you wanted 500 KDA on your wallet for Chain 4, you might have to send 20 from chain 1, 400 from chain 0, and 80 from chain 3. You have to do that 3 separate times, pay for gas each time, and wait several minutes each time. Each time it could fail, or could be “stuck in the void” and you have to get it through a tool Kadena provides. Wallet Dapp wants to take that kind of mental workload and requirement of prior knowledge away from the user. Users should be able to send “800 KDA from Wallet A to Wallet B on KDA Chain 3” without knowing how Kadena’s blockchain works, or having to send separate transactions themselves. Wallet Dapp should do that work for them.

Caption: this is a concept of the flow to send tokens in Wallet Dapp.

Aimed at crypto newcomers and laypeople

Wallet Dapp makes the process of sending tokens simple for newcomers and laypeople who don’t understand the technical details. In addition to understanding about the multiple chain architecture, newcomers to Kadena may also not understand other intricacies of how Kadena’s blockchain works. In some cases users risk losing their tokens or NFT when sending over Kadena. For example, some users after the recent K account change continued to use old wallets and lost KDA to squatting bots. Another intricacy of Kadena is the fact that the wallet “must exist on a chain” to send to it simply by sending your first KDA transaction to it. If it “does not exist”, there are barriers for users (like losing an NFT if it gets sent to a wallet that does not exist on a specific chain).

Caption: Newcomers to Kadena blockchain must understand the implications of sending to K accounts vs. “non-K accounts” lest they risk their funds being lost to squatting bots on other Kadena chains. Wallet Dapp should tell users when there’s any kind of risk they might face sending funds (failed tx, risk of lost funds, etc.).

Kadena Gas Stations

Gas is a concept you can’t escape as a user of crypto. Sending tokens, minting NFT, depositing liquidity, staking tokens, any time you interact with a blockchain it requires transaction gas fees. Sometimes gas on Ethereum can cost hundreds of dollars per transaction (like Ethereum network gas prices at times). Layer 2 solutions have been introduced to help solve Ethereum’s gas and scaling problem; Ethereum 2.0 is planned to solve these problems when there’s high network traffic.

Cross-chain NFT wallet

This is a gap in Kadena wallets today as Kadena is a “young blockchain”. Wallet Dapp aims to be the first Kadena wallet that allows users to hold, send, or receive NFT. We’ll also make this feature available for other blockchains like Ethereum and BSC, creating the world’s first cross-chain NFT wallet for the world. Bullish.

Showing token values in the wallet

Today websites like KittyKad and KDLaunch pull pricing data from Kadena’s DEX’s (Kaddex, Adenak, and KDSwap). Wallet Dapp should show accurate price estimates (across all exchanges) for the value in users’ wallets at any given time.

Caption: concept of showing the value of users’ tokens (and NFT in the future if we can make that happen).

Easy access to Testnet faucets

Today the Kadena Testnet Faucet allows users to get testnet KDA tokens to use on testnet dapps. Teams who rely on early user testing often provide incentives for bug testing before launch, but today the process of getting faucet tokens is convoluted for newcomers and non-technical people.

Exploring “Easy mode”

Beyond the things covered above, what does easy mode look like when each blockchain you interact with has its own logic for interacting with it? We’re going to explore and ideate what that could look like, but it would in theory focus on some of the confusing and frustrating aspects of blockchain to newcomers. Things like explaining how Kadena’s chains work or the requirements around secured accounts might play a role in making the experience more intuitive to users. The team will explore these topics each week through UX research.

Next steps

The project will run starting Monday, June 6th through Friday, July 29th

Apprentices and leads

Tech Fleet exists to provide mentorship opportunities plus real-world client work for individuals getting into the field for the first time. As such, our projects are structured as a “buddy system”: each role has a lead and several apprentices under it. They all cross-functionally work together everyday in their sprint work. The Wallet Dapp project will run for 8 weeks and will have the following roles:

Tentative Sprint Plan

We start all projects with a high-level roadmap, and in true Agile fashion adjust the plan as we complete each week of work and proceed with the project. Here’s our sprint schedule and goals as of the start of the project:

  1. Have a project kickoff to understand the goals and scope
  2. Competitive analysis of other wallet dapps
  3. Review of the vision and the high fidelity prototype
  4. Prepare for user research about crypto wallets
  5. MVP scoping and requirements work
  1. Perform user research about the UX of crypto wallets
  2. Usability test of Wallet Dapp
  3. More competitive analysis
  4. Audience personas
  5. Product Requirements work for Wallet Dapp
  1. Usability test of Wallet Dapp with users
  2. Other UX research with users
  3. More competitive analysis
  4. Audience personas
  5. Design work continues for Wallet Dapp
  6. Product Requirements work for Wallet Dapp
  1. UX research with users
  2. Product Requirements work for Wallet Dapp
  3. Design work continues for Wallet Dapp
  4. Development begins for Wallet Dapp
  1. UX research with users
  2. Product Requirements work for Wallet Dapp
  3. Design work continues for Wallet Dapp
  4. Development continues for Wallet Dapp
  1. UX research with users
  2. Product Requirements work for Wallet Dapp
  3. Design work continues for Wallet Dapp
  4. Development continues for Wallet Dapp
  1. UX research with users
  2. Product Requirements work for Wallet Dapp
  3. Design work continues for Wallet Dapp
  4. Development continues for Wallet Dapp
  5. Test Wallet Dapp MVP with users
  6. Prepare for beta with the community
  1. UX research with users
  2. Product Requirements work for Wallet Dapp
  3. Design work continues for Wallet Dapp
  4. Development continues for Wallet Dapp
  5. Test Wallet Dapp MVP with users
  6. Launch to beta with the community

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store