Author Topic: Keyhotee Status Update  (Read 157008 times)

0 Members and 1 Guest are viewing this topic.

Offline kmtan

  • Full Member
  • ***
  • Posts: 55
    • View Profile
Re: Keyhotee Status Update
« Reply #285 on: February 22, 2014, 07:27:30 pm »
Hi Dan,

ver5.5 show the both  my ID is registered with point. look great..

another problem i found is when compose a email i select to another ID but it seem it will send back the email to myself..do you have this problem?

Online dannotestein

  • Moderator
  • Hero Member
  • *****
  • Posts: 758
    • View Profile
    • BlockTrades International
  • BitShares: btsnow
Re: Keyhotee Status Update
« Reply #286 on: February 22, 2014, 07:33:15 pm »
Hi Dan,

ver5.5 show the both  my ID is registered with point. look great..

another problem i found is when compose a email i select to another ID but it seem it will send back the email to myself..do you have this problem?
I just made  a quick test and it seemed to work for me, but I just sent to one of my other identities. You can send to me and let's see if I get it: 5MqnjndmGZTVnteKPZbr5noMspHXEJBpntYYzwhuTzeRDUAXaL
You may need to create a contact with this public key first, I'm not sure if sending to anonymous keys is supported without an associated contact record yet (I've got this on my list of things to check).
http://blocktrades.us Fast/Safe/High-Liquidity Crypto Coin Converter

Offline CalabiYau

Re: Keyhotee Status Update
« Reply #287 on: February 22, 2014, 08:36:50 pm »
Thank you for the quick fix, registration is working now like a charm.
Msg sent.

Offline jae208

  • Hero Member
  • *****
  • Posts: 525
    • View Profile
Re: Keyhotee Status Update
« Reply #288 on: February 23, 2014, 10:39:11 am »
I downloaded the latest version of Keyhotee and now it says that I am unregistered
and that I have no points. My Keyhotee ID is Godfather and my public key is 81TRY6hzUMS8rGmkWeALpg17fYjeTY7ePbFqkMNG1cukYvmzzc
http://bitsharestutorials.com A work in progress
Subscribe to the Youtube Channel
https://www.youtube.com/user/BitsharesTutorials

Offline Ykw

  • Full Member
  • ***
  • Posts: 88
    • View Profile
Re: Keyhotee Status Update
« Reply #289 on: February 23, 2014, 01:00:05 pm »
All ok with 0.5.5.

Online dannotestein

  • Moderator
  • Hero Member
  • *****
  • Posts: 758
    • View Profile
    • BlockTrades International
  • BitShares: btsnow
Re: Keyhotee Status Update
« Reply #290 on: February 23, 2014, 03:17:57 pm »
I downloaded the latest version of Keyhotee and now it says that I am unregistered
and that I have no points. My Keyhotee ID is Godfather and my public key is 81TRY6hzUMS8rGmkWeALpg17fYjeTY7ePbFqkMNG1cukYvmzzc
Do you have 0.5.4 or 0.5.5? I checked the server and that's the key registered for GODFATHER. But there was a bug in 0.5.4 related to point reporting, so be sure you have 0.5.5.
http://blocktrades.us Fast/Safe/High-Liquidity Crypto Coin Converter

Offline Ykw

  • Full Member
  • ***
  • Posts: 88
    • View Profile
Re: Keyhotee Status Update
« Reply #291 on: February 23, 2014, 04:21:38 pm »
I was also able to recreate everything over a newly installed OS... with 0.5.5. Same pub... same points... looks good.

Online dannotestein

  • Moderator
  • Hero Member
  • *****
  • Posts: 758
    • View Profile
    • BlockTrades International
  • BitShares: btsnow
Re: Keyhotee Status Update
« Reply #292 on: February 23, 2014, 04:25:27 pm »
I was also able to recreate everything over a newly installed OS... with 0.5.5. Same pub... same points... looks good.
Thanks, it's important for us to know when things are working correctly as well as when they aren't!
http://blocktrades.us Fast/Safe/High-Liquidity Crypto Coin Converter

Offline cass

  • Hero Member
  • *****
  • Posts: 4311
  • /(┬.┬)\
    • View Profile
Re: Keyhotee Status Update
« Reply #293 on: February 23, 2014, 04:43:59 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

hi dannotestein, is that MAC version available?

guess it's in progress ... but don't exactly knowing wheter it's the version you mentioned or not

Here are two pull requests that fix compilation on mac os:

https://github.com/InvictusInnovations/fc/pull/13
https://github.com/InvictusInnovations/keyhotee/pull/299

after that, you can follow the instructions in this file to compile keyhotee

https://github.com/InvictusInnovations/keyhotee/blob/master/bootstrap_mac_dmg.sh

It is recommended to run in a new virtual machine, as it allows to have a clean environment, without any conflicts between system/macports/brew/... (which unfortunately happen often on mac)

Here's a compiled version of keyhotee (as of the version in the pull request): https://www.dropbox.com/s/ngq8c9hsbypxsvv/Keyhotee.dmg
█║▌║║█  - - -  The quieter you become, the more you are able to hear  - - -  █║▌║║█

Offline zhangweis

  • Sr. Member
  • ****
  • Posts: 304
    • View Profile
Re: Keyhotee Status Update
« Reply #294 on: February 23, 2014, 04:55:29 pm »
Hi Dan,
0.5.5 works for me too. Thanks for the update.
Weibo:http://weibo.com/zhangweis

