Author Topic: Keyhotee Status Update  (Read 184021 times)

0 Members and 1 Guest are viewing this topic.

Offline 麥可貓

  • Sr. Member
  • ****
  • Posts: 267
    • View Profile
Re: Keyhotee Status Update
« Reply #525 on: July 25, 2014, 01:42:02 pm »
Hello,  I have problems registering my founder IDs recently.
I could register them before using the folloing information with passwords and founder codes (they are recorded in keepass, so I think they are correct) before:

founder ID: jimewu
pubkey: 8feWmErUhkgxD8QnFpi1tixYvnDrZwjddDhHADFHm9zFv2mz7Q

founder ID: Apple
pubkey: 82zW4ESP6xiazQH4FueXovBMbqUBMzYBhh9QZD3gy1K71nF2z1

but now in the latest version, the founder IDs and pubkeys don't match with founder code.
Can someone please help?
What version did you register with? We sent out an announcement quite a while ago (been long enough I don't remember when even) to re-register with a later version when we changed the algorithm for calculating the public keys, possibly this could be the problem.


for "jimewu", I'm pretty sure that I had re-registered using Keyhotee0.7.0 Linux version.
the pubkey of pre-0.7.0 was 8ZC9yw9XSB1WyQqpVRphEa27VQz1uE6okjhdvzeDYu1uvpGQtK,
and in 0.7.0 I got 8feWmErUhkgxD8QnFpi1tixYvnDrZwjddDhHADFHm9zFv2mz7Q.
but both these two pubkeys doesn't match now.

for "Apple", I think it could be pre-0.7.0.
PTS: PmRVDPymZqSAZEXauHZSewrUrE66af7epT
BTSX: michaelcat
Delegate Team: x1.sun  x2.sun

Offline dannotestein

  • Moderator
  • Hero Member
  • *****
  • Posts: 760
    • View Profile
    • BlockTrades International
  • BitShares: btsnow
Re: Keyhotee Status Update
« Reply #526 on: July 25, 2014, 01:48:06 pm »
Hello,  I have problems registering my founder IDs recently.
I could register them before using the folloing information with passwords and founder codes (they are recorded in keepass, so I think they are correct) before:

founder ID: jimewu
pubkey: 8feWmErUhkgxD8QnFpi1tixYvnDrZwjddDhHADFHm9zFv2mz7Q

founder ID: Apple
pubkey: 82zW4ESP6xiazQH4FueXovBMbqUBMzYBhh9QZD3gy1K71nF2z1

but now in the latest version, the founder IDs and pubkeys don't match with founder code.
Can someone please help?
What version did you register with? We sent out an announcement quite a while ago (been long enough I don't remember when even) to re-register with a later version when we changed the algorithm for calculating the public keys, possibly this could be the problem.


for "jimewu", I'm pretty sure that I had re-registered using Keyhotee0.7.0 Linux version.
the pubkey of pre-0.7.0 was 8ZC9yw9XSB1WyQqpVRphEa27VQz1uE6okjhdvzeDYu1uvpGQtK,
and in 0.7.0 I got 8feWmErUhkgxD8QnFpi1tixYvnDrZwjddDhHADFHm9zFv2mz7Q.
but both these two pubkeys doesn't match now.

for "Apple", I think it could be pre-0.7.0.
Ok, be sure you are using the same capitalization for all the information you entered in your profile for the one you registered with 0.7.0. That's a common problem. But, I can't think of any other reason for a problem, there's been no changes to name registration since 0.7.0.
http://blocktrades.us Fast/Safe/High-Liquidity Crypto Coin Converter

Offline 麥可貓

  • Sr. Member
  • ****
  • Posts: 267
    • View Profile
Re: Keyhotee Status Update
« Reply #527 on: July 25, 2014, 02:21:01 pm »
Hello,  I have problems registering my founder IDs recently.
I could register them before using the folloing information with passwords and founder codes (they are recorded in keepass, so I think they are correct) before:

founder ID: jimewu
pubkey: 8feWmErUhkgxD8QnFpi1tixYvnDrZwjddDhHADFHm9zFv2mz7Q

founder ID: Apple
pubkey: 82zW4ESP6xiazQH4FueXovBMbqUBMzYBhh9QZD3gy1K71nF2z1

but now in the latest version, the founder IDs and pubkeys don't match with founder code.
Can someone please help?
What version did you register with? We sent out an announcement quite a while ago (been long enough I don't remember when even) to re-register with a later version when we changed the algorithm for calculating the public keys, possibly this could be the problem.


for "jimewu", I'm pretty sure that I had re-registered using Keyhotee0.7.0 Linux version.
the pubkey of pre-0.7.0 was 8ZC9yw9XSB1WyQqpVRphEa27VQz1uE6okjhdvzeDYu1uvpGQtK,
and in 0.7.0 I got 8feWmErUhkgxD8QnFpi1tixYvnDrZwjddDhHADFHm9zFv2mz7Q.
but both these two pubkeys doesn't match now.

for "Apple", I think it could be pre-0.7.0.
Ok, be sure you are using the same capitalization for all the information you entered in your profile for the one you registered with 0.7.0. That's a common problem. But, I can't think of any other reason for a problem, there's been no changes to name registration since 0.7.0.

Sorry that I've tried all possible combinations, but they don't work.
Is there any solution for this kind of situation? Or should I just give up?
PTS: PmRVDPymZqSAZEXauHZSewrUrE66af7epT
BTSX: michaelcat
Delegate Team: x1.sun  x2.sun

Offline dannotestein

  • Moderator
  • Hero Member
  • *****
  • Posts: 760
    • View Profile
    • BlockTrades International
  • BitShares: btsnow
Re: Keyhotee Status Update
« Reply #528 on: July 25, 2014, 02:24:56 pm »
Hello,  I have problems registering my founder IDs recently.
I could register them before using the folloing information with passwords and founder codes (they are recorded in keepass, so I think they are correct) before:

founder ID: jimewu
pubkey: 8feWmErUhkgxD8QnFpi1tixYvnDrZwjddDhHADFHm9zFv2mz7Q

founder ID: Apple
pubkey: 82zW4ESP6xiazQH4FueXovBMbqUBMzYBhh9QZD3gy1K71nF2z1

but now in the latest version, the founder IDs and pubkeys don't match with founder code.
Can someone please help?
What version did you register with? We sent out an announcement quite a while ago (been long enough I don't remember when even) to re-register with a later version when we changed the algorithm for calculating the public keys, possibly this could be the problem.


for "jimewu", I'm pretty sure that I had re-registered using Keyhotee0.7.0 Linux version.
the pubkey of pre-0.7.0 was 8ZC9yw9XSB1WyQqpVRphEa27VQz1uE6okjhdvzeDYu1uvpGQtK,
and in 0.7.0 I got 8feWmErUhkgxD8QnFpi1tixYvnDrZwjddDhHADFHm9zFv2mz7Q.
but both these two pubkeys doesn't match now.

for "Apple", I think it could be pre-0.7.0.
Ok, be sure you are using the same capitalization for all the information you entered in your profile for the one you registered with 0.7.0. That's a common problem. But, I can't think of any other reason for a problem, there's been no changes to name registration since 0.7.0.

Sorry that I've tried all possible combinations, but they don't work.
Is there any solution for this kind of situation? Or should I just give up?
What version are you using now? Are you using the last official "release" version (links at beginning of this thread to 0.7.100) or are you using something built from repo?
http://blocktrades.us Fast/Safe/High-Liquidity Crypto Coin Converter

Offline dannotestein

  • Moderator
  • Hero Member
  • *****
  • Posts: 760
    • View Profile
    • BlockTrades International
  • BitShares: btsnow
Re: Keyhotee Status Update
« Reply #529 on: July 25, 2014, 02:37:41 pm »
Sorry that I've tried all possible combinations, but they don't work.
Is there any solution for this kind of situation? Or should I just give up?

I just went thru the founder server logs and if I'm interpreting things correctly, it looks you originally used the correct capitalization, but that you had the wrong Founder code entered. Is the email address you used when you initially got your Keyhotee ID unchanged? If so, I can resend you your founder code.
http://blocktrades.us Fast/Safe/High-Liquidity Crypto Coin Converter

Offline 麥可貓

  • Sr. Member
  • ****
  • Posts: 267
    • View Profile
Re: Keyhotee Status Update
« Reply #530 on: July 25, 2014, 02:38:13 pm »
What version are you using now? Are you using the last official "release" version (links at beginning of this thread to 0.7.100) or are you using something built from repo?

I tried with 0.7.0 on linux from the status update:
https://bitsharestalk.org/index.php?topic=1433.msg50002#msg50002

and I also tried the latest windows version from the folloing link:
http://178.63.85.22/dl/Keyhotee/Windows/2014-07-24_00-50-01/Keyhotee-0.7.230-win32.exe
PTS: PmRVDPymZqSAZEXauHZSewrUrE66af7epT
BTSX: michaelcat
Delegate Team: x1.sun  x2.sun

Offline 麥可貓

  • Sr. Member
  • ****
  • Posts: 267
    • View Profile
Re: Keyhotee Status Update
« Reply #531 on: July 25, 2014, 02:44:46 pm »
Sorry that I've tried all possible combinations, but they don't work.
Is there any solution for this kind of situation? Or should I just give up?

I just went thru the founder server logs and if I'm interpreting things correctly, it looks you originally used the correct capitalization, but that you had the wrong Founder code entered. Is the email address you used when you initially got your Keyhotee ID unchanged? If so, I can resend you your founder code.

These two founder IDs, namely "jimewu" and "Apple", were registered by two different email addresses.
Please re-send founder code to their original email addresses, and I wish this can work out.
Thank you.
PTS: PmRVDPymZqSAZEXauHZSewrUrE66af7epT
BTSX: michaelcat
Delegate Team: x1.sun  x2.sun

Offline yidaidaxia

  • Full Member
  • ***
  • Posts: 179
    • View Profile
Re: Keyhotee Status Update
« Reply #532 on: July 25, 2014, 03:00:29 pm »
Help!

I'm a Keyhotee founder ID user and I'm sure that I registered it suscessfully with 0.7 version. Actually, my founder ID is "Mike HAO" which is listed in btsx genesis block acount list as "mikeh-hao".

My problem is, when I try to log in on my computer today for getting the private key to claim the ID in BTSX, I found I forget my Keyhotee login password, actually I think I remember it but anyway I tried hundreds times but failed.

So per my understanding of the mechanism of Keyhotee ID, I created a new acount w/ exactly same register profile info and brain key so that I believe I could re-generate my acount to get the into it and get the private key for BTSX. I think I succeed to get my acount re-generated since when I create a "new identity" w/ "Mike HAO", system remind me that I've created a similar ID before.. I notice that, both of mail network and btsx network status in right bottom concern of the client is both "disconnected". So maybe that's why my "Mike HAO" ID not shows in the client now...?

So in summary, my question is:

1. As I described above, did I re-generated my acount sucessfully? If not, how can I do?
2. If yes to first quesion, no ID in the re-generated account now is due to no network? If no, then why no ID in the list?
3. If yes to second question, when could we have the newwork available then I could access to my "Mike HAO" ID and get the private key for BTSX...

BTW, at that time, I posted my public key "5cU7QvmB7ZLxcVjm1bwmvSmgZxduqZGFBgMDh8TPhkdYMnjSgS" here and you confirmed it recorded, which is true because it's in BTSX genesis block now. And I'm using the last release windows verions(0.7.230-win32) now.

Appreciated if you could look it and provide me your advice..

Thanks a lot.
« Last Edit: July 25, 2014, 03:02:26 pm by yidaidaxia »
PTS: PmUT7H6e7Hvp9WtKtxphK8AMeRndnow2S8   /   BTC: 1KsJzs8zYppVHBp7CbyvQAYrEAWXEcNvmp   /   BTSX: yidaidaxia (暂用)
新浪微博: yidaidaxia_郝晓曦 QQ:36191175试手补天

Offline dannotestein

  • Moderator
  • Hero Member
  • *****
  • Posts: 760
    • View Profile
    • BlockTrades International
  • BitShares: btsnow
Re: Keyhotee Status Update
« Reply #533 on: July 25, 2014, 04:08:24 pm »
Help!

I'm a Keyhotee founder ID user and I'm sure that I registered it suscessfully with 0.7 version. Actually, my founder ID is "Mike HAO" which is listed in btsx genesis block acount list as "mikeh-hao".

My problem is, when I try to log in on my computer today for getting the private key to claim the ID in BTSX, I found I forget my Keyhotee login password, actually I think I remember it but anyway I tried hundreds times but failed.

So per my understanding of the mechanism of Keyhotee ID, I created a new acount w/ exactly same register profile info and brain key so that I believe I could re-generate my acount to get the into it and get the private key for BTSX. I think I succeed to get my acount re-generated since when I create a "new identity" w/ "Mike HAO", system remind me that I've created a similar ID before.. I notice that, both of mail network and btsx network status in right bottom concern of the client is both "disconnected". So maybe that's why my "Mike HAO" ID not shows in the client now...?

So in summary, my question is:

1. As I described above, did I re-generated my acount sucessfully? If not, how can I do?
2. If yes to first quesion, no ID in the re-generated account now is due to no network? If no, then why no ID in the list?
3. If yes to second question, when could we have the newwork available then I could access to my "Mike HAO" ID and get the private key for BTSX...

BTW, at that time, I posted my public key "5cU7QvmB7ZLxcVjm1bwmvSmgZxduqZGFBgMDh8TPhkdYMnjSgS" here and you confirmed it recorded, which is true because it's in BTSX genesis block now. And I'm using the last release windows verions(0.7.230-win32) now.

Appreciated if you could look it and provide me your advice..

Thanks a lot.
1) It sounds like you successfully regenerated your key. If the public key you got matches your old one, then you have regenerated your key sucessfully.
2) it's quite possible the mail server for KH is down right now, I've not been involved with mail server handling for a few months now. I logged on to the server just now, and it "appears" to not be running for some reason, don't know why.
3) You don't need the mail server to access your private key. Your private key is stored in your Keyhotee client itself along with your public key. You just need to export this key to your bitshares client. I haven't done this yet myself, but the procedure for it is here:
http://wiki.bitshares.org/index.php/BitShares_X_Solutions#How_to_import_Keyhotee_IDs
http://blocktrades.us Fast/Safe/High-Liquidity Crypto Coin Converter

Offline yidaidaxia

  • Full Member
  • ***
  • Posts: 179
    • View Profile
Re: Keyhotee Status Update
« Reply #534 on: July 25, 2014, 04:27:38 pm »
Help!

I'm a Keyhotee founder ID user and I'm sure that I registered it suscessfully with 0.7 version. Actually, my founder ID is "Mike HAO" which is listed in btsx genesis block acount list as "mikeh-hao".

My problem is, when I try to log in on my computer today for getting the private key to claim the ID in BTSX, I found I forget my Keyhotee login password, actually I think I remember it but anyway I tried hundreds times but failed.

So per my understanding of the mechanism of Keyhotee ID, I created a new acount w/ exactly same register profile info and brain key so that I believe I could re-generate my acount to get the into it and get the private key for BTSX. I think I succeed to get my acount re-generated since when I create a "new identity" w/ "Mike HAO", system remind me that I've created a similar ID before.. I notice that, both of mail network and btsx network status in right bottom concern of the client is both "disconnected". So maybe that's why my "Mike HAO" ID not shows in the client now...?

So in summary, my question is:

1. As I described above, did I re-generated my acount sucessfully? If not, how can I do?
2. If yes to first quesion, no ID in the re-generated account now is due to no network? If no, then why no ID in the list?
3. If yes to second question, when could we have the newwork available then I could access to my "Mike HAO" ID and get the private key for BTSX...

BTW, at that time, I posted my public key "5cU7QvmB7ZLxcVjm1bwmvSmgZxduqZGFBgMDh8TPhkdYMnjSgS" here and you confirmed it recorded, which is true because it's in BTSX genesis block now. And I'm using the last release windows verions(0.7.230-win32) now.

Appreciated if you could look it and provide me your advice..

Thanks a lot.
1) It sounds like you successfully regenerated your key. If the public key you got matches your old one, then you have regenerated your key sucessfully.
2) it's quite possible the mail server for KH is down right now, I've not been involved with mail server handling for a few months now. I logged on to the server just now, and it "appears" to not be running for some reason, don't know why.
3) You don't need the mail server to access your private key. Your private key is stored in your Keyhotee client itself along with your public key. You just need to export this key to your bitshares client. I haven't done this yet myself, but the procedure for it is here:
http://wiki.bitshares.org/index.php/BitShares_X_Solutions#How_to_import_Keyhotee_IDs

