Author Topic: wallet_import_keyhotee failed, caused my keyhotee id starts with numbers?  (Read 4620 times)

0 Members and 1 Guest are viewing this topic.

Offline toast

  • Hero Member
  • *****
  • Posts: 4001
    • View Profile
  • BitShares: nikolai
Keyhotee IDs that are not valid account names we were unable to reserve.

When register the found id, there's no rule said this is not a valid name, same others may have the same problem using numbers or symbols to start a name...

What to do in such situation? Dose the ID is lost?

They are still valid for keyhotee.
Getting into the BTSX genesis block was a bonus that not everyone could get because of name restrictions. You will still get keyhotee AGS via manual distribution like all founders.

That's too bad, when donate to the found id, it was claimed this will be part of the genesis block. When it changed to "Getting into the BTSX genesis block was a bonus that not everyone could get because of name restrictions"??

For keyhotee ids with space in names, how to handle them either?

It was claimed you will be part of the *keyhotee* genesis block. BTS did not even have names planned at that time.
For space in names, put your name in quotes like "First Name" MiddleName LastName
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

Offline 029xue

  • Full Member
  • ***
  • Posts: 142
    • View Profile
Keyhotee IDs that are not valid account names we were unable to reserve.

When register the found id, there's no rule said this is not a valid name, same others may have the same problem using numbers or symbols to start a name...

What to do in such situation? Dose the ID is lost?

They are still valid for keyhotee.
Getting into the BTSX genesis block was a bonus that not everyone could get because of name restrictions. You will still get keyhotee AGS via manual distribution like all founders.

That's too bad, when donate to the found id, it was claimed this will be part of the genesis block. When it changed to "Getting into the BTSX genesis block was a bonus that not everyone could get because of name restrictions"??

For keyhotee ids with space in names, how to handle them either?

Offline toast

  • Hero Member
  • *****
  • Posts: 4001
    • View Profile
  • BitShares: nikolai
Keyhotee IDs that are not valid account names we were unable to reserve.

When register the found id, there's no rule said this is not a valid name, same others may have the same problem using numbers or symbols to start a name...

What to do in such situation? Dose the ID is lost?

They are still valid for keyhotee.
Getting into the BTSX genesis block was a bonus that not everyone could get because of name restrictions. You will still get keyhotee AGS via manual distribution like all founders.
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

Offline 029xue

  • Full Member
  • ***
  • Posts: 142
    • View Profile
Keyhotee IDs that are not valid account names we were unable to reserve.

When register the found id, there's no rule said this is not a valid name, same others may have the same problem using numbers or symbols to start a name...

What to do in such situation? Dose the ID is lost?

Offline 029xue

  • Full Member
  • ***
  • Posts: 142
    • View Profile
I tried but not worked, you can see the keyhotee id correctly parsed, the error is thrown from

Code: [Select]
20017 invalid_name: invalid wallet name
nvalid Keyhotee name!
    {"keyhoteeid":"029xue"}
    bitshares  wallet.cpp:3629 bts::wallet::wallet::import_keyhotee
error creating private key using keyhotee info.

Any other ideas?

That name seems to not be registered on the blockchain
Code: [Select]
default (unlocked) >>> blockchain_get_account "029xue"
No account found.
default (unlocked) >>> blockchain_get_account 029xue
No account found.

You registered with a public key? what is the pubkey?

My public id is:
616nhQgVyYS6rpqhaGjwVFf7qR58KJ37VNCn1oX6Zxt1LxtppN

Please have a check. Thanks.

Offline bytemaster

Keyhotee IDs that are not valid account names we were unable to reserve.
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
I tried but not worked, you can see the keyhotee id correctly parsed, the error is thrown from

Code: [Select]
20017 invalid_name: invalid wallet name
nvalid Keyhotee name!
    {"keyhoteeid":"029xue"}
    bitshares  wallet.cpp:3629 bts::wallet::wallet::import_keyhotee
error creating private key using keyhotee info.

Any other ideas?

That name seems to not be registered on the blockchain
Code: [Select]
default (unlocked) >>> blockchain_get_account "029xue"
No account found.
default (unlocked) >>> blockchain_get_account 029xue
No account found.

You registered with a public key? what is the pubkey?

Offline 029xue

  • Full Member
  • ***
  • Posts: 142
    • View Profile
I tried but not worked, you can see the keyhotee id correctly parsed, the error is thrown from

Code: [Select]
20017 invalid_name: invalid wallet name
nvalid Keyhotee name!
    {"keyhoteeid":"029xue"}
    bitshares  wallet.cpp:3629 bts::wallet::wallet::import_keyhotee
error creating private key using keyhotee info.

Any other ideas?

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc

Offline 029xue

  • Full Member
  • ***
  • Posts: 142
    • View Profile
Hi,
I use wallet_import_keyhotee to import my keyhotee id but failed with below error:

Code: [Select]
wallet_import_keyhotee FIRSTNAME "" LASTNAME "brainkeyiscorrect" 029xue

20017 invalid_name: invalid wallet name
nvalid Keyhotee name!
    {"keyhoteeid":"029xue"}
    bitshares  wallet.cpp:3629 bts::wallet::wallet::import_keyhotee
error creating private key using keyhotee info.
    {"firstname":"FIRSTNAME","middlename":"","lastname":"LASTNAME","brainkey":"brainkeyiscorrect","keyhoteeid":"029xue"}
    bitshares  wallet.cpp:3644 bts::wallet::wallet::import_keyhotee

    {}
    bitshares  common_api_client.cpp:675 bts::rpc_stubs::common_api_client::wallet_import_keyhotee

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

Dose that "Invalid Keyhotee name!" caused by my keyhotee id starts with numbers?

I saw the register page seems not allowed account name start with numbers, how to workaround that?

Thanks.