Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - dannotestein

Pages: 1 ... 30 31 32 33 34 35 36 [37] 38 39 40 41 42 43 44 ... 51
541
Keyhotee / Re: Keyhotee Status Update
« on: July 25, 2014, 06:08:01 pm »
Sorry that I've tried all possible combinations, but they don't work.
Is there any solution for this kind of situation? Or should I just give up?

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


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

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

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

Anything else I could do?
Thank you
If you're getting a different public key, it means you're not entering the same profile info. The public key generated is a function of your keyhoteeId, first name, middle name, last name, and brainwallet key.

542
Keyhotee / Re: Keyhotee Status Update
« on: July 25, 2014, 04:08:24 pm »
Help!

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

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

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

So in summary, my question is:

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

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

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

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

543
Keyhotee / Re: Keyhotee Status Update
« on: July 25, 2014, 02:37:41 pm »
Sorry that I've tried all possible combinations, but they don't work.
Is there any solution for this kind of situation? Or should I just give up?

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

544
Keyhotee / Re: Keyhotee Status Update
« on: July 25, 2014, 02:24:56 pm »
Hello,  I have problems registering my founder IDs recently.
I could register them before using the folloing information with passwords and founder codes (they are recorded in keepass, so I think they are correct) before:

founder ID: jimewu
pubkey: 8feWmErUhkgxD8QnFpi1tixYvnDrZwjddDhHADFHm9zFv2mz7Q

founder ID: Apple
pubkey: 82zW4ESP6xiazQH4FueXovBMbqUBMzYBhh9QZD3gy1K71nF2z1

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


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

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

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

545
Keyhotee / Re: Keyhotee Status Update
« on: July 25, 2014, 01:48:06 pm »
Hello,  I have problems registering my founder IDs recently.
I could register them before using the folloing information with passwords and founder codes (they are recorded in keepass, so I think they are correct) before:

founder ID: jimewu
pubkey: 8feWmErUhkgxD8QnFpi1tixYvnDrZwjddDhHADFHm9zFv2mz7Q

founder ID: Apple
pubkey: 82zW4ESP6xiazQH4FueXovBMbqUBMzYBhh9QZD3gy1K71nF2z1

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


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

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

546
Keyhotee / Re: Keyhotee Status Update
« on: July 25, 2014, 01:34:49 pm »
Hello,  I have problems registering my founder IDs recently.
I could register them before using the folloing information with passwords and founder codes (they are recorded in keepass, so I think they are correct) before:

founder ID: jimewu
pubkey: 8feWmErUhkgxD8QnFpi1tixYvnDrZwjddDhHADFHm9zFv2mz7Q

founder ID: Apple
pubkey: 82zW4ESP6xiazQH4FueXovBMbqUBMzYBhh9QZD3gy1K71nF2z1

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

547
General Discussion / Re: New Delegate Support Thread
« on: July 23, 2014, 11:20:16 pm »
I've produced over 110 blocks so far since becoming a delegate. I missed 4 as a standby but none since being elected in. I have received zero pay in fees? Have I just been unlucky and producing blocks without any transactions? Or have I set up wrong?

I enabled block production and scan for transactions, is there anything else I should've done?
To see how much you've earned, use:

blockchain_get_account my_delegate_name


Got it thanks. I do have pay!

It doesnt let me withdraw.
I get this:

Code: [Select]
>> wallet_delegate_withdraw_pay skyscraperfarms

Command aborted.

To withdraw, use:
wallet_delegate_withdraw_pay <delegate_name> <to_account_name> <amount_to_withdraw> [memo]

548
General Discussion / Re: New Delegate Support Thread
« on: July 23, 2014, 10:59:20 pm »
I've produced over 110 blocks so far since becoming a delegate. I missed 4 as a standby but none since being elected in. I have received zero pay in fees? Have I just been unlucky and producing blocks without any transactions? Or have I set up wrong?

I enabled block production and scan for transactions, is there anything else I should've done?
To see how much you've earned, use:

blockchain_get_account my_delegate_name

549
Keyhotee / Re: Keyhotee Status Update
« on: July 18, 2014, 05:36:07 am »
Good day  :)

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

Founder ID is 6Ucdmzx5TCduvkdAdh85NefQtp8qtov7YH67etXYZULncPuz3p

Please send a test message.

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

My founder name is "V"

Thanks for checking, I do see point. Registered with xxx points
Yep, you're good to go.

550
Keyhotee / Re: Keyhotee Status Update
« on: July 17, 2014, 07:08:40 pm »
Good day  :)

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

Founder ID is 6Ucdmzx5TCduvkdAdh85NefQtp8qtov7YH67etXYZULncPuz3p

Please send a test message.

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

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

I'll update the build info shortly with the details.
Could you also publish updated binaries for those unable/unwilling to build from source?
We were planning to do that at the beginning of next week after we finished the integration work with bitshares_toolkit executable, but the installer needs to be updated for things like adding the bitshares_client.exe and its dependencies, etc. Right now bytemaster wants the polish dev group to start working on the bitshares_toolkit code itself as soon as possible, so that will probably be delayed a bit.

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

I'll update the build info shortly with the details.

553
Keyhotee / Re: Keyhotee Status Update
« on: May 29, 2014, 02:33:55 pm »
Just to clarify things a little, Keyhotee is still under very active development,

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

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

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

Both links do not work.
Ok, one was a bad cut/paste and the other required you to be signed into github. Try these, hopefully they will work for you:
http://github.com/InvictusInnovations/keyhotee/commits/master
http://github.com/BitShares/bitshares_toolkit/commits/master

554
Keyhotee / Re: Keyhotee Status Update
« on: May 29, 2014, 02:26:22 pm »
Just to clarify things a little, Keyhotee is still under very active development,

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

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

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

555
Keyhotte is a desperately needed now.  But as I was thinking it over, couldn't someone if they were sinister enough (or wanted free adveristing) just do a scan of all the ID's  (or public key) created on the blockchain and send them mass emails? 

Do I have this wrong, or are there any safeguards in the works to prevent this?
Keyhotee will require proof-of-work for sending broadcast messages to non-authorized friends, hence making it costly in terms of CPU power to spam (with an additional cost for each recipient added to the message). It will also support "cpu cheaper" messaging between friends.

Pages: 1 ... 30 31 32 33 34 35 36 [37] 38 39 40 41 42 43 44 ... 51