Offline gulu

  • Full Member
  • ***
  • Posts: 121
    • View Profile
Re: Keyhotee Status Update
« Reply #295 on: February 24, 2014, 05:29:14 am »
I registered my found ID with MAC client. Now I use the windows to see if it's indeed registered. And I see the points, which suggests it is.

I used same ID and same brainwallet phrase, but got a different public ID. Exact same input, different public ID. Can someone tell why? Or it is the way is.
BTC: 1FRsgcQELHKFY2VMFosBnyBaNxZgS4wj7x
PTS: Pf9yDYUknXShepu6YjwSEpMvm1ewNQLNgE
BTSX: gulu

Offline coolspeed

  • Hero Member
  • *****
  • Posts: 536
    • View Profile
    • My Blog
Re: Keyhotee Status Update
« Reply #296 on: February 24, 2014, 07:05:26 am »
I registered my found ID with MAC client. Now I use the windows to see if it's indeed registered. And I see the points, which suggests it is.

I used same ID and same brainwallet phrase, but got a different public ID. Exact same input, different public ID. Can someone tell why? Or it is the way is.

No, they should be the same.
The probable reasons:
1. ID IS character sensitive, WHEN you create your key pair. Because the private key is the hash of all you inputed.
2. The order of name, middle name, family name. It's very probable to take it wrong for Asian people. I myself once took it wrong, for example.

Basically, if you can't regenerate your key pair from memory only, you need to make a new pair of keys and redo the registration.
Please vote for  delegate.coolspeed    dac.coolspeed
BTS account: coolspeed
Sina Weibo:@coolspeed

Offline gulu

  • Full Member
  • ***
  • Posts: 121
    • View Profile
Re: Keyhotee Status Update
« Reply #297 on: February 24, 2014, 07:16:34 am »
I registered my found ID with MAC client. Now I use the windows to see if it's indeed registered. And I see the points, which suggests it is.

I used same ID and same brainwallet phrase, but got a different public ID. Exact same input, different public ID. Can someone tell why? Or it is the way is.

No, they should be the same.
The probable reasons:
1. ID IS character sensitive, WHEN you create your key pair. Because the private key is the hash of all you inputed.
2. The order of name, middle name, family name. It's very probable to take it wrong for Asian people. I myself once took it wrong, for example.

Basically, if you can't regenerate your key pair from memory only, you need to make a new pair of keys and redo the registration.
Thanks a lot. That's my thoughts too. But I took a photo of the input information. Can't be wrong. Yeah, I need to play around, I guess.
BTC: 1FRsgcQELHKFY2VMFosBnyBaNxZgS4wj7x
PTS: Pf9yDYUknXShepu6YjwSEpMvm1ewNQLNgE
BTSX: gulu

Offline coolspeed

  • Hero Member
  • *****
  • Posts: 536
    • View Profile
    • My Blog
Re: Keyhotee Status Update
« Reply #298 on: February 24, 2014, 08:44:55 am »
I registered my found ID with MAC client. Now I use the windows to see if it's indeed registered. And I see the points, which suggests it is.

I used same ID and same brainwallet phrase, but got a different public ID. Exact same input, different public ID. Can someone tell why? Or it is the way is.

No, they should be the same.
The probable reasons:
1. ID IS character sensitive, WHEN you create your key pair. Because the private key is the hash of all you inputed.
2. The order of name, middle name, family name. It's very probable to take it wrong for Asian people. I myself once took it wrong, for example.

Basically, if you can't regenerate your key pair from memory only, you need to make a new pair of keys and redo the registration.
Thanks a lot. That's my thoughts too. But I took a photo of the input information. Can't be wrong. Yeah, I need to play around, I guess.

Or it can be a bug relative to OS platform, though it is supposed to be cross-platform.
I suggest you to register on windows, cuz the registration is of the highest priority and keyhotee still buggy now. At least windows version is supported best as for now.
Please vote for  delegate.coolspeed    dac.coolspeed
BTS account: coolspeed
Sina Weibo:@coolspeed

Online dannotestein

  • Moderator
  • Hero Member
  • *****
  • Posts: 758
    • View Profile
    • BlockTrades International
  • BitShares: btsnow
Re: Keyhotee Status Update
« Reply #299 on: February 25, 2014, 03:08:56 am »
I registered my found ID with MAC client. Now I use the windows to see if it's indeed registered. And I see the points, which suggests it is.

I used same ID and same brainwallet phrase, but got a different public ID. Exact same input, different public ID. Can someone tell why? Or it is the way is.

No, they should be the same.
The probable reasons:
1. ID IS character sensitive, WHEN you create your key pair. Because the private key is the hash of all you inputed.
2. The order of name, middle name, family name. It's very probable to take it wrong for Asian people. I myself once took it wrong, for example.

Basically, if you can't regenerate your key pair from memory only, you need to make a new pair of keys and redo the registration.
Thanks a lot. That's my thoughts too. But I took a photo of the input information. Can't be wrong. Yeah, I need to play around, I guess.

Or it can be a bug relative to OS platform, though it is supposed to be cross-platform.
I suggest you to register on windows, cuz the registration is of the highest priority and keyhotee still buggy now. At least windows version is supported best as for now.
We did a test today to check profile creation across Windows and Linux, and it generated the same public key in our test. Still, if any problems are encountered, I agree that using Windows is probably safest choice.
http://blocktrades.us Fast/Safe/High-Liquidity Crypto Coin Converter