Thanks for quick response.

1. The new public key does not match the old one. But the client remind me that I've registered this ID(Mike HAO), and does not allow me to "save" it. The new public key is "76UX9KAnd4Au6d6EDqRSKQQjsLBDqvk8j6UpjaswatEreSVkMb", while the old one is "5cU7QvmB7ZLxcVjm1bwmvSmgZxduqZGFBgMDh8TPhkdYMnjSgS". I still think I've succeeded to re-generate mu account, otherwise how system could identify I(my acount) already had ID "Mike HAO" when the client not being sync to the newwork.

2. I know the process to claim my ID on BTSX, but I could not access to ID "Mike HAO" now, since there is no ID in my new re-generated account and I could not re-create "Mike HAO" in this account due to system identify it's as duplicated... and no private key could be exported...

Any further advice...? Thanks.
PTS: PmUT7H6e7Hvp9WtKtxphK8AMeRndnow2S8   /   BTC: 1KsJzs8zYppVHBp7CbyvQAYrEAWXEcNvmp   /   BTSX: yidaidaxia (暂用)
新浪微博: yidaidaxia_郝晓曦 QQ:36191175试手补天

Offline 麥可貓

  • Sr. Member
  • ****
  • Posts: 267
    • View Profile
Re: Keyhotee Status Update
« Reply #535 on: July 25, 2014, 05:02:08 pm »
Sorry that I've tried all possible combinations, but they don't work.
Is there any solution for this kind of situation? Or should I just give up?

