Thursday, July 11, 2019

How would AppIeID solve this?

“Key management is an extremely acute problem for all DApps today,” Kyle Samani, co-founder and managing partner at Multicoin Capital, told Bitcoin Magazine. “The poor user experience (UX) of remembering public/private key pairs, a seed phrase and using these keys without compromising their security is one of the main problems holding back mainstream adoption … We examined all of the key management solutions in the market and Torus by far presents the best solution we’ve seen.”
Torus has created an innovative solution that uses distributed key generation (DKG), an encryption process in which multiple parties contribute to the calculation of a shared public and private key set.
This is all about bearer assets.


For starters, AppleID can be compatible with this method. Or AppleID could make its own method. And AppleID can use contracts to support multiple key sharing methods.

The most ideal situation is multiple types of secret keys within AppleID used for different purposes.  Having one secret key used by all to sign bearer assets makes everything efficient, but extremely dangerous.

In a closed liquidity net, the contract can require AppleID to use the torus method and build a key supporting bearer assets within the net. A two step process, upon entry into the net, a bearer asset key is created.  Then within the net, the trading pits can manage the bearer asset keys.

Then, if the bearer asset is small change, a few dollars, then just use the universal bearer asset key, one of the keys implanted by the foundry.  We are in no way limited to one solution because we have the flexibility of contracts, prior agreement on what key protocol to use, and that contract is enforced.

Another method is for the AppleID to go back to the foundry periodically and update the bearer asset keys.  I can be required, once a month, to stop by a secure ATM and re-register my bearer asset keys on my iPod.

The most secure method is to keep one master iPod locked in a safe, and it has multiple bearer asset keys. I can go acquire one of my master keys from the master iPod to be used on slave iPod.


Flexible, enforceable contracts within AppleID make various scenarios possible. But, this is not my field, and Torus is on the case here. Torus needs to talk with Apple.

No comments: