PROJECT: Standardized Hardware API for Cryptographic Interoperability

**The Problem:** as a developer, have to learn the APIs for a number of different hardware devices; as a user, you have the NASCAR problem of a list of providers. Worse, if any individual company changes their API, then everything breaks.

**The Solutions:** Develop a uniform API and architecture with relatively few commands, with capability-discovering on error that help to answer the hardware and network side of things.
```
se⇔mcu⇔app⇔network⇔peers
```

- [ ] Write Hardware Wallet Use Cases ([early draft](https://hackmd.io/2DJUWUG8Ty2t0BNaUSujRw))
- [ ] Write Hardware Wallet Crypto API Analysis ([spreadsheet](https://docs.google.com/spreadsheets/d/1flpIl8YG7vqWBWoLvFOMVW7xMuuk36F4asaiBQ5LBVM>))
- [ ] Analyze Patterns
- [ ] Define Goals of Principals
- [ ] Define Overall Architecture for Standard Wallet API
- [ ] Integrate with SSKR Recovery
- [ ] Update crypto-requests as Needed
- [ ] Update Other URs as Needed
- [ ] Write Draft of Paper for Ideal API
- [ ] Update [Wallet Architecture Diagram and Article](https://github.com/WebOfTrustInfo/rwot9-prague/blob/master/topics-and-advance-readings/whats-wallet.md) (see #90)
- [ ] Implement MVP of API
- [ ] Choose branding for project
- [ ] Evangelize to community

This is expected to be a joint project of Blockchain Commons, CrossBar, and Proxy.

まず、リンクされている Hardware Wallet Use Cases のドラフトと Crypto API Analysis スプレッドシートを読み、次に #90 で参照されている Wallet Architecture Diagram と記事を確認してください。この issue は、プロジェクトのアーキテクチャ、API ドラフト、MVP、ドキュメント、コミュニティへの展開が定義され、チェックリストが完了した場合にのみ完了となります。

索引モデルが issue の本文から書いたものです。