communicating_between_keyhotee_clients.txt

== Communicating between Keyhotee clients Locally Without a Server ==

=== General notes ===
* If you build a release version of Keyhotee, the executable will be called "keyhotee". The debug version is called "keyhoteed".
* The Keyhotee executable is built to ${INVICTUS_ROOT}/bin


== Profiles in Keyhotee ==
* A profile is used by Keyhotee to store your identities, contacts, messages, etc. If multiple users plan to use Keyhotee on the same machine, each should generally create his own profile. You have to also create at least one identity in each profile with "New Identity" menu before you can communicate with other users from that profile.
* If the profile doesn't yet exist when Keyhotee is launched, a new profile will be created. In this case Keyhotee will launch a wizard to create your brain wallet and your first identity.
* If profiles exist, a dialog pops up with a dropdown where you can select the profile you want to use. You can also create new profiles from this dialog.
* For my profiles, I use: "default", "second", "third", etc.
* For my identities, I use "first", "second", "third", etc.
* I recommend using the same password for all your profiles, this makes it easier to remember.

=== Steps to setup communication between clients ===
* Run "keyhotee" (or keyhoteed if you built a debug version) and create a new identity (this first profile is "default" profile). I typically call this identity "first".

* Run a second copy of keyhotee and create a new identity. I typically call this identity "second".
* Shut down keyhotee (don't bother mining either identity yet).
* On windows, launch an explorer window and go to "C:\Users\Administrator\AppData\Local\KeyhoteeD\profiles" (or Keyhotee if you build release version I guess, the "D" here is for debug). You can get close to this directory by going to %appdata%. This directory stores your profile directories. You should see a default profile and a second profile directory. 
Go into the default directory and edit the config.json file. Change it to look like this:
{
  "data_dir": "C:/Users/Administrator/AppData/Local/KeyhoteeD/profiles/default/data",
  "network_port": 9876,
  "rpc_config": {
    "port": 9877,
    "user": "",
    "pass": ""
  },
  "enable_upnp": false,
  "default_nodes": [
  ]
}
This tells the default client to not hook up to the server and tells it to wait for connections on 9876.

Go into the second directory and edit the config.json file. Change it to look like this:
{
  "data_dir": "C:/Users/Administrator/AppData/Local/KeyhoteeD/profiles/second/data",
  "network_port": 10876,
  "rpc_config": {
    "port": 10877,
    "user": "",
    "pass": ""
  },
  "enable_upnp": false,
  "default_nodes": [
    "127.0.0.1:9876"
  ]
}
This tells the second client to hook up to the local default client on 9876.

* Delete blockchain directories that your clients received from the remote server: 
       delete C:\Users\Administrator\AppData\Local\KeyhoteeD\profiles\default\data\bitname\bitname\channel
       delete C:\Users\Administrator\AppData\Local\KeyhoteeD\profiles\second\data\bitname\bitname\channel
  Note: If you don't do this step, your clients probably won't sync up a block chain, since they may get slightly different block chains (because you
        or someone else might mine on the server during the interval between connection of each of your clients to the server). If they don't sync
		up, you won't be able to send msgs or email. So long story short: safest to delete these directories and start with a clean block chain.

=== Configuring the two clients to "know each other" so that they mine on same block chain ===
* Run "keyhoteed" again to launch the default profile client (this client must be started first).
* Run "keyhoteed second" to launch the second profile client.
* In both clients,  enable mining from the Identity/Enable Mining long enough to successfully mine each identity.
* In the default client, create a new contact for "second" (if it says this Keyhotee ID is not registered, it means it wasn't mined enough or else the two clients didn't connect up properly).
* In the "second" client, create a new contact for "first" (if it says this Keyhotee ID is not registered, it means it wasn't mined enough or else the two clients didn't connect up properly).
* You should now be able to send chats and emails back and forth between the two clients.