Quote from: dannotestein on April 21, 2014, 02:18:19 pm

2) Keyhotee Founders should run this version and create a new profile to re-register a new public key with the Founder Registration server (just create an identity in Keyhotee with the correct KeyhoteeFounder ID and Founder Code). All IDs must be registered with this version, even if they were registered with a previous version of Keyhotee, because the algorithm for computing the public keys changed.

Even I register with 0.7.0?

No, this is just an updated set of links to 0.7 as requested above, sorry for the confusion.

Quote from: donkeypong on April 18, 2014, 04:08:56 pm

Please chime in and help keep this thread (which I did not start) up on Reddit. The Bitcoin mods may take it down, so the second link below shows the article it references...which is superb for Bitshares, one of the best and most stoked explanations I have seen.

http://www.reddit.com/r/Bitcoin/comments/23d3ux/how_i_became_a_bitshares_believer_in_917_words/


http://crypt.la/2014/04/18/bitshares-believer/

While it is a positively written article for Bitshares, it's a terrible piece of work and the premise feels made up.

A terrible piece of work? I thought it was well-written and quite clear, something that's difficult to do when writing about new technology. And what premise felt made up to you?

Quote from: dannotestein on April 16, 2014, 03:03:02 pm

Quote from: bitshare007777 on April 16, 2014, 05:13:45 am

Could you please confirm my registration?I could not see the  “points”.
ID: 宏帮#Aggressive.
Public key: 64De4t8Effjj6PTkU6CeeJNNBLCzi7QoxikoXQazpEx9qdJxKo
Thank you ！

Hi Bitshares007777,

Your key is not yet registered. Are you sure you're using 0.70 to register the key? What platform are you running on? Also, please describe the steps you're taking when registering. If all else fails, please send me your diagnostic log (Help/Diagnostic log) after trying to register.

I am using 0.70 version form http://invictus.io/bin/Keyhotee-0.7.0-win32.exe on win7-64bit. I registered another founder ID with Public key: 7uRzWJYTwGiBGyffPqnAqdavLhqy3Ea6tdth9FBhgMzVAe3zYS successfully，the same environment，the same profile，the same steps.Maybe you should check the chinese character on your database.

I figured out the problem, there was a change in the way chinese characters were being converted to ASCII, so the founder ID wasn't matching up in the database. Please try registering again now. Sorry for the delay, got tied up with a bunch of other projects.

I recommend to change the default profilepath for the Keyhotee Windows version to a more dynamic location.
E.g. %appdata% or {CSIDL_APPDATA}
Using local userprofil path as now is not a very suitable solution for roaming profiles or terminal server environments.
In addition it would be great to control Keyhotee application settings via registry HKCU, e.g. profilepath etc.
This will become important as soon as Keyhotee hits the business segment and should be implemented early.

Keyhotee currently uses %appdata% on windows. The above explanations are just the typical "resolved" value for %appdata% on various user's machines.

Quote from: dannotestein on April 17, 2014, 06:14:28 pm

Quote from: cassiopaia on April 17, 2014, 06:00:54 pm

Quote from: cassiopaia on April 17, 2014, 11:35:41 am

Hi Dan,

when installing new keyhotee 0.0.7 version for osx all works fine till i have created a new profile.
When clicking finish i get this error message:

here link to doc with error details ... can't post over 30000 signs here on 1 Post

https://docs.google.com/document/d/16flWTP9eAeUzFv4GQnpu95zlG3mq8N8kKyX07_NjDZ0/edit?usp=sharing

Hope it could help ! I also tried to install keyhotee 0.0.7 on my win XP computer... but their i get also an error

Doesn't work for me. tried to delete profile etc folders, reboot but everytime when i've finished step 2) from mail keyhotee crashes...

Is it crashing on Mac and PC? If not, what is the behavior on the PC?
You can email me directly at dan at syncad.com

Und WinXP 0.0.7 works fine but i didn't delete profile folder before. Just created a new brainwallet on step 1. On OSX i've deleted the complete profile folder before.
Perhaps this cause this error... i don't know

It should be fine to delete the old profile folders. Can you email me the log file created by KH when you crash?

The easiest way to find the log on the Mac is to launch a terminal, then type "open $TMPDIR" which will open a Finder window showing the contents of your temporary folder.  Our log file will be a file whose name starts with "qt_temp."

I used my founder key which was emailed to me and while it worked on the old system, providing me points, now it says it's invalid.
This is for my Keyhotee ID: Gregory

Public key: 5CCX9nWysxrv8KkibWmqVopjdMusLWHkFu478fyqwZa8HhvxGf

Can you assist?

Hi Gregory,

I see your public key is registered in the system with 0.70, but the public key is:
7R21f...HeE

I'm guessing the public key above is from some old profile. Can you check and see if you have another profile that contains the identity above?

best regards,

Dan

i think that many people thought it was more along the lines of 'external auditing,' which is, i think, what people are actually looking for. generally the industry standard (at least in my industry) is that external audits provide third-part verification. from my perspective, using a consultant accountant does not constitute third-party verification.

Well, in fairness to Stan, he did say external accountant, not auditor, although he did say they audit the books. Which I think they do in this case, since they review the transactions made from the AGS funds. Anyways, the financial debacle of recent years has surely shown pretty clearly that external auditing isn't an absolute guarantee of anything anyways I suppose, although it makes me feel better.

For the amount of money involved, what Invictus is currently providing as verification seems like a reasonable level to me. Now, if we started getting a lot more AGS donations, I think we would need to revisit this topic. The good thing here is that the records don't go away, so any past action can't be easily fudged away, so there's a strong incentive to "play it straight".

Any ideas why with recent source build of keyhotee my identity shown as unauthorized?

Keyhotee ID alexxy
PubKey 7iziYTGbUmMPRQQHLiyjkRfpsApnpWsRBidr5jj7zUwG8bJpe2

PS another strange thing old pub key in profile was 7iziYTGbUmMPRQQHLiyjkRfpsApnpWsRBidr5jj7zUwGAtu6AC however now it was changed...

We had to change the public key generation code, this was one of the major changes in the latest release. This meant that the founder IDs needed to be re-registered.