Problem Statement (Abstract)

The Arkeo chain and airdrop is coming, and in order to claim, hold, or use Arkeo, users will need a wallet/interface that supports the network. If we don’t support Arkeo on ShapeShift’s interface and/or wallets, many FOX holders and ShapeShift users will not be able to claim their airdrop and will be forced to use a competitor’s wallet/interface.

On the flip side, there is opportunity to acquire users of other wallets/interfaces that are eligible for the airdrop and/or interested in holding Arkeo. Last but not least, supporting Arkeo in the ShapeShift API will make it easier for other wallets/apps to integrate Arkeo and could also attract new API customers

Resources

https://docs.arkeo.network/

Goals

  1. Include measurable (quantitative) and immeasurable (qualitative) goals

ShapeShift Goals (same goals as the Arkeo Claim spec):

  1. 50,000+ new wallet connectors in 3 months following launch. At least 10% of wallet connectors retained as visitors in the following month.

  2. At least 30% of claimed airdrops delegated; At least 15% delegated to the ShapeShift DAO Validator

Objectives:

  1. Add support for Arkeo in Unchained and host an Arkeo node
  2. Add support for Arkeo to KeepKey and ShapeShift wallet (possibly already completed by pastaghost)
  3. Add “base-cosmos” support for Arkeo to the ShapeShift app, including send, receive, add account, and stake/unstake/claim with the ShapeShift DAO validator
  4. Add support for Arkeo in the ShapeShift API?
  5. Stretch: Add support for Voting and Delegating to any validator for Arkeo and Cosmos
  6. Stretch: Add support for Arkeo to metamask snap

Non-goals

  1. Airdrop claiming is a separate spec
  2. Additional functionality beyond what the app currently supports for Cosmos is a separate spec

Revenues

ShapeShift DAO will receive ~5% of the total supply of Arkeo tokens via the Arkeo airdrop. These tokens can be liquidated, staked to earn additional Arkeo tokens, and/or used to pay Data Providers for blockchain infra requirements.

Infrastructure Requirements

Is any new infrastructure required to support this feature (ie. spinning up a new node or subgraph)?