BitShares Forum

Other => Graveyard => Keyhotee => Topic started by: bytemaster on December 17, 2013, 08:27:11 am

Title: Keyhotee Status Update
Post by: bytemaster on December 17, 2013, 08:27:11 am
Update 4/2/2014: Latest Version of Keyhotee Alpha for Windows, Linux, and OSX here
ftp://178.63.85.22/Keyhotee/Windows/2014-04-27_00-00-43/Keyhotee-0.7.100-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
(OSX requires Mountain Lion or later, currently)
Important Notes:
1) Any version of Keyhotee older than this will be incompatible with the mail server (you won't be able to send/receive mail)
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.


As promised yesterday, here is my official update on the status of Keyhotee.    I took the day to evaluate the progress of Keyhotee which has been delegated to a new team just a couple of weeks ago while I was busy with other tasks (BitShares, Vegas, etc). 

Here is my conclusion:

1) Basic functionality for email / chat / Keyhotee ID mining is in place.
2) It is buggy as hell right now and I have been filing a ton of tickets for our Poland team to address.
3) Most of the bugs are of the surface level user interface annoyances that can be rapidly fixed / polished.
4) I will not be getting much sleep between now and launch, but a launch is still possible.
5) The launch will be an alpha launch rather than the more polished launch I would have liked.

Functionality that will be available at launch:
1) Create a single identity
2) Mine Keyhotee IDs
3) Basic Email and Text Messaging
4) Currently routed through our central server for testing. 

It will not be ready for anyone but those who signed up to be alpha testers.  We will move forward as rapidly as the development team can do so.

In my opinion we have slipped about one month and the release we will make on Jan 1 will be closer to what I had hoped to deliver on November 17th to Alpha testers. 

Reasons leading to the delay include: 

1) ProtoShares launch, mining frenzy, and mining pool development consumed far more of my time than I had anticipated.
2) I made estimates based upon my development skills as someone familiar with the code prior to delegating to a new team.
3) Our new team has taken some time to get up to speed and familiar with the code.

We will continue to post regular updates in as transparent a manner as possible.  It is our desire to improve upon our estimates for future releases.

For a daily update with detailed progress info about Keyhotee development, you can visit the github repo at the links below:
https://github.com/InvictusInnovations/keyhotee/commits
https://github.com/InvictusInnovations/keyhotee/issues?state=open
https://github.com/InvictusInnovations/keyhotee/issues?state=closed
Title: Re: Keyhotee Status Update
Post by: hasher on December 17, 2013, 10:19:03 am
hello,
i have paid for keyhotee 3 days ago and still didnt got response, something happened?
Title: Re: Keyhotee Status Update
Post by: HackFisher on December 17, 2013, 01:51:29 pm
Thanks for your update.
Title: Re: Keyhotee Status Update
Post by: que23 on December 17, 2013, 02:03:25 pm
Thanks, I get an email every time you do something on Github. So I know you've been busy. Wish I was a better coder so I could help. Get some sleep.
Title: Re: Keyhotee Status Update
Post by: testz on December 17, 2013, 02:06:05 pm
Thanks for update.
Title: Re: Keyhotee Status Update
Post by: cass on December 17, 2013, 02:12:17 pm
cool to see everthing is in progress - thx byte for your update and explaining why we have a delay on it... Thumbs up - i like this transparent way of communication
Title: Re: Keyhotee Status Update
Post by: cass on December 17, 2013, 02:15:23 pm
can we make this info sticky!?
Title: Re: Keyhotee Status Update
Post by: phoenix on December 17, 2013, 03:08:54 pm
cool to see everthing is in progress - thx byte for your update and explaining why we have a delay on it... Thumbs up - i like this transparent way of communication

I agree, transparency is a huge plus :)
Title: Re: Keyhotee Status Update
Post by: Lighthouse on December 17, 2013, 03:20:37 pm
Sticky'd

Thank you for the update Bytemaster
Title: Re: Keyhotee Status Update
Post by: Stan on December 17, 2013, 04:53:50 pm
hello,
i have paid for keyhotee 3 days ago and still didnt got response, something happened?

All is well.  We are processing these manually and plan to send everyone their status in one swell foop after the bidding ends on Christmas eve.  The contents of everyone's Founder address are readily visible in the block chain.

If anyone wants a transaction receipt, just reply to the email that gave you the address and I'll hand-generate one.

I apologize for the manual nature of this one-time-only promotion but we didn't want to divert any developers to automating it.

 :)
Title: Re: Keyhotee Status Update
Post by: hasher on December 17, 2013, 11:25:12 pm
hello,
i have paid for keyhotee 3 days ago and still didnt got response, something happened?

All is well.  We are processing these manually and plan to send everyone their status in one swell foop after the bidding ends on Christmas eve.  The contents of everyone's Founder address are readily visible in the block chain.

If anyone wants a transaction receipt, just reply to the email that gave you the address and I'll hand-generate one.

I apologize for the manual nature of this one-time-only promotion but we didn't want to divert any developers to automating it.

 :)
Ok, thank you Stan!
Title: Re: Keyhotee Status Update
Post by: pvaladares on December 20, 2013, 09:56:49 pm
Very nice attitude, keeping completely transparent and sharing the update status with community.
Title: Re: Keyhotee Status Update
Post by: NineLives on December 21, 2013, 02:21:13 am
Loving it..  and watching.
Title: Re: Keyhotee Status Update
Post by: Pocket Sand on December 21, 2013, 06:43:50 pm
Thanks for the update
Title: Re: Keyhotee Status Update
Post by: robozombie on December 21, 2013, 07:25:07 pm
N.I.C.E!
Title: Re: Keyhotee Status Update
Post by: spoonman on December 24, 2013, 03:54:21 pm
Is it safe to assume if we haven't heard from Stan or BM that are first choice of names is petty much safe at this point?
Title: Re: Keyhotee Status Update
Post by: bytemaster on December 24, 2013, 04:26:05 pm
Is it safe to assume if we haven't heard from Stan or BM that are first choice of names is petty much safe at this point?

We will notify about conflicts tomorrow.
Title: Re: Keyhotee Status Update
Post by: cass on December 24, 2013, 04:50:16 pm
Is it safe to assume if we haven't heard from Stan or BM that are first choice of names is petty much safe at this point?

We will notify about conflicts tomorrow.

Merry Christmas :) thx for update info
Title: Re: Keyhotee Status Update
Post by: spoonman on December 24, 2013, 05:19:49 pm
Is it safe to assume if we haven't heard from Stan or BM that are first choice of names is petty much safe at this point?

We will notify about conflicts tomorrow.

Thanks! Don't work too hard it is Christmas!
Title: Re: Keyhotee Status Update
Post by: guang384 on December 25, 2013, 02:48:13 am
Is it safe to assume if we haven't heard from Stan or BM that are first choice of names is petty much safe at this point?

We will notify about conflicts tomorrow.

Merry Christmas
Title: Re: Keyhotee Status Update
Post by: jackie on December 25, 2013, 03:22:24 pm
Merry Christmas!I want a Keyhotee ID for Christmas,i already sent PTS to bid one.
Title: Re: Keyhotee Status Update
Post by: lordcirth on December 26, 2013, 02:31:26 am
I thought the bidding closed at New Year's Eve.  Guess I should have read more carefully?  There goes my founder ID.  Oh well, I'll just have to mine one at launch.  It's not going to be as hard to mine IDs as it was to get the 10 PTS, will it?
Title: Re: Keyhotee Status Update
Post by: solaaire on December 26, 2013, 04:11:13 am
I thought the bidding closed at New Year's Eve.  Guess I should have read more carefully?  There goes my founder ID.  Oh well, I'll just have to mine one at launch.  It's not going to be as hard to mine IDs as it was to get the 10 PTS, will it?

No, it should not be nearly as hard! Obtaining a Keyhotee ID will be as simple as downloading the client and letting it run for a little while, if I understand correctly. That said, IDs created in this manner will NOT be a founder ID. However, the only difference between a regular Keyhotee ID and a Founder ID is that with a Founder ID, your name will be etched into the genesis block of Keyhotee. I think I remember someone likening it to getting your name carved in stone in front of a monumental building.
Title: Re: Keyhotee Status Update
Post by: NineLives on December 26, 2013, 01:32:55 pm
Have I won?  eh eh eh?
Title: Re: Keyhotee Status Update
Post by: bytemaster on December 26, 2013, 03:16:35 pm
There are not many conflicts so you are probably safe.  Perhaps a few dozen out of 650.   We will contact the conflicts ASAP.


Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
Title: Re: Keyhotee Status Update
Post by: dacer on December 26, 2013, 04:31:35 pm
I bid for 3 founder ids, eagerly waiting for the results :)
Title: Re: Keyhotee Status Update
Post by: bytemaster on December 27, 2013, 12:14:15 am
I would like to request that everyone waiting for a status on their Keyhotee ID to please be patient as we had an onslaught of IDs to manually process in the last 2 days.  We will be in contact with everyone and post a summary report for everyone to check prior to launching the Genesis block.

The Genesis Block will not launch on Jan 1, but we will have the Alpha release that will allow you to generate your Public Key.  The genesis block will launch as soon as we have the Public Keys.   More details will follow as soon as we have them. 

If you did not receive an email with a PTS address to fund then please check your junk folder or contact bitsharestalk user Stan.

Thanks
Title: Re: Keyhotee Status Update
Post by: cogitativecurve on December 30, 2013, 07:34:23 am
Very nice attitude, keeping completely transparent and sharing the update status with community.

+1
Title: Re: Keyhotee Status Update
Post by: Gekko on December 30, 2013, 10:37:26 am
The genesis block will launch as soon as we have the Public Keys.
What are you going to do if you do not get all public keys (e.g. somebody (founder) died in the meantime).
Will there be a deadline to send in public keys? Will there be a PTS refund (the founder in a coma gets when he wakes up again)?
What happens to the ID that did not make it into the genesis block? Will the "second best" bidder get it or will it be freely available as a "normal" ID?


Title: Re: Keyhotee Status Update
Post by: lib on December 30, 2013, 11:52:26 am
The genesis block will launch as soon as we have the Public Keys.
What are you going to do if you do not get all public keys (e.g. somebody (founder) died in the meantime).
Will there be a deadline to send in public keys? Will there be a PTS refund (the founder in a coma gets when he wakes up again)?
What happens to the ID that did not make it into the genesis block? Will the "second best" bidder get it or will it be freely available as a "normal" ID?

I guess,
1) a deadline should be set.
2) (maybe)PTS will be sent back if the founder failed to reply the public key.
Title: Re: Keyhotee Status Update
Post by: bg002h on December 30, 2013, 05:44:52 pm
has anyone replied with their public key yet?  I got an email saying I got my 1st choice, but, that's all I've done so far...I've sent nothing...

ADDENDUM: looks like I've missed nothing yet! (12/[email protected] central USA)
Title: Re: Keyhotee Status Update
Post by: Riverhead on December 30, 2013, 06:26:18 pm
has anyone replied with their public key yet?  I got an email saying I got my 1st choice, but, that's all I've done so far...I've sent nothing...

ADDENDUM: looks like I've missed nothing yet! (12/[email protected] central USA)

Same here.  I think that email was just a heads up for further communication.  The next email I expect will have a download link for software we can use to mine our chosen founder ID's.
Title: Re: Keyhotee Status Update
Post by: bytemaster on December 30, 2013, 06:31:40 pm
has anyone replied with their public key yet?  I got an email saying I got my 1st choice, but, that's all I've done so far...I've sent nothing...

ADDENDUM: looks like I've missed nothing yet! (12/[email protected] central USA)

Same here.  I think that email was just a heads up for further communication.  The next email I expect will have a download link for software we can use to mine our chosen founder ID's.

Correct.  We are working as fast as we can to make sure this next step is done right as it is the most critical. 
Title: Re: Keyhotee Status Update
Post by: bg002h on December 30, 2013, 08:06:40 pm
Rock on Dan! 
Title: Re: Keyhotee Status Update
Post by: MrJeans on December 31, 2013, 10:14:54 am
So we still all go for midnight tonight?
Title: Re: Keyhotee Status Update
Post by: bytemaster on December 31, 2013, 03:06:55 pm
So we still all go for midnight tonight?

I am working my tail off along with our entire team in Poland.   There is no genesis block tonight, but we may have the tool for registering your Keyhotee ID.   
Title: Re: Keyhotee Status Update
Post by: Riverhead on December 31, 2013, 06:52:45 pm

I obviously can't speak for everyone but for me I'd rather the delivery a few days late and working than having you guys super stressed out, sleep deprived, and rushed to meet an artificial deadline.

Best of luck on the finishing touches.  Looking forward to seeing the fruits of your labors  8).

Title: Re: Keyhotee Status Update
Post by: bytemaster on December 31, 2013, 07:18:01 pm

I obviously can't speak for everyone but for me I'd rather the delivery a few days late and working than having you guys super stressed out, sleep deprived, and rushed to meet an artificial deadline.

Best of luck on the finishing touches.  Looking forward to seeing the fruits of your labors  8).

Deadlines help move us along :)   But I agree, if I do not believe it is solid then we would rather people complain about being late than broken.  If we release something broken we waste everyone's time.... if we delay then we save peoples time.  We value your time so would rather not release something that will cause problems.
Title: Re: Keyhotee Status Update
Post by: MrJeans on January 01, 2014, 12:16:12 am

I obviously can't speak for everyone but for me I'd rather the delivery a few days late and working than having you guys super stressed out, sleep deprived, and rushed to meet an artificial deadline.

Best of luck on the finishing touches.  Looking forward to seeing the fruits of your labors  8).

Deadlines help move us along :)   But I agree, if I do not believe it is solid then we would rather people complain about being late than broken.  If we release something broken we waste everyone's time.... if we delay then we save peoples time.  We value your time so would rather not release something that will cause problems.
Yep, best of luck.
We were all rooting for you guys. and look forward to a cool product when it does launch. Happy new year
Title: Re: Keyhotee Status Update
Post by: wasthatawolf on January 01, 2014, 05:07:53 am
Happy New Year!
Title: Re: Keyhotee Status Update
Post by: bytemaster on January 01, 2014, 05:10:50 am
We have a version of Keyhotee ready that will allow Founders to register their Public Key / ID, but my Windows team is taking the New Year off so we will have to wait until they compile a binary for everyone to use.   This will be a special addition that will not have the rest of the features of mail enabled/supported. 

Title: Re: Keyhotee Status Update
Post by: spoonman on January 01, 2014, 05:20:57 am
We have a version of Keyhotee ready that will allow Founders to register their Public Key / ID, but my Windows team is taking the New Year off so we will have to wait until they compile a binary for everyone to use.   This will be a special addition that will not have the rest of the features of mail enabled/supported.

Will the special version have an osx build? I don't like have anything key related done on windows...
Title: Re: Keyhotee Status Update
Post by: bytemaster on January 01, 2014, 05:21:32 am
We have a version of Keyhotee ready that will allow Founders to register their Public Key / ID, but my Windows team is taking the New Year off so we will have to wait until they compile a binary for everyone to use.   This will be a special addition that will not have the rest of the features of mail enabled/supported.

Will the special version have an osx build? I don't like have anything key related done on windows...

Yes, I will build an OS X version.
Title: Re: Keyhotee Status Update
Post by: Troglodactyl on January 01, 2014, 05:12:48 pm
We have a version of Keyhotee ready that will allow Founders to register their Public Key / ID, but my Windows team is taking the New Year off so we will have to wait until they compile a binary for everyone to use.   This will be a special addition that will not have the rest of the features of mail enabled/supported. 



Taking the New Year off?!?   :o  So we can expect it sometime in 2015?  :P
Title: Re: Keyhotee Status Update
Post by: locustin on January 01, 2014, 07:31:14 pm
Can we get some estimate on when a actual working product will be released? Give us a date you are comfortable with so we won't miss anymore deadlines.
Title: Re: Keyhotee Status Update
Post by: bytemaster on January 01, 2014, 07:42:19 pm
Can we get some estimate on when a actual working product will be released? Give us a date you are comfortable with so we won't miss anymore deadlines.

Since I have delegated the work to Dan Notestein and his team in Poland I will ask them to make estimates and get back to you.  I do agree that I would rather under-promise and over-deliver. 
Title: Re: Keyhotee Status Update
Post by: earthbound on January 01, 2014, 09:33:23 pm
That's a well-deserved day off :)

Happy New Year!
Title: Re: Keyhotee Status Update
Post by: lzr1900 on January 02, 2014, 02:04:04 pm
January 02 .
where is the keyhotee?No ETA?
Title: Re: Keyhotee Status Update
Post by: Riverhead on January 02, 2014, 03:35:27 pm
What's the rush?  Today, next week, early Q1....as long as it's a quality product I see no benefit in having it tomorrow vs next month.  You only get one chance at a first impression and if Keyhotee has teething issues because it was rushed it could adversely compromise the entire project.

I believe I'm preaching to the choir however as delayed release dates vs buggy releases seems to be the direction I3 has chosen.
 
Title: Re: Keyhotee Status Update
Post by: lib on January 02, 2014, 04:05:48 pm
What's the rush?  Today, next week, early Q1....as long as it's a quality product I see no benefit in having it tomorrow vs next month.  You only get one chance at a first impression and if Keyhotee has teething issues because it was rushed it could adversely compromise the entire project.

I believe I'm preaching to the choir however as delayed release dates vs buggy releases seems to be the direction I3 has chosen.

+1 
quality > speed at the moment.
Title: Re: Keyhotee Status Update
Post by: AdamBLevine on January 02, 2014, 09:02:18 pm
Can we get some estimate on when a actual working product will be released? Give us a date you are comfortable with so we won't miss anymore deadlines.

Since I have delegated the work to Dan Notestein and his team in Poland I will ask them to make estimates and get back to you.  I do agree that I would rather under-promise and over-deliver.

Any estimates?   Would be good to get a new, achievable timeframe.
Title: Re: Keyhotee Status Update
Post by: rysgc on January 02, 2014, 09:04:18 pm
Check BM's announcement: https://bitsharestalk.org/index.php?topic=1888.msg21731#msg21731 (https://bitsharestalk.org/index.php?topic=1888.msg21731#msg21731)
Title: Re: Keyhotee Status Update
Post by: bytemaster on January 04, 2014, 02:39:58 am
Good news everyone, we are ready for releasing the Alpha of Keyhotee.  We are packaging it up for distribution in a couple of hours.   

Title: Re: Keyhotee Status Update
Post by: pvaladares on January 04, 2014, 02:42:28 am
Excelent news :)
Title: Re: Keyhotee Status Update
Post by: arcke on January 04, 2014, 02:43:40 am
Great to hear this! I was not expecting this so fast.
Title: Re: Keyhotee Status Update
Post by: Amazon on January 04, 2014, 03:22:22 am
Super exciting!
Title: Re: Keyhotee Status Update
Post by: kmtan on January 04, 2014, 03:42:07 am
Good news everyone, we are ready for releasing the Alpha of Keyhotee.  We are packaging it up for distribution in a couple of hours.   

Great time ...Surprise..
Title: Re: Keyhotee Status Update
Post by: her0 on January 04, 2014, 03:44:14 am
Good news everyone, we are ready for releasing the Alpha of Keyhotee.  We are packaging it up for distribution in a couple of hours.   
nice work!
Title: Re: Keyhotee Status Update
Post by: heropzy on January 04, 2014, 04:02:20 am
Good news everyone, we are ready for releasing the Alpha of Keyhotee.  We are packaging it up for distribution in a couple of hours.   

Cheers!
Title: Re: Keyhotee Status Update
Post by: lzr1900 on January 04, 2014, 04:08:48 am
Awesome!Can I sign up a normal ID ?Or this is just for Keyhotee Founders ? thx.
Title: Re: Keyhotee Status Update
Post by: BTSInvestor on January 04, 2014, 04:26:39 am
is the alpha version only for the keyhotee founder to generate the public key? can the non-founder mine the keyhotee id?
Title: Re: Keyhotee Status Update
Post by: bytemaster on January 04, 2014, 06:28:46 am
is the alpha version only for the keyhotee founder to generate the public key? can the non-founder mine the keyhotee id?

No mining of IDs, but you can create IDs and share your public keys to send emails bitmessage style.   We are working out one last minute bug we discovered.

The primary purpose of this release is registration of Founder IDs and as a preview of what is coming.  This is very alpha software and that means we KNOW there are a lot of rough edges and bugs.  Founders will have until we resolve known bugs to register their ID.  We will attempt to release regular updates as this progresses.
Title: Re: Keyhotee Status Update
Post by: BTSInvestor on January 04, 2014, 06:49:27 am
i think the registration process can be treated as "mining",as the id creation process requires the POW hash computing. so the non-founder user also can create their profile in the alpha version, am i correct?
Title: Re: Keyhotee Status Update
Post by: alt on January 04, 2014, 06:54:50 am
yes, we can register an ID , but the blocks will reset when the stable version release, that means we will lose all the IDs, and have to register again.
the funders ID will init at the 1 block when the stable version release.

i think the registration process can be treated as "mining",as the id creation process requires the POW hash computing. so the non-founder user also can create their profile in the alpha version, am i correct?
Title: Re: Keyhotee Status Update
Post by: alt on January 04, 2014, 07:00:26 am
" wallet_index" , it confuse me. I think addressbook can not work correct, wish fix it before  this release.

is the alpha version only for the keyhotee founder to generate the public key? can the non-founder mine the keyhotee id?

No mining of IDs, but you can create IDs and share your public keys to send emails bitmessage style.   We are working out one last minute bug we discovered.

The primary purpose of this release is registration of Founder IDs and as a preview of what is coming.  This is very alpha software and that means we KNOW there are a lot of rough edges and bugs.  Founders will have until we resolve known bugs to register their ID.  We will attempt to release regular updates as this progresses.
Title: Re: Keyhotee Status Update
Post by: bytemaster on January 04, 2014, 07:07:38 am
" wallet_index" , it confuse me. I think addressbook can not work correct, wish fix it before  this release.

is the alpha version only for the keyhotee founder to generate the public key? can the non-founder mine the keyhotee id?

No mining of IDs, but you can create IDs and share your public keys to send emails bitmessage style.   We are working out one last minute bug we discovered.

The primary purpose of this release is registration of Founder IDs and as a preview of what is coming.  This is very alpha software and that means we KNOW there are a lot of rough edges and bugs.  Founders will have until we resolve known bugs to register their ID.  We will attempt to release regular updates as this progresses.

Yes it isn't working right now and that is what we are fixing prior to this release. 
Title: Re: Keyhotee Status Update
Post by: alt on January 04, 2014, 07:11:01 am
great!  thx!
" wallet_index" , it confuse me. I think addressbook can not work correct, wish fix it before  this release.

is the alpha version only for the keyhotee founder to generate the public key? can the non-founder mine the keyhotee id?

No mining of IDs, but you can create IDs and share your public keys to send emails bitmessage style.   We are working out one last minute bug we discovered.

The primary purpose of this release is registration of Founder IDs and as a preview of what is coming.  This is very alpha software and that means we KNOW there are a lot of rough edges and bugs.  Founders will have until we resolve known bugs to register their ID.  We will attempt to release regular updates as this progresses.

Yes it isn't working right now and that is what we are fixing prior to this release.
Title: Re: Keyhotee Status Update
Post by: DAY on January 04, 2014, 07:55:47 am
Pls release asap, thanks Sir
Title: Re: Keyhotee Status Update
Post by: robust8 on January 04, 2014, 08:47:49 am
Good news, I am waiting online :)
Title: Re: Keyhotee Status Update
Post by: mmao on January 04, 2014, 12:00:09 pm
How are things going?
Title: Re: Keyhotee Status Update
Post by: alt on January 04, 2014, 12:03:03 pm
I saw the bug had been fixed about 2 hours ago. I am waiting for the server up....
How are things going?
Title: Re: Keyhotee Status Update
Post by: mmao on January 04, 2014, 12:04:37 pm
I saw the bug had been fixed about 2 hours ago. I am waiting for the server up....
How are things going?

where to download?
Title: Re: Keyhotee Status Update
Post by: alt on January 04, 2014, 12:13:45 pm
get source code from github
I saw the bug had been fixed about 2 hours ago. I am waiting for the server up....
How are things going?

where to download?
Title: Re: Keyhotee Status Update
Post by: mmao on January 04, 2014, 12:16:51 pm
link to github?
Title: Re: Keyhotee Status Update
Post by: alt on January 04, 2014, 12:21:10 pm
https://github.com/InvictusInnovations/
link to github?
Title: Re: Keyhotee Status Update
Post by: mmao on January 04, 2014, 12:26:36 pm
Is there going to be a compiled binary version to download?
Title: Re: Keyhotee Status Update
Post by: bytemaster on January 04, 2014, 02:59:52 pm
Yes we are preparing binary for release today


Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
Title: Re: Keyhotee Status Update
Post by: RejectKid on January 04, 2014, 07:53:34 pm
Where is the alpha miner download for the founders?  I paid the 10PTS awhile ago so I believe I'm considered a founder.  Sorry I haven't found it quick enough so I figured I'd just ask again.
Title: Re: Keyhotee Status Update
Post by: bytemaster on January 04, 2014, 07:54:54 pm
Where is the alpha miner download for the founders?  I paid the 10PTS awhile ago so I believe I'm considered a founder.  Sorry I haven't found it quick enough so I figured I'd just ask again.

https://bitsharestalk.org/index.php?topic=1962.msg22546#msg22546

Sorry, I was doing some light testing without announcing it for everyone.  It seems to be going smoothly so I will post here.
Title: Re: Keyhotee Status Update
Post by: arubi on January 05, 2014, 01:28:26 pm
Did someone get this to build under linux?
I don't have any other way to use this...
Title: Re: Keyhotee Status Update
Post by: sva_h4cky0 on January 05, 2014, 03:02:42 pm
Did someone get this to build under linux?
I don't have any other way to use this...
yes, whats your problem? i manage to compile and run with arch linux.
Title: Re: Keyhotee Status Update
Post by: arubi on January 05, 2014, 03:08:30 pm
Did someone get this to build under linux?
I don't have any other way to use this...
yes, whats your problem? i manage to compile and run with arch linux.


Can you list the dependencies?
Did you use cmake at all?
Title: Re: Keyhotee Status Update
Post by: sva_h4cky0 on January 05, 2014, 05:15:01 pm
Did someone get this to build under linux?
I don't have any other way to use this...
yes, whats your problem? i manage to compile and run with arch linux.


Can you list the dependencies?
Did you use cmake at all?

afaik 'qt5 ''git' 'boost' 'gcc' 'cmake' 'make' 'openssl', please note name may different on other distro
Title: Re: Keyhotee Status Update
Post by: arubi on January 05, 2014, 05:17:22 pm
Did someone get this to build under linux?
I don't have any other way to use this...
yes, whats your problem? i manage to compile and run with arch linux.


Can you list the dependencies?
Did you use cmake at all?

afaik 'git' 'boost' 'gcc' 'cmake' 'make' 'openssl', please note name may different on other distro


I have all of these and I installed cmake 2.8.11+ from source, didn't you need QT5 libs for it?
I can't find the right ones...


Thanks
Title: Re: Keyhotee Status Update
Post by: sva_h4cky0 on January 05, 2014, 05:19:15 pm
Did someone get this to build under linux?
I don't have any other way to use this...
yes, whats your problem? i manage to compile and run with arch linux.


Can you list the dependencies?
Did you use cmake at all?

afaik 'git' 'boost' 'gcc' 'cmake' 'make' 'openssl', please note name may different on other distro


I have all of these and I installed cmake 2.8.11+ from source, didn't you need QT5 libs for it?
I can't find the right ones...


Thanks

yep, qt5, sorry forgot about that. whats your distro?
Title: Re: Keyhotee Status Update
Post by: arubi on January 05, 2014, 05:21:58 pm
yep, qt5, sorry forgot about that. whats your distro?


Mint 15 and I'll also try on Debian jessie
(really appreciate the quick replies)
Title: Re: Keyhotee Status Update
Post by: sva_h4cky0 on January 05, 2014, 05:31:12 pm
yep, qt5, sorry forgot about that. whats your distro?


Mint 15 and I'll also try on Debian jessie
(really appreciate the quick replies)

thats because we both online at same time  ;D

maybe this will help
https://bitsharestalk.org/index.php?topic=1672.0
https://bitsharestalk.org/index.php?topic=1565.0

i think the best way is using latest qt5, not from ubuntu/mint repos
Title: Re: Keyhotee Status Update
Post by: arubi on January 05, 2014, 05:34:17 pm
yep, qt5, sorry forgot about that. whats your distro?


Mint 15 and I'll also try on Debian jessie
(really appreciate the quick replies)

thats because we both online at same time  ;D

maybe this will help
https://bitsharestalk.org/index.php?topic=1672.0 (https://bitsharestalk.org/index.php?topic=1672.0)
https://bitsharestalk.org/index.php?topic=1565.0 (https://bitsharestalk.org/index.php?topic=1565.0)

i think the best way is using latest qt5, not from ubuntu/mint repos


Awesome :)
I'll try the links.
Title: Re: Keyhotee Status Update
Post by: Bitcoin3D on January 06, 2014, 08:15:00 am
Can someone please explain in depth how to actually install Keyhotee from here? I want to install to be able to register my Founders ID. I dont know what I am missing but I find it hard to find the right information to be able simply to install it. Do I have to compile the program? How do I do that? Cus I can not find any .exe. Thanks
Title: Re: Keyhotee Status Update
Post by: testz on January 06, 2014, 08:18:49 am
Can someone please explain in depth how to actually install Keyhotee from here? I want to install to be able to register my Founders ID. I dont know what I am missing but I find it hard to find the right information to be able simply to install it. Do I have to compile the program? How do I do that? Cus I can not find any .exe. Thanks

You can download client from here: https://bitsharestalk.org/index.php?topic=1962.msg23149#msg23149
Instruction here: https://bitsharestalk.org/index.php?topic=1962.0
Title: Re: Keyhotee Status Update
Post by: Bitcoin3D on January 06, 2014, 10:33:32 am
Thanks. I got it all working now. Great!
Title: Re: Keyhotee Status Update
Post by: earthbound on January 06, 2014, 03:52:55 pm
Can someone please explain in depth how to actually install Keyhotee from here? I want to install to be able to register my Founders ID. I dont know what I am missing but I find it hard to find the right information to be able simply to install it. Do I have to compile the program? How do I do that? Cus I can not find any .exe. Thanks