I just went thru the founder server logs and if I'm interpreting things correctly, it looks you originally used the correct capitalization, but that you had the wrong Founder code entered. Is the email address you used when you initially got your Keyhotee ID unchanged? If so, I can resend you your founder code.


Hello,
It turns out the founder codes you sent are the same with what I have now.
I think the difference should be the pubkey.
the pubkey of "jimewu" when I try to register now is "7SFLVfajtLFRPn4DKax8DxgxzupumUZ54dP48xDs2g449J2f9D",
but it was "8ZC9yw9XSB1WyQqpVRphEa27VQz1uE6okjhdvzeDYu1uvpGQtK" in pre-0.7.0,
and "8feWmErUhkgxD8QnFpi1tixYvnDrZwjddDhHADFHm9zFv2mz7Q".

The sitution of another ID "Apple" is the same.

Also I found no matter what password I choose, the pubkey of "jimewu" always returns "7SFLVfajtLFRPn4DKax8DxgxzupumUZ54dP48xDs2g449J2f9D", rather than "8feWmErUhkgxD8QnFpi1tixYvnDrZwjddDhHADFHm9zFv2mz7Q" I recorded.
Shouldn't them be correlated?

Anything else I could do?
Thank you
PTS: PmRVDPymZqSAZEXauHZSewrUrE66af7epT
BTSX: michaelcat
Delegate Team: x1.sun  x2.sun

