[ANN] Keyhotee users and Delegate requests for KeyID.

[toast]

Yes, TLD names will be removed and not allowed

[king]

This will be the ongoing list that I will edit as needed. 

mf-tzo  ->  zeus
King -> king

The keyhotee founder id "King" belongs to me, in addition, I have another Keyhotee founder id need to be modified,
Value -> com

"com" will not be a valid name.

according  to the rules 
it seems like  “com”  shoud registered to be delegate in bitsharesX  before the delegate snapshot
same for  net org

>> blockchain_get_account com

Name: com
Registered: 2014-07-19T03:38:50
Last Updated: 20 days ago
Owner Key: BTSX6Uf6USpptoXJUZHQEcMojyxdFkJjSM53yKRxJMJLtZUm64VvSX
Active Key History:
- BTSX6Uf6USpptoXJUZHQEcMojyxdFkJjSM53yKRxJMJLtZUm64VvSX, last used 20 days ago
Not a delegate.
Public Data:
{
  "gravatarID": ""
}


>> blockchain_get_account  org

Name: org
Registered: 2014-07-19T03:39:00
Last Updated: 20 days ago
Owner Key: BTSX8Z4mNXBZfEnPh5uY6LcHLJVtqgBCG7H3TAFDxyjJfZ3utXoDcH
Active Key History:
- BTSX8Z4mNXBZfEnPh5uY6LcHLJVtqgBCG7H3TAFDxyjJfZ3utXoDcH, last used 20 days ago
Not a delegate.
Public Data:
{
  "gravatarID": ""
}
>> blockchain_get_account  net

Name: net
Registered: 2014-07-19T03:39:10
Last Updated: 20 days ago
Owner Key: BTSX5oFP7nYNvChYnRt6yTtRo5XKZUkzbMckxbKD6hZ7yBowCaLs4r
Active Key History:
- BTSX5oFP7nYNvChYnRt6yTtRo5XKZUkzbMckxbKD6hZ7yBowCaLs4r, last used 20 days ago
Not a delegate.
Public Data:
{
  "gravatarID": ""
}

thanks,I did comply with changes to the rules, if possible, I hope this change:
"Value" -> "com"
Of course, "do" is my second choice

Name: do
Registered: 2014-07-19T20:56:20
Last Updated: 19 days ago
Owner Key: BTSX5U9uMfr28b6Trni3j7KhLzLufQkBaWrowjwvhHsaM9b2KSBQXe
Active Key History:
- BTSX5U9uMfr28b6Trni3j7KhLzLufQkBaWrowjwvhHsaM9b2KSBQXe, last used 19 days ago
Not a delegate.
Public Data:
{
  "gravatarID": "6047a5cdda2ce9f6630201c4ff2403f5"
}

[sudo]

This will be the ongoing list that I will edit as needed. 

mf-tzo  ->  zeus
King -> king

The keyhotee founder id "King" belongs to me, in addition, I have another Keyhotee founder id need to be modified,
Value -> com

"com" will not be a valid name.

according  to the rules 
it seems like  “com”  shoud registered to be delegate in bitsharesX  before the delegate snapshot
same for  net org

>> blockchain_get_account com

Name: com
Registered: 2014-07-19T03:38:50
Last Updated: 20 days ago
Owner Key: BTSX6Uf6USpptoXJUZHQEcMojyxdFkJjSM53yKRxJMJLtZUm64VvSX
Active Key History:
- BTSX6Uf6USpptoXJUZHQEcMojyxdFkJjSM53yKRxJMJLtZUm64VvSX, last used 20 days ago
Not a delegate.
Public Data:
{
  "gravatarID": ""
}


>> blockchain_get_account  org

Name: org
Registered: 2014-07-19T03:39:00
Last Updated: 20 days ago
Owner Key: BTSX8Z4mNXBZfEnPh5uY6LcHLJVtqgBCG7H3TAFDxyjJfZ3utXoDcH
Active Key History:
- BTSX8Z4mNXBZfEnPh5uY6LcHLJVtqgBCG7H3TAFDxyjJfZ3utXoDcH, last used 20 days ago
Not a delegate.
Public Data:
{
  "gravatarID": ""
}
>> blockchain_get_account  net

Name: net
Registered: 2014-07-19T03:39:10
Last Updated: 20 days ago
Owner Key: BTSX5oFP7nYNvChYnRt6yTtRo5XKZUkzbMckxbKD6hZ7yBowCaLs4r
Active Key History:
- BTSX5oFP7nYNvChYnRt6yTtRo5XKZUkzbMckxbKD6hZ7yBowCaLs4r, last used 20 days ago
Not a delegate.
Public Data:
{
  "gravatarID": ""
}

