KeepKey - Revision history

Mapple at 17:03, 18 April 2018

2018-04-18T17:03:31Z

Mapple: /* email contact with support@keepkey.com 17 Apr 2018 by @mapple */

2018-04-17T06:57:04Z

email contact with support@keepkey.com 17 Apr 2018 by @mapple

Mapple: documenting keepkey criteria and communication

2018-04-17T06:56:46Z

documenting keepkey criteria and communication

New page

=== email contact with support@keepkey.com 17 Apr 2018 by @mapple ===

Thanks for your feedback! It is exciting to hear about all the projects and assets our customers use. As you might imagine, we get a lot of requests to add new assets to KeepKey. This email will give you high-level overview of how we decide which new cryptoassets to prioritize.

The minimum requirements for adding support for an asset to KeepKey are:

# Listed by ShapeShift - Our integration with ShapeShift assumes that all supported coins are listed there.
# Insight API available - The KeepKey client relies on the Insight API to get blockchain data about each coin.
# Strong and sizable community - This is a factor in the financial analysis described below.
# An establish, stable value for the cryptoasset.

One final factor is a little more squishy and hard to define. At the end of the day, the question that we ask is whether adding a new cryptoasset will create a substantial and sustained bump in our sales. There are upfront costs and recurring costs associated with adding a cryptoasset. We have to reasonably believe that adding it can cover these costs through increased revenue.

After all of that, we have to prioritize the engineering and marketing efforts that will be needed to complete the integration against other cryptoassets and features on our roadmap.

I wish you the best with your new cryptocurrency. If you feel that the above requirements can be met and that a strong financial case can be made for integrating your new cryptoasset, please reply to this email and we can have further conversations.

Thanks for your interest in KeepKey.

----
my response
----
Thanks for the detailed response.

To be honest I don't think Ravencoin is there yet. I'm going to log your response on our wiki as something to revisit if and when Ravencoin gets more widely adopted.

@@ Line 1: / Line 1: @@
 === email contact with support@keepkey.com 17 Apr 2018 by @mapple ===
-Thanks for your feedback! It is exciting to hear about all the projects and assets our customers use. As you might imagine, we get a lot of requests to add new assets to KeepKey. This email will give you high-level overview of how we decide which new cryptoassets to prioritize.
+Keepkey: Thanks for your feedback! It is exciting to hear about all the projects and assets our customers use. As you might imagine, we get a lot of requests to add new assets to KeepKey. This email will give you high-level overview of how we decide which new cryptoassets to prioritize.
 The minimum requirements for adding support for an asset to KeepKey are:
@@ Line 17: / Line 17: @@
 Thanks for your interest in KeepKey.
 ----
-my response
+Mapple: Thanks for the detailed response.
 To be honest I don't think Ravencoin is there yet. I'm going to log your response on our wiki as something to revisit if and when Ravencoin gets more widely adopted.

@@ Line 5: / Line 5: @@
 The minimum requirements for adding support for an asset to KeepKey are:
- #   Listed by ShapeShift - Our integration with ShapeShift assumes that all supported coins are listed there.
+#   Listed by ShapeShift - Our integration with ShapeShift assumes that all supported coins are listed there.
- #   Insight API available - The KeepKey client relies on the Insight API to get blockchain data about each coin.
+#   Insight API available - The KeepKey client relies on the Insight API to get blockchain data about each coin.
- #   Strong and sizable community - This is a factor in the financial analysis described below.
+#   Strong and sizable community - This is a factor in the financial analysis described below.
- #   An establish, stable value for the cryptoasset.
+#   An establish, stable value for the cryptoasset.
 One final factor is a little more squishy and hard to define. At the end of the day, the question that we ask is whether adding a new cryptoasset will create a substantial and sustained bump in our sales. There are upfront costs and recurring costs associated with adding a cryptoasset. We have to reasonably believe that adding it can cover these costs through increased revenue.