BitShares Forum
Main => Technical Support => Topic started by: luks33 on March 18, 2018, 10:51:00 pm
-
Hi, i am using Tapin faucet to set up a testnet but i get this error when i am trying to create a account
Message: 'Traceback (most recent call last):\n File "/home/luks/bitshares/tapin/app/views.py", line 92, in tapbasic\n additional_active_keys=config.get("additional_active_keys", []),\n File "/home/luks/bitshares/tapin/src/bitshares/bitshares/bitshares.py", line 561, in create_account\n active_key, prefix=self.prefix)\n File "/home/luks/bitshares/tapin/src/bitshares/bitsharesbase/account.py", line 84, in __init__\n super(PublicKey, self).__init__(*args, **kwargs)\n File "/usr/local/lib/python3.5/dist-packages/graphenebase/account.py", line 216, in __init__\n self._pk = Base58(pk, prefix=prefix)\n File "/usr/local/lib/python3.5/dist-packages/graphenebase/base58.py", line 61, in __init__\n raise ValueError("Error loading Base58 object")\nValueError: Error loading Base58 object\n'
Arguments: ()
2018-03-18 18:44:56,214 - app - ERROR - Traceback (most recent call last):
File "/home/luks/bitshares/tapin/app/views.py", line 92, in tapbasic
additional_active_keys=config.get("additional_active_keys", []),
File "/home/luks/bitshares/tapin/src/bitshares/bitshares/bitshares.py", line 561, in create_account
active_key, prefix=self.prefix)
File "/home/luks/bitshares/tapin/src/bitshares/bitsharesbase/account.py", line 84, in __init__
super(PublicKey, self).__init__(*args, **kwargs)
File "/usr/local/lib/python3.5/dist-packages/graphenebase/account.py", line 216, in __init__
self._pk = Base58(pk, prefix=prefix)
File "/usr/local/lib/python3.5/dist-packages/graphenebase/base58.py", line 61, in __init__
raise ValueError("Error loading Base58 object")
ValueError: Error loading Base58 object
127.0.0.1 - - [18/Mar/2018 18:44:56] "POST /api/v1/accounts HTTP/1.1" 200 -
Any help please
-
Any help, please!!!
Thanks
-
That error tells me you'r public keys have a wrong format.
Are you running on BitShares? What's your config looking like?
-
That error tells me you'r public keys have a wrong format.
Are you running on BitShares? What's your config looking like?
Hi xeroc, i am running a testnet.
This is my config.yml file
secret_key: "yyyyyyyyyyyyyyyyyyyyyyyyyyyyyy" # Random keys
nobroadcast: True # Safety mode
mail_host: "SERVER:589"
mail_user: "user"
mail_pass: "password"
mail_from: "noreply@faucet.org"
admins:
- adminA@example.com
- adminB@example.com
minIPAge: 300 # How long in secs does an IP need to wait to register a new account?
witness_url: "ws://127.0.0.1:8090"
registrar: "luks"
default_referrer: "luks"
referrer_percent: 50 # in percent
wif: "xxxxxxxxxxxxxxxxxxxxxxxxxxx"
balance_mailthreshold: 500 # if balances goes below this, you will be notified
prefix: "NPY"
chain:
chain_id: "2e70810ddbefcb2bd523d9ce93f7ef100db99168b84023e0181b28fc1489e8d6"
core_symbol: "NPY"
prefix: "NPY"
core_asset: "NPY"
donation_amount: 10000
donation_asset: "NPY"
Thanks for your answer, is a big help!!!
-
the faucet has been written specifically for bitshares and the testnet (or more precisely, using pybitshares)
It cannot simply hook into a different blockchain because it needs to know the chain id and prefix of the blockchain it connects to.
see:
https://github.com/xeroc/python-bitshares/blob/develop/bitsharesbase/chains.py
-
the faucet has been written specifically for bitshares and the testnet (or more precisely, using pybitshares)
It cannot simply hook into a different blockchain because it needs to know the chain id and prefix of the blockchain it connects to.
see:
https://github.com/xeroc/python-bitshares/blob/develop/bitsharesbase/chains.py
hi xeroc, i realize about that file about two weeks ago and made that change, but the error persists
this is my chains.py file
known_chains = {
"NPY": {
"chain_id": "2e70810ddbefcb2bd523d9ce93f7ef100db99168b84023e0181b28fc1489e8d6",
"core_symbol": "NPY",
"prefix": "NPY"},
}
Any thing else i could try?
thanks in advance
-
I believe to make this work, the wallet-ui needs modifications too in order to format the pubkeys with the proper prefix. Else, the ui would try to crrate accoubt and provide illpresented pubkeys
-
I believe to make this work, the wallet-ui needs modifications too in order to format the pubkeys with the proper prefix. Else, the ui would try to crrate accoubt and provide illpresented pubkeys
Thank you very much xeroc, you point me in the right direction, i got it working now