[king]

This will be the ongoing list that I will edit as needed. 

mf-tzo  ->  zeus
King -> king

The keyhotee founder id "King" belongs to me, in addition, I have another Keyhotee founder id need to be modified,
Value -> com

"com" will not be a valid name.

ok,I changed to
Value -> do

[toast]

This will be the ongoing list that I will edit as needed. 

mf-tzo  ->  zeus
King -> king

The keyhotee founder id "King" belongs to me, in addition, I have another Keyhotee founder id need to be modified,
Value -> com

"com" will not be a valid name.

[king]

This will be the ongoing list that I will edit as needed. 

mf-tzo  ->  zeus
King -> king

The keyhotee founder id "King" belongs to me, in addition, I have another Keyhotee founder id need to be modified,
Value -> com

[sudo]

“mi” was note a delegate when i make an answer in this thread yesterday.So i think i have the right to update my id to "mi",because i believe 3i will be justice to everyone.

Keyhotee Founder:  XiaoMi ->  mi
Is your desired KeyID squatted on BTSX?:   yes,"mi" （it was registed by the other people but not me)

Finally thanks for your hard work! 

xiaomi  is not registed by me

mi is registed by me

why you not choose xiaomi ?  not a delegates id& he registered the"xiaomi" id  because of ID system‘s bug


>> blockchain_get_account  xiaomi

Name: xiaomi
Registered: 2014-07-19T22:41:00
Last Updated: 18 days ago
Owner Key: BTSX4wo1Hagazg17ffgonZRuCmDwWfk7uTC4A8gjhenw69wAtU2La1
Active Key History:
- BTSX4wo1Hagazg17ffgonZRuCmDwWfk7uTC4A8gjhenw69wAtU2La1, last used 18 days ago
Not a delegate.
Public Data:
{
  "gravatarID": "8e5bca264f2f60a4a8a408c93065a869"
}

gamey says  “I have yet to parse the BTSX chain for delegate IDs.”

I think  according to the rules
“All BTSX delegate names will be put inside the new DNS KeyID chain.
- Unless the owner wishes to substitute out a new name
- Unless this name is an existing Keyhotee name

All Keyhotee IDs will be put inside the new DNS KeyID chain by default if the name is legal. [1]
- Unless a substitution request is made.
”

anyone of bitshares id who have seen the thread  “ [ANN] Keyhotee users and Delegate requests for KeyID.  ”
have the rights to  decide Whether or not registered delegates  for saving time&costs in DNS before the  Bitshares delegate id snapshot.

for example   Bitshares delegate id snapshot is  Aug.14
after a week  Aug.21  DNS take  snapshot.

mi is delegates before Bitshares delegate id snapshot
mi is not keyhotee id


for example  toast have the id  "n"
not delegate now
if  it's still not  delegate ,any of keyhotee ider can rename his id to “n”
but if  toast  registered it to be delegates before snapshot,then the rename to be "n" is invalid
because  n  is not a keyhotee id before

[0dayZh]

Keyhotee Founder:  0dayZh ->  mr.sm
Is your desired KeyID squatted on BTSX?:   N/A

[JetainM]

“mi” was note a delegate when i make an answer in this thread yesterday.So i think i have the right to update my id to "mi",because i believe 3i will be justice to everyone.

Keyhotee Founder:  XiaoMi ->  mi
Is your desired KeyID squatted on BTSX?:   yes,"mi" （it was registed by the other people but not me)

Finally thanks for your hard work! 

xiaomi  is not registed by me

mi is registed by me

why you not choose xiaomi ?  not a delegates id& he registered the"xiaomi" id  because of ID system‘s bug


>> blockchain_get_account  xiaomi

Name: xiaomi
Registered: 2014-07-19T22:41:00
Last Updated: 18 days ago
Owner Key: BTSX4wo1Hagazg17ffgonZRuCmDwWfk7uTC4A8gjhenw69wAtU2La1
Active Key History:
- BTSX4wo1Hagazg17ffgonZRuCmDwWfk7uTC4A8gjhenw69wAtU2La1, last used 18 days ago
Not a delegate.
Public Data:
{
  "gravatarID": "8e5bca264f2f60a4a8a408c93065a869"
}

[liondani]