Offline dannotestein

  • Moderator
  • Hero Member
  • *****
  • Posts: 760
    • View Profile
    • BlockTrades International
  • BitShares: btsnow
Re: Keyhotee Status Update
« Reply #536 on: July 25, 2014, 06:08:01 pm »
Sorry that I've tried all possible combinations, but they don't work.
Is there any solution for this kind of situation? Or should I just give up?

I just went thru the founder server logs and if I'm interpreting things correctly, it looks you originally used the correct capitalization, but that you had the wrong Founder code entered. Is the email address you used when you initially got your Keyhotee ID unchanged? If so, I can resend you your founder code.


Hello,
It turns out the founder codes you sent are the same with what I have now.
I think the difference should be the pubkey.
the pubkey of "jimewu" when I try to register now is "7SFLVfajtLFRPn4DKax8DxgxzupumUZ54dP48xDs2g449J2f9D",
but it was "8ZC9yw9XSB1WyQqpVRphEa27VQz1uE6okjhdvzeDYu1uvpGQtK" in pre-0.7.0,
and "8feWmErUhkgxD8QnFpi1tixYvnDrZwjddDhHADFHm9zFv2mz7Q".

The sitution of another ID "Apple" is the same.

Also I found no matter what password I choose, the pubkey of "jimewu" always returns "7SFLVfajtLFRPn4DKax8DxgxzupumUZ54dP48xDs2g449J2f9D", rather than "8feWmErUhkgxD8QnFpi1tixYvnDrZwjddDhHADFHm9zFv2mz7Q" I recorded.
Shouldn't them be correlated?

