Metakeep is a frictionless web3 infrastructure that provides a secure developer experience to a cloud hosted noncustodial wallet
Wallets are generated onto a hardware secure element that only the user/developer can access through authenticated api
User is not inundated with complicated onboarding process, can export private key later if they wish
User pays a monthly subscription + fees to Metakeep until of worrying about blockchain transaction fees and gas variance
Metakeep and FIO
Metakeep has been searching for a decentralized naming solution to add to their infrastructure and has expressed interest in FIO protocol
Tasked with determining where FIO could integrated, we performed an analysis of their developer API
During account creation, user can optionally created a FIO Crypto Handle (FCH) under the metakeep domain (or create a FIO domain and FCH under here if they wish)
COIN API
Transferring tokens to FCH
Requesting tokens from FCH
NFT API
Transferring assets to FCH
Requesting assets from FCH
Creating an NFT generates signature on the FIO chain using FCH
Dynamic NFTs (n/a until FIO has user generated asset capability)
Integration Requirements:
Unkowns:
How can Metakeep use FIO to support their subscription model?
Domain level bundles - bundles are purchased at the domain level and distributed to FCHs on that domain by the owner as needed and reflected within the users subscription costs
Such a feature would allow an organization like Metakeep or one of their users to make large bundle purchases from the FIO network to support their growing subscriber base
Opera has auto-bundle renewal. This might be usable for this purpose
If a user has generated their keys on a platform before it has integrated Metakeep, can they import or migrate to their infrastructure ?
Meetings: