Metakeep (https://metakeep.xyz)

Metakeep is a frictionless web3 infrastructure that provides a secure developer experience to a cloud hosted noncustodial wallet

Introduction to Metakeep

  • 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 instead 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)

    • Register FIO Handle

    • Register FIO Domain

    • Add addresses to FCH

  • COIN API

    • Transferring tokens to FCH

    • Requesting tokens from FCH

    • FIO Requests (tokens)

  • NFT API

    • Transferring assets to FCH

    • Requesting assets from FCH

    • Creating an NFT generates signature on the FIO chain using FCH

    • FIO Requests (NFTs)

  • Dynamic NFTs (n/a until FIO has user generated asset capability)

 

Integration Requirements:

Use case #1

In this use case Metakeep does the crypto handle registrations for all users and a FIO subscription model is worked out for how much to charge per month per user handle.

Prerequisites:

  • FIO funds an account for Metakeep and gives Metakeep regaddress permissions on that account

  • Metakeep creates an API for reghandle that can be called to register alice@game type handles

    • It may be possible to use the generic Metakeep sign transaction call, but the data would have to be parsed and the signing actor would have to be changed to the FIO Metakeep account.

  • Business model is created to have Metakeep charge the game a monthly fee for crypto handles and pay FIO. There may be a charge per handle per month, or a certain number of handles is allowed for a specific monthly payment.

Use case:

  • Player joins Game and gets Metakeep wallet

  • Player requests a FIO handle

  • Game checks availability (via Metakeep API or directly to FIO chain)

  • Game gets player's Metakeep FIO public key

  • Game calls reghandle API with player’s FIO Public Key

  • Metakeep receives reghandle API data and registers handle on player’s FIO public key (Metakeep pays using push transaction)

  • Player uses Metakeep API to map their public addresses to the FIO handle just created (player pays using bundles using push transaction).

Unknowns:

  • 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 ?

    • Feedback: Not currently supported. Recommended action is transfer of assets to a new key



Meetings:

12/19/2022 https://app.fireflies.ai/view/Metakeep::EFgEdnw4Kt
12/28/2022 https://app.fireflies.ai/view/Your-meeting::2bG6B6XwGq