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
hello,
i have paid for keyhotee 3 days ago and still didnt got response, something happened?
Ok, thank you Stan!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.
:)
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?
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.
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.
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.
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?
Very nice attitude, keeping completely transparent and sharing the update status with community.
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).
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?
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/30@12pm central USA)
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/30@12pm 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.
So we still all go for midnight tonight?
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).
Yep, best of luck.
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.
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.
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...
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.
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.
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.
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.
Good news everyone, we are ready for releasing the Alpha of Keyhotee. We are packaging it up for distribution in a couple of hours.
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!
Good news everyone, we are ready for releasing the Alpha of Keyhotee. We are packaging it up for distribution in a couple of hours.
is the alpha version only for the keyhotee founder to generate the public key? can the non-founder mine the keyhotee id?
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?
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.
" 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.
" 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.
How are things going?
I saw the bug had been fixed about 2 hours ago. I am waiting for the server up....How are things going?
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?
link to github?
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.
Did someone get this to build under linux?yes, whats your problem? i manage to compile and run with arch linux.
I don't have any other way to use this...
Did someone get this to build under linux?yes, whats your problem? i manage to compile and run with arch linux.
I don't have any other way to use this...
Did someone get this to build under linux?yes, whats your problem? i manage to compile and run with arch linux.
I don't have any other way to use this...
Can you list the dependencies?
Did you use cmake at all?
Did someone get this to build under linux?yes, whats your problem? i manage to compile and run with arch linux.
I don't have any other way to use this...
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
Did someone get this to build under linux?yes, whats your problem? i manage to compile and run with arch linux.
I don't have any other way to use this...
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?
yep, qt5, sorry forgot about that. whats your distro?
Mint 15 and I'll also try on Debian jessie
(really appreciate the quick replies)
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
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
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
That is the status of the OSX version of Keyhotee?
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).
Does Invictus have security people to go through the code? I know Keyhotee is behind schedule, but I'd hate to see it rushed.
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).
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).
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?
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.
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?
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.
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.
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.
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.
Any updates on the OSX client?Toast is supposedly working on it. I am working on BTS full time.
Is it possible to release a statically linked linux client, or should I drudge through the dependency hell until I get it compiled?
+1
Couple things,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.
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.
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)Couple things,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.
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.
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.
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.
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.
Update 1/20/2014: Latest Version of Keyhotee Alpha here
http://invictus.io/bin/keyhotee_0.5.2.zip
[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.
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:
- 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...
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.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.
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.
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.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.
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.
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:
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.
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.
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.
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.
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 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 !!!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.
Hi Adam,
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.
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.
Dan,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.
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?
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.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.
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) :)
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.
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.
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 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.
-Protoshare Gpu mining is is just a little better that CPU mining, so to me this was a success.
- 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
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.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.
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.
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.
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 itQuoteMaybe 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.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.
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.
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.
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.
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.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.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, we'll definitely have new binaries out for osx and linux soon.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.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
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)
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: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.
- 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.
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.
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 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?
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.
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 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?
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.
Points are just the number of times you have renewed or solved a block. They are non-transferrable.
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!!<snip>
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.
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...)
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.Thanks! Yes, I have registered all three at http://invictus-innovations.com/founder-sign-up/
Anyone not registered by February 28 will be unable to claim the founders balance in bitshares XT.
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...)
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?I believe I read that the last one submitted up to Feb 28th would be your final for the Gen Block.
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?
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 66ctxGvvAierWrMty3utS2vKBo22yPY7PDs5tiQjMMMMSugTfqThere 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.
its ok, ??? please confirm or something wrong?
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.
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.
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.
+5%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.
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?
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.
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 accountHi toast,
I'm not following every thread, so my question is: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:
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)
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 accountHi 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).
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!
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'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...
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...
+5%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.
I'm not following every thread, so my question is: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:
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)
(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.
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.I'm not following every thread, so my question is: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:
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)
(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.I'm not following every thread, so my question is: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:
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)
(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?
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.
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.
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.
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.
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%
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).
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.
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".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.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.
My client is not showing any points. I've registered on the website twice about a week ago. The console window continually says: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.
"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.
this is using Keyhotee_0.5.3.exeyes, I think you've got an old config.json file in your profile directory with the old port number.
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, "john" is properly registered in the database with 5yQRwuHnu9iRF4NuzvcDaDwgZch74EVT6X8b4pfecrwbnnMTLF, so your id will work properly show up as a Founder ID once the blockchain is initialized.
Another user reported a similar problem today, so I reviewed the code today that reports the points and I'm pretty sure I know the problem: for security reasons, the name server requires that the identity be created with the "Founder Code" in order to report your points (basically Keyhotee sends the KeyhoteeID, the public key, and the founder code to the founder registration server to be verified). I suspect that your identity info is either missing the founder code or it has the wrong one. You can check the founder code entered by looking in the "Notes" section of your contact info for your identity. If it's blank or if the code is wrong, this would explain the issue. Note this doesn't mean your Founder Id isn't registered, just that it won't show as registered in your Keyhotee until the blockchain is initialized.
I'm going to look into a possible method for notifying anyone who might be experiencing this problem today, and I'll report back with more details late tonight or tomorrow.
I'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: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: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?
http://invictus.io/bin/keyhotee_0.5.4.zip
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)).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: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?
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)).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: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?
http://invictus.io/bin/keyhotee_0.5.4.zip
hi dannotestein, is that MAC version available?
In related news, I've uploaded the next alpha of the Linux version here:
http://invictus.io/bin/keyhotee_0.5.4.gz
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.
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.
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").
This info matches the record inside the server, so we've got your correct public key.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
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.
Sure, PM your founder ID and I'll check it's status.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.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?
You're correctly registered in the founder database, so you're set.
My founder ID is:
Jin
My public key is:
77Zio9rYhbHJMu48B4K7qD5PhizgK4vNNkAbw7e3tcBzeM68bh
Thank you.
Hi dan,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.
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
Hi dan,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.
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
This info matches the record inside the server, so we've got your correct public key.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
You're correctly registered in the founder database, so you're set.
My founder ID is:
Jin
My public key is:
77Zio9rYhbHJMu48B4K7qD5PhizgK4vNNkAbw7e3tcBzeM68bh
Thank you.
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?
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
Hi Dan,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
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 downloaded the latest version of Keyhotee and now it says that I am unregisteredDo 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.
and that I have no points. My Keyhotee ID is Godfather and my public key is 81TRY6hzUMS8rGmkWeALpg17fYjeTY7ePbFqkMNG1cukYvmzzc
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!
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: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?
http://invictus.io/bin/keyhotee_0.5.4.zip
hi dannotestein, is that MAC version available?
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
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.
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.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.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.
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.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.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.
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.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.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.
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.
0.5.5 works fine. Thanks Dan!Points are just some rough equivalent in US dollars of the amount donated by the KeyhoteeID holder.
And i would like to know how the points calculated? forgive me about the question if anyone has asked before.
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.
I downloaded the latest version of Keyhotee and now it says that I am unregisteredDo 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.
and that I have no points. My Keyhotee ID is Godfather and my public key is 81TRY6hzUMS8rGmkWeALpg17fYjeTY7ePbFqkMNG1cukYvmzzc
Could you please confirm my registration?confirmed
ID: Stas
Public key: 7t6vbJZiQctZNauUBiyysrvDQA9VP1XuqkxJcbhAAfVeuGvs6F
Hello,confirmed
Could you please confirm my Founder ID registration :)
Public Key: 7pR8hE1LvFBe9QjkxHmSE52WK9U7hwF7BWXZBNw9nvCNq5dG1A
Thank you
V
Could you please confirm my registration?confirmed
ID: 宏帮#Aggressive
Public key: 51LtToqDYtepwC68F957P4P3iw8kozWxWUftD5AzfvYrBXFZu8
Thank you !
Hi Dan,both are confirmed
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
I have a strange question.I'm trying to find out what the state of the Mac client is (it's being done as part of an outside bounty).
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?
Can you check that id alexxy 7iziYTGbUmMPRQQHLiyjkRfpsApnpWsRBidr5jj7zUwGAtu6AC registered?confirmed
..SNIP..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.
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.
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.
Hi Dan,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
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?
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).
Hi Dan,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.
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.
I am already using it since version 0.5.2 to give updates to a friend.. =)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:
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.
2. Chinese character question mark '?' still cause application crashes every time I input it.1) Which OS version are you using specifically?
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.
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
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.
QuoteWe'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.
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 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..
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)
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)
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.
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:I have two suggestions for linux version
http://invictus.io/keyhotee.php
(current OSX version requires Mountain Lion or later, we're working to lower this requirement)
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)
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.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 :/
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.
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.
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
0.6.1 /Win7/32/ :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.
(http://i.imgur.com/qVqhY8O.png)
0.6.1 /Win7/32/ :For anyone who encountered the above error with 0.6.1,there is a fixed version here:
(http://i.imgur.com/qVqhY8O.png)
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.
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.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.
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.
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".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.
Founder ID - Evan
Keyhotee 0.7 Public Key - 7CkhKJBks2KHQiLVszhyPNcuGVBoFgeTtf4iDHrKfEjcMXxtJ1
Unsuccessful: "Invalid ID/Founderkey pair"Same here.
Hi Ashaman,Unsuccessful: "Invalid ID/Founderkey pair"Same here.
mac 10.8 keyhotee 0.7.0退出出现 Receiving email message<s> is in progress .Please wait until transmission finishes ???I have the same problem.
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.
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.
Re-registered in Keyhotee 0.7.0, the public key is:Nope, that's it.
5Cjgva2jU4cPhKCn83oyg1TeqLThahVa141gK8EqFKsvdhcrJM
Any more do I need to do?
Hi Dan,Yes, there's no need to click register column now, that's only for registering with the blockchain once it starts.
if i create identity without click with the Register column, is that ok?
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?
Any ideas why with recent source build of keyhotee my identity shown as unauthorized?Unauthorized or unregistered?
Keyhotee ID alexxy
PubKey 7iziYTGbUmMPRQQHLiyjkRfpsApnpWsRBidr5jj7zUwG8bJpe2
donstein unauthorized. check post above. I modifyed itunauthorized 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.
Any ideas why with recent source build of keyhotee my identity shown as unauthorized?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.
Keyhotee ID alexxy
PubKey 7iziYTGbUmMPRQQHLiyjkRfpsApnpWsRBidr5jj7zUwG8bJpe2
PS another strange thing old pub key in profile was 7iziYTGbUmMPRQQHLiyjkRfpsApnpWsRBidr5jj7zUwGAtu6AC however now it was changed...
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?
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
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.
Could not regenerate the same key .. gonna recheck when back home
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.
Could you please confirm my registration?I could not see the “points”.Hi Bitshares007777,
ID: 宏帮#Aggressive.
Public key: 64De4t8Effjj6PTkU6CeeJNNBLCzi7QoxikoXQazpEx9qdJxKo
Thank you !
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.Could you please confirm my registration?I could not see the “points”.Hi Bitshares007777,
ID: 宏帮#Aggressive.
Public key: 64De4t8Effjj6PTkU6CeeJNNBLCzi7QoxikoXQazpEx9qdJxKo
Thank you !
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 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.Hi Gregory,
This is for my Keyhotee ID: Gregory
Public key: 5CCX9nWysxrv8KkibWmqVopjdMusLWHkFu478fyqwZa8HhvxGf
Can you assist?
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 5UEnYkxWvjHRX4qe16KpYRdwiEBfK51TNJe9UB8FKKjmDMx2dKYou're registered. At some point we'll send out the registration state for all the founders via email so that they can check it.
I figured out the problem, there was a change in the way chinese characters were being converted to ASCII, so the founder ID wasn't matching up in the database. Please try registering again now. Sorry for the delay, got tied up with a bunch of other projects.I 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.Could you please confirm my registration?I could not see the “points”.Hi Bitshares007777,
ID: 宏帮#Aggressive.
Public key: 64De4t8Effjj6PTkU6CeeJNNBLCzi7QoxikoXQazpEx9qdJxKo
Thank you !
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.
Looks like http://invictus.io is down? I wanted to create my new key today.
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
Registered with “points”!Thank you dan!I figured out the problem, there was a change in the way chinese characters were being converted to ASCII, so the founder ID wasn't matching up in the database. Please try registering again now. Sorry for the delay, got tied up with a bunch of other projects.I 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.Could you please confirm my registration?I could not see the “points”.Hi Bitshares007777,
ID: 宏帮#Aggressive.
Public key: 64De4t8Effjj6PTkU6CeeJNNBLCzi7QoxikoXQazpEx9qdJxKo
Thank you !
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.
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.
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.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?
only founder Id?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.
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.
DPOS requires that we can register delegates in the blockchain.holy moly ... more excitenment...
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.
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?
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.
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?
...
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?
You'll see a point value associated with your ID.Where?
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.
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.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.
Ok thanks.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.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.
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.
I sure would like to test out my email if possible?
My public key is:
8mLdcFGwfUuWcjgt6YSSd8rcrsm2ZKVEtrVvBwiqhs4hY31fwL
Thanks for the update.
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 ?
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.
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.
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.
help pleaseeee1) What link did you use to download?
the latest build still doesn work for me.
it just doesnt start up on windows 8 ... idk why :(
Any news on this?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.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.
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.Any news on this?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.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.
When I go to New identity and enter "vito" I have the public key 8BmwDMW6GKG6i5m8AH1uvXW53kUYWWY2iQSsVTWdn1y58Uwkcg.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.Any news on this?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.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.
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).
help pleaseeee1) What link did you use to download?
the latest build still doesn work for me.
it just doesnt start up on windows 8 ... idk why :(
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.
Try this to find the relevant folder. It might be in different position possibly with different versions of Windows or Keyhotee:help pleaseeee1) What link did you use to download?
the latest build still doesn work for me.
it just doesnt start up on windows 8 ... idk why :(
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
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.
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.
Hello guys, i registered id with version 0.7.0Yes, that's all that's needed, you're fine.
its shows as registered in ver 0.7.1 too
public key 8dc9ejdw8vVoESvmVCHFwX8LCqodziLB3KUoGPGpZErb1Xxb1p
is it well enough?
the link in the op doesnt seem to work.. any working links available?
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
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
server down
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: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.
"..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!
Any body send me a message so I could know I'm on board?
Public Key: 616nhQgVyYS6rpqhaGjwVFf7qR58KJ37VNCn1oX6Zxt1LxtppN
Public Key: 7GzjRYvJm33mXUN3M3aLURrdSLej5qkGt4Poqo1qrT4Pj18PCN
Thanks.
May I ask what time officially outThere'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.
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.
Did this thread move? Seems like a while since the last update.
rubbish product
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).
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: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.
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.
Could you also publish updated binaries for those unable/unwilling to build from source?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.
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.Could you also publish updated binaries for those unable/unwilling to build from source?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.
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?
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 :)
Good day :)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.
Can someone please confirm that my founder ID is registered properly?
Founder ID is 6Ucdmzx5TCduvkdAdh85NefQtp8qtov7YH67etXYZULncPuz3p
Please send a test message.
Thank you
V
Good day :)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.
Can someone please confirm that my founder ID is registered properly?
Founder ID is 6Ucdmzx5TCduvkdAdh85NefQtp8qtov7YH67etXYZULncPuz3p
Please send a test message.
Thank you
V
Yep, you're good to go.Good day :)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.
Can someone please confirm that my founder ID is registered properly?
Founder ID is 6Ucdmzx5TCduvkdAdh85NefQtp8qtov7YH67etXYZULncPuz3p
Please send a test message.
Thank you
V
My founder name is "V"
Thanks for checking, I do see point. Registered with xxx points
Hello, I have problems registering my founder IDs recently.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.
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?
Hello, I have problems registering my founder IDs recently.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.
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?
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.Hello, I have problems registering my founder IDs recently.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.
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?
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.Hello, I have problems registering my founder IDs recently.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.
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?
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.
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?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.Hello, I have problems registering my founder IDs recently.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.
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?
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.
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?
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?
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.
Help!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.
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.
Help!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.
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.
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
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.
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.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, 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).Help!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.
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.
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.
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?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).
Sent from my iPhone using Tapatalk
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.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).
Thanks
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.
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.
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).Help!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.
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.
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.
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.
quesiont: is login password part of "profile data" ?
If you just want to claim your BTSX, check out details in this thread: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?
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.
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.
quesiont: is login password part of "profile data" ?
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.
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.
quesiont: is login password part of "profile data" ?
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
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
Is the shortcut still pointing to the .exe? Can you try running the executable directly?yea it points..
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.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?
idk i just lost my way here since i was not involved in testing process,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.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?
In the BitsharesX wallet use the left menu to go to the console screen and do the following:i did it before, name - hasher, it in genesis chain,
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
where is keyhotee going now?
where is keyhotee going now?
I was wondering the same question...
I have no idea :(