Anything else I could do?
Thank you
If you're getting a different public key, it means you're not entering the same profile info. The public key generated is a function of your keyhoteeId, first name, middle name, last name, and brainwallet key.
http://blocktrades.us Fast/Safe/High-Liquidity Crypto Coin Converter

Offline dannotestein

  • Moderator
  • Hero Member
  • *****
  • Posts: 760
    • View Profile
    • BlockTrades International
  • BitShares: btsnow
Re: Keyhotee Status Update
« Reply #537 on: July 25, 2014, 06:10:01 pm »
Help!

I'm a Keyhotee founder ID user and I'm sure that I registered it suscessfully with 0.7 version. Actually, my founder ID is "Mike HAO" which is listed in btsx genesis block acount list as "mikeh-hao".

My problem is, when I try to log in on my computer today for getting the private key to claim the ID in BTSX, I found I forget my Keyhotee login password, actually I think I remember it but anyway I tried hundreds times but failed.

So per my understanding of the mechanism of Keyhotee ID, I created a new acount w/ exactly same register profile info and brain key so that I believe I could re-generate my acount to get the into it and get the private key for BTSX. I think I succeed to get my acount re-generated since when I create a "new identity" w/ "Mike HAO", system remind me that I've created a similar ID before.. I notice that, both of mail network and btsx network status in right bottom concern of the client is both "disconnected". So maybe that's why my "Mike HAO" ID not shows in the client now...?