It may depend on what platform you're running it on. I just extracted the .zip archive on Windows and then double-clicked Keyhotee.exe.
Title: Re: Keyhotee Status Update
Post by: James212 on January 08, 2014, 02:41:18 am
That is the status of the OSX version of Keyhotee?
Title: Re: Keyhotee Status Update
Post by: dannotestein on January 08, 2014, 03:42:46 am
That is the status of the OSX version of Keyhotee?

We're still doing alpha releases right now, so we're not focusing on multiple platforms too much yet. We're building Windows binaries,  but Linux and OSX have to be build from github source (both of these have been tested and do work fine). My team only has Windows and Linux boxes, bytemaster is the only OSX dev at Invictus currently, as far as I'm aware.

We're planning another alpha release this Friday with fixes for many of the issues reported for the first alpha, with a special emphasis on bugs related to profile creation problems (a few users had hangs while trying to create profiles).
Title: Re: Keyhotee Status Update
Post by: alt on January 08, 2014, 04:10:59 am
Good work, thx!
That is the status of the OSX version of Keyhotee?

We're still doing alpha releases right now, so we're not focusing on multiple platforms too much yet. We're building Windows binaries,  but Linux and OSX have to be build from github source (both of these have been tested and do work fine). My team only has Windows and Linux boxes, bytemaster is the only OSX dev at Invictus currently, as far as I'm aware.

We're planning another alpha release this Friday with fixes for many of the issues reported for the first alpha, with a special emphasis on bugs related to profile creation problems (a few users had hangs while trying to create profiles).
Title: Re: Keyhotee Status Update
Post by: NineLives on January 08, 2014, 02:58:45 pm
Hi guys,

mining isn't enabled yet is it?
Title: Re: Keyhotee Status Update
Post by: Riverhead on January 08, 2014, 03:06:26 pm
Nope, no mining yet.
Title: Re: Keyhotee Status Update
Post by: king on January 08, 2014, 03:14:06 pm
Thinks for update.
Title: Re: Keyhotee Status Update
Post by: que23 on January 09, 2014, 12:35:57 am
Does Invictus have security people to go through the code? I know Keyhotee is behind schedule, but I'd hate to see it rushed.
Title: Re: Keyhotee Status Update
Post by: bytemaster on January 09, 2014, 02:06:09 am

Does Invictus have security people to go through the code? I know Keyhotee is behind schedule, but I'd hate to see it rushed.

Yes we just hired a security expert but he does not start for two weeks.


Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
Title: Re: Keyhotee Status Update
Post by: AdamBLevine on January 09, 2014, 04:42:04 am
Seems like maybe there should be a bounty for this especially?  Our new sponsor Crowdcurity might be interested in helping you
Title: Re: Keyhotee Status Update
Post by: muse-umum on January 10, 2014, 07:54:26 am
That is the status of the OSX version of Keyhotee?

We're still doing alpha releases right now, so we're not focusing on multiple platforms too much yet. We're building Windows binaries,  but Linux and OSX have to be build from github source (both of these have been tested and do work fine). My team only has Windows and Linux boxes, bytemaster is the only OSX dev at Invictus currently, as far as I'm aware.

We're planning another alpha release this Friday with fixes for many of the issues reported for the first alpha, with a special emphasis on bugs related to profile creation problems (a few users had hangs while trying to create profiles).

Friday now. Any updates ?
Title: Re: Keyhotee Status Update
Post by: dannotestein on January 10, 2014, 03:15:08 pm
We're on track with testing so far, so we're still planning to release late today per our original plan (unless something unexpected pops up in testing).
Title: Re: Keyhotee Status Update
Post by: smiley35 on January 10, 2014, 10:38:35 pm
That is the status of the OSX version of Keyhotee?

We're still doing alpha releases right now, so we're not focusing on multiple platforms too much yet. We're building Windows binaries,  but Linux and OSX have to be build from github source (both of these have been tested and do work fine). My team only has Windows and Linux boxes, bytemaster is the only OSX dev at Invictus currently, as far as I'm aware.

We're planning another alpha release this Friday with fixes for many of the issues reported for the first alpha, with a special emphasis on bugs related to profile creation problems (a few users had hangs while trying to create profiles).

So as a founder and a mac user, will I be able to register my name before the genisis block?
Title: Re: Keyhotee Status Update
Post by: bytemaster on January 10, 2014, 10:39:39 pm
That is the status of the OSX version of Keyhotee?

We're still doing alpha releases right now, so we're not focusing on multiple platforms too much yet. We're building Windows binaries,  but Linux and OSX have to be build from github source (both of these have been tested and do work fine). My team only has Windows and Linux boxes, bytemaster is the only OSX dev at Invictus currently, as far as I'm aware.

We're planning another alpha release this Friday with fixes for many of the issues reported for the first alpha, with a special emphasis on bugs related to profile creation problems (a few users had hangs while trying to create profiles).

So as a founder and a mac user, will I be able to register my name before the genisis block?

Yes.  Toast is working on this. 
Title: Re: Keyhotee Status Update
Post by: dannotestein on January 11, 2014, 04:52:45 am
I've uploaded new Keyhotee alpha 2 release binary for Windows to:
 http://invictus.io/bin/keyhotee_0.5.2.zip

The main focus for this release was fixing bugs associated with profile creation and loading, including problems related to network issues and foreign language characters. It also has better reporting of successful registration of Keyhotee Founder IDs (previously this could only be checked when creating an identity, now this info is persistently available in the contact info page for that identity). We plan to release a linux binary in a few days, assuming no major problems are reported in the interim.
Title: Re: Keyhotee Status Update
Post by: Riverhead on January 11, 2014, 05:02:08 am
I've uploaded new Keyhotee alpha 2 release binary for Windows to:
 http://invictus.io/bin/keyhotee_0.5.2.zip (http://invictus.io/bin/keyhotee_0.5.2.zip)

The main focus for this release was fixing bugs associated with profile creation and loading, including problems related to network issues and foreign language characters. It also has better reporting of successful registration of Keyhotee Founder IDs (previously this could only be checked when creating an identity, now this info is persistently available in the contact info page for that identity). We plan to release a linux binary in a few days, assuming no major problems are reported in the interim.


Profile recreated on Windows with no issues (it generated the same pub key for me).
Title: Re: Keyhotee Status Update
Post by: dannotestein on January 11, 2014, 05:48:31 am
Great, thanks for the quick feedback!
Title: Re: Keyhotee Status Update
Post by: Ykw on January 11, 2014, 02:28:45 pm
OK,

Not very successful but here it is all the tests I made (saved all info to make tests reproducible):

Current keyhotee (A) = C:\keyhotee_0.5.0
Profile password for A - (A.1)
New keyhotee (B) = C:\keyhotee_0.5.2
Profile password created with B - (B.1)
Profile information (C) = C:\Users\<user>\AppData\Local\KEYHOTEE

- Test 1:
Set B and open KEYHOTEE.EXE with A.1
Result: My profile opens without errors and I am able to see everything I had before except that my Keyhotee ID is now "Unregistered". Apart from that everything shows up as before. The language of my country also appears as I translated (maybe add an option in future to change language). I still have to make some adjustments to translated values. I have also used "http://invictus-innovations.com/founder-sign-up/" with the information I had before and the first pub-key. And if I try to create a new identity for the same keyhotee ID it will show the same original public-key.

- Test 2:
Deleted C
Created a new profile with A and using the same information that I had previously entered when creating A in first place.
Results: It was possible to load the same profile with A or B, and both generated the same pub-key for a certain keyhotee ID. Although the key is not the same as the one I have created in first place. For example... my first key is 5kKsqBdtpiStC3Ww9GG9SfF4ecqBV9FpHwPpDtcTd4iHJayRMe and with a new generated profile it is 6TC7hRoaYs5JYvn12qZzbMJahoHuF3brF6p2cuahUNsTSrMUwK.

- Test 3:
Deleted C again.
Created a new profile with B and using the same information that I had previously entered when creating A in first place.
Results: It was possible to load the same profile with B only, but it generated the same pub-key as in Test 2 for a certain keyhotee ID (and profile password): 6TC7hRoaYs5JYvn12qZzbMJahoHuF3brF6p2cuahUNsTSrMUwK

Error generated in Test 3 when I try to open with version 0.5.0:
#########################################################
3431762ms th_a       LoginDialog.cpp:57            onLogin              ] error
assert
fc::exists( file ):
    {}
    th_a  aes.cpp:295 fc::aes_load

    {"file":"C:/Users/<user>/AppData/Local/KEYHOTEE/profiles/<my profile with spaces>/.s
tretched_seed"}
    th_a  aes.cpp:311 fc::aes_load

    {"profile_dir":"C:/Users/<user>/AppData/Local/KEYHOTEE/profiles/<my profile with spaces>"}
    th_a  profile.cpp:124 bts::profile::open

    {}
    th_a  application.cpp:341 bts::application::load_profile
#########################################################

Other notes:
- Using different profile passwords generated different Public-keys.
- Noticed that over creation in A the middle name is not used for profile creation and in B it is.

Question?
What should be done now? Should I re-register the new pub-key I have with my key in "http://invictus-innovations.com/founder-sign-up/"??? I found it strange because when in Test 2 or 3 i use my Keyhotee ID (the pub-key is then 6TC7hRoaYs5JYvn12qZzbMJahoHuF3brF6p2cuahUNsTSrMUwK) and Founder Code... it says "invalid"... But before it did say the correct stuff.
Title: Re: Keyhotee Status Update
Post by: bobmaloney on January 11, 2014, 08:28:43 pm
Thanks guys
Update successful for Win 7 64.

No longer refuses password.
Title: Re: Keyhotee Status Update
Post by: Bitcoin3D on January 13, 2014, 12:00:36 am
I've uploaded new Keyhotee alpha 2 release binary for Windows to:
 http://invictus.io/bin/keyhotee_0.5.2.zip

The main focus for this release was fixing bugs associated with profile creation and loading, including problems related to network issues and foreign language characters. It also has better reporting of successful registration of Keyhotee Founder IDs (previously this could only be checked when creating an identity, now this info is persistently available in the contact info page for that identity). We plan to release a linux binary in a few days, assuming no major problems are reported in the interim.

I'm confused now. I installed v 0.5.2 But now my Id shows up as unregistered. And when I tried to open the older version it shows the same. Before that It showed registered. Please let me know how to fix this. Should I delete my profile in APPDATA and re-register or what should I do?
Title: Re: Keyhotee Status Update
Post by: dannotestein on January 13, 2014, 01:07:54 am
I'm confused now. I installed v 0.5.2 But now my Id shows up as unregistered. And when I tried to open the older version it shows the same. Before that It showed registered. Please let me know how to fix this. Should I delete my profile in APPDATA and re-register or what should I do?

Previously, the only way to tell if your ID was registered was during the New Identity dialog (it would report the points there). You may have seen your ID as being a Keyhotee Founder later in your contact info page, but this wasn't checking with the registration database, this would be checking against the blockchain. Currently there's no true blockchain yet since we're collecting Founder IDs now, so this would just be some local blockchain mined on your local client (and therefore not meaningful).

So it sounds like your ID was never actually registered. I recommend deleting your profile and re-registering your new identity as you suggested. If you're probably registering, your contact info page should now show the same points information that should be displayed when you creating your New Identity from the menu option.
Title: Re: Keyhotee Status Update
Post by: Bitcoin3D on January 13, 2014, 02:37:16 am
I'm confused now. I installed v 0.5.2 But now my Id shows up as unregistered. And when I tried to open the older version it shows the same. Before that It showed registered. Please let me know how to fix this. Should I delete my profile in APPDATA and re-register or what should I do?

Previously, the only way to tell if your ID was registered was during the New Identity dialog (it would report the points there). You may have seen your ID as being a Keyhotee Founder later in your contact info page, but this wasn't checking with the registration database, this would be checking against the blockchain. Currently there's no true blockchain yet since we're collecting Founder IDs now, so this would just be some local blockchain mined on your local client (and therefore not meaningful).

So it sounds like your ID was never actually registered. I recommend deleting your profile and re-registering your new identity as you suggested. If you're probably registering, your contact info page should now show the same points information that should be displayed when you creating your New Identity from the menu option.

Thanks danno, actually I know from registering with the first alfaversion that I was registered. Now I did like I asked; I deleted my profiile in the appdata-folder and did a clean install and created a new ID  with my founders ID and all seem to be working fine  now. It says " Registered with xxx points" That should mean that I am registered I assume? I guess was a conflict with the two installation reading from the same appdata and that made it confusing when it tried to read from the same folder. But that is just my guess
Title: Re: Keyhotee Status Update
Post by: dannotestein on January 13, 2014, 02:44:16 am
It says " Registered with xxx points" That should mean that I am registered I assume? I guess was a conflict with the two installation reading from the same appdata and that made it confusing when it tried to read from the same folder.
Yes, the "registered with points" means you're registered.

Profiles should be compatible between versions, but you can't open the same profile simultaneously in two Keyhotee's as the databases inside get locked by the first client to open it. Not sure if you're saying that's what you were doing or not.
Title: Re: Keyhotee Status Update
Post by: Bitcoin3D on January 13, 2014, 02:53:58 am
It says " Registered with xxx points" That should mean that I am registered I assume? I guess was a conflict with the two installation reading from the same appdata and that made it confusing when it tried to read from the same folder.
Yes, the "registered with points" means you're registered.

Profiles should be compatible between versions, but you can't open the same profile simultaneously in two Keyhotee's as the databases inside get locked by the first client to open it. Not sure if you're saying that's what you were doing or not.

I never had them open simultaneously no. But I believe there could be a problem with the way the program read my profile since it contained a Swedish letter Ö in it and it reformatted that to some alt symbols after the first time I installed the latest version. That might be useful for you to know in that case. Anyways I'm all good now.
Title: Re: Keyhotee Status Update
Post by: dannotestein on January 13, 2014, 03:14:30 am
I never had them open simultaneously no. But I believe there could be a problem with the way the program read my profile since it contained a Swedish letter Ö in it and it reformatted that to some alt symbols after the first time I installed the latest version. That might be useful for you to know in that case. Anyways I'm all good now.

We were expecting the reformatting of some alt symbols for legacy profiles that would show up visibly in the profile selection dialog at startup, but we didn't expect any other issue (it seemed to work in our testing). But it's been a slight fear of mine that it could cause some problem. Thanks for letting me know you're good now: I'll recommend this approach to anyone else with a similar problem.
Title: Re: Keyhotee Status Update
Post by: Riverhead on January 13, 2014, 01:41:03 pm



This may be the wrong thread and perhaps a bit premature as an Alpha issue however:


I have my main Keyhotee founder ID registered and the pubkey is repeatable by generating new profiles. I am all good there, form submitted on the website, etc.


In the same profile I created a new Identity (Riverhead) and got a public key.  Previously I had exchanged a few messages with someone using Riverhead and all was well.  In the new version I recreated Riverhead and got the same pub key however it never became registered (as expected as there is no block chain yet).  So I deleted Riverhead from my contacts then tried to re-create and it says, "You have already created this identity".


So my question is if I create a second identity (not a founder but in the same profile) and then delete the contact should I be able to re-add it?  Where is Riverhead now?  Will I still get messages send to the pub key? Is there another way to add a pub key I generated with my primary profile?


Riverhead: 54bkuu78GAm2YcRVueQFt4io2AbwV7Dg7RioovCUzYdkjgCQ81


Again, if this is more of a Beta issue please feel free to disregard or move to another thread.


Thanks!
Title: Re: Keyhotee Status Update
Post by: bytemaster on January 13, 2014, 02:44:26 pm



This may be the wrong thread and perhaps a bit premature as an Alpha issue however:


I have my main Keyhotee founder ID registered and the pubkey is repeatable by generating new profiles. I am all good there, form submitted on the website, etc.


In the same profile I created a new Identity (Riverhead) and got a public key.  Previously I had exchanged a few messages with someone using Riverhead and all was well.  In the new version I recreated Riverhead and got the same pub key however it never became registered (as expected as there is no block chain yet).  So I deleted Riverhead from my contacts then tried to re-create and it says, "You have already created this identity".


So my question is if I create a second identity (not a founder but in the same profile) and then delete the contact should I be able to re-add it?  Where is Riverhead now?  Will I still get messages send to the pub key? Is there another way to add a pub key I generated with my primary profile?


Riverhead: 54bkuu78GAm2YcRVueQFt4io2AbwV7Dg7RioovCUzYdkjgCQ81


Again, if this is more of a Beta issue please feel free to disregard or move to another thread.


Thanks!

This is a known issue and is being worked on. Thanks for reporting it.
Title: Re: Keyhotee Status Update
Post by: Riverhead on January 13, 2014, 06:07:54 pm
This is a known issue and is being worked on. Thanks for reporting it.


Right, sorry.  Hard to keep up with the large volume of traffic :).  Just an FYI I can still send/receive with Riverhead so this is clearly just a GUI issue.


I'll let you get back to preparing to knock our socks off in Miami ;).
Title: Re: Keyhotee Status Update
Post by: smiley35 on January 13, 2014, 10:18:46 pm
Any updates on the OSX client?
Title: Re: Keyhotee Status Update
Post by: bytemaster on January 14, 2014, 04:54:19 am
Any updates on the OSX client?
Toast is supposedly working on it.  I am working on BTS full time.
Title: Re: Keyhotee Status Update
Post by: foolsh on January 15, 2014, 02:58:24 am
Is it possible to release a statically linked linux client, or should I drudge through the dependency hell until I get it compiled?
Title: Re: Keyhotee Status Update
Post by: dannotestein on January 15, 2014, 03:51:02 am
Is it possible to release a statically linked linux client, or should I drudge through the dependency hell until I get it compiled?

We're working on this now, we should have it ready very soon I think, possibly tomorrow.
Title: Re: Keyhotee Status Update
Post by: jae208 on January 17, 2014, 05:40:52 am
When exactly will Keehote be released?
Title: Re: Keyhotee Status Update
Post by: Riverhead on January 17, 2014, 05:58:10 am
That's a hard question to answer. As I used to tell my mangers when I was involved with projects like this, "We're doing something that's never been done and encountering issues that have never been faced. It's nearly impossible to say with any accuracy how long it's going to take to solve problems we've never seen before." At best I am hoping for this or next quarter but I don't want it rushed.
Title: Re: Keyhotee Status Update
Post by: aero101 on January 17, 2014, 12:38:04 pm
want to know does the next edition of keyhotee will be full function release,just like the introduction video showing us,such as combine with the wallet of PTS,BTC or LTC ?Many thx.
Title: Re: Keyhotee Status Update
Post by: Giga on January 17, 2014, 12:41:53 pm
i second the osx client would like to chk it out
Title: Re: Keyhotee Status Update
Post by: James212 on January 19, 2014, 03:05:50 pm
+1
Title: Re: Keyhotee Status Update
Post by: logramuda on January 20, 2014, 12:45:39 am
+1

Yes.   Mac Client would be wonderful.
Title: Re: Keyhotee Status Update
Post by: lzr1900 on January 20, 2014, 11:56:14 am
Where is the OSX clinet!!!!!
Title: Re: Keyhotee Status Update
Post by: bytemaster on January 20, 2014, 02:54:07 pm
https://www.dropbox.com/s/ngq8c9hsbypxsvv/Keyhotee.dmg
Title: Re: Keyhotee Status Update
Post by: CryptoN8 on January 20, 2014, 11:06:28 pm
Couple things,
Can it be the standard that the links to new/updated versions of software get updated in the OP? It is a real pain to search for latest releases going through page after page. (I know QQ)

We got some good press in Hacker News, but it sent to the new http://invictus.io and the DL link for Keyhotee is borked.

Currently: (Dead)
http://invictus.io/bin/keyhotee_0.5.0.zip
Should be:
http://invictus.io/bin/keyhotee_0.5.2.zip

Thanks.
Title: Re: Keyhotee Status Update
Post by: dannotestein on January 21, 2014, 04:34:04 am
Couple things,
Can it be the standard that the links to new/updated versions of software get updated in the OP? It is a real pain to search for latest releases going through page after page. (I know QQ)

We got some good press in Hacker News, but it sent to the new http://invictus.io and the DL link for Keyhotee is borked.

Currently: (Dead)
http://invictus.io/bin/keyhotee_0.5.0.zip
Should be:
http://invictus.io/bin/keyhotee_0.5.2.zip

Thanks.
Normally, that would be the case, but I didn't update the OP link immediately because I didn't want too many downloading it right away, before it got tested by a few intrepid alpha testers. That said, I should have updated it afterward. I'll update it now, especially since the Keyhotee Founder Id registration checking now receives the updates from the web form (well, at least after a few days) so that Keyhotee can be used to verify Founder Ids. One thing you said did confuse me: as far as I can tell the old link 0.50 does work.
Title: Re: Keyhotee Status Update
Post by: James212 on January 22, 2014, 01:41:25 am
I never recevied the follow email regarding Keyhotee Founder registeration.  Is that still to come?   

Also, can anyone point me to the instructions on how to register ones founder id.  Thanks. 


On second thought.......it looks like I was able to figure it out.  Setup is fairly streight forward. 
Title: Re: Keyhotee Status Update
Post by: CryptoN8 on January 22, 2014, 02:59:58 pm
Couple things,
Can it be the standard that the links to new/updated versions of software get updated in the OP? It is a real pain to search for latest releases going through page after page. (I know QQ)

We got some good press in Hacker News, but it sent to the new http://invictus.io and the DL link for Keyhotee is borked.

Currently: (Dead)
http://invictus.io/bin/keyhotee_0.5.0.zip
Should be:
http://invictus.io/bin/keyhotee_0.5.2.zip

Thanks.
Normally, that would be the case, but I didn't update the OP link immediately because I didn't want too many downloading it right away, before it got tested by a few intrepid alpha testers. That said, I should have updated it afterward. I'll update it now, especially since the Keyhotee Founder Id registration checking now receives the updates from the web form (well, at least after a few days) so that Keyhotee can be used to verify Founder Ids. One thing you said did confuse me: as far as I can tell the old link 0.50 does work.
The link for the download was not working for a while there, but it has been fixed. Thank you. The new site(s) are looking great by the way. 8)
Title: Re: Keyhotee Status Update
Post by: jae208 on January 23, 2014, 01:07:28 pm
That's a hard question to answer. As I used to tell my mangers when I was involved with projects like this, "We're doing something that's never been done and encountering issues that have never been faced. It's nearly impossible to say with any accuracy how long it's going to take to solve problems we've never seen before." At best I am hoping for this or next quarter but I don't want it rushed.

True but it would be nice to have weekly updates from those involved in developing the project.
Title: Re: Keyhotee Status Update
Post by: bytemaster on January 23, 2014, 01:22:33 pm
That's a hard question to answer. As I used to tell my mangers when I was involved with projects like this, "We're doing something that's never been done and encountering issues that have never been faced. It's nearly impossible to say with any accuracy how long it's going to take to solve problems we've never seen before." At best I am hoping for this or next quarter but I don't want it rushed.

True but it would be nice to have weekly updates from those involved in developing the project.

We aim for daily updates, or at least that I what I have requested from Dan Notestein.   Based on my last talk with Dan, we should have the genesis block ready early Feb.
Title: Re: Keyhotee Status Update
Post by: jae208 on January 23, 2014, 03:30:04 pm
That's a hard question to answer. As I used to tell my mangers when I was involved with projects like this, "We're doing something that's never been done and encountering issues that have never been faced. It's nearly impossible to say with any accuracy how long it's going to take to solve problems we've never seen before." At best I am hoping for this or next quarter but I don't want it rushed.

True but it would be nice to have weekly updates from those involved in developing the project.

We aim for daily updates, or at least that I what I have requested from Dan Notestein.   Based on my last talk with Dan, we should have the genesis block ready early Feb.

Thank you!
Title: Re: Keyhotee Status Update
Post by: diaobanxian on January 24, 2014, 05:29:16 am
good news
Title: Re: Keyhotee Status Update
Post by: yago on January 28, 2014, 01:19:12 pm
Update 1/20/2014: Latest Version of Keyhotee Alpha here
http://invictus.io/bin/keyhotee_0.5.2.zip     

Only the dmg there, that link gives a 404 error.

