0.5.4 still doesn't work for me but it's ok for me as long as the public key and founder code is correctly registered on the server database and will be included in the genesis block.

Quote from: zhangweis on February 21, 2014, 12:35:58 AM

Quote from: dannotestein on February 20, 2014, 02:26:22 PM
Yes, "john" is properly registered in the database with 5yQRwuHnu9iRF4NuzvcDaDwgZch74EVT6X8b4pfecrwbnnMTLF, so your id will work properly show up as a Founder ID once the blockchain is initialized.

Another user reported a similar problem today, so I reviewed the code today that reports the points and I'm pretty sure I know the problem: for security reasons, the name server requires that the identity be created with the "Founder Code" in order to report your points (basically Keyhotee sends the KeyhoteeID, the public key, and the founder code to the founder registration server to be verified). I suspect that your identity info is either missing the founder code or it has the wrong one. You can check the founder code entered by looking in the "Notes" section of your contact info for your identity. If it's blank or if the code is wrong, this would explain the issue. Note this doesn't mean your Founder Id isn't registered, just that it won't show as registered in your Keyhotee until the blockchain is initialized.

I'm going to look into a possible method for notifying anyone who might be experiencing this problem today, and I'll report back with more details late tonight or tomorrow.

Thanks for the clarification. I'll wait for the blockchain. Is there any other way for me to recreate the identity with founder code or add founder code to the existing identity?

I've modified the founder registration server and made a new 0.5.4 alpha release that will report if the kehoteeID and public key match the ones stored on the server even when there's no founder code entered. So if you install  the new version, you should be able to check your identity now. The new version is here:
http://invictus.io/bin/keyhotee_0.5.4.zip

Quote from: dannotestein on February 20, 2014, 02:26:22 PM
Yes, "john" is properly registered in the database with 5yQRwuHnu9iRF4NuzvcDaDwgZch74EVT6X8b4pfecrwbnnMTLF, so your id will work properly show up as a Founder ID once the blockchain is initialized.

Another user reported a similar problem today, so I reviewed the code today that reports the points and I'm pretty sure I know the problem: for security reasons, the name server requires that the identity be created with the "Founder Code" in order to report your points (basically Keyhotee sends the KeyhoteeID, the public key, and the founder code to the founder registration server to be verified). I suspect that your identity info is either missing the founder code or it has the wrong one. You can check the founder code entered by looking in the "Notes" section of your contact info for your identity. If it's blank or if the code is wrong, this would explain the issue. Note this doesn't mean your Founder Id isn't registered, just that it won't show as registered in your Keyhotee until the blockchain is initialized.

I'm going to look into a possible method for notifying anyone who might be experiencing this problem today, and I'll report back with more details late tonight or tomorrow.

Thanks for the clarification. I'll wait for the blockchain. Is there any other way for me to recreate the identity with founder code or add founder code to the existing identity?

Thanks. Fixed the connection issue but still no points.  I'll wait for the next version like you said. Thanks!

Quote from: Xeldal on February 20, 2014, 10:10:04 PM
this is using Keyhotee_0.5.3.exe

the About menu item lists:
version 1.0 Beta1
keyhotee built from fa53b569b876....

I must have needed to get rid of something before running the new client, i guess?

yes, I think you've got an old config.json file in your profile directory with the old port number.

this is using Keyhotee_0.5.3.exe

the About menu item lists:
version 1.0 Beta1
keyhotee built from fa53b569b876....

I must have needed to get rid of something before running the new client, i guess?

Quote from: Xeldal on February 20, 2014, 09:29:46 PM
My client is not showing any points.  I've registered on the website twice about a week ago.  The console window continually says:

"No connection can be made because the target machine actively refused it"
error connecting to 162.243.67.4:9876
unable to connect to 162.243.67.4:9876

I was assuming this was the BitShare network refusing the connection which makes sense but now i'm unsure.

The messaging seems to work just fine.

The fact that your client is using 9876 instead of 7896 means you've got an old KH client, that's why the server is refusing it.

We're planning on uploading a new alpha release tonight, to address some "unregistered" messages several Founder ID holders are seeing, so please hold off downloading a new version until then.

My client is not showing any points.  I've registered on the website twice about a week ago.  The console window continually says:

"No connection can be made because the target machine actively refused it"
error connecting to 162.243.67.4:9876
unable to connect to 162.243.67.4:9876

I was assuming this was the BitShare network refusing the connection which makes sense but now i'm unsure.

