If we're to add bitshares to steem, both to dawn, and steem +dawn to bitshares, we're going to need a way of knowing who's who between the chains.  This is that index.  

#### Finished Tasks

* Design it

The plan:  Instead of using libraries to access APIs on either side of this process, I will use net/http or the curl library that you can use from golang.  Here are the two key things we will support:

- A cross-chain account table 
 basically it's hard today to know that @jake on glogchain is @faddat on steem @faddat on golos and @jacobgadikian on bitshares.  This ledger will allow users to register their accounts in a third party site.  No, no private keys held for this service, not ever.  We're going to try running it as a global public good service, and see what comes of it.  

#### Diagram: account table

| Steem        | Bitshares           | Dawn  |
| ------------- |:-------------:| -----:|
| faddat     | jacobgadikian | jake |


#### Code it: account table
Plan:  
* Use STORM on top of BoltDB to keep a very simple n column table.  We will add columns to the table when adding new currencies.
* Create an appropriate user flow for the site.  Use busy.org's steemconnect to verify the user's steem account is as claimed.  The other accounts are values for the steem account's key, eg:  k:v,v 
* At login user should see three fields, the left-most of which will already be filled in due to a steem-connect login.  The user will be able to enter a username in the center and right fields.   

- [ ] Test it: account table
* Solicit feedback on the application, run it, and iterate.  

# Objective

This would allow applications using these blockchains to create economic and data flows between each other with greater ease, and help users discover one another.