Any news about the linux binary?
Title: Re: Keyhotee Status Update
Post by: dannotestein on January 29, 2014, 04:47:07 am
[Any news about the linux binary?
Another dependency got added (berkeleyDb) that we had to add as a static library, so that delayed Linux a bit. We've taken care of that now, so we're just waiting for a final build with an older version of glibc to maximize compatibility across Linux versions. I think it'll be another day or two to test the new build on different Linux versions, then it should be ready.
Title: Re: Keyhotee Status Update
Post by: ppimp on January 31, 2014, 12:56:58 am
I use to be a Invictus investor and very bullish on the PTS shares, but I recently pulled out with the steep decline in PTS price coupled with the confusion around AngelShares and not knowing which I should be holding on to. I am still very interested in seeing you succeed and and be first to deploy but honestly there is a lot more competition from Nxt, MasterCoin, Ethereum.

Its not exactly the thread to discuss this, but it's coming out with the frustration on failing to deliver on Keyhotee, and as I check back what I am seeing.

There is still issues with Keyhotee that I find unacceptable if Invictus wants to be competitive, reputable organization:


Can you please fix these and be more transparent in communication, and delivery. Thanks.
Title: Re: Keyhotee Status Update
Post by: dannotestein on January 31, 2014, 01:06:42 am
  • Dan/Bytemaster mentioned they aim for daily status updates 7 days ago. They missed 6 out of 7 of those daily status updates.
  • What about the Keyhotee Windows build?
  • The download for alpha keyhotee is not working. I clicked the .zip file on the first page of this thread and it goes to 404 Error not found...
Dan/Bytemaster asked for me to do daily updates, but I don't really see the point, nor is it obvious to me how to translate detailed bugs addressed on a daily basis into a digestible form. If you want daily updates, here's the best place:

https://github.com/InvictusInnovations/keyhotee/issues?state=open

We're using github to track every bug fix and feature being added. Ideally, I think a written update should be delivered about once a week.

We're planning to release a new Linux and Windows version within the next day or three, depending on how the static build for Linux goes tomorrow. The hold up, as I mentioned a few posts above is that we've kept finding additional dependencies that we don't want to rely on in the base Linux system (today, we ended up adding libssl as a static lib to avoid that dependency). I think we're done at this point, so probably the release will be late tomorrow.

As far as the link being broken, I've got no idea about that personally, but I'd guess it has something to do with the fact that the web site is in progress of being updated/moved. For sure, we'll have new links soon anyways, so it's probably not worth downloading the old alpha at this point.

Title: Re: Keyhotee Status Update
Post by: Pocket Sand on January 31, 2014, 03:18:36 am
I use to be a Invictus investor and very bullish on the PTS shares, but I recently pulled out with the steep decline in PTS price coupled with the confusion around AngelShares and not knowing which I should be holding on to. I am still very interested in seeing you succeed and and be first to deploy but honestly there is a lot more competition from Nxt, MasterCoin, Ethereum.

Its not exactly the thread to discuss this, but it's coming out with the frustration on failing to deliver on Keyhotee, and as I check back what I am seeing.

There is still issues with Keyhotee that I find unacceptable if Invictus wants to be competitive, reputable organization:

  • Dan/Bytemaster mentioned they aim for daily status updates 7 days ago. They missed 6 out of 7 of those daily status updates.
  • What about the Keyhotee Windows build?
  • The download for alpha keyhotee is not working. I clicked the .zip file on the first page of this thread and it goes to 404 Error not found...

Can you please fix these and be more transparent in communication, and delivery. Thanks.
Sorry what has ethereum actually delivered thus far that you're crediting being first to deploy/more efficient dev? Also mastercoin has had a lot more money for a lot longer of a time and still has yet to have a solid release, nxt is an interesting concept but they have not yet delivered on many promises.Dan has already established an alpha release for bitshares and keyhotee, while moved back, is still scheduled to be released soon.
Title: Re: Keyhotee Status Update
Post by: bytemaster on January 31, 2014, 05:17:22 am
I use to be a Invictus investor and very bullish on the PTS shares, but I recently pulled out with the steep decline in PTS price coupled with the confusion around AngelShares and not knowing which I should be holding on to. I am still very interested in seeing you succeed and and be first to deploy but honestly there is a lot more competition from Nxt, MasterCoin, Ethereum.

Its not exactly the thread to discuss this, but it's coming out with the frustration on failing to deliver on Keyhotee, and as I check back what I am seeing.

There is still issues with Keyhotee that I find unacceptable if Invictus wants to be competitive, reputable organization:

  • Dan/Bytemaster mentioned they aim for daily status updates 7 days ago. They missed 6 out of 7 of those daily status updates.
  • What about the Keyhotee Windows build?
  • The download for alpha keyhotee is not working. I clicked the .zip file on the first page of this thread and it goes to 404 Error not found...

Can you please fix these and be more transparent in communication, and delivery. Thanks.
From what I see the download of Keyhotee from the website is working just fine, if this thread is out of date then I am sure a mod can fix it.   

Everyone knew we were at the conference in Miami and we posted every day from the event, of course you cannot expect new software development from me during that time.


Title: Re: Keyhotee Status Update
Post by: dannotestein on February 01, 2014, 02:18:52 am
Keyhotee Alpha 3 release for Linux is here: http://invictus.io/keyhotee.php
We're still working to make it compatible with more versions of Linux, so please let us know if it doesn't run on your system.
Title: Re: Keyhotee Status Update
Post by: AdamBLevine on February 01, 2014, 12:44:08 pm

Dan/Bytemaster asked for me to do daily updates, but I don't really see the point, nor is it obvious to me how to translate detailed bugs addressed on a daily basis into a digestible form. If you want daily updates, here's the best place:


The point is that you were asked in public to do it, and then you didn't.    It goes to further reinforce the impression that Bytemaster has no real ability to make any commitments even over the short term because his employees do not follow his instructions.   

As a project lead, when you tell people you'll do something and then don't do it, they stop believing you when you say you'll do something.  You are training Invictus investors to not trust invictus.  When Bytemaster requests something, either do it or to lodge your complaint early so the situation can be corrected, your decision to just not has obvious and predictable consequences.   

If I were you, I'd say "January 31st - Fixing Bugs today, dealing with a bad one in linux dependencies.  Looking like we're on schedule to have the latest version out in a week barring show-stopping bugs"

Thats it

Two sentences per day, I now have some idea what's happening and I know that the schedule has not changed.  It also fulfills what Bytemaster publicly committed to.
Title: Re: Keyhotee Status Update
Post by: valtr on February 01, 2014, 02:20:53 pm
I was able to run Keyhotee on Ubuntu 12.04 64 bit and 13.10 64 bit.
Title: Re: Keyhotee Status Update
Post by: toast on February 01, 2014, 02:24:50 pm

Dan/Bytemaster asked for me to do daily updates, but I don't really see the point, nor is it obvious to me how to translate detailed bugs addressed on a daily basis into a digestible form. If you want daily updates, here's the best place:


The point is that you were asked in public to do it, and then you didn't.    It goes to further reinforce the impression that Bytemaster has no real ability to make any commitments even over the short term because his employees do not follow his instructions.   

As a project lead, when you tell people you'll do something and then don't do it, they stop believing you when you say you'll do something.  You are training Invictus investors to not trust invictus.  When Bytemaster requests something, either do it or to lodge your complaint early so the situation can be corrected, your decision to just not has obvious and predictable consequences.   

If I were you, I'd say "January 31st - Fixing Bugs today, dealing with a bad one in linux dependencies.  Looking like we're on schedule to have the latest version out in a week barring show-stopping bugs"

Thats it

Two sentences per day, I now have some idea what's happening and I know that the schedule has not changed.  It also fulfills what Bytemaster publicly committed to.


It may be sufficient to just post this link to this thread every day, and some days you will naturally want to say more
https://github.com/InvictusInnovations/keyhotee/commits/master
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 01, 2014, 04:27:12 pm
I'm not sure how everyone else receives messages on the forum, but every time I post to a topic, afterwards I get a message in my email box every time someone else posts to that topic.

Ideally, I'd like my posts to trigger emails to people when I've actually posted something of reasonable significance, like "we've found a serious bug alpha testers should be aware of" or "we've got a new release for testing" or even "the schedule for delivery has changed". In other words, I want to reserve this thread for more substantial announcements that are of interest to all Keyhotee fans and should probably trigger some action on their part.

I understand that there are people who actually want to know on a day-to-day basis what's changed in the software. To meet this desire, I've modified the original head post for this thread with useful links to the commit repo (a modified form of toast's suggestion). The data there gets updated on a daily basis (or rather, as soon as a change is made) and it's all done automatically as changes are made to the code.
Title: Re: Keyhotee Status Update
Post by: AdamBLevine on February 01, 2014, 04:34:30 pm
I'm not sure how everyone else receives messages on the forum, but every time I post to a topic, afterwards I get a message in my email box every time someone else posts to that topic.

Ideally, I'd like my posts to trigger emails to people when I've actually posted something of reasonable significance, like "we've found a serious bug alpha testers should be aware of" or "we've got a new release for testing" or even "the schedule for delivery has changed". In other words, I want to reserve this thread for more substantial announcements that are of interest to all Keyhotee fans and should probably trigger some action on their part.

I understand that there are people who actually want to know on a day-to-day basis what's changed in the software. To meet this desire, I've modified the original head post for this thread with useful links to the commit repo (a modified form of toast's suggestion). The data there gets updated on a daily basis (or rather, as soon as a change is made) and it's all done automatically as changes are made to the code.

You realize the only issue is that daily updates were explicitly promised and then routinely and repeatedly not delivered with no explanation?
Title: Re: Keyhotee Status Update
Post by: CryptoN8 on February 01, 2014, 04:39:10 pm
Thanks for the update. Another suggestion on build releases would be to have the most recent version/build/platform with the released date linked in the OP. It makes it much easier to find and not have to dig through pages or be sent to another site. Keep up the great work, this is very exciting stuff.
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 01, 2014, 05:01:48 pm
Thanks for the update. Another suggestion on build releases would be to have the most recent version/build/platform with the released date linked in the OP.
I plan to do that soon actually, I just want to make this a "staged" release. In other words, first I just post here, where the most intrepid will download, then if we don't get a barrage of error reports, I'll add a link to the original posting.
Title: Re: Keyhotee Status Update
Post by: ppimp on February 01, 2014, 05:43:47 pm
Adam hits the nail on the head.
Taking 5 minutes out of your day and giving everyone one an update is extremely easy to do, and as you can tell goes along way. Keep in mind, Invictus has FAILED to deliver on their commitment and time frame. Why else do you think we ware asking?

Listen, if you guys could just pick a date, commit to that date, and release on that date. I wouldn't even want a status update. Also I never even wanted daily status updates. That's something that the CEO OF THE COMPANY asked you to do in public, and not only you refused, you are arguing with your investors on WHY YOU FEEL you shouldn't do it.

How do I have faith in such a company? Couple that with the fact that you are not the only game in town now. That's why I brought up the other alt-technologies. Mastercoin already has a DATE for distributed exchange (bitshares) and a website with a countdown clock. Whats the date for bitshares release I have no idea?

Again I was very very bullish on Invictus because the idea's Dan espoused (especially on LTB) at the time, was much earlier and advanced than anyone else. Unfortunately they were not able to deliver.

I suggest you all come up with a date of a release, a formal plan on communication, and stick to it like a professional organization.

Thanks
Title: Re: Keyhotee Status Update
Post by: ppimp on February 01, 2014, 05:49:21 pm
Finally you guys are asking to be a DAC or corporation, so you need to start acting like it. YOu have millions of dollars in investor funds. This isn't a fun open-source side project.

Furthermore, Dan you have likened yourself and organization to Apple, or what Apple has done. And you call Invictus a corporation. Imagine if Apple had the same debacle with a release of one of their flagship products.

No one is asking you to get things in early or fast or whatever. You guys chose New Years Eve. What i'm asking you is whatever time you need take it. But you need to be consistent and professional, and the way you are running the keyhotee release (your first product) is far from it...
Title: Re: Keyhotee Status Update
Post by: James212 on February 01, 2014, 05:57:43 pm
+1
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 01, 2014, 07:01:31 pm
Listen, if you guys could just pick a date, commit to that date, and release on that date. I wouldn't even want a status update. Also I never even wanted daily status updates. That's something that the CEO OF THE COMPANY asked you to do in public, and not only you refused, you are arguing with your investors on WHY YOU FEEL you shouldn't do it.
So, you don't think it's reasonable for me to explain why I disagree with generating daily status reports or to propose an alternate method of delivering this information? Invictus isn't a dictatorship. We debate issues like this, then move ahead. Unlike most companies, we don't do it behind closed doors, we do it here on the forums, so that others have a chance to at least contribute their opinions. I apologize to anyone who's upset that I didn't register my disagreement on this issue earlier, but I hope I've provided a solution to this issue that should work for those who want daily information about Keyhotee and those who don't. I'm sure I'm not going to make you happy, but it's pretty clear from your 3 posts so far to bitshares.org that you're not a supporter of bitshares, and I personally believe that you're actively working against our success.

As far as dates go for a release of Keyhotee with a blockchain attached, there's two separate issues that will dictate the release date: when we've collected all the Keyhotee Founder Id registrations we think we're can reasonably collect and when the software has a reasonable set of initial features and sufficient stability. The first issue is somewhat outside of our complete control, of course, although the alpha releases we put out do affect it. Right now our goal is release the blockchain version of Keyhotee by the end of February, but I'm certainly not promising that date, it's just my best estimate with the current information I have. Initial releases of software aren't like follow-on releases: after you've released a stable product, it's typically not so difficult to estimate the impact of incremental changes to the product, but in the initial stages of new software it's possible to overlook major issues that delay releases.
Title: Re: Keyhotee Status Update
Post by: ppimp on February 01, 2014, 07:23:15 pm
Well I appreciate your viewpoint, and I am not working against your success. I am expressing my frustration, and maybe expecting too much.

I've actually been a longtime lurker on this forum and have finally created an account to express that i'm upset.

And to disapprove your accusation that I have ulterior intentions:

Go to www.reddit.com and look up my name (PPimP) you will see a post I made in r/letstalkbitcoin on Episode 57 where Dan has a interview and in that thread, I ask where can I purchase protoshares? That post was 2 months ago.

Which pretty much verifies everything I've said in my 3 posts...
Title: Re: Keyhotee Status Update
Post by: AdamBLevine on February 01, 2014, 07:44:13 pm
Listen, if you guys could just pick a date, commit to that date, and release on that date. I wouldn't even want a status update. Also I never even wanted daily status updates. That's something that the CEO OF THE COMPANY asked you to do in public, and not only you refused, you are arguing with your investors on WHY YOU FEEL you shouldn't do it.
So, you don't think it's reasonable for me to explain why I disagree with generating daily status reports or to propose an alternate method of delivering this information? Invictus isn't a dictatorship. We debate issues like this, then move ahead. Unlike most companies, we don't do it behind closed doors, we do it here on the forums, so that others have a chance to at least contribute their opinions. I apologize to anyone who's upset that I didn't register my disagreement on this issue earlier, but I hope I've provided a solution to this issue that should work for those who want daily information about Keyhotee and those who don't. I'm sure I'm not going to make you happy, but it's pretty clear from your 3 posts so far to bitshares.org that you're not a supporter of bitshares, and I personally believe that you're actively working against our success.

As far as dates go for a release of Keyhotee with a blockchain attached, there's two separate issues that will dictate the release date: when we've collected all the Keyhotee Founder Id registrations we think we're can reasonably collect and when the software has a reasonable set of initial features and sufficient stability. The first issue is somewhat outside of our complete control, of course, although the alpha releases we put out do affect it. Right now our goal is release the blockchain version of Keyhotee by the end of February, but I'm certainly not promising that date, it's just my best estimate with the current information I have. Initial releases of software aren't like follow-on releases: after you've released a stable product, it's typically not so difficult to estimate the impact of incremental changes to the product, but in the initial stages of new software it's possible to overlook major issues that delay releases.

I think it's in really poor taste to not take responsibility for the issue you caused here Dan and instead attack a former investor.   The reason why I spend my time trying to help you guys see when you've gone astray is because I am not the only one with this opinion, i'm the average non-dyed-in-the-wool skeptical investor and you guys are making me want to not be one because you continue to fail to perform as you yourself predict.

Personally I don't think it's appropriate to direct investors to GitHub to look at change-dates or whatever, they are investors and given the inability to deliver to a self-set schedule so far I now actually want daily updates just to see if it's possible for Invictus to perform at this basic level.

You are destroying the trust that remains in Invictus, and it would be great if you could stop that.

So given you know who I am, am I also working against your success?    So far you only seem willing to respond to critiques that follow on my original critiques and respond to me indirectly, I find that a little discouraging for such a transparent company.     I really hope you'll do the right thing.
Title: Re: Keyhotee Status Update
Post by: onceuponatime on February 01, 2014, 07:56:34 pm
I am a Keyhoteed Founder and an early and frequent investor in Angelshares.

I am completely in concurrence with AdamBLevine's recent posts in this thread. I came to know of Invictus through Lets Talk Bitcoin, and I think it unconscionable that Adam's points were not responded to directly, but at one remove.

Title: Re: Keyhotee Status Update
Post by: oco101 on February 01, 2014, 08:11:58 pm
Listen, if you guys could just pick a date, commit to that date, and release on that date. I wouldn't even want a status update. Also I never even wanted daily status updates. That's something that the CEO OF THE COMPANY asked you to do in public, and not only you refused, you are arguing with your investors on WHY YOU FEEL you shouldn't do it.
So, you don't think it's reasonable for me to explain why I disagree with generating daily status reports or to propose an alternate method of delivering this information? Invictus isn't a dictatorship. We debate issues like this, then move ahead. Unlike most companies, we don't do it behind closed doors, we do it here on the forums, so that others have a chance to at least contribute their opinions. I apologize to anyone who's upset that I didn't register my disagreement on this issue earlier, but I hope I've provided a solution to this issue that should work for those who want daily information about Keyhotee and those who don't. I'm sure I'm not going to make you happy, but it's pretty clear from your 3 posts so far to bitshares.org that you're not a supporter of bitshares, and I personally believe that you're actively working against our success.
I agree that Invictus it is very open and we all appreciated you transparency as a company. This it is one of the reason we have trust in bytemaster and the full 3I team. Indeed you provided a good solution about the daily updates and this should solve the problem you are a programmer after all . I have no doubt that all of you are doing a amazing job and advancing as quickly as you on can in all fronts. Keep up the good work !!!
But you said   "Unlike most companies, we don't do it behind closed doors, we do it here on the forums, so that others have a chance to at least contribute their opinions." And that exactly what PPimp and AdamBLevine are doing and I have to agree with all the other points they make. I don't see any accusations they are simply pointing  up some facts that should be taken in consideration.
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 01, 2014, 08:22:48 pm

I think it's in really poor taste to not take responsibility for the issue you caused here Dan and instead attack a former investor.   The reason why I spend my time trying to help you guys see when you've gone astray is because I am not the only one with this opinion, i'm the average non-dyed-in-the-wool skeptical investor and you guys are making me want to not be one because you continue to fail to perform as you yourself predict.

Personally I don't think it's appropriate to direct investors to GitHub to look at change-dates or whatever, they are investors and given the inability to deliver to a self-set schedule so far I now actually want daily updates just to see if it's possible for Invictus to perform at this basic level.

You are destroying the trust that remains in Invictus, and it would be great if you could stop that.

So given you know who I am, am I also working against your success?    So far you only seem willing to respond to critiques that follow on my original critiques and respond to me indirectly, I find that a little discouraging for such a transparent company.     I really hope you'll do the right thing.
Hi Adam,

I thought I had responded to your previous post, even though I didn't directly quote you. In your previous post, you said:
You realize the only issue is that daily updates were explicitly promised and then routinely and repeatedly not delivered with no explanation?
I apologized to those who were upset with me not immediately expressing my disagreement with the idea of a daily status update, and I assumed it was obvious that you were one such person. I further assumed that was taking responsibility for the issue. If it's part of forum etiquette I wasn't aware of to always include a direct quote when responding to a post, I apologize for that too, I wasn't aware of it, perhaps as I haven't traditionally used forum posting as a major communications means. As far as your statement goes, you were correct, as soon as I read Dan's post requesting it, I should have responded with my reasons why I think it's not a useful way to communicate the development of software. To me, there's no obvious way to summarize a set of changes made every day to software that will benefit anyone. If the commit comments aren't clear enough to non-progammers (and I'm sure they're not always clear), at least commits should be quite a bit of reassurance that work is actively being performed by a number of individuals at a fairly constant rate.
Title: Re: Keyhotee Status Update
Post by: AdamBLevine on February 01, 2014, 08:42:00 pm
To be clear, neither you nor anyone else will be providing daily updates?   I believe it would do a lot to restore confidence if that were to happen instead of being another initiative announced and abandoned with little fanfare.
Title: Re: Keyhotee Status Update
Post by: ppimp on February 01, 2014, 08:42:40 pm
Dan,
 To your point, this is not a dictatorship, so why if YOU are the only one here who does not feel their should be a daily status update. Then there should not be one. Isn't that a dictatorship?

I want to express to you that Invictus is unfortunately not in a good position and does not have a good track record. Remember that the current value and worth is based on investors and their speculation. That speculation is based on what we see, hear, and feel about the companies ability to deliver. I want to list out for you the current status of Invictus, and I do this not to take away from your success. But I do this to make you realize that since you are not in a good position, you should go ABOVE and BEYOND in terms of meeting the requests of the stakeholders in your company. I want you to see the perspective from an early adopter and protoshares investor:


So I bring all this up, because I ask you. As a investor. How am I supposed to speculate on the given success of Invictus. Given that now i'm still interested, come on your website to share my frustration, and get attacked as a conspirator and get abrasive responses.

You guys should really hire someone to handle PR/Customer Relations.

(I apologize if any of my facts were incorrect, and welcome factual evidence based corrections) :)
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 01, 2014, 09:04:29 pm
Dan,
 To your point, this is not a dictatorship, so why if YOU are the only one here who does not feel their should be a daily status update. Then there should not be one. Isn't that a dictatorship?
No, I'm not saying there shouldn't be a daily status update. I've given links to provide the best possible daily status update that I can think of to provide. If someone has a better way to do it, I still haven't heard it.

Quote
So I bring all this up, because I ask you. As a investor. How am I supposed to speculate on the given success of Invictus. Given that now i'm still interested, come on your website to share my frustration, and get attacked as a conspirator and get abrasive responses.

You guys should really hire someone to handle PR/Customer Relations.

(I apologize if any of my facts were incorrect, and welcome factual evidence based corrections) :)
I'm not our marketing manager, so it probably isn't appropriate for me to respond in detail to your view of Invictus's success or failure to date: I'm supposed to be spending my time heading up Keyhotee software development (and since we don't stop for weekends, its what I've been doing between all these posts). I do feel free to say that I'm personally a significant and ongoing donator to the AngelShares fund, because I do believe strongly in Invictus's goals and potential. Perhaps to you, Invictus has been moving slowly, but from my own 25+ years experience in software development, Invictus is moving very rapidly from a very small start. Our team is growing at a reasonable, steady pace, and AngelShares has really opened up the possibility for more rapid growth in the future.
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 01, 2014, 09:11:52 pm
To be clear, neither you nor anyone else will be providing daily updates?   I believe it would do a lot to restore confidence if that were to happen instead of being another initiative announced and abandoned with little fanfare.
I've given links to provide the best possible daily status update that I can think of to provide. I'm not trying to be disingenuous here: I simply don't know a better way to summarize a day's programming work. Generally, major changes in software don't happen in one day.
Title: Re: Keyhotee Status Update
Post by: rysgc on February 01, 2014, 09:24:19 pm
I understand it's hard to give daily updates, after all the majority won't be interested in every little bug fix or small new feature in the likes of 'Look now you can add a hyperlink to a message'. On the other hand people are desperately waiting for a steady release and might get impatient or look somewhere else if there aren't any updates available. That being said I think there are better ways for people to solve this then to start a flame thread which might make things worse.

Maybe it's an idea to just create a simple list online (split in work items and bugfixes) build from your todo list and break it down to easy to digest parts so it's clear for everyone, if possible even with an expected delivery date. Whenever something is finished just mark it as completed and point the people to the updated document online once or twice a week. So at least it's clear what's to come and where you're standing in the development process.

Note to my self: I have to do this as well for KIDARC  :-[
Title: Re: Keyhotee Status Update
Post by: AdamBLevine on February 01, 2014, 09:24:43 pm

Dan/Bytemaster asked for me to do daily updates, but I don't really see the point, nor is it obvious to me how to translate detailed bugs addressed on a daily basis into a digestible form. If you want daily updates, here's the best place:


If I were you, I'd say "January 31st - Fixing Bugs today, dealing with a bad one in linux dependencies.  Looking like we're on schedule to have the latest version out in a week barring show-stopping bugs"

Thats it


Maybe you're thinking I mean "Blog post" - I do not.  I mean an update so when something goes awry we see it that day instead of at some arbitrary point in the future you decide to publicly talk about it.
Two sentences per day, I now have some idea what's happening and I know that the schedule has not changed.  It also fulfills what Bytemaster publicly committed to.
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 01, 2014, 09:32:12 pm
Maybe it's an idea to just create a simple list online (split in work items and bugfixes) build from your todo list and break it down to easy to digest parts so it's clear for everyone, if possible even with an expected delivery date. Whenever something is finished just mark it as completed and point the people to the updated document online once or twice a week. So at least it's clear what's to come and where you're standing in the development process.
Essentially that's what the github links are. We have a list of issues, which are either new features we need to add or bugs that we need to fix. We also have a wiki page where the design is laid out over the long term and should be more static (this latter needs a lot of work still, and I hoped to spend time on it today, hence I haven't wanted to add an explicit link to it yet). Now github may not be the best system for this, but it's what we've had to work with so far. It's been working reasonably well for coordinating a geographically distributed team. I know that other guys at Invictus are currently working on rolling out a potentially better system, but I'm not directly involved in that effort, I'll just be a consumer once it's done.
Title: Re: Keyhotee Status Update
Post by: oco101 on February 01, 2014, 09:37:48 pm

  • Invictus first release was Protoshares. The innovation that was introduced was the Proof-Of-Work algorithm that was supposed to be hardened or resistant based on memory bus speeds. However this was not successful.
  • Protoshares was also not the most ideal form of crowd-funding for the company so they confused the matter and hurt early adopters  of Protoshares by introducing AngelShares. Regardless of how the math works out, introducing another form of investment seed into the company confused/goes back on the social contract.
  • Invictus planned to release keyhotee the first product on NYE 2013. That was not a success. The next status and estimate was late January. That was not a success. Now you are saying end of february, without a hard committal date.
  • Invictus plans on releasing bitshares its real first claim to fame, and one of the first originators of distributed exchange concept. Here we have no real idea where they are in development, and what the release date is. Meanwhile we have other big ventures competing in the space WITH a release date

-Protoshare Gpu mining is is just a little better that CPU mining, so to me this was a success.
-How AngelShare hurt Protoshare investors ? Now you got a much better deal as a protoshare holder  then before. The only unhappy protoshare holders are those that wanted to make a quick profit and view protoshare as another altcoin.  Angelshares actualy helps protoshare holders in the long run. The AGS founds will be use to help  DAC industry. Now 3I could do a lot more then before and this give protoshare much more value then ever, more founds more DAC's more developer, more marketing more of everything.
-I think we a have a real idea  on the bitshares developments and the timeline. Daily updates are here : https://bitsharestalk.org/index.php?topic=1890.0
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 01, 2014, 09:48:47 pm

If I were you, I'd say "January 31st - Fixing Bugs today, dealing with a bad one in linux dependencies.  Looking like we're on schedule to have the latest version out in a week barring show-stopping bugs"

Thats it


Quote
Maybe you're thinking I mean "Blog post" - I do not.  I mean an update so when something goes awry we see it that day instead of at some arbitrary point in the future you decide to publicly talk about it.
Two sentences per day, I now have some idea what's happening and I know that the schedule has not changed.  It also fulfills what Bytemaster publicly committed to.
Ok, here's today's post: We're currently planning to release a blockchain version around Feb 28th. We'll also be releasing a Windows alpha 3 release soon and very probably an OSX release, pending positive feedback on the Linux 3 alpha release from yesterday.
Title: Re: Keyhotee Status Update
Post by: AdamBLevine on February 01, 2014, 09:56:12 pm
 +5%
Title: Re: Keyhotee Status Update
Post by: ppimp on February 01, 2014, 10:14:55 pm
Guys hope I didn't come off as too harsh, but I played devils advocate on purpose, and appreciate the responses I got. Thanks.
Title: Re: Keyhotee Status Update
Post by: onceuponatime on February 01, 2014, 10:41:15 pm
Thanks Dan. You nu have inspired me to donate for more AGS   :)
Title: Re: Keyhotee Status Update
Post by: CryptoN8 on February 02, 2014, 05:34:24 am

If I were you, I'd say "January 31st - Fixing Bugs today, dealing with a bad one in linux dependencies.  Looking like we're on schedule to have the latest version out in a week barring show-stopping bugs"

Thats it


Quote
Maybe you're thinking I mean "Blog post" - I do not.  I mean an update so when something goes awry we see it that day instead of at some arbitrary point in the future you decide to publicly talk about it.
Two sentences per day, I now have some idea what's happening and I know that the schedule has not changed.  It also fulfills what Bytemaster publicly committed to.
Ok, here's today's post: We're currently planning to release a blockchain version around Feb 28th. We'll also be releasing a Windows alpha 3 release soon and very probably an OSX release, pending positive feedback on the Linux 3 alpha release from yesterday.
I think this is a great start. I know that it's hard to provide daily updates in layman's terms with all the intricacy of programming, but I think that short updates like this will go a long way. I can see that you are trying to convey your progress in the most efficient method utilizing a tool that you are most likely in a good portion of your day. I can respect that thought process and using the status updates on GitHub, while does provide the most accurate metric for progress, it does not give the distilled down one or two sentences that I think many would like to see going forward. I know I like to receive the email alert that there is an update to this thread, and for many, that is the extent they are wanting to go to get an update. Digging around at another location and having to translate progress does not have much appeal for the non-programmer types. This is not a slight or jab at you directly or programmers, I'm just providing feedback, another point of view. I'm more of the IT Manager/Investor type so I can see both sides. I think you are doing a great job, appreciate the work you are doing, and very excited to see the final product when released.
Title: Re: Keyhotee Status Update
Post by: CalabiYau on February 02, 2014, 07:47:17 am
Ok, here's today's post: We're currently planning to release a blockchain version around Feb 28th. We'll also be releasing a Windows alpha 3 release soon and very probably an OSX release, pending positive feedback on the Linux 3 alpha release from yesterday.

Thank you for clarification and the update.
The culture of communications are discussed in an open space. This process is a development too. As an investor, my trust in the capabilities and commitment of this development team are all intact.
I am still convinced that this professional, steady process in financing and
development will give this project(s) an edge in the future. 
Title: Re: Keyhotee Status Update
Post by: bytemaster on February 03, 2014, 02:47:35 am
Dan lost internet connection tonight so asked me to post his update.   He took the day off to celebrate his birthday with family.
Title: Re: Keyhotee Status Update
Post by: oco101 on February 03, 2014, 04:31:19 am
Happy birthday Dan  !!!!!
Title: Re: Keyhotee Status Update
Post by: codinat on February 03, 2014, 05:14:42 am
Dan,生日快乐!
Title: Re: Keyhotee Status Update
Post by: alt on February 03, 2014, 05:51:59 am
丹,生日快乐!

Sent from my Lenovo K860i using Tapatalk 2

Title: Re: Keyhotee Status Update
Post by: Pocket Sand on February 03, 2014, 07:21:00 am
Happy birthday Dan
Title: Re: Keyhotee Status Update
Post by: xeroc on February 03, 2014, 10:35:24 am
+5% ??
Title: Re: Keyhotee Status Update
Post by: Ykw on February 03, 2014, 10:55:55 pm
Best time to loose internet connection ever =) happy birthday...

 +5% +5% +5% +5% +5% = 25%! :=)
Title: Re: Keyhotee Status Update (Important one for all Keyhotee Founder ID owners)
Post by: dannotestein on February 04, 2014, 02:19:48 am
While Keyhotee IDs are not generally meant to be "case-sensitive", we've recently determined that they are case-sensitive in one aspect: when you create an identity, the exact string you type for your KeyhoteeID is used to generate the associated public key. For example, if your ID was "alpha" and you create your identity on one machine as "alpha" and on another as "Alpha", they will generate different public keys, even when you use the same brainwallet password. So don't do that :-)

We thought about changing this functionality, but it would require many people to re-register and it didn't seem like a big burden for users to remember the capitalization they used for their ID as well as their brainwallet password.

A related bug is that the current client allows two such identities to be created in one profile. We've fixed this bug in the repo, and the fix will be incorporated into new builds we plan to put up in the next day or two.
Title: Re: Keyhotee Status Update
Post by: codinat on February 04, 2014, 08:49:52 am
Dan,keyhotee是于2月28日之前上线?还是28日当天和bts同时发布?谢谢
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 04, 2014, 02:10:59 pm
Dan,keyhotee是于2月28日之前上线?还是28日当天和bts同时发布?谢谢
The 28th is just a rough estimate of the date we plan to go live with the blockchain. It could before or after, it's not necessarily synchronized  with bts, although there may be some advantages to a simultaneous release. Mainly, we have to be sure that all the registration issues are out of the way before we release a blockchain, since we would rather not to have to restart the chain.
Title: Re: Keyhotee Status Update
Post by: toast on February 04, 2014, 02:29:42 pm
Dan,keyhotee是于2月28日之前上线?还是28日当天和bts同时发布?谢谢
The 28th is just a rough estimate of the date we plan to go live with the blockchain. It could before or after, it's not necessarily synchronized  with bts, although there may be some advantages to a simultaneous release. Mainly, we have to be sure that all the registration issues are out of the way before we release a blockchain, since we would rather not to have to restart the chain.

!!!
BTS has a hard dependency on keyhotee genesis block!

https://bitsharestalk.org/index.php?topic=2591.msg32999#msg32999
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 04, 2014, 02:57:07 pm
Dan,keyhotee是于2月28日之前上线?还是28日当天和bts同时发布?谢谢
The 28th is just a rough estimate of the date we plan to go live with the blockchain. It could before or after, it's not necessarily synchronized  with bts, although there may be some advantages to a simultaneous release. Mainly, we have to be sure that all the registration issues are out of the way before we release a blockchain, since we would rather not to have to restart the chain.

!!!
BTS has a hard dependency on keyhotee genesis block!

https://bitsharestalk.org/index.php?topic=2591.msg32999#msg32999
Yep, I read that a while back, but it's never been clear to me how having Keyhotee blockchain impacts bts. You need to have created your KH key pair and sent us your founder public key, but that info will be registered into the bts blockchain, not the KH blockchain, and will be controlled by a bts wallet.
Title: Re: Keyhotee Status Update
Post by: toast on February 04, 2014, 03:46:12 pm
Dan,keyhotee是于2月28日之前上线?还是28日当天和bts同时发布?谢谢
The 28th is just a rough estimate of the date we plan to go live with the blockchain. It could before or after, it's not necessarily synchronized  with bts, although there may be some advantages to a simultaneous release. Mainly, we have to be sure that all the registration issues are out of the way before we release a blockchain, since we would rather not to have to restart the chain.

!!!
BTS has a hard dependency on keyhotee genesis block!

https://bitsharestalk.org/index.php?topic=2591.msg32999#msg32999
Yep, I read that a while back, but it's never been clear to me how having Keyhotee blockchain impacts bts. You need to have created your KH key pair and sent us your founder public key, but that info will be registered into the bts blockchain, not the KH blockchain, and will be controlled by a bts wallet.