The messaging seems to work just fine.

Thank you for the frequent updates, they are much appreciated.

Quote from: zhangweis on February 20, 2014, 06:51:19 AM
I also have the issue of showing as "unregistered". Can you have a check for me? Thanks. My public key is "5yQRwuHnu9iRF4NuzvcDaDwgZch74EVT6X8b4pfecrwbnnMTLF" and the founder id should be "john".

Quote from: dannotestein on February 17, 2014, 07:48:30 PM

Quote from: JustHayden on February 17, 2014, 07:38:33 PM
Where those points are it says "Unregistered" on mine. But it still says "Keyhotee Founder" beside it.

The Keyhotee Founder message is not meaningful in this case, it just means you "mined" your name locally in a temporary blockchain, probably using one of the early betas before identity mining was disabled.

The important thing is the points message, which apparently is not showing properly on your client. On the founder server, I see JustHayden has been registered with a public key like this: 6ked...V6Bb.  Does that match the public key shown in your KH client?

Also, are you using the 0.5.3 alpha client?
If possible, please reply to me via dan at syncad.com to speed my replies.

Yes, "john" is properly registered in the database with 5yQRwuHnu9iRF4NuzvcDaDwgZch74EVT6X8b4pfecrwbnnMTLF, so your id will work properly show up as a Founder ID once the blockchain is initialized.

Another user reported a similar problem today, so I reviewed the code today that reports the points and I'm pretty sure I know the problem: for security reasons, the name server requires that the identity be created with the "Founder Code" in order to report your points (basically Keyhotee sends the KeyhoteeID, the public key, and the founder code to the founder registration server to be verified). I suspect that your identity info is either missing the founder code or it has the wrong one. You can check the founder code entered by looking in the "Notes" section of your contact info for your identity. If it's blank or if the code is wrong, this would explain the issue. Note this doesn't mean your Founder Id isn't registered, just that it won't show as registered in your Keyhotee until the blockchain is initialized.

I'm going to look into a possible method for notifying anyone who might be experiencing this problem today, and I'll report back with more details late tonight or tomorrow.

I also have the issue of showing as "unregistered". Can you have a check for me? Thanks. My public key is "5yQRwuHnu9iRF4NuzvcDaDwgZch74EVT6X8b4pfecrwbnnMTLF" and the founder id should be "john".

Quote from: dannotestein on February 17, 2014, 07:48:30 PM

Quote from: JustHayden on February 17, 2014, 07:38:33 PM
Where those points are it says "Unregistered" on mine. But it still says "Keyhotee Founder" beside it.

The Keyhotee Founder message is not meaningful in this case, it just means you "mined" your name locally in a temporary blockchain, probably using one of the early betas before identity mining was disabled.

The important thing is the points message, which apparently is not showing properly on your client. On the founder server, I see JustHayden has been registered with a public key like this: 6ked...V6Bb.  Does that match the public key shown in your KH client?

Also, are you using the 0.5.3 alpha client?
If possible, please reply to me via dan at syncad.com to speed my replies.

Quote from: dannotestein on February 20, 2014, 04:58:33 AM
I've updated the founder server with the latest submissions from the web form. If you submitted a public key for your Founder ID via the web form in the past two days, you can now check your contact info inside Keyhotee to see if your public key submission was accepted by the system (your identity will show points beside the name if it was accepted).

+1

I've updated the founder server with the latest submissions from the web form. If you submitted a public key for your Founder ID via the web form in the past two days, you can now check your contact info inside Keyhotee to see if your public key submission was accepted by the system (your identity will show points beside the name if it was accepted).

Quote from: dannotestein on February 17, 2014, 05:25:34 AM
This point display is actually just a temporary one we're using to let people know their KH Founder ID is registered with our name server, so there's no point to buying more at this point. It's unrelated to the reputation system that will be used once the blockchain is launched.

+5%

Quote from: dannotestein on February 19, 2014, 04:10:21 AM
Today I took a break from writing code in order to analyze the existing code for creating keys inside keyhotee and document it on the wiki, and I found one possible snag in regeneration of the keys generated for exchanges between authorized users (regeneration would be useful in the case of having to recreate a lost profile), but I think I have a reasonable solution to the problem, just waiting for Bytemaster to double-check my idea.

New Keyhotee FounderID submissions continue to trickle in from the web form, and I plan to update the server tomorrow night with the latest submissions.

Thank you very much for your updates. I really appreciate these updates on your work. Looking forward to it!