I believe that I successfully re-registered my Keyhotee Founder ID since the points showed up when I entered my information, but when I click on my identity under Contacts, the yellow box says "Unregistered".

Founder ID - Evan
Keyhotee 0.7 Public Key - 7CkhKJBks2KHQiLVszhyPNcuGVBoFgeTtf4iDHrKfEjcMXxtJ1

Yes, the server shows you as registered to this key. It really should say the points under your identity for the contact also, however, unless it lost connectivity to the founder server (it just sends the same message it sent when you initially created the Identity). If this persists, PM me and we can try to figure out what the problem is.

No, it's not changeable at this time.

Founder IDs need to be re-registered with Keyhotee 0.7.0

We recently discovered a problem with the way we're generating public keys in Keyhotee, and the best solution we could come up will require re-registering your Keyhotee Founder IDs. However, we've worked hard to make this process simpler than in the past, so it shouldn't be too bad I think. Below is a full description of the problem and our solution. Since we had to make this breaking change, we've also incorporated several other “breaking changes” that will require use of Keyhotee 0.7.0 versus the older alpha clients.


The Problem: city_hash64 is not stable across versions and is not well standardized

The algorithm Keyhotee uses to automatically generate the public key for a Keyhotee ID employs a hashing function called city_hash. While recently investigating the city_hash algorithm, we found that it's not a unchanging algorithm that will generate the same hash value over different versions of the function. This is in contrast to the standard cryptographic hashes like sha2 which are guaranteed to produce the same hash number for a given input across all implementations of sha2.

This guarantee provided by the standard cryptographic hash functions is important for Keyhotee IDs, because it is desirable for a user to be able to re-generate the same public keys for a profile when using many different Keyhotee-style clients. For example, a user might use the existing C++-based Keyhotee client on his desktop and a Java-based Keyhotee client (not yet developed) on an Android phone, and he would want to be able to use the same Keyhotee IDs on either system.

The Solution: Replace city_hash with sha2

To eliminate this problem so that the public keys are easy to regenerate on different Keyhotee-client implementations, we are replacing all uses of city_hash in the generation of Keyhotee clients with sha2 based hashes. The only problem with this solution is that it requires that all Keyhotee founder Ids to be registered again with the new public keys generated using sha2 hashing.

Steps to register your Founder ID(s)

1) Download the appropriate OS version of Keyhotee 0.7.0 here:
ftp://178.63.85.22/Keyhotee/Windows/2014-04-21_00-00-43/Keyhotee-0.7.92-win32.exe
ftp://178.63.85.22/Keyhotee/Linux/2014-04-21_15-48-02/Keyhotee.tar.gz
ftp://178.63.85.22/Keyhotee/MacOS/2014-04-05_00-01-42/Keyhotee.dmg


2) Create a NEW profile (existing profiles are invalid). Record in a safe location the information you enter to create your profile (first/middle/last name, your brainwallet passcode, and your profile password).

3) From the main Keyhotee GUI menu, select the menu option “New Identity”. In the New Identity dialog, enter your Keyhotee Founder ID and your Keyhotee Founder Code. If you've entered the information correctly, you should see some “points” appear at the bottom of the dialog. The points message indicates that you have successfully registered your Keyhotee ID with our server. If you no longer have your Founder ID or Founder Code, you can contact Stan for this information.

We're currently in the middle of implementing peer discovery for the p2p network code. As of yesterday we have a set of test nodes connecting up to each other and sharing the peer date in each node's local peer database.

Quote from: etherbroker on March 20, 2014, 05:59:49 am

Its like saying I can't trade my property with someone else.  Of course I can.

Sent using Tapatalk

If I sell you my house, you can change the locks.

If I sell you my AGS donation keys, you can't prove I don't still have a copy of the keys. In essence, you can't change the locks.

I think that's a good analogy to the current situation.

However, as a personal "holder" of AGS (not as an Invictus employee), my feeling is that recognition of AGS will inevitably move to a liquid form, just given the entrepreneurial nature of our community. I suspect this will happen not long after the AGS donation phase is completed. Bear in my mine, this is just my personal opinion (and desire, since I feel it will raise the value of AGS).

As you can see I am a Newbie!! 

I gather from the previous comments that one can't download to help test Keyhotee at this point due to lack of a Keyhotee ID?

You don't need a Keyhotee ID to help test it, you can create an identity with just a public key (not tied to a KH ID) and use the public key as your mailing address for now. That's actually how everyone tests it right now.

I haven't posted status for a few days, since I wanted to get to a well-defined point in our design work first, so here's where we're at now:

Together with Bytemaster, we defined the interface between the generic peer-to-peer (p2p) network layer and the generic blockchain code for DACs (and also Keyhotee).  Since then, Bytemaster has been working independently on the generic blockchain code. Eric and I are currently designing the generic p2p network layer . We finished designing the algorithm for syncing to peers, plus broadcast and validation of transactions and blocks during normal operation today, and moved on to designing the peer discovery algorithm, which we'll likely finish in the next day or two. After that, we'll do a final review of the design and move on to implementation. Keyhotee GUI guys are working independently on current outstanding feature requests and bugs listed in github.

There are times that keyhotee cannot load my profile . Any user also had experienced this bug?

Is it possible you have another copy running? Only one copy can open a particular profile at any given time (that's happened before to me).