@Brent .. probably only brentallsop is a valid inital name for new DACS as the 'dot' in the name indicates sub account names ... to have one of those you need to register 'allsop' ..

it is unfortunate that keyhotee naming is different from bitshares naming .. but I see the security is a good reason for this ..

Thanks xeroc,

so if I get allsop, will I then be able to create and use brent.allsop as my domain id in the DAC?



I guess I want brentallsop and allsop.  What do I need to do to get these in the new domain DAC?

If I am right register as delegates on BTSX:

allsop
brent.allsop
brentallsop

normaly all three will be yours on the new DNS DAC

[gamey]

I am going to send out emails to everyone tomorrow who has not provided a valid name.

If you have provided a valid name in this thread and receive the email, please ignore it. 

I don't really wish to comment on any specific case until I am able to look into it.  I have yet to parse the BTSX chain for delegate IDs.

I will prioritize any Keyhotee founder or elected delegate.  If these 2 people collide over a name then I will have to make a decision.

If you are active in the community I will do my best to accommodate your wishes.

[alt]

can I change both the name and the address?
because the delegate account is running in a VPS,  I think it's not much safe.
delegate-alt  rename to alt
delegate-baozi rename to baozi
delegate-dorian rename to dorian
delegate-watchman rename to sjtu
delegate-dragon rename to am

Code: [Select]

  "    },{",
  "      \"name\": \"alt\",",
  "      \"delegate_pay_rate\": 100,",
  "      \"owner\": \"BTSX84PrLNkoLdo8p3SmfkN8reg7EsLL5PkKh6p7bdmKvkiA3RoWsf\"",
  "    },{",
  "      \"name\": \"dorian\",",
  "      \"delegate_pay_rate\": 100,",
  "      \"owner\": \"BTSX6JiUxJ1aq1CdZNJ8nUpi2VtFU37XGuYAEkNNYKp8aAUwkBncbd\"",
  "    },{",
  "      \"name\": \"baozi\",",
  "      \"delegate_pay_rate\": 100,",
  "      \"owner\": \"BTSX8EUcKLoARmJgivsTpwcUkSShPvg4g4xp5HL3qN1h3RWaLadgEG\"",
  "    },{",
  "      \"name\": \"sjtu\",",
  "      \"delegate_pay_rate\": 100,",
  "      \"owner\": \"BTSX6sEHMQtfKBSFGHbzub3yhDKFQKN7UU1xVhaU3kiaL4K1ZiyfGC\"",
  "    },{",
  "      \"name\": \"am\",",
  "      \"delegate_pay_rate\": 100,",
  "      \"owner\": \"BTSX5pJNUShegiHr2nfN2v4oqrvJDdQXXkcphkSz7ypucQAWu2rgRX\"",
 

[sudo]

Keyhotee Founder:  XiaoMi ->  mi
Is your desired KeyID squatted on BTSX?:   yes,"mi" （it was registed by the other people but not me)

Finally thanks for your hard work! 

xiaomi  is not registed by me

mi is registed by me

why you not choose xiaomi ?  not a delegates id& he registered the"xiaomi" id  because of ID system‘s bug


>> blockchain_get_account  xiaomi

Name: xiaomi
Registered: 2014-07-19T22:41:00
Last Updated: 18 days ago
Owner Key: BTSX4wo1Hagazg17ffgonZRuCmDwWfk7uTC4A8gjhenw69wAtU2La1
Active Key History:
- BTSX4wo1Hagazg17ffgonZRuCmDwWfk7uTC4A8gjhenw69wAtU2La1, last used 18 days ago
Not a delegate.
Public Data:
{
  "gravatarID": "8e5bca264f2f60a4a8a408c93065a869"
}

[Brent.Allsop]

@Brent .. probably only brentallsop is a valid inital name for new DACS as the 'dot' in the name indicates sub account names ... to have one of those you need to register 'allsop' ..

it is unfortunate that keyhotee naming is different from bitshares naming .. but I see the security is a good reason for this ..

Thanks xeroc,

so if I get allsop, will I then be able to create and use brent.allsop as my domain id in the DAC?

I guess I want brentallsop and allsop.  What do I need to do to get these in the new domain DAC?

[sudo]

if  someone's(A) keyhotee id is  "aaaa"
someone's(B) btsx id is  "bbbb"  with delegate registered   &  "bbbb"  is not a  keyhotee founder id

then  aaaa want's chang to "bbbb"

then   who(AorB?)  get the  "bbbb" id in  DNS?