Right so the blockchain doesn't have to actually launch but you need to know exactly what keys will go in it, which means we need binaries for osx and linux (most recent one I tried ~1 week ago wasn't working)
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 04, 2014, 04:16:30 pm
Dan,keyhotee是于2月28日之前上线?还是28日当天和bts同时发布?谢谢
The 28th is just a rough estimate of the date we plan to go live with the blockchain. It could before or after, it's not necessarily synchronized  with bts, although there may be some advantages to a simultaneous release. Mainly, we have to be sure that all the registration issues are out of the way before we release a blockchain, since we would rather not to have to restart the chain.

!!!
BTS has a hard dependency on keyhotee genesis block!

https://bitsharestalk.org/index.php?topic=2591.msg32999#msg32999
Yep, I read that a while back, but it's never been clear to me how having Keyhotee blockchain impacts bts. You need to have created your KH key pair and sent us your founder public key, but that info will be registered into the bts blockchain, not the KH blockchain, and will be controlled by a bts wallet.

Right so the blockchain doesn't have to actually launch but you need to know exactly what keys will go in it, which means we need binaries for osx and linux (most recent one I tried ~1 week ago wasn't working)
Yep, we'll definitely have new binaries out for osx and linux soon.
Title: Re: Keyhotee Status Update
Post by: slacking on February 04, 2014, 08:58:20 pm
I almost hate to venture an opinion on how update notifications should be done since emotions seem to be running high on this issue BUT, for me personally, going to Github to see issues outstanding seems like a much better way of tracking progress than to detail them on this forum. The issue I do have, is when clicking on the milestones tab at https://github.com/InvictusInnovations/keyhotee/issues there isn't any relevent information about the milestones. For example, the two milestones listed are "End Of Year" and "Milestone II", neither have due dates or explanations of what was hoping to be accomplished in them. Also, there isn't a milestone roadmap so to speak (and I'm not a developer) but shouldn't there be a listing of all anticipated milestones, something like:


I know these aren't the real steps of software development but hopefully everyone gets the idea. The idea being a comprehensive milestone roadmap that we can follow using Github.
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 04, 2014, 09:13:42 pm
I almost hate to venture an opinion on how update notifications should be done since emotions seem to be running high on this issue BUT, for me personally, going to Github to see issues outstanding seems like a much better way of tracking progress than to detail them on this forum. The issue I do have, is when clicking on the milestones tab at https://github.com/InvictusInnovations/keyhotee/issues there isn't any relevent information about the milestones. For example, the two milestones listed are "End Of Year" and "Milestone II", neither have due dates or explanations of what was hoping to be accomplished in them. Also, there isn't a milestone roadmap so to speak (and I'm not a developer) but shouldn't there be a listing of all anticipated milestones, something like:

  • Milestone 1 - Requirements analysis
  • Milestone 2 - Coding of non-gui elements
  • Milestone 3 - Coding of gui
  • Milestone 4 - 1st round beta testing
  • Milestone 5 - Fix bugs from beta 1
  • Milestone 6 - 2nd round of beta testing
  • Milestone 7 - Fix bugs from beta 2
  • Milestone 8 - Implement enhancements
  • Milestone 9 - Final testing and bug fixes
  • Milestone 10 - Alpha release