So in summary, my question is:

1. As I described above, did I re-generated my acount sucessfully? If not, how can I do?
2. If yes to first quesion, no ID in the re-generated account now is due to no network? If no, then why no ID in the list?
3. If yes to second question, when could we have the newwork available then I could access to my "Mike HAO" ID and get the private key for BTSX...

BTW, at that time, I posted my public key "5cU7QvmB7ZLxcVjm1bwmvSmgZxduqZGFBgMDh8TPhkdYMnjSgS" here and you confirmed it recorded, which is true because it's in BTSX genesis block now. And I'm using the last release windows verions(0.7.230-win32) now.

Appreciated if you could look it and provide me your advice..

Thanks a lot.
1) It sounds like you successfully regenerated your key. If the public key you got matches your old one, then you have regenerated your key sucessfully.
2) it's quite possible the mail server for KH is down right now, I've not been involved with mail server handling for a few months now. I logged on to the server just now, and it "appears" to not be running for some reason, don't know why.
3) You don't need the mail server to access your private key. Your private key is stored in your Keyhotee client itself along with your public key. You just need to export this key to your bitshares client. I haven't done this yet myself, but the procedure for it is here:
http://wiki.bitshares.org/index.php/BitShares_X_Solutions#How_to_import_Keyhotee_IDs

Thanks for quick response.

1. The new public key does not match the old one. But the client remind me that I've registered this ID(Mike HAO), and does not allow me to "save" it. The new public key is "76UX9KAnd4Au6d6EDqRSKQQjsLBDqvk8j6UpjaswatEreSVkMb", while the old one is "5cU7QvmB7ZLxcVjm1bwmvSmgZxduqZGFBgMDh8TPhkdYMnjSgS". I still think I've succeeded to re-generate mu account, otherwise how system could identify I(my acount) already had ID "Mike HAO" when the client not being sync to the newwork.

2. I know the process to claim my ID on BTSX, but I could not access to ID "Mike HAO" now, since there is no ID in my new re-generated account and I could not re-create "Mike HAO" in this account due to system identify it's as duplicated... and no private key could be exported...

Any further advice...? Thanks.
If you're getting a different public key, you haven't successfully regenerated your account. To get the correct public key regenerated, you need the exact profile data previously entered (and the exact same KeyhoteeId).
http://blocktrades.us Fast/Safe/High-Liquidity Crypto Coin Converter

bitbro

  • Guest
Re: Keyhotee Status Update
« Reply #538 on: July 25, 2014, 06:31:06 pm »
What is the general status of keyhotee atm? Can you also update us to any revised visions of the product?  And offer a timeline for production?


Sent from my iPhone using Tapatalk

Offline James212

  • Sr. Member
  • ****
  • Posts: 312
    • View Profile
Re: Keyhotee Status Update
« Reply #539 on: July 26, 2014, 01:53:54 am »
Dan, what is the status on the updated working version of Keyhote 7.0 for OSX?  I am still waiting on a working version to be able to re-register my founder ID.

Thanks
BTS: theangelwaveproject