I know these aren't the real steps of software development but hopefully everyone gets the idea. The idea being a comprehensive milestone roadmap that we can follow using Github.
Something along these lines (well, with quite a few less milestones, but you've got the general idea) was what I was planning on adding and transcribing from my paper notes this last weekend. It's hard to do something like this in the middle of the week as I get more interruptions then, typically. Still, I'm trying to fit github updates in this week as time permits. The primary thing I need to do is make sure all our programmers have relevant work to do so they don't idle, but I hope to soon have up a clearer roadmap for at least the next month of work.
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 06, 2014, 03:57:11 am
Planning to release Windows alpha 0.5.3 tomorrow night, barring any issues popping up. Next major feature to implement is database versioning, I want to get this in ASAP to give us more flexibility with regards to profile data structures.
Title: Re: Keyhotee Status Update
Post by: CryptoN8 on February 06, 2014, 04:32:56 am
Planning to release Windows alpha 0.5.3 tomorrow night, barring any issues popping up. Next major feature to implement is database versioning, I want to get this in ASAP to give us more flexibility with regards to profile data structures.
Good to hear, look forward to playing with it. Thanks.
Title: Re: Keyhotee Status Update
Post by: bytemaster on February 06, 2014, 08:35:07 am
Today I attempted to build the Mac version of Keyhotee only to find that the updates to the build system for UNIX did not apply to apple.   I finally got things compiled but my hacks are not friendly to build on UNIX so I will need to do some work clean up the build so it works in both places.

I need to recompile boost with clang++ and then I should be able to get a mac binary out.
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 07, 2014, 02:37:23 am
Alpha 3 release for Windows is available at http://invictus.io/bin/keyhotee_0.5.3.zip. I expect it will be at least a week before we put up another Windows alpha.

I've also updated the Keyhotee Founder ID registration server with names collected from web form (if you registered via the web form in last 12 hours, your registration might not be there). You can check if your Founder ID is correctly registered by running Keyhotee and verifying that "points" are displayed in the contact records for your Founder identity.
Title: Re: Keyhotee Status Update
Post by: CryptoN8 on February 07, 2014, 07:05:27 am
Alpha 3 release for Windows is available at http://invictus.io/bin/keyhotee_0.5.3.zip. I expect it will be at least a week before we put up another Windows alpha.

I've also updated the Keyhotee Founder ID registration server with names collected from web form (if you registered via the web form in last 12 hours, your registration might not be there). You can check if your Founder ID is correctly registered by running Keyhotee and verifying that "points" are displayed in the contact records for your Founder identity.
I downloaded and installed, created a few profiles for my various IDs with zero issues. I have a question about the points, long term are those going to be BTS or AGS?
Title: Re: Keyhotee Status Update
Post by: bytemaster on February 07, 2014, 08:14:16 am
Alpha 3 release for Windows is available at http://invictus.io/bin/keyhotee_0.5.3.zip. I expect it will be at least a week before we put up another Windows alpha.

I've also updated the Keyhotee Founder ID registration server with names collected from web form (if you registered via the web form in last 12 hours, your registration might not be there). You can check if your Founder ID is correctly registered by running Keyhotee and verifying that "points" are displayed in the contact records for your Founder identity.
I downloaded and installed, created a few profiles for my various IDs with zero issues. I have a question about the points, long term are those going to be BTS or AGS?

Points are just the number of times you have renewed or solved a block.  They are non-transferrable. 
Title: Re: Keyhotee Status Update
Post by: CalabiYau on February 07, 2014, 08:46:08 am
updated, works flawless on win32, found everything, even my registration is now o.k. Thx !
Title: Re: Keyhotee Status Update
Post by: CryptoN8 on February 07, 2014, 03:54:24 pm
Points are just the number of times you have renewed or solved a block.  They are non-transferrable.

Just curious then, how do we know about this AGS distribution listed below? I looked through a couple pages but could not find a description.

This is a copy of BitShares AGS ("angel shares") announcement by Invictus Innovations Inc, discussion can also be found: https://bitsharestalk.org/index.php?topic=1631.0

<snip>
Merry Christmas Keyhotee Founders!!
The first 10,000 AGS are set-aside proportionally for Keyhotee Founders.  Invictus Innovations shareholders are not eligible.  Donations to Keyhotee after Dec 24, 2013 at Midnight GMT don't count.
<snip>
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 07, 2014, 04:48:15 pm
A minor correction to bytemaster's post: the points shown beside the founder's ID is the points donated to get the Founder's ID (it's the dollar equivalent of the donation). The points bytemaster is talking about are "repute points" which are related to blockchain mining (which currently isn't enabled).
Title: Re: Keyhotee Status Update
Post by: CryptoN8 on February 07, 2014, 04:59:34 pm
A minor correction to bytemaster's post: the points shown beside the founder's ID is the points donated to get the Founder's ID (it's the dollar equivalent of the donation). The points bytemaster is talking about are "repute points" which are related to blockchain mining (which currently isn't enabled).
Ok but is there a way to determine how that equates to AGS? This is what I'm trying to do. I have a spreadsheet with all of my PTS to AGS holdings. I am trying to add any additional AGS positions I may have acquired through my three Founder ID's submitted prior to Dec, 24th. Is there a way to find that out? Thanks. (Sorry, maybe this is the wrong thread to ask...)
Title: Re: Keyhotee Status Update
Post by: bytemaster on February 07, 2014, 05:02:55 pm
I will have Stan prepare a AGS balance for every founder.    But we need to make sure you are registered as a founder before we can give you that balance.   

Anyone not registered by February 28 will be unable to claim the founders balance in bitshares XT. 


Sent from my iPhone using Tapatalk (http://tapatalk.com/m?id=1)
Title: Re: Keyhotee Status Update
Post by: CryptoN8 on February 07, 2014, 05:06:08 pm
I will have Stan prepare a AGS balance for every founder.    But we need to make sure you are registered as a founder before we can give you that balance.   

Anyone not registered by February 28 will be unable to claim the founders balance in bitshares XT. 
Thanks! Yes, I have registered all three at http://invictus-innovations.com/founder-sign-up/
Title: Re: Keyhotee Status Update
Post by: Stan on February 07, 2014, 05:53:51 pm
A minor correction to bytemaster's post: the points shown beside the founder's ID is the points donated to get the Founder's ID (it's the dollar equivalent of the donation). The points bytemaster is talking about are "repute points" which are related to blockchain mining (which currently isn't enabled).
Ok but is there a way to determine how that equates to AGS? This is what I'm trying to do. I have a spreadsheet with all of my PTS to AGS holdings. I am trying to add any additional AGS positions I may have acquired through my three Founder ID's submitted prior to Dec, 24th. Is there a way to find that out? Thanks. (Sorry, maybe this is the wrong thread to ask...)

There are 10,000 AGS allocated (1 day's worth) to be distributed proportionally by points earned among registered Founder ID's.  About 1/3 of the Founders have not yet registered their public keys.  So we won't know the exact mapping of AGS to each founder until registration ends and the final denominator is known.



Title: Re: Keyhotee Status Update
Post by: spoonman on February 07, 2014, 08:24:26 pm
A minor correction to bytemaster's post: the points shown beside the founder's ID is the points donated to get the Founder's ID (it's the dollar equivalent of the donation). The points bytemaster is talking about are "repute points" which are related to blockchain mining (which currently isn't enabled).
Ok but is there a way to determine how that equates to AGS? This is what I'm trying to do. I have a spreadsheet with all of my PTS to AGS holdings. I am trying to add any additional AGS positions I may have acquired through my three Founder ID's submitted prior to Dec, 24th. Is there a way to find that out? Thanks. (Sorry, maybe this is the wrong thread to ask...)

There are 10,000 AGS allocated (1 day's worth) to be distributed proportionally by points earned among registered Founder ID's.  About 1/3 of the Founders have not yet registered their public keys.  So we won't know the exact mapping of AGS to each founder until registration ends and the final denominator is known.

I need to redo mine, assuming it ok to still change our public keys if we already sent them to you?
Title: Re: Keyhotee Status Update
Post by: CryptoN8 on February 07, 2014, 10:07:57 pm
I need to redo mine, assuming it ok to still change our public keys if we already sent them to you?
I believe I read that the last one submitted up to Feb 28th would be your final for the Gen Block.
Title: Re: Keyhotee Status Update
Post by: Stan on February 07, 2014, 10:53:32 pm
A minor correction to bytemaster's post: the points shown beside the founder's ID is the points donated to get the Founder's ID (it's the dollar equivalent of the donation). The points bytemaster is talking about are "repute points" which are related to blockchain mining (which currently isn't enabled).
Ok but is there a way to determine how that equates to AGS? This is what I'm trying to do. I have a spreadsheet with all of my PTS to AGS holdings. I am trying to add any additional AGS positions I may have acquired through my three Founder ID's submitted prior to Dec, 24th. Is there a way to find that out? Thanks. (Sorry, maybe this is the wrong thread to ask...)

There are 10,000 AGS allocated (1 day's worth) to be distributed proportionally by points earned among registered Founder ID's.  About 1/3 of the Founders have not yet registered their public keys.  So we won't know the exact mapping of AGS to each founder until registration ends and the final denominator is known.

I need to redo mine, assuming it ok to still change our public keys if we already sent them to you?

Yes, we will use your last one registered.
Title: Re: Keyhotee Status Update
Post by: codinat on February 08, 2014, 09:30:20 am
请给已经提交公钥的ID发邮件确认啊
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 09, 2014, 04:02:10 am
I'll update the Keyhotee ID registration database from the web form on Monday, so that anyone who's filled out the form over the weekend (or since the last update) will be able to check their Founder registration status via Keyhotee after that.
Title: Re: Keyhotee Status Update
Post by: heropzy on February 09, 2014, 06:17:18 am
I have registed the Keyhotee founder ID weeks ago on the website. And I used the Mac version, today I opened the Keyhotee, still it said 'invalid ID/Founderkey pair'
What's that mean?

My public key is
8bwUu8eayGmNU4bRJDSNArDHApvAY4nBh7yBJXbpxJ9PB5cQkY
Title: Re: Keyhotee Status Update
Post by: infovortice2013 on February 10, 2014, 08:02:22 pm
hi i upgrade 0.5.3 keyhotee, im founder and inside on yellow flag say unregistered, next to mi id: Han Solo and the public key 66ctxGvvAierWrMty3utS2vKBo22yPY7PDs5tiQjMMMMSugTfq

its ok, ??? please confirm or something wrong?
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 11, 2014, 02:39:07 am
hi i upgrade 0.5.3 keyhotee, im founder and inside on yellow flag say unregistered, next to mi id: Han Solo and the public key 66ctxGvvAierWrMty3utS2vKBo22yPY7PDs5tiQjMMMMSugTfq

its ok, ??? please confirm or something wrong?
There were some issues caused by the discovery of case-sensitivity in the keyhotee Ids that will require some cleanup in the reporting of KH founder ID registration, this is why your ID isn't showing as registered properly. It should be cleaned up within the next day or two. I'll make a posting once the capitalization issues have been fully corrected.
Title: Re: Keyhotee Status Update
Post by: codinat on February 11, 2014, 02:58:36 am
chat功能尽早取消吧,典型忽悠特性。突出加密特性邮件,不提倡用这样贵的资源,实现华而不实的聊天。再说,无法解决的p2p结构造成的延时,chat体验也不会很好。
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 11, 2014, 03:11:03 am
chat功能尽早取消吧,典型忽悠特性。突出加密特性邮件,不提倡用这样贵的资源,实现华而不实的聊天。再说,无法解决的p2p结构造成的延时,chat体验也不会很好。
The chat feature will be mainly used via "direct connect", not via broadcast messaging, so it should be efficient in it's final form. No proof-of-work will be required for direct connections between friends.
Title: Re: Keyhotee Status Update
Post by: muse-umum on February 11, 2014, 03:42:25 am
chat功能尽早取消吧,典型忽悠特性。突出加密特性邮件,不提倡用这样贵的资源,实现华而不实的聊天。再说,无法解决的p2p结构造成的延时,chat体验也不会很好。
The chat feature will be mainly used via "direct connect", not via broadcast messaging, so it should be efficient in it's final form. No proof-of-work will be required for direct connections between friends.

what about the group chat ?

btw, the keyhotee progress is much slower than what i expected.  even now you can't release the 'decentralized' features.
Title: Re: Keyhotee Status Update
Post by: Stan on February 11, 2014, 04:19:40 am
chat功能尽早取消吧,典型忽悠特性。突出加密特性邮件,不提倡用这样贵的资源,实现华而不实的聊天。再说,无法解决的p2p结构造成的延时,chat体验也不会很好。
The chat feature will be mainly used via "direct connect", not via broadcast messaging, so it should be efficient in it's final form. No proof-of-work will be required for direct connections between friends.

what about the group chat ?

btw, the keyhotee progress is much slower than what i expected.  even now you can't release the 'decentralized' features.

What is the source of your expertise in determining an expectation for how long it should take to develop an application?

Title: Re: Keyhotee Status Update
Post by: dannotestein on February 11, 2014, 04:57:53 am
The Keyhotee registration database queried by Keyhotee is undergoing work for the next 24 hours as we adjust for the capitalization issues, so if you're suddenly shown as unregistered in Keyhotee after previously being registered, don't worry about it yet.
Title: Re: Keyhotee Status Update
Post by: codinat on February 11, 2014, 05:22:57 am
chat功能尽早取消吧,典型忽悠特性。突出加密特性邮件,不提倡用这样贵的资源,实现华而不实的聊天。再说,无法解决的p2p结构造成的延时,chat体验也不会很好。
The chat feature will be mainly used via "direct connect", not via broadcast messaging, so it should be efficient in it's final form. No proof-of-work will be required for direct connections between friends.
+5%
Title: Re: Keyhotee Status Update
Post by: muse-umum on February 11, 2014, 06:09:26 am
chat功能尽早取消吧,典型忽悠特性。突出加密特性邮件,不提倡用这样贵的资源,实现华而不实的聊天。再说,无法解决的p2p结构造成的延时,chat体验也不会很好。
The chat feature will be mainly used via "direct connect", not via broadcast messaging, so it should be efficient in it's final form. No proof-of-work will be required for direct connections between friends.

what about the group chat ?

btw, the keyhotee progress is much slower than what i expected.  even now you can't release the 'decentralized' features.

What is the source of your expertise in determining an expectation for how long it should take to develop an application?

i am not a coder,  and don't know exactly how long it should take to develop an application like keyhotee. are there any experienced coders willing to make some comments ?

what attracts me most in keyhotee is the concept (by now , only concept) of the decentralized and encrypted communication system with btc/ltc/whatever coin wallets.

but it has been nearly 7 months since the keyhotee was introduced last year on July, and i still can't see those shining parts which will actually make keyhotee valuable.
Title: Re: Keyhotee Status Update
Post by: AdamBLevine on February 11, 2014, 11:56:52 pm
chat功能尽早取消吧,典型忽悠特性。突出加密特性邮件,不提倡用这样贵的资源,实现华而不实的聊天。再说,无法解决的p2p结构造成的延时,chat体验也不会很好。
The chat feature will be mainly used via "direct connect", not via broadcast messaging, so it should be efficient in it's final form. No proof-of-work will be required for direct connections between friends.

what about the group chat ?

btw, the keyhotee progress is much slower than what i expected.  even now you can't release the 'decentralized' features.

What is the source of your expertise in determining an expectation for how long it should take to develop an application?

Given the launch of the genesis block for Keyhotee was publicly announced for New Years Eve, then January and now the end of February it seems pretty apparent progress has not gone to plan.  No commenter has suggested they were experts at predicting progress, I think the better question is what can Invictus do to better manage the expectations of their community?    Daily updates on the core products are a great start and seem to have gone a ways in instilling confidence into the system, but being challenging and passive aggressive responses to the people supporting your work and whose expectations are not being met by your mismanagement does not seem like a wise long term strategy to me.

Embrace your weaknesses, don't get prickly.  We're all humans, we all have failing and we're all working as hard as we can to bring a brighter future into being.   Complaints are critique, and while unvested critique might be noise the signal is listening to those who have enabled your success and continued progress.  Their interests align with yours, that was the whole point of this exercise. 
Title: Re: Keyhotee Status Update
Post by: toast on February 12, 2014, 03:01:14 am
Given the launch of the genesis block for Keyhotee was publicly announced for New Years Eve, then January and now the end of February it seems pretty apparent progress has not gone to plan.  No commenter has suggested they were experts at predicting progress, I think the better question is what can Invictus do to better manage the expectations of their community?    Daily updates on the core products are a great start and seem to have gone a ways in instilling confidence into the system, but being challenging and passive aggressive responses to the people supporting your work and whose expectations are not being met by your mismanagement does not seem like a wise long term strategy to me.

Embrace your weaknesses, don't get prickly.  We're all humans, we all have failing and we're all working as hard as we can to bring a brighter future into being.   Complaints are critique, and while unvested critique might be noise the signal is listening to those who have enabled your success and continued progress.  Their interests align with yours, that was the whole point of this exercise.

 +5%

People who don't do software don't see why it should be any harder to make time estimates about software development than about any other kinds of projects, but they are not unreasonable for thinking that and your PR should take that into account
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 12, 2014, 03:47:49 am
People who don't do software don't see why it should be any harder to make time estimates about software development than about any other kinds of projects, but they are not unreasonable for thinking that and your PR should take that into account
Hi toast,

Yes, you're right, this is one of those battles that software developers are always having with their managers too, I suppose. I'm not a PR guy, but I guess a PR guy might have trouble explaining the details of software development, so I'll take a stab at it.

Management always wants a hard date for software delivery, whereas the software guys know they can't really guarantee one, because on any reasonable size software project, it's very difficult to scope out enough details of the design ahead of time (nor is it even often fruitful to try to take the "design it all out first" approach, since once you get into prototyping the code, you sometimes find you need to take a different path than you originally anticipated).

Unexpected problems almost always arise in any truly "new" software (as opposed to adding a feature to an existing piece of stable software, where dates can often be set as long as the feature isn't "big"). As an example, in my own personal work in the past few days, I'd hoped to finish up the database versioning code, but I'm only partially done as I've had to fight problems related to register KHIDs with different capitalization and some related issues (collapsing of similar names like qqq and qqqq to be the same name). Fully understanding the problems associated with this (none of these issues were in code that I had personally worked with before), coming up with a solution that put the least demands on Keyhotee founders, then implementing and testing it,  took several days I didn't expect to spend. But any real programmer will tell you this is typical of the job.

I understand people's frustration, especially as, by Bytemaster's own admission, his original deadlines were unrealistic, but all I can really say is that we're competent programmers, we're working as hard as we can, but we don't want to rush the software out before it's well tested. This just results in more problems, and makes it take longer to deliver a correct version of the software, since we then have to work around legacy problems from software delivered too early. Whether it's the end of February, the end of March, or even later, my main goal is to have a solid, upgradeable experience for Keyhotee users once the block chain is launched.

Anyways, I hope none of the above gets anyone too upset. It's just my own personal feelings about software development, and it's not been "vetted" by Invictus (or our PR department).
Title: Re: Keyhotee Status Update
Post by: codinat on February 12, 2014, 04:51:02 am
Dan,我们也在坚定着信念!相信3i团队!我的2/3pts捐了ags,但持续的影响力是策划部门所必须的,信心非常重要!你们创意很好,产品需要得到检验才能是个伟大的公司。
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 13, 2014, 04:41:57 am
I'm currently working on the database versioning code, other guys are working on gui features, improving build process, etc. I've prepared a report for Stan of all "failed web form" public key updates for KH founder ids, based on data from the founder registration server used by Keyhotee. Stan's going to analyze the results and contact founders if they somehow used an invalid founder code, or send me corrections for cases where a transcription error was made by us when creating the initial registration database. I'll update the founder registration server late Friday based on new submissions to the web form and also corrections from Stan.
Title: Re: Keyhotee Status Update
Post by: Gekko on February 13, 2014, 12:43:41 pm
I'm not following every thread, so my question is:
Is there a way to quickly check the status of the own Keyhotee founder ID?
(I mean like an online check which just says "Your ID will be in the genesis block" or "will NOT be..." or "is currently unknown"... something like that)

Title: Re: Keyhotee Status Update
Post by: dannotestein on February 13, 2014, 01:53:34 pm
I'm not following every thread, so my question is:
Is there a way to quickly check the status of the own Keyhotee founder ID?
(I mean like an online check which just says "Your ID will be in the genesis block" or "will NOT be..." or "is currently unknown"... something like that)
Yes, launch Keyhotee and go to the contact view info for your identity, if it's registered in the name server, it will show points beside the name, like this:
(http://s28.postimg.org/8hz0pt4hp/Keyhoteefullwindow.png)
Note this only happens after the Keyhotee rgistration server is updated from the latest web form submissions, which we manually do every couple of days. Next planned update is Friday night.
Title: Re: Keyhotee Status Update
Post by: fuzzy on February 13, 2014, 04:15:52 pm
People who don't do software don't see why it should be any harder to make time estimates about software development than about any other kinds of projects, but they are not unreasonable for thinking that and your PR should take that into account
Hi toast,

Yes, you're right, this is one of those battles that software developers are always having with their managers too, I suppose. I'm not a PR guy, but I guess a PR guy might have trouble explaining the details of software development, so I'll take a stab at it.

Management always wants a hard date for software delivery, whereas the software guys know they can't really guarantee one, because on any reasonable size software project, it's very difficult to scope out enough details of the design ahead of time (nor is it even often fruitful to try to take the "design it all out first" approach, since once you get into prototyping the code, you sometimes find you need to take a different path than you originally anticipated).

Unexpected problems almost always arise in any truly "new" software (as opposed to adding a feature to an existing piece of stable software, where dates can often be set as long as the feature isn't "big"). As an example, in my own personal work in the past few days, I'd hoped to finish up the database versioning code, but I'm only partially done as I've had to fight problems related to register KHIDs with different capitalization and some related issues (collapsing of similar names like qqq and qqqq to be the same name). Fully understanding the problems associated with this (none of these issues were in code that I had personally worked with before), coming up with a solution that put the least demands on Keyhotee founders, then implementing and testing it,  took several days I didn't expect to spend. But any real programmer will tell you this is typical of the job.

I understand people's frustration, especially as, by Bytemaster's own admission, his original deadlines were unrealistic, but all I can really say is that we're competent programmers, we're working as hard as we can, but we don't want to rush the software out before it's well tested. This just results in more problems, and makes it take longer to deliver a correct version of the software, since we then have to work around legacy problems from software delivered too early. Whether it's the end of February, the end of March, or even later, my main goal is to have a solid, upgradeable experience for Keyhotee users once the block chain is launched.

Anyways, I hope none of the above gets anyone too upset. It's just my own personal feelings about software development, and it's not been "vetted" by Invictus (or our PR department).

One thing I can definitely say, is that if you look at all some of the best products on the market in software, it is often the case that the public awaits the projected launch date just to be dissappointed 2, 3, 4 times.  Though this is not always the rule and certainly not the best practice, the community tends to appreciate a polished product even if it frustrates them to launch it late. 

Imo, taking the time to produce a superior product is best, but definitely worth it to provide the community with updates when it is taking longer than planned.  Glad to see that so many changes coming down the pipeline though...
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 14, 2014, 05:27:23 am
The database versioning code seems to work in preliminary testing. If it passes more rigorous testing tomorrow, I'll update all the KH database structures to support versioning and commit it tomorrow.
Title: Re: Keyhotee Status Update
Post by: Anytime on February 14, 2014, 06:04:57 am
When will keyhotee be finished? (with wallet funtion available )
Title: Re: Keyhotee Status Update
Post by: rysgc on February 14, 2014, 01:27:44 pm
The database versioning code seems to work in preliminary testing. If it passes more rigorous testing tomorrow, I'll update all the KH database structures to support versioning and commit it tomorrow.
Great news!
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 15, 2014, 05:29:06 am
I'm going to update the KH Founder ID database tomorrow night instead of tonight, as Stan was traveling yesterday, plus I had forgotten about an important US holiday today that took up most of my evening...
Title: Re: Keyhotee Status Update
Post by: bytemaster on February 15, 2014, 06:54:03 am
I'm going to update the KH Founder ID database tomorrow night instead of tonight, as Stan was traveling yesterday, plus I had forgotten about an important US holiday today that took up most of my evening...

I thought I told you women were a distraction that we could not afford!    >:(
Title: Re: Keyhotee Status Update
Post by: sfinder on February 15, 2014, 09:58:03 pm
Have you implemented wallet function  for this updates? otherwise it just a funny clone email client which has been open-sourced for many years.

I'm going to update the KH Founder ID database tomorrow night instead of tonight, as Stan was traveling yesterday, plus I had forgotten about an important US holiday today that took up most of my evening...
Title: Re: Keyhotee Status Update
Post by: Troglodactyl on February 15, 2014, 10:42:19 pm
Have you implemented wallet function  for this updates? otherwise it just a funny clone email client which has been open-sourced for many years.

I'm going to update the KH Founder ID database tomorrow night instead of tonight, as Stan was traveling yesterday, plus I had forgotten about an important US holiday today that took up most of my evening...

It's still in testing, and the chain is not yet live.  Wallets have been done before, and I don't think anyone has serious concerns about technical implementation hurdles for integrating basic wallet functionality into Keyhotee.  I think wallet integration is much less urgent than getting the email system finished and thoroughly tested, especially those "funny" parts of it that have never been done before.
Title: Re: Keyhotee Status Update
Post by: rysgc on February 15, 2014, 11:29:50 pm
Have you implemented wallet function  for this updates? otherwise it just a funny clone email client which has been open-sourced for many years.

I'm going to update the KH Founder ID database tomorrow night instead of tonight, as Stan was traveling yesterday, plus I had forgotten about an important US holiday today that took up most of my evening...

It's still in testing, and the chain is not yet live.  Wallets have been done before, and I don't think anyone has serious concerns about technical implementation hurdles for integrating basic wallet functionality into Keyhotee.  I think wallet integration is much less urgent than getting the email system finished and thoroughly tested, especially those "funny" parts of it that have never been done before.
+5%
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 16, 2014, 05:07:04 am
Committed the database versioning code today along with embedded docs for how to use it when updating a database's object format.

Made some updates to the founder ID server to patch up improperly transcribed KH Founder IDs, but still haven't updated the KHID server with latest web form submissions yet, because 1) want to give Stan a little more time to get some feedback on web form submissions that don't have right Founder code or reference a bad KH ID and 2) code for founder ID server didn't compile after I pulled the latest repo changes to the linux box that hosts it and it's a little late to dig into the problem. Probably will do the update tomorrow, or Monday at the latest.
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 17, 2014, 05:17:11 am
I've updated the KH Founder ID server with the latest public keys submitted from the web form. You can check if you're registered by using the latest Keyhotee client and looking at your identity contact (see previous post for screenshot). If the client is not reporting registered and you think you should be (e.g. you've tried to register via KH client or via the webform), send Stan an email and we'll check into it.

On a related note, Stan has already sent out emails to several people who submitted with the wrong Founder Code, etc. and he'll probably be sending out a few more emails tomorrow. If you're the recipient of one of the emails, please resubmit to the web form with your corrected data.
Title: Re: Keyhotee Status Update
Post by: fuzzy on February 17, 2014, 05:22:01 am
I'm not following every thread, so my question is:
Is there a way to quickly check the status of the own Keyhotee founder ID?
(I mean like an online check which just says "Your ID will be in the genesis block" or "will NOT be..." or "is currently unknown"... something like that)
Yes, launch Keyhotee and go to the contact view info for your identity, if it's registered in the name server, it will show points beside the name, like this:
(http://s28.postimg.org/8hz0pt4hp/Keyhoteefullwindow.png)
Note this only happens after the Keyhotee rgistration server is updated from the latest web form submissions, which we manually do every couple of days. Next planned update is Friday night.

Will people be able to buy points for their account with BitShares? 
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 17, 2014, 05:25:34 am
I'm not following every thread, so my question is:
Is there a way to quickly check the status of the own Keyhotee founder ID?
(I mean like an online check which just says "Your ID will be in the genesis block" or "will NOT be..." or "is currently unknown"... something like that)
Yes, launch Keyhotee and go to the contact view info for your identity, if it's registered in the name server, it will show points beside the name, like this:
(http://s28.postimg.org/8hz0pt4hp/Keyhoteefullwindow.png)
Note this only happens after the Keyhotee rgistration server is updated from the latest web form submissions, which we manually do every couple of days. Next planned update is Friday night.

Will people be able to buy points for their account with BitShares?
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.
Title: Re: Keyhotee Status Update
Post by: JustHayden on February 17, 2014, 07:38:33 pm
I'm not following every thread, so my question is:
Is there a way to quickly check the status of the own Keyhotee founder ID?
(I mean like an online check which just says "Your ID will be in the genesis block" or "will NOT be..." or "is currently unknown"... something like that)
Yes, launch Keyhotee and go to the contact view info for your identity, if it's registered in the name server, it will show points beside the name, like this:
(http://s28.postimg.org/8hz0pt4hp/Keyhoteefullwindow.png)
Note this only happens after the Keyhotee rgistration server is updated from the latest web form submissions, which we manually do every couple of days. Next planned update is Friday night.

Will people be able to buy points for their account with BitShares?
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.

Where those points are it says "Unregistered" on mine. But it still says "Keyhotee Founder" beside it.
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 17, 2014, 07:48:30 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.
Title: Re: Keyhotee Status Update
Post by: spoonman on February 18, 2014, 02:05:31 am
I've been away for awhile, were are we with a reliable OSX client?
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 18, 2014, 03:07:07 am
I've been away for awhile, were are we with a reliable OSX client?
My team is not assigned to it, but as I understand it, it's being done as a sub-part of a larger bounty that's supposed to be completed within a week (I believe by Don Schoe et al). Naturally, if anything falls through there (which we're not expecting it to in this case), we would take it on double-quick to get it done.
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 18, 2014, 04:17:27 am
We're currently finishing up a system for allowing two users to exchange a deterministic sequence of public keys (GUI is done, now we're finished up the backend code). This feature will ultimately be used to enhance the privacy of blockchain transactions made between these users.
Title: Re: Keyhotee Status Update
Post by: bytemaster on February 18, 2014, 05:05:35 am
I've been away for awhile, were are we with a reliable OSX client?
My team is not assigned to it, but as I understand it, it's being done as a sub-part of a larger bounty that's supposed to be completed within a week (I believe by Don Schoe et al). Naturally, if anything falls through there (which we're not expecting it to in this case), we would take it on double-quick to get it done.

This is part of the Jenkins nightly build system which requires that a Mac version of Keyhotee is produced in ready to download and distribute form after almost every commit to github.
Title: Re: Keyhotee Status Update
Post by: 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.
Title: Re: Keyhotee Status Update
Post by: jae208 on February 19, 2014, 06:31:47 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!
Title: Re: Keyhotee Status Update
Post by: fuzzy on February 19, 2014, 06:05:40 pm
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%
Title: Re: Keyhotee Status Update
Post by: 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).
Title: Re: Keyhotee Status Update
Post by: jae208 on February 20, 2014, 05:41:56 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
Title: Re: Keyhotee Status Update
Post by: 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".
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.
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 20, 2014, 02:26:22 pm
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".
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.
Title: Re: Keyhotee Status Update
Post by: solaaire on February 20, 2014, 07:16:20 pm
Thank you for the frequent updates, they are much appreciated.
Title: Re: Keyhotee Status Update
Post by: 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.
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 20, 2014, 09:42:18 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.
Title: Re: Keyhotee Status Update
Post by: 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?
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 20, 2014, 10:33:41 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.
Title: Re: Keyhotee Status Update
Post by: Xeldal on February 20, 2014, 11:32:52 pm
Thanks. Fixed the connection issue but still no points.  I'll wait for the next version like you said. Thanks!
Title: Re: Keyhotee Status Update
Post by: zhangweis on February 21, 2014, 12:35:58 am
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?
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 21, 2014, 02:35:32 am
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
Title: Re: Keyhotee Status Update
Post by: zhangweis on February 21, 2014, 10:30:24 am
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.
Title: Re: Keyhotee Status Update
Post by: kmtan on February 21, 2014, 03:12:55 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?
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 21, 2014, 03:21:14 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?
The MAC release is being prepared by another group as part of a larger bounty. The last comments I saw in the forum about it seemed to indicate the full bounty was supposed to be completed on Feb 28th, but I guess they will release the Mac version prior to that (or else the snapshot for BitSharesX would have to be delayed (well maybe that's not true, since I suppose the AGS allocation for donators is independent of the allocation for founder ID holders)).

In related news, I've uploaded the next alpha of the Linux version here:
http://invictus.io/bin/keyhotee_0.5.4.gz
Title: Re: Keyhotee Status Update
Post by: Stan on February 21, 2014, 05:13:50 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?
The MAC release is being prepared by another group as part of a larger bounty. The last comments I saw in the forum about it seemed to indicate the full bounty was supposed to be completed on Feb 28th, but I guess they will release the Mac version prior to that (or else the snapshot for BitSharesX would have to be delayed (well maybe that's not true, since I suppose the AGS allocation for donators is independent of the allocation for founder ID holders)).

In related news, I've uploaded the next alpha of the Linux version here:
http://invictus.io/bin/keyhotee_0.5.4.gz

The two are not tied together on the 28th.  The BTS genesis block needs both inputs:  The BTC/PTS chain snapshots from the 28th of Feb and the Keyhotee Founder's registered keys being collected now.  These get combined in the genesis block targeted for the Ides of March. 

So we Founders all need to get our IDs registered Real Soon Now.    :)

(Alas, Invictus shareholders are not eligible for Founder AGS credits anyway.)
Title: Re: Keyhotee Status Update
Post by: codinat on February 22, 2014, 04:52:23 am
你好,我的founder ID 显示 Registered With 127.8 points 是否提示我已经更新了公钥??7yuAC1KFm5z9SsDcEWaYKdYYQkx3rmLCagEWsFhpVfDWip9CR5
Title: Re: Keyhotee Status Update
Post by: CalabiYau on February 22, 2014, 08:41:40 am
The new version is producing some uncertainty:

0.5.3 (http://i.imgur.com/vkSI1Zo.png)

0.5.4 (http://i.imgur.com/xsRi60j.png)

As long it does not affect the previous correct registration I don`t mind, otherwise thank you for correcting this.
Title: Re: Keyhotee Status Update
Post by: CryptoN8 on February 22, 2014, 09:18:31 am
The new version is producing some uncertainty:

0.5.3 (http://i.imgur.com/vkSI1Zo.png)

0.5.4 (http://i.imgur.com/xsRi60j.png)

As long it does not affect the previous correct registration I don`t mind, otherwise thank you for correcting this.

I am seeing the exact same results going from 0.5.3 to 0.5.4. Is this normal until the new blockchain is live?
Title: Re: Keyhotee Status Update
Post by: coolspeed on February 22, 2014, 10:22:07 am
Hi Dan,
Both 0.5.3 and 0.5.4 don't display my founder ID correctly.
0.5.3 displays "unregistered" in yellow color, and 0.5.4 displays "registered" in green color, both no point displayed.
In fact, I mailed Stan at 13th January, to request for lock of my binding with my founder ID and public key. Stan told me to commit this in the web form. And I did as he told me, at the same day.
The deadline is closing in. Please tell me my founder ID registration status ASAP.
My founder ID is:
Jin
My public key is:
77Zio9rYhbHJMu48B4K7qD5PhizgK4vNNkAbw7e3tcBzeM68bh

Thank you.
Title: Re: Keyhotee Status Update
Post by: yidaidaxia on February 22, 2014, 01:39:49 pm
I have same problem.  0.5.4 displays "registered" in green color and no point displayed.  Hasn't tried 0.5.3 since I think we should refer to the latest version. I also submitted my below information and all the other information in the web form as required (and posted in the thread "Post your Alpha Keyhotee Public Key and Be known").

2/28 is closing, pls correct it and update the status to me or let me know if anything additional I need to do. Thanks.

My Keyhotee Founder ID:
Mike HAO

Public Key:
8RD8pPoyFDr3dkTudsMfuyZeu3NZieJ49n8bubno354oLiZtPT


Hi there,
Both 0.5.3 and 0.5.4 don't display my founder ID correctly.
0.5.3 displays "unregistered" in yellow color, and 0.5.4 displays "registered" in green color, both no point displayed.
In fact, I mailed Stan at 13th January, to request for lock of my binding with my founder ID and public key. Stan told me to commit this in the web form. And I did as he told me, at the same day.
The deadline is closing in. Please tell me my founder ID registration status ASAP.
My founder ID is:
Jin
My public key is:
77Zio9rYhbHJMu48B4K7qD5PhizgK4vNNkAbw7e3tcBzeM68bh

Thank you.
Title: Re: Keyhotee Status Update
Post by: Xeldal on February 22, 2014, 01:55:27 pm
I have same problem.  0.5.4 displays "registered" in green color and no point displayed.  Hasn't tried 0.5.3 since I think we should refer to the latest version. I also submitted my below information and all the other information in the web form as required (and posted in the thread "Post your Alpha Keyhotee Public Key and Be known").


I'm having the same problem, 0.5.4 - Green "Registered" with no points.
ID - EasyBTC
publik Key - 5dm3WAx5TCgsuC5rpJuwWAGyQeyjbv2TXjHBUmD4qAghWgvmMH
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 22, 2014, 03:03:39 pm
We'll look into what's going on with 0.5.4, but if 0.5.3 reported you as registered with points, you can be sure your Founder ID is properly registered.
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 22, 2014, 03:05:47 pm
I have same problem.  0.5.4 displays "registered" in green color and no point displayed.  Hasn't tried 0.5.3 since I think we should refer to the latest version. I also submitted my below information and all the other information in the web form as required (and posted in the thread "Post your Alpha Keyhotee Public Key and Be known").


I'm having the same problem, 0.5.4 - Green "Registered" with no points.
ID - EasyBTC
publik Key - 5dm3WAx5TCgsuC5rpJuwWAGyQeyjbv2TXjHBUmD4qAghWgvmMH
This info matches the record inside the server, so we've got your correct public key.
Title: Re: Keyhotee Status Update
Post by: coolspeed on February 22, 2014, 04:19:27 pm
We'll look into what's going on with 0.5.4, but if 0.5.3 reported you as registered with points, you can be sure your Founder ID is properly registered.

Hi, Dan, 0.5.3 also doesn't display my ID correctly, it shows "unregistered" and no point displayed. I guess it may because the founder code went wrong. Could you help me verify this?
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 22, 2014, 04:22:05 pm
We'll look into what's going on with 0.5.4, but if 0.5.3 reported you as registered with points, you can be sure your Founder ID is properly registered.

Hi, Dan, 0.5.3 also doesn't display my ID correctly, it shows "unregistered" and no point displayed. I guess it may because the founder code went wrong. Could you help me verify this?
Sure, PM your founder ID and I'll check it's status.
Title: Re: Keyhotee Status Update
Post by: coolspeed on February 22, 2014, 04:28:38 pm
We'll look into what's going on with 0.5.4, but if 0.5.3 reported you as registered with points, you can be sure your Founder ID is properly registered.

Hi, Dan, 0.5.3 also doesn't display my ID correctly, it shows "unregistered" and no point displayed. I guess it may because the founder code went wrong. Could you help me verify this?
Sure, PM your founder ID and I'll check it's status.

It seems that you missed a few posts : ) I guess I do not need to delete my ID I wrote in this thread, because others already saw it.

------

Hi there,
Both 0.5.3 and 0.5.4 don't display my founder ID correctly.
0.5.3 displays "unregistered" in yellow color, and 0.5.4 displays "registered" in green color, both no point displayed.
In fact, I mailed Stan at 13th January, to request for lock of my binding with my founder ID and public key. Stan told me to commit this in the web form. And I did as he told me, at the same day.
The deadline is closing in. Please tell me my founder ID registration status ASAP.
My founder ID is:
Jin
My public key is:
77Zio9rYhbHJMu48B4K7qD5PhizgK4vNNkAbw7e3tcBzeM68bh

Thank you.
Title: Re: Keyhotee Status Update
Post by: kmtan on February 22, 2014, 04:31:26 pm
Hi dan,

i need your help .

Keyhotee version 5.2 and 5.3 show my keyhotee founder ID registered with point but when i log in keyhotee version 5.4, its show that my ID unregistered. Would you please help to verify my 2 ID if the ID register and submit well in the server.

ID: kmtan
Public key: 5FNwG3Y6htWKnpsAsM1UrFC8NmVKFHQu4ZAvtjvGr4HxfXrM6c

ID: aviva
Public key: 64ApWtiYjpXEztwCfcy3bVhXemnVcAZ1KXTwLfNt49r6d4MyaW
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 22, 2014, 04:32:02 pm

My founder ID is:
Jin
My public key is:
77Zio9rYhbHJMu48B4K7qD5PhizgK4vNNkAbw7e3tcBzeM68bh

Thank you.
You're correctly registered in the founder database, so you're set.
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 22, 2014, 04:34:13 pm
Hi dan,

i need your help .

Keyhotee version 5.2 and 5.3 show my keyhotee founder ID registered with point but when i log in keyhotee version 5.4, its show that my ID unregistered. Would you please help to verify my 2 ID if the ID register and submit well in the server.

ID: kmtan
Public key: 5FNwG3Y6htWKnpsAsM1UrFC8NmVKFHQu4ZAvtjvGr4HxfXrM6c

ID: aviva
Public key: 64ApWtiYjpXEztwCfcy3bVhXemnVcAZ1KXTwLfNt49r6d4MyaW
There's a bug in 0.5.4 which I'm fixing now. Someone else's changes came in around the same time as I was making the 0.5.4 release which broke the reporting of points. Anyone who's ID reported with points in 0.5.3 and 0.5.2 is still registered.
Title: Re: Keyhotee Status Update
Post by: kmtan on February 22, 2014, 04:39:35 pm
Hi dan,

i need your help .

Keyhotee version 5.2 and 5.3 show my keyhotee founder ID registered with point but when i log in keyhotee version 5.4, its show that my ID unregistered. Would you please help to verify my 2 ID if the ID register and submit well in the server.

ID: kmtan
Public key: 5FNwG3Y6htWKnpsAsM1UrFC8NmVKFHQu4ZAvtjvGr4HxfXrM6c

ID: aviva
Public key: 64ApWtiYjpXEztwCfcy3bVhXemnVcAZ1KXTwLfNt49r6d4MyaW
There's a bug in 0.5.4 which I'm fixing now. Someone else's changes came in around the same time as I was making the 0.5.4 release which broke the reporting of points. Anyone who's ID reported with points in 0.5.3 and 0.5.2 is still registered.

thanks Dan
Title: Re: Keyhotee Status Update
Post by: yidaidaxia on February 22, 2014, 04:46:57 pm
Good, Thanks!

I have same problem.  0.5.4 displays "registered" in green color and no point displayed.  Hasn't tried 0.5.3 since I think we should refer to the latest version. I also submitted my below information and all the other information in the web form as required (and posted in the thread "Post your Alpha Keyhotee Public Key and Be known").


I'm having the same problem, 0.5.4 - Green "Registered" with no points.
ID - EasyBTC
publik Key - 5dm3WAx5TCgsuC5rpJuwWAGyQeyjbv2TXjHBUmD4qAghWgvmMH
This info matches the record inside the server, so we've got your correct public key.
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 22, 2014, 05:05:09 pm
I've uploaded a new 0.5.5 alpha for Windows that I think fixes the two bugs that got introduced with 0.5.4 release. I still plan to do more testing, naturally, but it should definitely work better than 0.5.4. I've temporarily redirected the Linux release back to 0.5.3 until we have one built for Linux. If anyone wants to help me test 0.5.5, it's here:
http://invictus.io/bin/keyhotee_0.5.5.zip
Title: Re: Keyhotee Status Update
Post by: coolspeed on February 22, 2014, 05:28:27 pm

My founder ID is:
Jin
My public key is:
77Zio9rYhbHJMu48B4K7qD5PhizgK4vNNkAbw7e3tcBzeM68bh

Thank you.
You're correctly registered in the founder database, so you're set.

Thank you very much :)
Title: Re: Keyhotee Status Update
Post by: CryptoN8 on February 22, 2014, 06:05:19 pm
The new version is producing some uncertainty:

0.5.3 (http://i.imgur.com/vkSI1Zo.png)

0.5.4 (http://i.imgur.com/xsRi60j.png)

As long it does not affect the previous correct registration I don`t mind, otherwise thank you for correcting this.

I am seeing the exact same results going from 0.5.3 to 0.5.4. Is this normal until the new blockchain is live?

The new build 0.5.5 has fixed my Registered display issues. Thanks!
Title: Re: Keyhotee Status Update
Post by: kmtan on February 22, 2014, 06:21:29 pm
I've uploaded a new 0.5.5 alpha for Windows that I think fixes the two bugs that got introduced with 0.5.4 release. I still plan to do more testing, naturally, but it should definitely work better than 0.5.4. I've temporarily redirected the Linux release back to 0.5.3 until we have one built for Linux. If anyone wants to help me test 0.5.5, it's here:
http://invictus.io/bin/keyhotee_0.5.5.zip

ok. i would like to have a test
Title: Re: Keyhotee Status Update
Post by: kmtan 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?
Title: Re: Keyhotee Status Update
Post by: dannotestein 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).
Title: Re: Keyhotee Status Update
Post by: CalabiYau on February 22, 2014, 08:36:50 pm
Thank you for the quick fix, registration is working now like a charm.
Msg sent.
Title: Re: Keyhotee Status Update
Post by: jae208 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
Title: Re: Keyhotee Status Update
Post by: Ykw on February 23, 2014, 01:00:05 pm
All ok with 0.5.5.
Title: Re: Keyhotee Status Update
Post by: dannotestein 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.
Title: Re: Keyhotee Status Update
Post by: Ykw 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.
Title: Re: Keyhotee Status Update
Post by: dannotestein 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!
Title: Re: Keyhotee Status Update
Post by: cass 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
Title: Re: Keyhotee Status Update
Post by: zhangweis on February 23, 2014, 04:55:29 pm
Hi Dan,
0.5.5 works for me too. Thanks for the update.
Title: Re: Keyhotee Status Update
Post by: gulu 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.
Title: Re: Keyhotee Status Update
Post by: coolspeed 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.
Title: Re: Keyhotee Status Update
Post by: gulu 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.
Title: Re: Keyhotee Status Update
Post by: coolspeed 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.
Title: Re: Keyhotee Status Update
Post by: dannotestein 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.
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 25, 2014, 03:09:34 am
I've updated the founder server with the names submitted this weekend and earlier today from the web form.
Title: Re: Keyhotee Status Update
Post by: onceuponatime on February 25, 2014, 03:48:54 am
I introduced Keyhotee to two people who both use MAC only. They both donated for Founders IDs. Neither of them is a programmer or developer of any kind and have only general public level computer skills. Is there going to be an easy method for them to download Keyhotee and register their Founder ID's in time?

I myself downloaded and registered quite a while ago with Windows, and introduced another person who used Windows to register sucessfully.

I hope my name doesn't become mud with the first two above.
Title: Re: Keyhotee Status Update
Post by: gulu on February 25, 2014, 06:15:32 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.
Thanks again. It turned out that it is a bug on me. I forgot I registered with windows, and then generated a random brain phrase on MAC. Now I re-generated my profile on MAC with the brain phrase, and I got the exact same publick ID.
Title: Re: Keyhotee Status Update
Post by: lib on February 25, 2014, 04:19:26 pm
0.5.5 works fine. Thanks Dan!
And i would like to know how the points calculated? forgive me about the question if anyone has asked before.
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 25, 2014, 05:22:41 pm
0.5.5 works fine. Thanks Dan!
And i would like to know how the points calculated? forgive me about the question if anyone has asked before.
Points are just some rough equivalent in US dollars of the amount donated by the KeyhoteeID holder.
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 25, 2014, 08:29:07 pm
I introduced Keyhotee to two people who both use MAC only. They both donated for Founders IDs. Neither of them is a programmer or developer of any kind and have only general public level computer skills. Is there going to be an easy method for them to download Keyhotee and register their Founder ID's in time?
We have a plan in place to cover any Keyhotee Founder donator that doesn't register by the 28th deadline against loss of their ID. They will still be able to claim their KeyhoteeId (and get credited with AGS/BTS/etc) later even if they don't get registered by the 28th. We will use a "placeholder" key for all these unclaimed IDs, then updated versions of the Keyhotee client will be created later that recognize late registrations.
Title: Re: Keyhotee Status Update
Post by: 38PTSWarrior on February 25, 2014, 08:49:10 pm
Big up for your work dannotenstein at this place!
Title: Re: Keyhotee Status Update
Post by: busygin on February 26, 2014, 11:11:54 pm
Could you please confirm my registration?
ID: Stas
Public key: 7t6vbJZiQctZNauUBiyysrvDQA9VP1XuqkxJcbhAAfVeuGvs6F
Title: Re: Keyhotee Status Update
Post by: jae208 on February 27, 2014, 11:06:41 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
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.

I downloaded 0.5.5 but I was still running 0.5.4, my mistake :)

0.5.5 works thank you so much!
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 27, 2014, 01:25:31 pm
Could you please confirm my registration?
ID: Stas
Public key: 7t6vbJZiQctZNauUBiyysrvDQA9VP1XuqkxJcbhAAfVeuGvs6F
confirmed
Title: Re: Keyhotee Status Update
Post by: quasar on February 27, 2014, 07:04:23 pm
Hello,

Could you please confirm my Founder ID registration :)
Public Key: 7pR8hE1LvFBe9QjkxHmSE52WK9U7hwF7BWXZBNw9nvCNq5dG1A

Thank you
V
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 27, 2014, 07:53:43 pm
Hello,

Could you please confirm my Founder ID registration :)
Public Key: 7pR8hE1LvFBe9QjkxHmSE52WK9U7hwF7BWXZBNw9nvCNq5dG1A

Thank you
V
confirmed
Title: Re: Keyhotee Status Update
Post by: bitshare007777 on February 28, 2014, 02:32:47 am
Could you please confirm my registration?
ID: 宏帮#Aggressive
Public key: 51LtToqDYtepwC68F957P4P3iw8kozWxWUftD5AzfvYrBXFZu8
Thank you !
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 28, 2014, 03:03:51 am
Could you please confirm my registration?
ID: 宏帮#Aggressive
Public key: 51LtToqDYtepwC68F957P4P3iw8kozWxWUftD5AzfvYrBXFZu8
Thank you !
confirmed
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 28, 2014, 03:51:18 am
We've fixed the bug introduced in 0.5.5. that several people experienced related to sending to wrong contacts with a total overhaul of the "auto-completer" used in email to/from/cc/etc fields. The bug was the result of a small "fix" that didn't get tested well since we rushed 0.5.5 out to simplify validation of founder IDs. I want to keep the focus on getting Founder IDs registered until after the 28th, so we're holding off a new binary release with the completer fix until then. My current plan is to release a new binary release on Monday.

If you own a Founder ID, please try to register before the 28th deadline. However, there's no need to panic about the deadline, as we're going to "reserve" any unregistered Founder IDs, so you won't lose it if you miss the deadline.

Also, please note that Founder IDs can be registered and regenerated across OS platforms. In other words, you can create a profile with an identity on one computer (e.g. Windows), then later create the same profile with the same identity and key on another computer running a different OS (e.g. Mac). The only requirement is that you remember the information you entered when you first created the profile (First/Middle/Last Name, brainwallet key, and password) including the capitalization of the words you enter (this is really important for everyone to remember).

So if you're a Mac user who doesn't want to compile from source, you can register your Founder ID on a Windows or Linux machine for now, assuming you have access to one.
Title: Re: Keyhotee Status Update
Post by: smiley35 on February 28, 2014, 05:23:37 am
I have a strange question.

I downloaded the MAC client back when it was available. I registered an ID but Keyhotee said I wasn't connected to the network. I also tried to get a message using my pub key but I never received it. Keyhotee then just mysteriously disappeared from my computer... gone.... I didn't delete it. I registered that pub key on the founders website, but I am not confident that I even really created an ID in the first place as far as the system is concerned.... what do I do?
Title: Re: Keyhotee Status Update
Post by: kmtan on February 28, 2014, 03:42:10 pm
Hi Dan,

to be safe , please help me to confirm my keyhotee ID as following:

1. ID: kmtan Public key:5FNwG3Y6htWKnpsAsM1UrFC8NmVKFHQu4ZAvtjvGr4HxfXrM6c

2. ID: aviva Public key:64ApWtiYjpXEztwCfcy3bVhXemnVcAZ1KXTwLfNt49r6d4MyaW

thanks
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 28, 2014, 03:59:53 pm
Hi Dan,

to be safe , please help me to confirm my keyhotee ID as following:

1. ID: kmtan Public key:5FNwG3Y6htWKnpsAsM1UrFC8NmVKFHQu4ZAvtjvGr4HxfXrM6c

2. ID: aviva Public key:64ApWtiYjpXEztwCfcy3bVhXemnVcAZ1KXTwLfNt49r6d4MyaW

thanks
both are confirmed
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 28, 2014, 04:03:13 pm
I have a strange question.

I downloaded the MAC client back when it was available. I registered an ID but Keyhotee said I wasn't connected to the network. I also tried to get a message using my pub key but I never received it. Keyhotee then just mysteriously disappeared from my computer... gone.... I didn't delete it. I registered that pub key on the founders website, but I am not confident that I even really created an ID in the first place as far as the system is concerned.... what do I do?
I'm trying to find out what the state of the Mac client is (it's being done as part of an outside bounty).

Let me know your Founder ID and I'll check the status of it, then suggest some course of action. You can PM me for greater privacy about it.
Title: Re: Keyhotee Status Update
Post by: alexxy on February 28, 2014, 04:13:53 pm
Can you check that id alexxy  7iziYTGbUmMPRQQHLiyjkRfpsApnpWsRBidr5jj7zUwGAtu6AC registered?
Title: Re: Keyhotee Status Update
Post by: dannotestein on February 28, 2014, 04:36:02 pm
Can you check that id alexxy  7iziYTGbUmMPRQQHLiyjkRfpsApnpWsRBidr5jj7zUwGAtu6AC registered?
confirmed
Title: Re: Keyhotee Status Update
Post by: dannotestein on March 03, 2014, 11:06:07 pm
The new Keyhotee alpha release 0.5.6 is available here: http://invictus.io/bin/keyhotee_0.5.6.zip
Linux release to follow tomorrow, assuming no major problem reports.

This version fixes the "send to wrong contact" bug introduced in 0.5.5 that was causing emails to be lost, plus many other smaller bug fixes.

One change you'll note if you create a new profile is that there's less info requested on profile creation. There's also a mail server icon that reports the status of your connection to the mail server (it's beside the bitshares "plug" that currently reports "disconnected" for alpha testers unless you're running a special build). 

There's a new feature for selecting a contact from your contact list and emailing it to other users for import into their contact list (new contact is sent as an attachment that can be selected for import by recipient). In another day or so, this will be updated to send multiple contacts. There's also an authorization feature that will ultimately be used for a couple of things (sharing transaction keys for increased privacy transactions, direct connect IM, etc), but this feature doesn't yet do much on the surface.

Now that the hectic support activity from Keyhotee founder ids has settled down, I've been diving into the existing code for keyhotee ID mining. Getting that operational is the next major task for me. I have a rough idea of what needs to be done, but I'm still mapping out the details before I make major changes.
Title: Re: Keyhotee Status Update
Post by: CryptoN8 on March 04, 2014, 12:21:56 am
..SNIP..
Now that the hectic support activity from Keyhotee founder ids has settled down, I've been diving into the existing code for keyhotee ID mining. Getting that operational is the next major task for me. I have a rough idea of what needs to be done, but I'm still mapping out the details before I make major changes.
This is great news. I have a feeling once we can turn other people on to Keyhotee, getting them setup so we can securely communicate (Chat/Kmail), it will be the "hook" that opens the opportunity to learn more about Invictus. It will also help them get interesting and excited about current and future DACs. +5% Crypto and privacy are going to be huge this year.
Title: Re: Keyhotee Status Update
Post by: coolspeed on March 04, 2014, 12:19:42 pm
The new Keyhotee alpha release 0.5.6 is available here: http://invictus.io/bin/keyhotee_0.5.6.zip
Linux release to follow tomorrow, assuming no major problem reports.

This version fixes the "send to wrong contact" bug introduced in 0.5.5 that was causing emails to be lost, plus many other smaller bug fixes.

One change you'll note if you create a new profile is that there's less info requested on profile creation. There's also a mail server icon that reports the status of your connection to the mail server (it's beside the bitshares "plug" that currently reports "disconnected" for alpha testers unless you're running a special build). 

There's a new feature for selecting a contact from your contact list and emailing it to other users for import into their contact list (new contact is sent as an attachment that can be selected for import by recipient). In another day or so, this will be updated to send multiple contacts. There's also an authorization feature that will ultimately be used for a couple of things (sharing transaction keys for increased privacy transactions, direct connect IM, etc), but this feature doesn't yet do much on the surface.

Now that the hectic support activity from Keyhotee founder ids has settled down, I've been diving into the existing code for keyhotee ID mining. Getting that operational is the next major task for me. I have a rough idea of what needs to be done, but I'm still mapping out the details before I make major changes.

These problems still exist:
1. Every time I open the application, it receives several mails (the same ones every time) which are marked unread.

2. Chinese character question mark '?' still cause application crashes every time I input it.

Generally, it is still too buggy to use for now, only for me?
Title: Re: Keyhotee Status Update
Post by: Ykw on March 04, 2014, 12:33:58 pm
I am already using it since version 0.5.2 to give updates to a friend.. =)

We are getting there... =) Hey.. i am sure it's not a priority.. but add an option to change language. I need to correct some PT translations I did.. and complete some others... and it takes some time to "evaluate" what I did with changing system LANG..

Tks.. and keep up the valuable work!


EDIT: Or if there is a way to input a flag to force a LANG.. that's also ok.
Title: Re: Keyhotee Status Update
Post by: kmtan on March 04, 2014, 12:55:45 pm
Hi Dan,

i just update my mac keyhotee that build by wackou that i believe should be version 0.5.5
i add your public key and try to send you an email, but seem it is the mail unable to reach you.. during the mail, the receiver are dedicate to you but after pressing send it is random switch to another address in my contact.


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).
Title: Re: Keyhotee Status Update
Post by: dannotestein on March 04, 2014, 01:43:34 pm
Hi Dan,
i just update my mac keyhotee that build by wackou that i believe should be version 0.5.5
i add your public key and try to send you an email, but seem it is the mail unable to reach you.. during the mail, the receiver are dedicate to you but after pressing send it is random switch to another address in my contact.
Yes, this is a known bug with 0.5.5. We put out 0.5.5 too quickly in order to let KH give better verification of founder status before the Mar 28 BTS snapshot, and by rushing we let this bug slip into that release. It's been fixed in 0.5.6.
Title: Re: Keyhotee Status Update
Post by: dannotestein on March 04, 2014, 01:53:30 pm
I am already using it since version 0.5.2 to give updates to a friend.. =)

We are getting there... =) Hey.. i am sure it's not a priority.. but add an option to change language. I need to correct some PT translations I did.. and complete some others... and it takes some time to "evaluate" what I did with changing system LANG..

Tks.. and keep up the valuable work!


EDIT: Or if there is a way to input a flag to force a LANG.. that's also ok.
You can do it by launching a cmd prompt and temporarily setting the LANG environment variable to your alternate language there, then launch Keyhotee. For example, to use simplified chinese on Windows:
<Ctrl>-R
cmd
set LANG=zh-CN
keyhotee
A similar method works for Linux as well.
Title: Re: Keyhotee Status Update
Post by: CalabiYau on March 04, 2014, 02:48:42 pm
Version 0.5.6 : sending bug fixed - confirmed  :)
Title: Re: Keyhotee Status Update
Post by: dannotestein on March 04, 2014, 06:00:41 pm
2. Chinese character question mark '?' still cause application crashes every time I input it.
1) Which OS version are you using specifically?
2) Can you give the specific steps you use to enter these characters?
Our main problem right now is we don't know how to reproduce this issue on our systems. Here's the github issue, can you reply there with more details?
https://github.com/InvictusInnovations/keyhotee/issues/301
Title: Re: Keyhotee Status Update
Post by: dannotestein on March 04, 2014, 08:06:13 pm
The new Keyhotee alpha release 0.5.6 for Linux is available here: http://invictus.io/bin/keyhotee_0.5.6.gz
Title: Re: Keyhotee Status Update
Post by: dannotestein on March 05, 2014, 03:58:49 am
For all you Mac OS testers out there, just saw this post in another thread by drekrob:
The jenkins server we are setting up already supplies nightly builds for mac and linux here:
ftp://178.63.85.22/
Would be nice to get some feedback if they run, cause i can only test them on the build server. If any dependencies are missing i would not notice as they are installed there.
Title: Re: Keyhotee Status Update
Post by: coolspeed on March 05, 2014, 07:36:10 am
2. Chinese character question mark '?' still cause application crashes every time I input it.
1) Which OS version are you using specifically?
2) Can you give the specific steps you use to enter these characters?
Our main problem right now is we don't know how to reproduce this issue on our systems. Here's the github issue, can you reply there with more details?
https://github.com/InvictusInnovations/keyhotee/issues/301

Sorry,I treated this thread as the bug report thread for one second, cuz I also update that thread frequently recently.
I can reproduce that issue every time. Yep, I will write down the process with more details, as soon as I can.
Title: Re: Keyhotee Status Update
Post by: coolspeed on March 05, 2014, 11:21:35 am
Dan, I went back to the bug report thread to update my bug report, not to derail this thread.
Please check it there.
Title: Re: Keyhotee Status Update
Post by: dannotestein on March 07, 2014, 01:05:25 am
I think I found a solution for the intermittent "duplicate mails" issue, going to commit a fix to the mail server tomorrow after I've given it some final thought. We're also going to add a "crash reporter" so that testers can submit a report with a stack dump for any crash we can't duplicate here. Has anyone yet had a chance to try out the Mac client built by brownbear, drekrob, et al? It's located here: ftp://178.63.85.22/Keyhotee/MacOS/2014-03-06_02-02-21/
Title: Re: Keyhotee Status Update
Post by: AdamBLevine on March 07, 2014, 01:09:58 am
Thanks for the update Dan
Title: Re: Keyhotee Status Update
Post by: coolspeed on March 07, 2014, 03:43:19 am
Quote
We're also going to add a "crash reporter" so that testers can submit a report with a stack dump for any crash we can't duplicate here.

Looking forward to it.
Title: Re: Keyhotee Status Update
Post by: muse-umum on March 07, 2014, 05:08:20 am
Quote
We're also going to add a "crash reporter" so that testers can submit a report with a stack dump for any crash we can't duplicate here.

Looking forward to it.

你对3I一定是真爱,对keyhotee不离不弃。我又相信爱情了。

You are quite dead-set on 3I.
Title: Re: Keyhotee Status Update
Post by: kmtan on March 07, 2014, 04:51:03 pm
I think I found a solution for the intermittent "duplicate mails" issue, going to commit a fix to the mail server tomorrow after I've given it some final thought. We're also going to add a "crash reporter" so that testers can submit a report with a stack dump for any crash we can't duplicate here. Has anyone yet had a chance to try out the Mac client built by brownbear, drekrob, et al? It's located here: ftp://178.63.85.22/Keyhotee/MacOS/2014-03-06_02-02-21/

i would like to have a try..
Title: Re: Keyhotee Status Update
Post by: kmtan on March 08, 2014, 08:34:32 am
I think I found a solution for the intermittent "duplicate mails" issue, going to commit a fix to the mail server tomorrow after I've given it some final thought. We're also going to add a "crash reporter" so that testers can submit a report with a stack dump for any crash we can't duplicate here. Has anyone yet had a chance to try out the Mac client built by brownbear, drekrob, et al? It's located here: ftp://178.63.85.22/Keyhotee/MacOS/2014-03-06_02-02-21/

i would like to have a try..

this version crash during firmware opening ...i unable to save the crash reporter...
Title: Re: Keyhotee Status Update
Post by: toast on March 08, 2014, 05:05:16 pm
Can we get an update on when the blockchain will be launched? That was supposed to be in early January and it seems like all the features being worked on right now are much lower priority... Can we get a p2p daemon without all the whistles and bells so other developers can start working on the KID ecosystem?
Title: Re: Keyhotee Status Update
Post by: rysgc on March 08, 2014, 05:15:36 pm
Can we get an update on when the blockchain will be launched? That was supposed to be in early January and it seems like all the features being worked on right now are much lower priority... Can we get a p2p daemon without all the whistles and bells so other developers can start working on the KID ecosystem?
KIDARC will be only this month after lotsss of delay as well, were some other priorities I had come in between but as from this week I can work on it a lot again, there's not so much which needs to be done got everything running marketplace, jobboard, profile, voting etc. Just have to work on signup procedure and te Keyhotee integration for messaging.  http://kidarc.com/members/2 (http://kidarc.com/members/2)
Title: Re: Keyhotee Status Update
Post by: toast on March 08, 2014, 05:25:43 pm
Can we get an update on when the blockchain will be launched? That was supposed to be in early January and it seems like all the features being worked on right now are much lower priority... Can we get a p2p daemon without all the whistles and bells so other developers can start working on the KID ecosystem?
KIDARC will be only this month after lotsss of delay as well, were some other priorities I had come in between but as from this week I can work on it a lot again, there's not so much which needs to be done got everything running marketplace, jobboard, profile, voting etc. Just have to work on signup procedure and te Keyhotee integration for messaging.  http://kidarc.com/members/2 (http://kidarc.com/members/2)

This is my point - how can you keep developing this without a working blockchain+daemon?
Title: Re: Keyhotee Status Update
Post by: rysgc on March 08, 2014, 05:29:53 pm
Yeah, I'm just waiting for it to become available. I'll opt for mail notifications or let people manually contact  each other in the meantime but of course that should be temporary.
Title: Re: Keyhotee Status Update
Post by: dannotestein on March 09, 2014, 02:03:47 am
The crash reporter has been committed and we'll probably finish testing that tomorrow or Monday. My bug fix for duplicate messages didn't cover all the sources of duplicate messages, but I think I've found the remaining problem: insufficient granularity on time stamp of messages (stored as seconds rather than microseconds). Depending on what solution I go with, I may be able to get the fix in tomorrow. After that, we can move back to working on the mining/blockchain code again. Given that a lot of the remaining immediate work is related to the backend code, we've added a new network-experienced programmer to the team this week, previously it's mainly been me looking at those issues.
Title: Re: Keyhotee Status Update
Post by: jae208 on March 09, 2014, 04:51:43 am
The crash reporter has been committed and we'll probably finish testing that tomorrow or Monday. My bug fix for duplicate messages didn't cover all the sources of duplicate messages, but I think I've found the remaining problem: insufficient granularity on time stamp of messages (stored as seconds rather than microseconds). Depending on what solution I go with, I may be able to get the fix in tomorrow. After that, we can move back to working on the mining/blockchain code again. Given that a lot of the remaining immediate work is related to the backend code, we've added a new network-experienced programmer to the team this week, previously it's mainly been me looking at those issues.

 +5%
thanks for the update keep up the great work!
Title: Re: Keyhotee Status Update
Post by: dannotestein on March 11, 2014, 01:14:52 am
We're planning to put out an alpha release tomorrow with crash reporting support, fixes for the duplicate mail issue, plus a couple other mail-server related fixes. The fixes to the mail server will require use of updated versions of Keyhotee, so we're releasing tomorrow so that we can release all three KH clients at once (Windows, Linux, and Mac OS).
Title: Re: Keyhotee Status Update
Post by: dannotestein on March 11, 2014, 05:18:13 pm
We've uploaded alpha 0.6.0 clients for Windows, Linux, and OSX. Older clients will no longer be able to send/receive email as we've also upgraded the mail server as part of this process, so all testers should upgrade to 0.6.0. Links to the three clients can be found here:

http://invictus.io/keyhotee.php
(current OSX version requires Mountain Lion or later, we're working to lower this requirement)
Title: Re: Keyhotee Status Update
Post by: alt on March 12, 2014, 06:29:04 am
We've uploaded alpha 0.6.0 clients for Windows, Linux, and OSX. Older clients will no longer be able to send/receive email as we've also upgraded the mail server as part of this process, so all testers should upgrade to 0.6.0. Links to the three clients can be found here:

http://invictus.io/keyhotee.php
(current OSX version requires Mountain Lion or later, we're working to lower this requirement)
I have two suggestions for linux version
1. rename the application to Keyhotee, because profile dir will change with different application name.
2. run strip -d Keyhotee before gzip it. The size of the file is too huge now.
Title: Re: Keyhotee Status Update
Post by: CrazyCriple on March 12, 2014, 11:58:12 am
We've uploaded alpha 0.6.0 clients for Windows, Linux, and OSX. Older clients will no longer be able to send/receive email as we've also upgraded the mail server as part of this process, so all testers should upgrade to 0.6.0. Links to the three clients can be found here:

http://invictus.io/keyhotee.php
(current OSX version requires Mountain Lion or later, we're working to lower this requirement)

Where can I find my public key in this client? I think I looked about everywhere :/
Title: Re: Keyhotee Status Update
Post by: dannotestein on March 12, 2014, 05:59:05 pm
We've uploaded alpha 0.6.0 clients for Windows, Linux, and OSX. Older clients will no longer be able to send/receive email as we've also upgraded the mail server as part of this process, so all testers should upgrade to 0.6.0. Links to the three clients can be found here:

http://invictus.io/keyhotee.php
(current OSX version requires Mountain Lion or later, we're working to lower this requirement)

Where can I find my public key in this client? I think I looked about everywhere :/
First, use the menu option "New Identity" to create a new identity. After that, select the menu option "Show Contacts" and click on your identity in the list to view the public key for that identity.
Title: Re: Keyhotee Status Update
Post by: dannotestein on March 13, 2014, 03:58:24 am
Fixed one more error in the mail server that caused connections to stay around on the mail server after KH clients dropped their connection. At this point, we haven't seen any more issues in the message communication between the server and KH, so a couple of us are meeting tomorrow with Bytemaster to discuss the design of the overlay network. This is common code that will be used by KH, BitSharesX, and other DACs as well.
Title: Re: Keyhotee Status Update
Post by: dannotestein on March 15, 2014, 12:17:18 am
We've uploaded alpha release 0.6.1 with a fix for a crash bug related to the contacts list (reported via several automated crash reports today):
http://invictus.io/bin/Keyhotee-0.6.1-win32.exe
http://invictus.io/bin/Keyhotee-0.6.1.gz
http://invictus.io/bin/Keyhotee-0.6.1.dmg


Currently we're working on design of the p2p networking layer that processes DAC blockchains.
Title: Re: Keyhotee Status Update
Post by: testz on March 15, 2014, 03:52:10 am
We've uploaded alpha release 0.6.1 with a fix for a crash bug related to the contacts list (reported via several automated crash reports today):
http://invictus.io/bin/Keyhotee-0.6.1-win32.exe
http://invictus.io/bin/Keyhotee-0.6.1.gz
http://invictus.io/bin/Keyhotee-0.6.1.dmg


Currently we're working on design of the p2p networking layer that processes DAC blockchains.

Keyhotee-0.6.1 release +5%  +5%  +5% Looks much better
Title: Re: Keyhotee Status Update
Post by: blackbeard on March 15, 2014, 07:18:02 am
We've uploaded alpha release 0.6.1 with a fix for a crash bug related to the contacts list (reported via several automated crash reports today):
http://invictus.io/bin/Keyhotee-0.6.1-win32.exe
http://invictus.io/bin/Keyhotee-0.6.1.gz
http://invictus.io/bin/Keyhotee-0.6.1.dmg


Currently we're working on design of the p2p networking layer that processes DAC blockchains.


Is the mac version new? Don't think I've seen that before
Title: Re: Keyhotee Status Update
Post by: kmtan on March 15, 2014, 01:30:31 pm
We've uploaded alpha release 0.6.1 with a fix for a crash bug related to the contacts list (reported via several automated crash reports today):
http://invictus.io/bin/Keyhotee-0.6.1-win32.exe
http://invictus.io/bin/Keyhotee-0.6.1.gz
http://invictus.io/bin/Keyhotee-0.6.1.dmg


Currently we're working on design of the p2p networking layer that processes DAC blockchains.


Is the mac version new? Don't think I've seen that before

version 0.6.1 just release today..fresh cook version
Title: Re: Keyhotee Status Update
Post by: CalabiYau on March 15, 2014, 02:36:08 pm
0.6.1 /Win7/32/ :
   
(http://i.imgur.com/qVqhY8O.png)
Title: Re: Keyhotee Status Update
Post by: dannotestein on March 15, 2014, 02:40:25 pm
0.6.1 /Win7/32/ :
   
(http://i.imgur.com/qVqhY8O.png)
Yes, someone reported this on the error thread already, the problem is the new Windows installer didn't include VS2012 runtime libs. We should have a new version up in a few hours that corrects it on machines that don't have it installed already.
Title: Re: Keyhotee Status Update
Post by: dannotestein on March 15, 2014, 03:37:29 pm
0.6.1 /Win7/32/ :
   
(http://i.imgur.com/qVqhY8O.png)
For anyone who encountered the above error with 0.6.1,there is a fixed version here:
http://invictus.io/bin/Keyhotee-0.6.2-win32.exe
(only needed if you encountered this error, there's no other difference vs 0.6.1)
Title: Re: Keyhotee Status Update
Post by: CalabiYau on March 15, 2014, 04:04:53 pm
Thank you for this real quick fix, 0.6.2 is working +5%
Title: Re: Keyhotee Status Update
Post by: megadeth92 on March 15, 2014, 06:48:12 pm
Thanks for update!
Title: Re: Keyhotee Status Update
Post by: dannotestein on March 19, 2014, 03:55:28 am
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.
Title: Re: Keyhotee Status Update
Post by: bitbro on March 19, 2014, 01:03:56 pm

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.

dan notestein is going to be a goddamn hero when this is all said and done


Sent from my iPhone using Tapatalk
Title: Re: Keyhotee Status Update
Post by: dannotestein on March 20, 2014, 03:52:07 am
We completed an initial set of rules for peer discovery today. Naturally we read bitcoin documentation on how it's done there, but the docs left us with more questions than answers, so we decided to start with some relatively simple rules that nodes will use to maintain and broadcast their peer database, then tweak the various parameters of the rules via network simulations as necessary once we've coded them up. We've moved on now to coding up a very simplified version of the blockchain manager that our p2p node will be tested against.

Since all this code is common to all BitShares DACs, it's being developed in github here:
https://github.com/BitShares/bitshares_toolkit

We're primarily working in the libraries/net and libraries/client directories. Most of our algorithms are documented in libraries/net/p2p_design_notes.h for those who are curious about the details of the design, although there's a few points that haven't been updated yet as of today's design work.
Title: Re: Keyhotee Status Update
Post by: jae208 on March 23, 2014, 04:48:24 pm
 +5% +5%
Title: Re: Keyhotee Status Update
Post by: dannotestein on March 27, 2014, 12:45:29 pm
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.
Title: Re: Keyhotee Status Update
Post by: toast on March 27, 2014, 03:11:14 pm
 +5%
"core bitshares code" should have its own status update thread IMO, this is awesome news but is hidden
Title: Re: Keyhotee Status Update
Post by: clout on March 27, 2014, 05:53:55 pm
In what ways is Keyhotee different than OneName?
Title: Re: Keyhotee Status Update
Post by: dannotestein on April 02, 2014, 09:18:56 pm
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.
Title: Re: Keyhotee Status Update
Post by: Ykw on April 02, 2014, 10:09:19 pm
Successfully recreated profile and identity..

New Pub key: 7W73zQHPmKuApHzzNzRVzq8FScdDd65UpMyVbxhoeYXGCQ4mdC

Points show up.. =)
Title: Re: Keyhotee Status Update
Post by: phoenix on April 02, 2014, 11:03:42 pm
Successfully re-registered with public key: 7sbZnqBqdJbtYrHZqJ4bYjbG19b3ynHtUdV54K9zYwcEQtMYU1
Title: Re: Keyhotee Status Update
Post by: marx on April 03, 2014, 03:21:59 am
me too :5deGAz8QdeSWAE5xfms5kzsUH5R1Fyh39aWScEqYiPoKwxGLzH
Title: Re: Keyhotee Status Update
Post by: alt on April 03, 2014, 03:25:05 am
Please disable case sensitive!!
and some other rules for the ID, like disable space.
you can ask toast, he had make some  rules for the  domain name.
It's a good chance!
Title: Re: Keyhotee Status Update
Post by: trytinysmart on April 03, 2014, 03:32:33 am
Founder id: trytinysmart
New pub key: 5MZKHUAp5C2z6ZtU5twJ6vTSVH8gAv9UEPpr1tQGbpsmUxUzzv
Title: Re: Keyhotee Status Update
Post by: Tuck Fheman on April 03, 2014, 06:21:26 am
Tuck_Fheman
8XMN6Z1BrmxFsfsFQKWY4Ln59vXQhgiT2A9vxyqMB4S1CL7tSN

Only problem is, I see no "points", but I'm not sure where I should see them.
Title: Re: Keyhotee Status Update
Post by: taoljj on April 03, 2014, 07:20:17 am
Unsuccessful: "Invalid ID/Founderkey pair"
Title: Re: Keyhotee Status Update
Post by: arubi on April 03, 2014, 09:00:46 am
same here
Title: Re: Keyhotee Status Update
Post by: xeroc on April 03, 2014, 09:12:26 am
all worked fine here
Title: Re: Keyhotee Status Update
Post by: xeroc on April 03, 2014, 09:12:57 am
all worked fine here
Title: Re: Keyhotee Status Update
Post by: codinat on April 03, 2014, 11:01:41 am
Founder id: codinat
New pub key:6Gy3FvEw3tyNB4M2KsBukL7ntghM3DGQ5aXBKfQGot3M31AuH5
Title: Re: Keyhotee Status Update
Post by: codinat on April 03, 2014, 11:09:20 am
mac 10.8    keyhotee 0.7.0退出出现  Receiving email message<s> is in progress .Please wait until transmission finishes ???
Title: Re: Keyhotee Status Update
Post by: dannotestein on April 03, 2014, 02:01:39 pm
I thought of one problem this morning in the shower (I guess I should have taken one last night): old KH clients were still able to register a public key with the server, and if this happened, it could block the new 0.7.0 KH clients from re-register it.

Fortunately, it's possible to distinguish old format keys from new ones, so I modified the founder server just now to reject old-format keys and I also cleared the founder database of any old-style keys that got re-registered. So if you had trouble registering with 0.7.0, please try it again and see if it lets you register your founder ID now.
Title: Re: Keyhotee Status Update
Post by: Riverhead on April 03, 2014, 02:20:25 pm
I can't seem to find the link to the web form where we submit our founder ID and public key.  I'm guessing this form needs to be resubmitted with version 0.7?  Can someone please post the link.


Thank you.
Title: Re: Keyhotee Status Update
Post by: dannotestein on April 03, 2014, 02:26:15 pm
I can't seem to find the link to the web form where we submit our founder ID and public key.  I'm guessing this form needs to be resubmitted with version 0.7?  Can someone please post the link.


Thank you.
It's much better to register your public key with KH 0.7.0 if you can. The web form link is best only used if you previously registered a public key with 0.7.0 and now you want to change that public key. I'll dig up the web form link, in case KH-based registration isn't working for you and PM you.
Title: Re: Keyhotee Status Update
Post by: Riverhead on April 03, 2014, 02:33:15 pm

It's much better to register your public key with KH 0.7.0 if you can. The web form link is best only used if you previously registered a public key with 0.7.0 and now you want to change that public key. I'll dig up the web form link, in case KH-based registration isn't working for you and PM you.


Thank you.  Registering the first time with 0.7 worked for me.  I think I'm in good shape.


Founder ID: James
Pub Key: 8J4HTvByJSXTBYMSB3XHwu6EGL8iaAQTwP1JRkXSRSZnRZuPiF
Title: Re: Keyhotee Status Update
Post by: Evan on April 03, 2014, 06:08:30 pm
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
Title: Re: Keyhotee Status Update
Post by: dannotestein on April 03, 2014, 06:14:08 pm
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.
Title: Re: Keyhotee Status Update
Post by: infovortice2013 on April 03, 2014, 07:33:48 pm
Updated to v 0.7.0 create new profile and id, ok. say registered in yellow

write mail to try y write back

publicID: 5rUhuLCDWUA2FStkKVRTWYEqY1mZhwpfVdRmYEvMRFRD1bqYAL


what mean code on the Note of my profile?
Title: Re: Keyhotee Status Update
Post by: CalabiYau on April 03, 2014, 07:53:04 pm
ID - CalabiYau

New Keyhotee 0.7.0 PubKey - 6EU8sAqbiXk9Xw8yidyrghhPUhAhyRZQRLG9LsdZRNHJpv8Lyx

 Thx :)
Title: Re: Keyhotee Status Update
Post by: Ashaman on April 03, 2014, 10:04:02 pm
Unsuccessful: "Invalid ID/Founderkey pair"
Same here.
Title: Re: Keyhotee Status Update
Post by: dannotestein on April 04, 2014, 01:12:39 am
Unsuccessful: "Invalid ID/Founderkey pair"
Same here.
Hi Ashaman,

Ok, I'm guessing you did the same as taoljj then (registered once with 0.7.0, then tried to register again with a different profile), because I see that ASHAMAN did get registered with a new key. The server will only accept one key registration, so if you need to change it now, you will need to fill out the webform and your key will get updated in a day or two. The webform is located at: http://invictus-innovations.com/founder-sign-up/

Note to everyone: the webform should only be used if you have registered with 0.7.0 and now want to change your public key because you lost the profile you registered. In general, it's best to register with the KH client instead.
Title: Re: Keyhotee Status Update
Post by: diaobanxian on April 04, 2014, 05:12:03 am
There is a warning when I closed the keyhotee, it says "Receiving email message(s) is in progress please wait until transmission finishes"
What does this mean ? should I wait?
Title: Re: Keyhotee Status Update
Post by: diaobanxian on April 04, 2014, 05:24:23 am
mac 10.8    keyhotee 0.7.0退出出现  Receiving email message<s> is in progress .Please wait until transmission finishes ???
I have the same problem.
Title: Re: Keyhotee Status Update
Post by: JustHayden on April 04, 2014, 06:31:23 pm
I've Re-registered fine with my founders code and everything, but there is no indication that I am a founder anymore, just registered with 200 points. Is this how it is for all founders for the time being, or has my founders status disappeared somehow?
Title: Re: Keyhotee Status Update
Post by: dannotestein on April 04, 2014, 06:34:36 pm
I've Re-registered fine with my founders code and everything, but there is no indication that I am a founder anymore, just registered with 200 points. Is this how it is for all founders for the time being, or has my founders status disappeared somehow?
That's how it is for all founders. You're good to go.
Title: Re: Keyhotee Status Update
Post by: JustHayden on April 04, 2014, 06:35:47 pm
I've Re-registered fine with my founders code and everything, but there is no indication that I am a founder anymore, just registered with 200 points. Is this how it is for all founders for the time being, or has my founders status disappeared somehow?
That's how it is for all founders. You're good to go.

Sweet thanks for the reply!
Title: Re: Keyhotee Status Update
Post by: zhangweis on April 05, 2014, 09:49:44 am
Successfully re-registered with (john) public key: 6cTkAWcJs881Dq7K4KwCFUWxVfNafNfsXr16Li2AEH7BbjY1YG
Title: Re: Keyhotee Status Update
Post by: 520Bit on April 06, 2014, 12:58:26 pm
Re-registered in Keyhotee 0.7.0, the public key is:

5Cjgva2jU4cPhKCn83oyg1TeqLThahVa141gK8EqFKsvdhcrJM

Any more do I need to do?
Title: Re: Keyhotee Status Update
Post by: dannotestein on April 06, 2014, 03:29:29 pm
Re-registered in Keyhotee 0.7.0, the public key is:

5Cjgva2jU4cPhKCn83oyg1TeqLThahVa141gK8EqFKsvdhcrJM

Any more do I need to do?
Nope, that's it.
Title: Re: Keyhotee Status Update
Post by: hasher on April 06, 2014, 05:33:56 pm
Hello,
registered with pkey 8dc9ejdw8vVoESvmVCHFwX8LCqodziLB3KUoGPGpZErb1Xxb1p
Title: Re: Keyhotee Status Update
Post by: aero101 on April 07, 2014, 12:48:11 pm
Fine,
New public ID:8ZKACM5BaTEMN92Jjz8mpCY4sTWgBDPnyHTiNfY9F4i1vYWQjY
Title: Re: Keyhotee Status Update
Post by: marx on April 07, 2014, 03:38:32 pm
谷歌翻译:“win7 32位 系统会有假死现象。”win7 32-bit systems have the phenomenon of suspended animation.
Title: Re: Keyhotee Status Update
Post by: dannotestein on April 09, 2014, 12:25:53 am
alt recently pointed out on the forums that Chinese blank characters could be used to spoof KeyhoteeIDs, so we had to take a deeper look at how to avoid spoofing from the huge variety of characters available via Unicode. We settled on a strategy similar to that used to avoid spoofing of DNS names (with slightly tighter restrictions in our system) using the ICU library's implementation of SpoofChecker and Punycode.
Title: Re: Keyhotee Status Update
Post by: dannotestein on April 10, 2014, 06:52:52 pm
We fixed a problem with KH where the connection to the mail server could drop after the client was running for a couple of hours and it wasn't detected to restart the connection. We're also migrating the code to boost library to version 1.55 to use some new features, so we're taking advantage of the change to upgrade other subsystems as well (openssl, ICU) and we're moving to Visual Studio Express 2013 on Windows. This latter change will allow us to use more C++ 11 features as well (gcc already supported them, but VS 2012 didn't allow several of them). We're already building this way locally on our devel machines with 2013, and there's some work going on now to get jenkins builder to compile it all: jenkins needs to be upgraded from using make to cmake (this will also allow us to make windows binary releases directly from jenkins). Next up is to integrate the p2p code to Dan's blockchain code in bitshares toolkit, bring the new bitshares toolkit code into KH to replace the old blockchain/mining code, and work on the GUI wallet (some prototype GUI committed now, but it doesn't do anything yet).
Title: Re: Keyhotee Status Update
Post by: Riverhead on April 10, 2014, 08:05:37 pm
Great update. Thank you.
Title: Re: Keyhotee Status Update
Post by: kmtan on April 11, 2014, 03:43:09 pm
Hi Dan,

if i create identity without click with the Register column, is that ok?
Title: Re: Keyhotee Status Update
Post by: dannotestein on April 11, 2014, 03:51:08 pm
Hi Dan,

if i create identity without click with the Register column, is that ok?
Yes, there's no need to click register column now, that's only for registering with the blockchain once it starts.
Title: Re: Keyhotee Status Update
Post by: yidaidaxia on April 13, 2014, 12:01:48 pm
Successfully re-register as new public key:

5cU7QvmB7ZLxcVjm1bwmvSmgZxduqZGFBgMDh8TPhkdYMnjSgS

Thank you Dan.
Title: Re: Keyhotee Status Update
Post by: xeroc on April 13, 2014, 01:29:07 pm
I used the official binary to reregister my new key . But once i compiled from githib source i could not generate the same pubkey from identical inputs :-(
Title: Re: Keyhotee Status Update
Post by: dannotestein on April 13, 2014, 02:16:12 pm
I used the official binary to reregister my new key . But once i compiled from githib source i could generate the same pubkey from identical inputs :-(
Did you mean you "could" or "could not" generate the same pubkey?
Title: Re: Keyhotee Status Update
Post by: alexxy on April 13, 2014, 03:09:25 pm
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...
Title: Re: Keyhotee Status Update
Post by: dannotestein on April 13, 2014, 03:14:45 pm
Any ideas why with recent source build of keyhotee my identity shown as unauthorized?

Keyhotee ID alexxy
PubKey 7iziYTGbUmMPRQQHLiyjkRfpsApnpWsRBidr5jj7zUwG8bJpe2
Unauthorized or unregistered?
Title: Re: Keyhotee Status Update
Post by: alexxy on April 13, 2014, 03:15:43 pm
donstein unauthorized. check post above. I modifyed it
Title: Re: Keyhotee Status Update
Post by: dannotestein on April 13, 2014, 03:19:40 pm
donstein unauthorized. check post above. I modifyed it
unauthorized just implies you haven't setup a "contact authorization" with that contact. Generally, you probably won't have any "authorized" contacts right now, as this code is still in development.

This is a separate thing from having your founder ID registered, so it's not a problem.
Title: Re: Keyhotee Status Update
Post by: dannotestein on April 13, 2014, 03:22:14 pm
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.
Title: Re: Keyhotee Status Update
Post by: alexxy on April 13, 2014, 03:29:43 pm
Ok so what should i do for it?
Title: Re: Keyhotee Status Update
Post by: xeroc on April 13, 2014, 04:14:33 pm
I used the official binary to reregister my new key . But once i compiled from githib source i could generate the same pubkey from identical inputs :-(
Did you mean you "could" or "could not" generate the same pubkey?

Could not regenerate the same key .. gonna recheck when back home
Title: Re: Keyhotee Status Update
Post by: alexxy on April 13, 2014, 04:24:29 pm
I used the official binary to reregister my new key . But once i compiled from githib source i could generate the same pubkey from identical inputs :-(
Did you mean you "could" or "could not" generate the same pubkey?

Could not regenerate the same key .. gonna recheck when back home

May be you get same problem as me..
Title: Re: Keyhotee Status Update
Post by: dannotestein on April 13, 2014, 06:00:57 pm
Ok so what should i do for it?
Download the 0.70 client, create your profile with whatever info you like (record it so that you can dup it later), create a New Identity with your founder ID and founder code. This will automatically register you with the founder server. You will see points show up in the new identity dialog if you've correctly registered.
Title: Re: Keyhotee Status Update
Post by: xeroc on April 13, 2014, 06:54:16 pm

Could not regenerate the same key .. gonna recheck when back home

Turns out that cmake uses a new folder to store the binaries in. I was still using the old binary...

Now everthing works out nicely.
Title: Re: Keyhotee Status Update
Post by: alexxy on April 13, 2014, 07:11:52 pm
Ok so what should i do for it?
Download the 0.70 client, create your profile with whatever info you like (record it so that you can dup it later), create a New Identity with your founder ID and founder code. This will automatically register you with the founder server. You will see points show up in the new identity dialog if you've correctly registered.

Ok. I reregistered my ID. So now it said that its registered with some number of points =)

New pub key is 6J5x1ArwBR5JAEK5eXfYmcTZsCccv9LdwMAEarQfRTSEg3E2rA
Title: Re: Keyhotee Status Update
Post by: 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 !
Title: Re: Keyhotee Status Update
Post by: dannotestein on April 16, 2014, 03:03:02 pm
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.
Title: Re: Keyhotee Status Update
Post by: WildWex on April 16, 2014, 11:48:55 pm
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?
Title: Re: Keyhotee Status Update
Post by: bitshare007777 on April 17, 2014, 12:33:36 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.
Title: Re: Keyhotee Status Update
Post by: Troglodactyl on April 17, 2014, 02:31:27 am
v0.7.0 Public Key: 8cMZ3Was5orWHpkkjDnEjvVmcj16Ekpj4Decb164hY3hobExKd
Title: Re: Keyhotee Status Update
Post by: dannotestein on April 17, 2014, 04:13:23 pm
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
Title: Re: Keyhotee Status Update
Post by: smiley35 on April 18, 2014, 03:51:11 am
Hey Dan, I know your getting a lot of these, thought I would confirm mine to. I registered the ID Rob with the pub key 5UEnYkxWvjHRX4qe16KpYRdwiEBfK51TNJe9UB8FKKjmDMx2dK
Title: Re: Keyhotee Status Update
Post by: dannotestein on April 18, 2014, 01:36:47 pm
Hey Dan, I know your getting a lot of these, thought I would confirm mine to. I registered the ID Rob with the pub key 5UEnYkxWvjHRX4qe16KpYRdwiEBfK51TNJe9UB8FKKjmDMx2dK
You're registered. At some point we'll send out the registration state for all the founders via email so that they can check it.
Title: Re: Keyhotee Status Update
Post by: dannotestein on April 18, 2014, 03:19:35 pm
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.
Title: Re: Keyhotee Status Update
Post by: spoonman on April 18, 2014, 09:00:29 pm
Looks like http://invictus.io is down? I wanted to create my new key today.
Title: Re: Keyhotee Status Update
Post by: smiley35 on April 18, 2014, 10:42:21 pm
Looks like http://invictus.io is down? I wanted to create my new key today.

i'll email you the keyhotee .dmg if you want
Title: Re: Keyhotee Status Update
Post by: smiley35 on April 18, 2014, 10:46:49 pm
Looks like http://invictus.io is down? I wanted to create my new key today.

i'll email you the keyhotee .dmg if you want

or even better

http://bitshares.org/downloads/

Download it from here and you don't have to trust me.
Title: Re: Keyhotee Status Update
Post by: bitshare007777 on April 19, 2014, 12:36:51 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.
Registered with “points”!Thank you dan!
Title: Re: Keyhotee Status Update
Post by: spoonman on April 20, 2014, 08:09:49 pm
Looks like http://invictus.io is down? I wanted to create my new key today.

i'll email you the keyhotee .dmg if you want

or even better

http://bitshares.org/downloads/

Download it from here and you don't have to trust me.

Thanks
Title: Re: Keyhotee Status Update
Post by: xOR on April 21, 2014, 09:16:45 am
Hey Dan, maybe you could update your post on the re-registration (https://bitsharestalk.org/index.php?topic=1433.msg50002#msg50002) to include the bitshares download link instead? The invictus.io link is still down and the mentioned post is the first one found when searching for "Founder IDs need to be re-registered with Keyhotee 0.7.0".
Or alternatively just repair the invictus.io download  ;)
Thanks!
Title: Re: Keyhotee Status Update
Post by: dannotestein on April 21, 2014, 02:18:19 pm
Update 4/2/2014: Latest Version of Keyhotee Alpha for Windows, Linux, and OSX 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
(OSX requires Mountain Lion or later, currently)
Title: Re: Keyhotee Status Update
Post by: testz on April 21, 2014, 02:33:39 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?
Title: Re: Keyhotee Status Update
Post by: dannotestein on April 21, 2014, 02:44:01 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.
Title: Re: Keyhotee Status Update
Post by: Stan on April 25, 2014, 03:05:59 pm


Public Notice

Keyhotee Founder IDs will have an expanded role in the genesis block of many Bitshares DACs.

You should register your Keyhotee Founder ID's by the end of April to gain maximum advantage from them.

After that we can't guarantee that the next genesis block to be initialized will include them.

 ;)

The expanded role will be explained soon,
just wanted to alert you to the need to finish registering using the new version of Keyhotee.
Title: Re: Keyhotee Status Update
Post by: BTSdac on April 25, 2014, 03:28:54 pm


Public Notice

Keyhotee Founder IDs will have an expanded role in the genesis block of many Bitshares DACs.

You should register your Keyhotee Founder ID's by the end of April to gain maximum advantage from them.

After that we can't guarantee that the next genesis block to be initialized will include them.

 ;)

The expanded role will be explained soon,
just wanted to alert you to the need to finish registering using the new version of Keyhotee.
only founder Id?
Title: Re: Keyhotee Status Update
Post by: bitbro on April 25, 2014, 03:36:01 pm
Are we going to substitute "keyhotee" for BitShares ID and BitID?  The website alludes to this...  If so, sounds good to me!


Sent from my iPhone using Tapatalk
Title: Re: Keyhotee Status Update
Post by: bytemaster on April 25, 2014, 03:41:31 pm
DPOS requires that we can register delegates in the blockchain.
Delegates are more easily identified by name than number
Hence we have the ability to register names in every blockchain

Therefore, we will reserve all Keyhotee Founders in the genesis block of every chain.   

Title: Re: Keyhotee Status Update
Post by: 麥可貓 on April 25, 2014, 04:11:19 pm
DPOS requires that we can register delegates in the blockchain.
Delegates are more easily identified by name than number
Hence we have the ability to register names in every blockchain

Therefore, we will reserve all Keyhotee Founders in the genesis block of every chain.

Translated from here (https://bitsharestalk.org/index.php?topic=1953.msg55087#msg55087):
Since that Keyhotee founder IDs are more important now,  is there any chance to acquire new founder IDs?
Title: Re: Keyhotee Status Update
Post by: xeroc on April 25, 2014, 06:11:20 pm
DPOS requires that we can register delegates in the blockchain.
Delegates are more easily identified by name than number
Hence we have the ability to register names in every blockchain

Therefore, we will reserve all Keyhotee Founders in the genesis block of every chain.
holy moly ... more excitenment...
Title: Re: Keyhotee Status Update
Post by: bytemaster on April 25, 2014, 07:29:34 pm
DPOS requires that we can register delegates in the blockchain.
Delegates are more easily identified by name than number
Hence we have the ability to register names in every blockchain

Therefore, we will reserve all Keyhotee Founders in the genesis block of every chain.

Translated from here (https://bitsharestalk.org/index.php?topic=1953.msg55087#msg55087):
Since that Keyhotee founder IDs are more important now,  is there any chance to acquire new founder IDs?

We are not going to start any new funding methods until we have delivered a working product.   We will make a few more announcements regarding how the name system will work and I think it will address your desire to purchase life-time IDs.
Title: Re: Keyhotee Status Update
Post by: AdamBLevine on April 25, 2014, 11:30:23 pm


Public Notice

Keyhotee Founder IDs will have an expanded role in the genesis block of many Bitshares DACs.

You should register your Keyhotee Founder ID's by the end of April to gain maximum advantage from them.

After that we can't guarantee that the next genesis block to be initialized will include them.

 ;)

The expanded role will be explained soon,
just wanted to alert you to the need to finish registering using the new version of Keyhotee.

You're really only giving five days notice?

Is this going to be shared anywhere besides pages deep in an update thread on a forum?

How many founders do you anticipate losing?
Title: Re: Keyhotee Status Update
Post by: liondani on April 25, 2014, 11:50:06 pm
Can I register also a  Keyhotee ID's or is it only for them they participate on Decembers snapshot?
As a new member of bitshares I have lost the snapshot, what can I do to participate now with a Keyhotee ID? And why should new member not have a way to participate? If existing members want also advantages on future dacs via keyhotee? Is there a solution? What to do? You must be carefull because the side effect is that many of us would feel like second category members... Am I missing something? Will we have the oportunity in future to have same advantages?
Title: Re: Keyhotee Status Update
Post by: Riverhead on April 26, 2014, 12:00:06 am
My understanding is that founders are getting special perks or recognition for contributing funds early so that this project could get off the ground. Without them this project may not have happened.

We all want to go back and be early investors in Google or Microsoft but sadly we can't.
Title: Re: Keyhotee Status Update
Post by: Stan on April 26, 2014, 12:58:22 am
Can I register also a  Keyhotee ID's or is it only for them they participate on Decembers snapshot?
As a new member of bitshares I have lost the snapshot, what can I do to participate now with a Keyhotee ID? And why should new member not have a way to participate? If existing members want also advantages on future dacs via keyhotee? Is there a solution? What to do? You must be carefull because the side effect is that many of us would feel like second category members... Am I missing something? Will we have the oportunity in future to have same advantages?

Everybody will have a chance to get a regular ID.  Founders took extra risks by donating to help us get started, so they get special recognition for doing that.  It's sort of like having your name carved in the cornerstone of a building for helping to fund it.

As far as Bitshares goes, PTS is now much cheaper so you can still get a great deal on shares in future DAC snapshots.  Those who got shares in XTS paid more, but they will soon be able to sell them to you in a free market.  So you can still get in on everything one way or another.

But it is always true that new investors take smaller risks and get smaller payoffs than earlier investors.

The good news is that everybody here today will be viewed as a high-payoff early investor when the rest of the world discovers what we have brewing here! 



Title: Re: Keyhotee Status Update
Post by: 520Bit on April 26, 2014, 05:50:41 am
Can anybody identify whether my Keyhotee public key is OK?

My Keyhotee public key: 5Cjgva2jU4cPhKCn83oyg1TeqLThahVa141gK8EqFKsvdhcrJM

It was registered in version 0.7.0. And I can login in version 0.7.99. How can I know if I need to register again or not?

And I received two test messages, are they from the dev?

One is from 7zW2f8ATR8zEhfwKxDKmW8ijq4aXB6DkeiWQw198D2qt8H1Xc7, another is from 6EU8sAqbiXk9Xw8yidyrghhPUhAhyRZQRLG9LsdZRNHJpv8Lyx.
Title: Re: Keyhotee Status Update
Post by: Troglodactyl on April 26, 2014, 06:45:51 am
...

You're really only giving five days notice?

Is this going to be shared anywhere besides pages deep in an update thread on a forum?

How many founders do you anticipate losing?

They did send an email to founders on the 15th stating that IDs should be registered using the new client, but it didn't specify a deadline.  They should definitely send another email if there are any still unregistered.  Hopefully we can avoid losing any founders without too much more delay.
Title: Re: Keyhotee Status Update
Post by: codinat on April 26, 2014, 08:23:40 am
mac os10.8的keyhotee 还是0.7.0,怎么不更新到0.7.99?还有退出时总出问题,解决了吗?
Title: Re: Keyhotee Status Update
Post by: BldSwtTrs on April 26, 2014, 11:42:20 pm
How do we check that the registration with 0.7 is OK?

My ID is "vito" and my public key 8BmwDMW6GKG6i5m8AH1uvXW53kUYWWY2iQSsVTWdn1y58Uwkcg
Title: Re: Keyhotee Status Update
Post by: Riverhead on April 27, 2014, 12:08:13 am
You'll see a point value associated with your ID.
Title: Re: Keyhotee Status Update
Post by: BldSwtTrs on April 27, 2014, 12:13:04 am
You'll see a point value associated with your ID.
Where?
Title: Re: Keyhotee Status Update
Post by: Riverhead on April 27, 2014, 12:22:59 am
After registering your identity go to contacts and double click in your founder id. It'll be there with a gold background.
Title: Re: Keyhotee Status Update
Post by: BldSwtTrs on April 27, 2014, 12:51:32 am
After registering your identity go to contacts and double click in your founder id. It'll be there with a gold background.
Well then it doesn't work.

In contacts I only have one another ID ("Vito" instead of "vito" without majuscule) where it's indicate Invalid ID/Founder key. But not the one I just created ("vito" without majuscule). And no gold background.

And when I go back to "new identity" to try to re-register ("vito" without majuscule) I have a message write in red "Register with 127.8 points". But still when I go to "contacts" I have the wrong ID, Invalid ID/Founder Key and no gold background.
Title: Re: Keyhotee Status Update
Post by: Riverhead on April 27, 2014, 01:08:31 am
This issue is above my pay grade, but certainly sounds off.
Title: Re: Keyhotee Status Update
Post by: dannotestein on April 27, 2014, 03:10:53 am
After registering your identity go to contacts and double click in your founder id. It'll be there with a gold background.
Well then it doesn't work.

In contacts I only have one another ID ("Vito" instead of "vito" without majuscule) where it's indicate Invalid ID/Founder key. But not the one I just created ("vito" without majuscule). And no gold background.

And when I go back to "new identity" to try to re-register ("vito" without majuscule) I have a message write in red "Register with 127.8 points". But still when I go to "contacts" I have the wrong ID, Invalid ID/Founder Key and no gold background.
I noticed that in the database there is an _VITO as well as VITO, and I have a suspicion this could be the problem. I'll dig into this more tomorrow.

Also, give the problems that have come up since the "register by the 1st" deadline was posted, I think it's reasonable to assume that the deadline to get your founder ID is going to be pushed out some, so I don't want anyone to panic about it. I'll confirm that with Bytemaster and Stan tomorrow morning.
Title: Re: Keyhotee Status Update
Post by: Koberon on April 27, 2014, 09:35:23 am
Hi guys,

just to let you know I've updated to the latest version v.0.7.92 successfully. I had the missing .dll file issue but I've now resolved that by downloading the file as per instructions.

My points are showing up, so I guess that means my founder ('Koberon') ID is registered, unless there's anything else I need to do?

I sure would like to test out my email if possible?
My public key is:
8mLdcFGwfUuWcjgt6YSSd8rcrsm2ZKVEtrVvBwiqhs4hY31fwL

Thanks for the update.
Title: Re: Keyhotee Status Update
Post by: voldemort628 on April 27, 2014, 10:29:56 am
I have problem installing KH 0.7.0...
some dll file was missing. the problem wasnt fixed when I downloaded the required file. the error shown then said that "something was not designed for something bla bla".

can someone help please ?
Title: Re: Keyhotee Status Update
Post by: BldSwtTrs on April 27, 2014, 01:25:09 pm
After registering your identity go to contacts and double click in your founder id. It'll be there with a gold background.
Well then it doesn't work.

In contacts I only have one another ID ("Vito" instead of "vito" without majuscule) where it's indicate Invalid ID/Founder key. But not the one I just created ("vito" without majuscule). And no gold background.

And when I go back to "new identity" to try to re-register ("vito" without majuscule) I have a message write in red "Register with 127.8 points". But still when I go to "contacts" I have the wrong ID, Invalid ID/Founder Key and no gold background.
I noticed that in the database there is an _VITO as well as VITO, and I have a suspicion this could be the problem. I'll dig into this more tomorrow.

Also, give the problems that have come up since the "register by the 1st" deadline was posted, I think it's reasonable to assume that the deadline to get your founder ID is going to be pushed out some, so I don't want anyone to panic about it. I'll confirm that with Bytemaster and Stan tomorrow morning.
Ok thanks.
Title: Re: Keyhotee Status Update
Post by: xOR on April 27, 2014, 01:56:00 pm
I sure would like to test out my email if possible?
My public key is:
8mLdcFGwfUuWcjgt6YSSd8rcrsm2ZKVEtrVvBwiqhs4hY31fwL

Thanks for the update.

Just sent you a test mail through Keyhotee  ;)
Title: Re: Keyhotee Status Update
Post by: Fox on April 27, 2014, 02:50:37 pm
I have problem installing KH 0.7.0...
some dll file was missing. the problem wasnt fixed when I downloaded the required file. the error shown then said that "something was not designed for something bla bla".

can someone help please ?

TLDR: I too had this issue with 0.7.92-win32 on x64.  Resolved by installing 0.7.100:
ftp://178.63.85.22/Keyhotee/Windows/2014-04-27_00-00-43/Keyhotee-0.7.100-win32.exe

Detail:
Machine 1: Windows Server 2012 R2 with C++ 2012 Redistribute Update 4
Machine 2: Windows 8 (x64) with C++ 2012 Redistribute Update 4

Running Keyhotee 0.7.92 would produce the error MSVCP110.dll is not found. 

I went to the Windows folder on the FTP server:
ftp://178.63.85.22/Keyhotee/Windows/
Found the latest update by date (0.7.100 at the time) and installed.

Result: worked fine.
Title: Re: Keyhotee Status Update
Post by: Talos on April 27, 2014, 03:11:48 pm
With the Keyhotee points registration, if these are showing below the Mining Effort trackbar on the right-sided Info Tab, does this prove founder status? Not sure if I should be seeing "Founder member" anywhere on my profile.
Title: Re: Keyhotee Status Update
Post by: dannotestein on April 27, 2014, 03:37:12 pm
With the Keyhotee points registration, if these are showing below the Mining Effort trackbar on the right-sided Info Tab, does this prove founder status? Not sure if I should be seeing "Founder member" anywhere on my profile.
You won't see "Founder member" anywhere right now, that will only happen once the blockchain is active. All you should see now is the points.
Title: Re: Keyhotee Status Update
Post by: dannotestein on April 27, 2014, 10:38:15 pm
I've confirmed with Bytemaster that the deadline for registering your Keyhotee ID has been extended for a bit, so please don't sweat about it. It was really meant as a soft deadline anyways (we wanted people to register by then, but we weren't going to be ogres about it).

We'll give at least a week notice of when you need to register by, and we'll get the profile creation bug that seems to be randomly occurring on some Mac systems fixed first.
Title: Re: Keyhotee Status Update
Post by: 520Bit on April 28, 2014, 04:31:22 am
Can anybody identify whether my Keyhotee public key is OK?

My Keyhotee public key: 5Cjgva2jU4cPhKCn83oyg1TeqLThahVa141gK8EqFKsvdhcrJM

It was registered in version 0.7.0. And I can login in version 0.7.99. How can I know if I need to register again or not?

And I received two test messages, are they from the dev?

One is from 7zW2f8ATR8zEhfwKxDKmW8ijq4aXB6DkeiWQw198D2qt8H1Xc7, another is from 6EU8sAqbiXk9Xw8yidyrghhPUhAhyRZQRLG9LsdZRNHJpv8Lyx.

So nobody can answer my question here. I am a little worried now.
Title: Re: Keyhotee Status Update
Post by: Troglodactyl on April 28, 2014, 05:43:54 am
Can anybody identify whether my Keyhotee public key is OK?

My Keyhotee public key: 5Cjgva2jU4cPhKCn83oyg1TeqLThahVa141gK8EqFKsvdhcrJM

It was registered in version 0.7.0. And I can login in version 0.7.99. How can I know if I need to register again or not?

And I received two test messages, are they from the dev?

One is from 7zW2f8ATR8zEhfwKxDKmW8ijq4aXB6DkeiWQw198D2qt8H1Xc7, another is from 6EU8sAqbiXk9Xw8yidyrghhPUhAhyRZQRLG9LsdZRNHJpv8Lyx.

So nobody can answer my question here. I am a little worried now.

Sorry, when you login and select your identity from the contact list, does it say "Registered with [number] points"?  If you see that, you should be fine.

I don't know who sent you messages, but you can send me some if you want to test more: 8cMZ3Was5orWHpkkjDnEjvVmcj16Ekpj4Decb164hY3hobExKd
Title: Re: Keyhotee Status Update
Post by: voldemort628 on April 28, 2014, 02:17:53 pm
help pleaseeee

the latest build still doesn work for me.
it just doesnt start up on windows 8 ... idk why :(
Title: Re: Keyhotee Status Update
Post by: dannotestein on April 28, 2014, 02:24:03 pm
help pleaseeee

the latest build still doesn work for me.
it just doesnt start up on windows 8 ... idk why :(
1) What link did you use to download?
2) Also, make sure you aren't running an older version.
3) You should probably delete your old profiles by removing the directory: %localappdata%\Keyhotee, then try re-launching Keyhotee.
Title: Re: Keyhotee Status Update
Post by: BldSwtTrs on April 28, 2014, 07:48:05 pm
After registering your identity go to contacts and double click in your founder id. It'll be there with a gold background.
Well then it doesn't work.

In contacts I only have one another ID ("Vito" instead of "vito" without majuscule) where it's indicate Invalid ID/Founder key. But not the one I just created ("vito" without majuscule). And no gold background.

And when I go back to "new identity" to try to re-register ("vito" without majuscule) I have a message write in red "Register with 127.8 points". But still when I go to "contacts" I have the wrong ID, Invalid ID/Founder Key and no gold background.
I noticed that in the database there is an _VITO as well as VITO, and I have a suspicion this could be the problem. I'll dig into this more tomorrow.
Any news on this?
Title: Re: Keyhotee Status Update
Post by: dannotestein on April 28, 2014, 08:01:12 pm
After registering your identity go to contacts and double click in your founder id. It'll be there with a gold background.
Well then it doesn't work.

In contacts I only have one another ID ("Vito" instead of "vito" without majuscule) where it's indicate Invalid ID/Founder key. But not the one I just created ("vito" without majuscule). And no gold background.

And when I go back to "new identity" to try to re-register ("vito" without majuscule) I have a message write in red "Register with 127.8 points". But still when I go to "contacts" I have the wrong ID, Invalid ID/Founder Key and no gold background.
I noticed that in the database there is an _VITO as well as VITO, and I have a suspicion this could be the problem. I'll dig into this more tomorrow.
Any news on this?
After some research, tt looks like there's no conflict in the system between these two names. Also, both seem to be registered as founders now.
Currently I see VITO registered with a public key of 8BmwDM... and _VIT0 registered with 6Rf1a2...

You shouldn't see a gold background beside your contact, but you should see a points display in the info for the contact associated with your identity. Do you not see any points for VITO when you look at that contact record? Also, does your public key match the one above? Please note that it's important that the identity's case matches that which you used to originally register it (I can't tell what that is from the database, btw, it just shows them in all caps).
Title: Re: Keyhotee Status Update
Post by: Amazon on April 28, 2014, 09:09:36 pm
My founder ID BitSharesTalk
Public key: 7xyqdvDdRMTouTwSAQmc66s9TfjFXAAZgcBrRt3QUbydsKPWHn
registered with 0.7.92

Can you help me to verify? Thanks,
Title: Re: Keyhotee Status Update
Post by: BldSwtTrs on April 28, 2014, 09:18:35 pm
After registering your identity go to contacts and double click in your founder id. It'll be there with a gold background.
Well then it doesn't work.

In contacts I only have one another ID ("Vito" instead of "vito" without majuscule) where it's indicate Invalid ID/Founder key. But not the one I just created ("vito" without majuscule). And no gold background.

And when I go back to "new identity" to try to re-register ("vito" without majuscule) I have a message write in red "Register with 127.8 points". But still when I go to "contacts" I have the wrong ID, Invalid ID/Founder Key and no gold background.
I noticed that in the database there is an _VITO as well as VITO, and I have a suspicion this could be the problem. I'll dig into this more tomorrow.
Any news on this?
After some research, tt looks like there's no conflict in the system between these two names. Also, both seem to be registered as founders now.
Currently I see VITO registered with a public key of 8BmwDM... and _VIT0 registered with 6Rf1a2...

You shouldn't see a gold background beside your contact, but you should see a points display in the info for the contact associated with your identity. Do you not see any points for VITO when you look at that contact record? Also, does your public key match the one above? Please note that it's important that the identity's case matches that which you used to originally register it (I can't tell what that is from the database, btw, it just shows them in all caps).
When I go to New identity and enter "vito" I have the public key 8BmwDMW6GKG6i5m8AH1uvXW53kUYWWY2iQSsVTWdn1y58Uwkcg.

But when I go to Contacts "in public key" I have another string of numbers, I have no idea why. Therefore I have the message Invalid ID/Founder Key and I don't see points. The problem is that I cannot eraze that wrong public key to add the right one, the box is grey.

And when I try to create a new contact, I can add the public key "8BmwDMW6GKG6i5m8AH1uvXW53kUYWWY2iQSsVTWdn1y58Uwkcg", but I cannot write into the Keyhotee ID, this time it's the Keyhotee ID which is grey.


EDIT: OK IT'S FINE NOW
I have deleted my contact record and then registered. Now the public key 8BmwDMW6GKG6i5m8AH1uvXW53kUYWWY2iQSsVTWdn1y58Uwkcg is correct and I see my points. Thanks :)

Title: Re: Keyhotee Status Update
Post by: voldemort628 on April 29, 2014, 06:40:58 am
help pleaseeee

the latest build still doesn work for me.
it just doesnt start up on windows 8 ... idk why :(
1) What link did you use to download?
2) Also, make sure you aren't running an older version.
3) You should probably delete your old profiles by removing the directory: %localappdata%\Keyhotee, then try re-launching Keyhotee.

1) i used the latest one at the start of this thread
2)i uninstalled the one version
3) i couldnt fine this folder :(

and no i tried and sill coulnt start KH
Title: Re: Keyhotee Status Update
Post by: pgbit on April 29, 2014, 11:53:00 am
help pleaseeee

the latest build still doesn work for me.
it just doesnt start up on windows 8 ... idk why :(
1) What link did you use to download?
2) Also, make sure you aren't running an older version.
3) You should probably delete your old profiles by removing the directory: %localappdata%\Keyhotee, then try re-launching Keyhotee.

1) i used the latest one at the start of this thread
2)i uninstalled the one version
3) i couldnt fine this folder :(

and no i tried and sill coulnt start KH
Try this to find the relevant folder. It might be in different position possibly with different versions of Windows or Keyhotee:

Click Start button
Type %appdata% in the search box, press return
Navigate *up* a folder and some more folders should be there - look in those to view your Keyhotee profiles already created. You should find them there.

I think it might be best to move any redundant profiles from the folder, and move to a backup folder on another drive / area of the hard disc.





 
Title: Re: Keyhotee Status Update
Post by: voldemort628 on April 29, 2014, 12:21:08 pm
okay so figured it out and managed to start keyhotee..but my founder code and ID do not add up. no point or anything shown but "Invalid ID/FounderKey Pair" ...
Title: Re: Keyhotee Status Update
Post by: pgbit on April 29, 2014, 12:35:33 pm
okay so figured it out and managed to start keyhotee..but my founder code and ID do not add up. no point or anything shown but "Invalid ID/FounderKey Pair" ...
I guess you have checked to be sure the Name you chose was correctly capitalized - that might be relevant. If not, message Dan Notestein on this forum. I had a small issue, messaged him and its sorted now.
Title: Re: Keyhotee Status Update
Post by: voldemort628 on April 29, 2014, 12:37:01 pm
Thanks for your help!
I have msged him :)

okay so figured it out and managed to start keyhotee..but my founder code and ID do not add up. no point or anything shown but "Invalid ID/FounderKey Pair" ...
I guess you have checked to be sure the Name you chose was correctly capitalized - that might be relevant. If not, message Dan Notestein on this forum. I had a small issue, messaged him and its sorted now.


okay so figured it out and managed to start keyhotee..but my founder code and ID do not add up. no point or anything shown but "Invalid ID/FounderKey Pair" ...
I guess you have checked to be sure the Name you chose was correctly capitalized - that might be relevant. If not, message Dan Notestein on this forum. I had a small issue, messaged him and its sorted now.
Title: Re: Keyhotee Status Update
Post by: hasher on April 29, 2014, 05:31:46 pm
Hello guys, i registered id with version 0.7.0
its shows as registered in ver 0.7.1 too
public key 8dc9ejdw8vVoESvmVCHFwX8LCqodziLB3KUoGPGpZErb1Xxb1p
is it well enough?
Title: Re: Keyhotee Status Update
Post by: dannotestein on April 29, 2014, 05:46:34 pm
Hello guys, i registered id with version 0.7.0
its shows as registered in ver 0.7.1 too
public key 8dc9ejdw8vVoESvmVCHFwX8LCqodziLB3KUoGPGpZErb1Xxb1p
is it well enough?
Yes, that's all that's needed, you're fine.
Title: Re: Keyhotee Status Update
Post by: bitdraw on April 30, 2014, 08:15:48 am
the link in the op doesnt seem to work.. any working links available?
Title: Re: Keyhotee Status Update
Post by: cass on April 30, 2014, 09:42:34 am
the link in the op doesnt seem to work.. any working links available?

Pls provide more information about.
Which OS version doesn't work for you?

ftp://178.63.85.22/Keyhotee/Windows/2014-04-27_00-00-43/Keyhotee-0.7.100-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
Title: Re: Keyhotee Status Update
Post by: bitdraw on April 30, 2014, 09:46:02 am
the link in the op doesnt seem to work.. any working links available?

Pls provide more information about.
Which OS version doesn't work for you?

ftp://178.63.85.22/Keyhotee/Windows/2014-04-27_00-00-43/Keyhotee-0.7.100-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

for all version. tried in different browsers.. cant get a connection/website not available
Title: Re: Keyhotee Status Update
Post by: cass on April 30, 2014, 09:50:24 am
the link in the op doesnt seem to work.. any working links available?

Pls provide more information about.
Which OS version doesn't work for you?

ftp://178.63.85.22/Keyhotee/Windows/2014-04-27_00-00-43/Keyhotee-0.7.100-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

for all version. tried in different browsers.. cant get a connection/find the files

seems they doesn't work temporarily...i'll write Dan about issue... thx for info
Title: Re: Keyhotee Status Update
Post by: dexinwong on April 30, 2014, 11:15:01 am
server down
Title: Re: Keyhotee Status Update
Post by: cass on April 30, 2014, 02:15:51 pm
server down

server up again ... sry for delays
Title: Re: Keyhotee Status Update
Post by: James212 on April 30, 2014, 11:53:28 pm
Guys I need some help.  I'm on a MAC OSX 10.9.2 computer.  When I  try to register founder ID on Keyhotee 7.0,  I receive the following error:


"..Cannot create profile: eof
unexpected end of file
    {}
    th_a  json.cpp:342 variant_from_stream

    {}
    th_a  application.cpp:518 create_profile.."



Please help!
Title: Re: Keyhotee Status Update
Post by: 029xue on May 01, 2014, 01:31:17 am
Any body send me a message so I could know I'm on board?


Public Key: 616nhQgVyYS6rpqhaGjwVFf7qR58KJ37VNCn1oX6Zxt1LxtppN
Public Key: 7GzjRYvJm33mXUN3M3aLURrdSLej5qkGt4Poqo1qrT4Pj18PCN


Thanks.
Title: Re: Keyhotee Status Update
Post by: dannotestein on May 01, 2014, 03:29:47 am
Guys I need some help.  I'm on a MAC OSX 10.9.2 computer.  When I  try to register founder ID on Keyhotee 7.0,  I receive the following error:


"..Cannot create profile: eof
unexpected end of file
    {}
    th_a  json.cpp:342 variant_from_stream

    {}
    th_a  application.cpp:518 create_profile.."



Please help!
This is a known problem on some macs that is currently being investigated. There'll be plenty of time to register after we fix this issue, so don't worry about it for now.
Title: Re: Keyhotee Status Update
Post by: codinat on May 02, 2014, 08:58:02 am
 :)Thanks. my Public key  6Gy3FvEw3tyNB4M2KsBukL7ntghM3DGQ5aXBKfQGot3M31AuH5
Title: Re: Keyhotee Status Update
Post by: CalabiYau on May 02, 2014, 04:44:44 pm
Any body send me a message so I could know I'm on board?


Public Key: 616nhQgVyYS6rpqhaGjwVFf7qR58KJ37VNCn1oX6Zxt1LxtppN
Public Key: 7GzjRYvJm33mXUN3M3aLURrdSLej5qkGt4Poqo1qrT4Pj18PCN


Thanks.

Msg sent to Public Key: 616nhQgVyYS6rpqhaGjwVFf7qR58KJ37VNCn1oX6Zxt1LxtppN   o.k.

Not working: Public Key: 7GzjRYvJm33mXUN3M3aLURrdSLej5qkGt4Poqo1qrT4Pj18PCN   failed
Title: Re: Keyhotee Status Update
Post by: KyLin on May 11, 2014, 09:10:18 am
May I ask what time officially out
Title: Re: Keyhotee Status Update
Post by: dannotestein on May 11, 2014, 09:49:52 pm
May I ask what time officially out
There's no official date set right now, but the official release won't be until at least a week minimum after the bitshares_toolkit blockchain code is released, since it will use that code. And that code is currently undergoing a major design change, although I think it's a better design that will save us a lot of time in the future.

I'll have a better idea about the status once we've had a few days to evaluate the impact of the design change on things like the current p2p network code.
Title: Re: Keyhotee Status Update
Post by: Troglodactyl on May 11, 2014, 11:27:10 pm
With DPOS ID registrations in every chain, will there still be a dedicated Keyhotee chain, or will Keyhotee basically be the name for the multi-DPOS chain wallet with communication features built in?  If there will be a dedicated chain, will it just be barebones DPOS, or will it have additional features that aren't in all the other DPOS chains?
Title: Re: Keyhotee Status Update
Post by: James212 on May 12, 2014, 02:00:48 am
Any news on the fix for the IOS version of Keyhotee?

Thanks in advance.
Title: Re: Keyhotee Status Update
Post by: dannotestein on May 12, 2014, 12:43:03 pm
With DPOS ID registrations in every chain, will there still be a dedicated Keyhotee chain, or will Keyhotee basically be the name for the multi-DPOS chain wallet with communication features built in?  If there will be a dedicated chain, will it just be barebones DPOS, or will it have additional features that aren't in all the other DPOS chains?
It's currently planned to be a separate chain, with at least some differences because of the increased flexibility of what names are allowed in the Keyhotee blockchain.
Title: Re: Keyhotee Status Update
Post by: Riverhead on May 28, 2014, 02:19:02 am
Did this thread move? Seems like a while since the last update.
Title: Re: Keyhotee Status Update
Post by: lzr1900 on May 28, 2014, 03:59:16 am
rubbish product
Title: Re: Keyhotee Status Update
Post by: AdamBLevine on May 28, 2014, 04:00:51 am
All the eggs are currently in the Bitshares basket, work on Keyhotee has been halted until that product ships.
Title: Re: Keyhotee Status Update
Post by: dannotestein on May 28, 2014, 04:47:39 am
Did this thread move? Seems like a while since the last update.

It didn't move exactly, but a lot of the work being done on Keyhotee right now (including work I'm directly working on) is on the backend side: peer-to-peer code, web wallets, json-rpc interface, blockchain, etc, and the status for this work is being updated in the btishares xt status update thread rather than here.

On the Keyhotee GUI side, the main changes have been and/or in progress are addition of a webkit widget-based web browser (to support displaying our web wallets inside Keyhotee), work to integrate the bitshares_toolkit code into the Keyhotee code base, code to establish friend-based peer networks, and miscellaneous bug fixes. After that the other major planned change is to modify the way we send messages to multiple recipients for better network efficiency.
Title: Re: Keyhotee Status Update
Post by: cass on May 28, 2014, 11:04:07 am
rubbish product

any arguments? Yes i know deadline issue but behind that ..
Title: Re: Keyhotee Status Update
Post by: Riverhead on May 28, 2014, 11:07:59 am
Dan, thank you for the update. I'll start following the other threads as well.
Title: Re: Keyhotee Status Update
Post by: dannotestein on May 29, 2014, 02:26:22 pm
Just to clarify things a little, Keyhotee is still under very active development,

both on the GUI side:
https://github.com/InvictusInnovations/d

as well as the new backend side:
https://github.com/orgs/BitShares/dashboard

I haven't been reported details on the development of the GUI side because I'm not personally managing the details of it at the moment (I'm working on the backend side). Vogel67 on github is doing the day-to-day management on the GUI side for now. I'll make another posting when we hit the next major milestone (integration with the new backend).
Title: Re: Keyhotee Status Update
Post by: DonJoe on May 29, 2014, 02:28:17 pm
Just to clarify things a little, Keyhotee is still under very active development,

both on the GUI side:
https://github.com/InvictusInnovations/d

as well as the new backend side:
https://github.com/orgs/BitShares/dashboard

I haven't been reported details on the development of the GUI side because I'm not personally managing the details of it at the moment (I'm working on the backend side). Vogel67 on github is doing the day-to-day management on the GUI side for now. I'll make another posting when we hit the next major milestone (integration with the new backend).

Both links do not work.
Title: Re: Keyhotee Status Update
Post by: dannotestein on May 29, 2014, 02:33:55 pm
Just to clarify things a little, Keyhotee is still under very active development,

both on the GUI side:
https://github.com/InvictusInnovations/d

as well as the new backend side:
https://github.com/orgs/BitShares/dashboard

I haven't been reported details on the development of the GUI side because I'm not personally managing the details of it at the moment (I'm working on the backend side). Vogel67 on github is doing the day-to-day management on the GUI side for now. I'll make another posting when we hit the next major milestone (integration with the new backend).

Both links do not work.
Ok, one was a bad cut/paste and the other required you to be signed into github. Try these, hopefully they will work for you:
http://github.com/InvictusInnovations/keyhotee/commits/master
http://github.com/BitShares/bitshares_toolkit/commits/master
Title: Re: Keyhotee Status Update
Post by: id10tothe9 on July 10, 2014, 08:39:25 am
The mac version is not working (ftp://178.63.85.22/Keyhotee/MacOS/2014-04-05_00-01-42/Keyhotee.dmg)

At start after I enter profile data, brain wallet and passphrase, then "finish", the software crashes. new start, it gives me the profile name I provided but the passphrase does not work.

Also, I just found out about registering founder ID and keyhotee software, I was waiting for an email after I registered last year and now I see the link with registration info was hidden in the only newsletter I got back on January 4th. I think this wasn't good communication and maybe there are other founders who did not register yet since no other update was sent via email. I get hundreds of newsletters so I didn't read that one! (I'm just a little pissed you can say because I was wondering about it but thought I'll get an update. initially I was so amazed and excited about this concept even in it's early stage when I heard about it on let's talk bitcoin, and now you just blew my mind! so I hope I can still register my ID :D, and great job otherwise and good luck !! ;))
Title: Re: Keyhotee Status Update
Post by: id10tothe9 on July 10, 2014, 12:07:04 pm
hm also on windows it does not work! I gett a message that MSVCP110.dll is missing, followed online tips to install Visual C++ redistributable packages, registry check etc to no result..
Title: Re: Keyhotee Status Update
Post by: xeroc on July 10, 2014, 12:10:39 pm
most devs currently focus on finalizing bitshares_toolkit

afaik once that one is polished they will focus on keyhotee again
Title: Re: Keyhotee Status Update
Post by: id10tothe9 on July 10, 2014, 01:27:09 pm
thanks! so no working version of keyhotee is functional right now? I did not register my ID that I bought last year, will I still be able to do it later?
Title: Re: Keyhotee Status Update
Post by: xeroc on July 10, 2014, 01:40:13 pm
Oh .. that IS an issue ... could you pm "Stan"? He should know how to work that out
Title: Re: Keyhotee Status Update
Post by: dannotestein on July 10, 2014, 01:56:51 pm
thanks! so no working version of keyhotee is functional right now? I did not register my ID that I bought last year, will I still be able to do it later?
It's functional if you build from source (at least on windows, haven't tested on Mac). I built it yesterday, but the build instructions also need some updating for the integration work that's being done with the bitshares_toolkit, so this could be related to the problem you experienced.

I'll update the build info shortly with the details.
Title: Re: Keyhotee Status Update
Post by: xeroc on July 10, 2014, 02:00:25 pm
thanks! so no working version of keyhotee is functional right now? I did not register my ID that I bought last year, will I still be able to do it later?
It's functional if you build from source (at least on windows, haven't tested on Mac). I built it yesterday, but the build instructions also need some updating for the integration work that's being done with the bitshares_toolkit, so this could be related to the problem you experienced.

I'll update the build info shortly with the details.
Could you also publish updated binaries for those unable/unwilling to build from source?
Title: Re: Keyhotee Status Update
Post by: dannotestein on July 10, 2014, 02:21:23 pm
thanks! so no working version of keyhotee is functional right now? I did not register my ID that I bought last year, will I still be able to do it later?
It's functional if you build from source (at least on windows, haven't tested on Mac). I built it yesterday, but the build instructions also need some updating for the integration work that's being done with the bitshares_toolkit, so this could be related to the problem you experienced.

I'll update the build info shortly with the details.
Could you also publish updated binaries for those unable/unwilling to build from source?
We were planning to do that at the beginning of next week after we finished the integration work with bitshares_toolkit executable, but the installer needs to be updated for things like adding the bitshares_client.exe and its dependencies, etc. Right now bytemaster wants the polish dev group to start working on the bitshares_toolkit code itself as soon as possible, so that will probably be delayed a bit.
Title: Re: Keyhotee Status Update
Post by: cass on July 11, 2014, 12:01:20 am
thanks! so no working version of keyhotee is functional right now? I did not register my ID that I bought last year, will I still be able to do it later?

http://invictus-innovations.com/founder-sign-up/

try that :)
Title: Re: Keyhotee Status Update
Post by: vikram on July 11, 2014, 05:53:54 am
thanks! so no working version of keyhotee is functional right now? I did not register my ID that I bought last year, will I still be able to do it later?

http://invictus-innovations.com/founder-sign-up/

try that :)

That website is deprecated and founder sign ups ended in December.
Title: Re: Keyhotee Status Update
Post by: id10tothe9 on July 11, 2014, 06:44:46 am
Thanks a lot guys! I'll try to contact stan now, and if you could create the updated binaries it would be great because it's difficult for me to build from the source  :)
Title: Re: Keyhotee Status Update
Post by: quasar on July 17, 2014, 06:12:39 pm
Good day  :)

Can someone please confirm that my founder ID is registered properly?

Founder ID is 6Ucdmzx5TCduvkdAdh85NefQtp8qtov7YH67etXYZULncPuz3p

Please send a test message.

Thank you
V
Title: Re: Keyhotee Status Update
Post by: dannotestein on July 17, 2014, 07:08:40 pm
Good day  :)

Can someone please confirm that my founder ID is registered properly?

Founder ID is 6Ucdmzx5TCduvkdAdh85NefQtp8qtov7YH67etXYZULncPuz3p

Please send a test message.

Thank you
V
Receiving a test message directly to the public key won't tell you if you're registered, but you can tell by seeing if "points" show up beside your identity's contact info. Also, if you tell me your founder name, I can check the founder database to see if it's registered now.
Title: Re: Keyhotee Status Update
Post by: quasar on July 18, 2014, 12:54:12 am
Good day  :)

Can someone please confirm that my founder ID is registered properly?

Founder ID is 6Ucdmzx5TCduvkdAdh85NefQtp8qtov7YH67etXYZULncPuz3p

Please send a test message.

Thank you
V
Receiving a test message directly to the public key won't tell you if you're registered, but you can tell by seeing if "points" show up beside your identity's contact info. Also, if you tell me your founder name, I can check the founder database to see if it's registered now.

My founder name is "V"

Thanks for checking, I do see point. Registered with xxx points
Title: Re: Keyhotee Status Update
Post by: dannotestein on July 18, 2014, 05:36:07 am
Good day  :)

Can someone please confirm that my founder ID is registered properly?

Founder ID is 6Ucdmzx5TCduvkdAdh85NefQtp8qtov7YH67etXYZULncPuz3p

Please send a test message.

Thank you
V
Receiving a test message directly to the public key won't tell you if you're registered, but you can tell by seeing if "points" show up beside your identity's contact info. Also, if you tell me your founder name, I can check the founder database to see if it's registered now.

My founder name is "V"

Thanks for checking, I do see point. Registered with xxx points
Yep, you're good to go.
Title: Re: Keyhotee Status Update
Post by: 麥可貓 on July 25, 2014, 10:17:29 am
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?
Title: Re: Keyhotee Status Update
Post by: dannotestein on July 25, 2014, 01:34:49 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.
Title: Re: Keyhotee Status Update
Post by: 麥可貓 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.
Title: Re: Keyhotee Status Update
Post by: dannotestein 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.
Title: Re: Keyhotee Status Update
Post by: 麥可貓 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?
Title: Re: Keyhotee Status Update
Post by: dannotestein 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?
Title: Re: Keyhotee Status Update
Post by: dannotestein 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.
Title: Re: Keyhotee Status Update
Post by: 麥可貓 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
Title: Re: Keyhotee Status Update
Post by: 麥可貓 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.
Title: Re: Keyhotee Status Update
Post by: yidaidaxia 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.
Title: Re: Keyhotee Status Update
Post by: dannotestein 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
Title: Re: Keyhotee Status Update
Post by: yidaidaxia 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.
Title: Re: Keyhotee Status Update
Post by: 麥可貓 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
Title: Re: Keyhotee Status Update
Post by: dannotestein 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.
Title: Re: Keyhotee Status Update
Post by: dannotestein 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).
Title: Re: Keyhotee Status Update
Post by: bitbro 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
Title: Re: Keyhotee Status Update
Post by: James212 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
Title: Re: Keyhotee Status Update
Post by: king on July 26, 2014, 03:46:38 am
I registered keyhotee founder "King" and "Value", took part in the 0.5.3 version of the test, but did not participate in the 0.7.x version of the test, in BTSX the genesis block, there is no written my founder, how should I do ?
Title: Re: Keyhotee Status Update
Post by: dannotestein on July 26, 2014, 04:13:22 am
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
Over the past few months, it's mostly just been bug fixes and minor feature improvements in Keyhotee because of the focus on bitsharesX. The last major change of recent times that I'm aware of was code for integrating Keyhotee with the Bitshares wallet (and code to allow integration with other web wallets as well). That code is about 90% done, probably just needs some minor cleanup once we can assign someone to it (recently all the remaining programmers were pulled off to help with the release of BitsharesX and followup  releases).

The three biggest features that need to be implemented currently are 1) integration with the new bitshares toolkit-based blockchains, 2) cleanup code associated with instant messaging, and 3) a revised methodology for sending to multiple recipients (currently a separate message is generated to each recipient, which is rather inefficient, IMO).

I don't expect any of the above work to start immediately as I suspect we'll be tied up with bitsharesX related issues for a few weeks.
Title: Re: Keyhotee Status Update
Post by: dannotestein on July 26, 2014, 04:19:04 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
My group finally does have a Mac system to test with, but unfortunately we don't have one that has the problem that some Mac systems have (seems to be some older Macs). I know of one person loosely associated with Hypertas that has a system with the problem, but collecting data from them isn't easy and we don't have anyone to analyze it at the moment anyways. Once BitSharesX development cools down a little, we can assign someone to finally put this issue to bed. For now, I recommend just using a friend's machine to register your founder ID (just make sure you record ALL your profile information, probably take a screenshot even).
Title: Re: Keyhotee Status Update
Post by: dannotestein on July 26, 2014, 04:30:08 am
I registered keyhotee founder "King" and "Value", took part in the 0.5.3 version of the test, but did not participate in the 0.7.x version of the test, in BTSX the genesis block, there is no written my founder, how should I do ?
All the unregistered Keyhotee Founder Ids were registered with a placeholder key. Once things cool down a bit, there'll be some instructions about how unregistered founders will be able to claim their IDs. But right now all developers are working 7 days a week on functionality and stability of bitsharesX itself.
Title: Re: Keyhotee Status Update
Post by: king on July 26, 2014, 04:41:41 am
I registered keyhotee founder "King" and "Value", took part in the 0.5.3 version of the test, but did not participate in the 0.7.x version of the test, in BTSX the genesis block, there is no written my founder, how should I do ?
All the unregistered Keyhotee Founder Ids were registered with a placeholder key. Once things cool down a bit, there'll be some instructions about how unregistered founders will be able to claim their IDs. But right now all developers are working 7 days a week on functionality and stability of bitsharesX itself.

Okay, but now I want to get the founder of btsx, how should I do it?
Title: Re: Keyhotee Status Update
Post by: yidaidaxia on July 26, 2014, 12:16:28 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).

quesiont: is login password part of "profile data" ?
Title: Re: Keyhotee Status Update
Post by: dannotestein on July 27, 2014, 04:56:04 am

quesiont: is login password part of "profile data" ?
No, I checked the code and it's not used in the key generation itself, so you don't need to remember it for regeneration of your key.
Title: Re: Keyhotee Status Update
Post by: dannotestein on July 27, 2014, 05:00:15 am
I registered keyhotee founder "King" and "Value", took part in the 0.5.3 version of the test, but did not participate in the 0.7.x version of the test, in BTSX the genesis block, there is no written my founder, how should I do ?
All the unregistered Keyhotee Founder Ids were registered with a placeholder key. Once things cool down a bit, there'll be some instructions about how unregistered founders will be able to claim their IDs. But right now all developers are working 7 days a week on functionality and stability of bitsharesX itself.

Okay, but now I want to get the founder of btsx, how should I do it?
If you just want to claim your BTSX, check out details in this thread:
https://bitsharestalk.org/index.php?topic=5943.0
Title: Re: Keyhotee Status Update
Post by: 麥可貓 on July 27, 2014, 05:06:13 am

quesiont: is login password part of "profile data" ?
No, I checked the code and it's not used in the key generation itself, so you don't need to remember it for regeneration of your key.

I used the name,  brain password,  password,  founder code recorded in my keepass,  but I still can not get my ID back.  Is there anything I can do to get my ID back? I have the original email and pts address used for my IDs.
Title: Re: Keyhotee Status Update
Post by: Riverhead on July 27, 2014, 01:03:38 pm

quesiont: is login password part of "profile data" ?
No, I checked the code and it's not used in the key generation itself, so you don't need to remember it for regeneration of your key.

I used the name,  brain password,  password,  founder code recorded in my keepass,  but I still can not get my ID back.  Is there anything I can do to get my ID back? I have the original email and pts address used for my IDs.


Can you see your id with console command blockchain_get_account <name>?


Also remember that the wallet_import_keyhotee the Keyhotee id at the end IS case sensative.  If you had Steve as your keyhotee id and steve shows up in the blockchain you'll need to specify Steve on the command line.


For me it was (because I didn't use a middle name):


wallet_import_keyhotee Bob "" Smith "My brain key went here" Riverhead



Title: Re: Keyhotee Status Update
Post by: 麥可貓 on July 27, 2014, 03:06:08 pm

quesiont: is login password part of "profile data" ?
No, I checked the code and it's not used in the key generation itself, so you don't need to remember it for regeneration of your key.

I used the name,  brain password,  password,  founder code recorded in my keepass,  but I still can not get my ID back.  Is there anything I can do to get my ID back? I have the original email and pts address used for my IDs.


Can you see your id with console command blockchain_get_account <name>?


Also remember that the wallet_import_keyhotee the Keyhotee id at the end IS case sensative.  If you had Steve as your keyhotee id and steve shows up in the blockchain you'll need to specify Steve on the command line.


For me it was (because I didn't use a middle name):


wallet_import_keyhotee Bob "" Smith "My brain key went here" Riverhead

Thank you.
Using the method you mentioned, I registered "jimewu" and the interface returned "OK".
However, the strange thing is that I lost all my account in "My Accounts" in qt_wallet, but I can click into the acocunt names shown in transaction histroy.
Then I sent 10 BTSX from another ID to "jimewu",  but till now the balance of "jimewu" is still zero.

Another ID "Apple" did not register succesfully.
Using the method you mentioned, it returned the following:
Code: [Select]
10 assert_exception: Assert Exception
false: Account name is already registered under a different key
    {}
    bitshares  wallet.cpp:1417 add_contact_account

    {"account_name":"apple","key":"BTSX56fKG3fD6pYxsBXSrmX2v7GSfGnmZa7zEouYV9GiipYxRQhiaf"}
    bitshares  wallet.cpp:1448 add_contact_account

    {"account_name":"apple"}
    bitshares  wallet.cpp:1619 import_private_key
error creating private key using keyhotee info.
    {"firstname":"Yi-Pei","middlename":"","lastname":"Lin","brainkey":"3P1XoZeK10ulpBOxyrHBGEDnNU5GEBKv","keyhoteeid":"Apple"}
    bitshares  wallet.cpp:3931 import_keyhotee

    {}
    bitshares  common_api_client.cpp:675 wallet_import_keyhotee

    {"command":"wallet_import_keyhotee"}
    bitshares  cli.cpp:540 execute_command

How come the founder ID is registered? Isn't it reserved?
Title: Re: Keyhotee Status Update
Post by: Riverhead on July 27, 2014, 11:45:53 pm



The first issue sounds like a Gui issue.  You can try a wallet_rescan_blockchain and see it that helps.  The second issue, Apple, did you pay for two founder IDs?  I had Riverhead and a couple others in Keyhotee but only actually paid for one ID with my 15 PTS donation many moons ago.error


The error you got with Apple was the same I got when I didn't have the brain key or Keyhotee ID just right.


Glad you got it somewhat working though :) .  The GUI has some bugs still to work out for sure.
Title: Re: Keyhotee Status Update
Post by: hasher on August 06, 2014, 12:12:24 pm
recently i changed my laptop and kept old hard drive, but now i cant start keyhotee 0.7.1 on this new machine, its just wont load in memory after i click on shortcut, any ideas?
Title: Re: Keyhotee Status Update
Post by: Riverhead on August 06, 2014, 12:27:10 pm
Is the shortcut still pointing to the .exe?  Can you try running the executable directly?
Title: Re: Keyhotee Status Update
Post by: hasher on August 06, 2014, 12:35:51 pm
Is the shortcut still pointing to the .exe?  Can you try running the executable directly?
yea it points..
any ideas how i can found wif_key if i cant run keyhotee?

looks like 0.7.1 cant run on 32 bit Windows... i have no 64 bit OS near me..what i can do with this situation?
Title: Re: Keyhotee Status Update
Post by: Riverhead on August 06, 2014, 01:10:55 pm
Is the shortcut still pointing to the .exe?  Can you try running the executable directly?
yea it points..
any ideas how i can found wif_key if i cant run keyhotee?

looks like 0.7.1 cant run on 32 bit Windows... i have no 64 bit OS near me..what i can do with this situation?
I guess nothing :(.  What are you trying to do with Keyhotee?  If it's just unlocking your Founder ID and BTSX in the BitsharesX client you don't need to run Keyhotee for that.  You can do it from the BitsharesX client.
Title: Re: Keyhotee Status Update
Post by: hasher on August 06, 2014, 01:29:41 pm
Is the shortcut still pointing to the .exe?  Can you try running the executable directly?
yea it points..
any ideas how i can found wif_key if i cant run keyhotee?

looks like 0.7.1 cant run on 32 bit Windows... i have no 64 bit OS near me..what i can do with this situation?
I guess nothing :(.  What are you trying to do with Keyhotee?  If it's just unlocking your Founder ID and BTSX in the BitsharesX client you don't need to run Keyhotee for that.  You can do it from the BitsharesX client.
idk i just lost my way here since i was not involved in testing process,
all right i figured out,
i want to claim keyhotee founders id with command
wallet_import_keyhotee
its shows me:
10 assert_exception: Assert Exception
false: Account name is already registered under a different key
??? it registered but how i can claim it in btsx wallet?
Title: Re: Keyhotee Status Update
Post by: Riverhead on August 06, 2014, 01:32:44 pm
In the BitsharesX wallet use the left menu to go to the console screen and do the following:

The wallet_import_keyhotee: Keyhotee id at the end IS case sensative.  If you had Steve as your keyhotee id and steve shows up in the blockchain you'll need to specify Steve on the command line.

For me it was (because I didn't use a middle name):

wallet_import_keyhotee Bob "" Smith "My brain key went here" Riverhead
Title: Re: Keyhotee Status Update
Post by: hasher on August 06, 2014, 01:40:58 pm
In the BitsharesX wallet use the left menu to go to the console screen and do the following:

The wallet_import_keyhotee: Keyhotee id at the end IS case sensative.  If you had Steve as your keyhotee id and steve shows up in the blockchain you'll need to specify Steve on the command line.

For me it was (because I didn't use a middle name):

wallet_import_keyhotee Bob "" Smith "My brain key went here" Riverhead
i did it before, name - hasher, it in genesis chain,
btsx wallet have crashed 1st time,now when i trying to execute the same command line again it tells me

10 assert_exception: Assert Exception
false: Account name is already registered under a different key

i figured it out, going to download latest version of keyhotee (i hope it runs on 32 bit win) from http://bitshares.org/resources/downloads/
then use "export function for private key" in keyhotee
then use command line "wallet_import_keyhotee" "wallet_import_private_key" in btsx wallet

i did it at last, thank you for help, now its time to claim btsx..
Title: Re: Keyhotee Status Update
Post by: eureka on September 11, 2014, 01:16:50 pm
where is keyhotee going now?
Title: Re: Keyhotee Status Update
Post by: megadeth92 on November 13, 2014, 03:42:48 am
where is keyhotee going now?

I was wondering the same question...
I have no idea :(
Title: Re: Keyhotee Status Update
Post by: Troglodactyl on November 13, 2014, 04:41:40 am
where is keyhotee going now?

I was wondering the same question...
I have no idea :(

Secure mail and IDs will be built into Bitshares.