Author Topic: Test Net for Advanced Users  (Read 263606 times)

0 Members and 1 Guest are viewing this topic.

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
//EDIT: got it, it's due to wrong starting parameters.

Another "5J" problem.. Can't start my witness even though it's voted in :(
Code: [Select]
726136ms th_a       witness.cpp:88                plugin_initialize    ] 10 assert_exception: Assert Exception
base58str.substr( 0, prefix_len ) == prefix:
    {"base58str":"5J9YY***********************************wVCN"}
    th_a  types.cpp:54 public_key_type
726144ms th_a       main.cpp:173                  main                 ] Exiting with error:
10 assert_exception: Assert Exception
base58str.substr( 0, prefix_len ) == prefix:
    {"base58str":"5J9YY***********************************wVCN"}
    th_a  types.cpp:54 public_key_type
rethrow
    {}
    th_a  witness.cpp:88 plugin_initialize

Before restart:
Code: [Select]
unlocked >>> get_witness in.abit
{
  "id": "1.6.5156",
  "witness_account": "1.2.38793",
  "signing_key": "GPH65XNUxWdYGqGyW9NtXdRpNntumLYT1cJ7CNE7F78Pwxrnx6cbV",
  "next_secret_hash": "d210b0644edfcee411f00058dd862279402c61b4",
  "previous_secret": "0000000000000000000000000000000000000000",
  "vote_id": "1:5284",
  "total_votes": 2389598829,
  "url": "url-to-proposal"
}
« Last Edit: August 15, 2015, 10:21:20 pm by abit »
BitShares committee member: abit
BitShares witness: in.abit

Offline puppies

  • Hero Member
  • *****
  • Posts: 1659
    • View Profile
  • BitShares: puppies
After I finally got it right it hung for five to ten minutes.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline betax

  • Hero Member
  • *****
  • Posts: 808
    • View Profile
How long does it take to sync ? Just in case I am still doing something wrong
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline puppies

  • Hero Member
  • *****
  • Posts: 1659
    • View Profile
  • BitShares: puppies
Is there a way to withdraw witness pay yet?

Also I know it's not a big deal but I was going that our bts id's would transfer over to 2.0.  For example I'm kinda proud of the fact that dele-puppy is account number 1193 in bts.  Just as a status symbol that it's an old account.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline betax

  • Hero Member
  • *****
  • Posts: 808
    • View Profile
Thanks, I was wondering what was that parameter.. and why it was not loading from config.

This is my final version, which parses correctly the private key, I have removed the -d test-net as per puppies recommendation.
Code: [Select]
./witness_node --rpc-endpoint "127.0.0.1:8090"  --genesis-json aug-14-test-genesis.json -s 104.200.28.117:61705 --witness-id '"1.6.5155"' --private-key '["GP...................................oy", "5KW.......................P8a"]'

Edit:
I edited the wiki, to fix the parameter issues. Mainly you need to wrap strings that required double quotes, with single quotes.
« Last Edit: August 15, 2015, 10:15:57 pm by betax »
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline puppies

  • Hero Member
  • *****
  • Posts: 1659
    • View Profile
  • BitShares: puppies
Well next issue my key / private are not loading, they are different ones from the config, and getting a parsing error as parameters

It took me awhile to realize that the -d test_net I'm bytemasters instructions was the data directory.  I was modifying the wrong config.ini.  that might be your issue.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline betax

  • Hero Member
  • *****
  • Posts: 808
    • View Profile
Well next issue my key / private are not loading, they are different ones from the config, and getting a parsing error as parameters
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline betax

  • Hero Member
  • *****
  • Posts: 808
    • View Profile
Code: [Select]
./witness_node --rpc-endpoint "127.0.0.1:8090"  --genesis-json aug-14-test-genesis.json -d test_net -s 104.200.28.117:61705 --enable-stale-production -w '"1.6.5155"' I have my key, private key in the config.ini

https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline clayop

  • Hero Member
  • *****
  • Posts: 2033
    • View Profile
    • Bitshares Korea
  • BitShares: clayop
I guess that array parameters have been a new addition and xeroc has not been able to catch up on his document.

Great! Can you write down an example (EXCEPT your private key) for dummies like me?
Bitshares Korea - http://www.bitshares.kr
Vote for me and see Korean Bitshares community grows
delegate-clayop

Offline betax

  • Hero Member
  • *****
  • Posts: 808
    • View Profile
It might be a recent transaction that wasn't on the snapshot.

Edit: Just noticed you said all the 5Js so it is a pattern... Ill check when my witness finish synching loading, and see if I have a 5j to test.
« Last Edit: August 15, 2015, 09:24:23 pm by betax »
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
//EDIT: solved. my fault again. copy & paste but lost one character..

I met a problem while importing balance (the real keys replaced by *** ):

Code: [Select]
import_balance in.abit [5K58****dGSz,5KSE****EHJd,5HuJ****uzj7,5KPR****zmq8,5KUn****kzno,5Jtc****D4R4,5Jus****EpCH,5JNv****KfWz] true
10 assert_exception: Assert Exception
priv_key: Invalid Private Key
    {"key":"5Jtc****D4R4"}
    th_a  wallet.cpp:2710 import_balance

    {"name_or_id":"in.abit"}
    th_a  wallet.cpp:2757 import_balance
It works if I remove that key from the array. It also work if I import that key alone.
Any thoughts?
« Last Edit: August 15, 2015, 11:27:36 pm by abit »
BitShares committee member: abit
BitShares witness: in.abit

Offline betax

  • Hero Member
  • *****
  • Posts: 808
    • View Profile
I guess that array parameters have been a new addition and xeroc has not been able to catch up on his document.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline betax

  • Hero Member
  • *****
  • Posts: 808
    • View Profile
I have found the issue, you  both were right. It needs to be changed on the wiki too.

From the github main page, this is the right format.
Code: [Select]
./witness_node --rpc-endpoint 127.0.0.1:8090 --enable-stale-production -w '"1.6.0"' '"1.6.1"' '"1.6.2"' '"1.6.3"' '"1.6.4"' '"1.6.5"' '"1.6.6"' '"1.6.7"' '"1.6.8"' '"1.6.9"'

It needs to be wrapped in single quotes and double quotes, so when parsing is not treated as a number.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline puppies

  • Hero Member
  • *****
  • Posts: 1659
    • View Profile
  • BitShares: puppies
Thanks clayop.. your brackets on the other post hinted the answer. Xeroc don't worry your instructions are really good.

Another problem, now when I try to start the witness, I get a decimal parse error for --witness-id "1.6.5155"

Code: [Select]
parse_error_exception: Parse Error
Can't parse a number with two decimal places
    {}
    th_a  json.cpp:277 number_from_stream

    {"str":"1.6.5155"}
    th_a  json.cpp:478 from_string
rethrow
    {}
    th_a  witness.cpp:88 plugin_initialize

I have tried to configure the witness-id in the config.ini but I get this warning:

Code: [Select]
3312033ms th_a       witness.cpp:70                plugin_initialize    ] key_id_to_wif_pair: ["GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV","wif key"]
3312121ms th_a       thread.cpp:95                 thread               ] name:ntp tid:139624819738368
3312121ms ntp        ntp.cpp:77                    request_now          ] resolving... ["pool.ntp.org",123]
3312121ms th_a       thread.cpp:95                 thread               ] name:p2p tid:139624800855808
3312289ms ntp        ntp.cpp:81                    request_now          ] sending request to 172.82.134.52:123
3312289ms th_a       application.cpp:116           reset_p2p_node       ] Adding seed node 104.200.28.117:61705
3312290ms th_a       application.cpp:128           reset_p2p_node       ] Configured p2p node to listen on 0.0.0.0:53031
3312292ms th_a       application.cpp:178           reset_websocket_serv ] Configured websocket rpc to listen on 127.0.0.1:8090
[b]3312292ms th_a       witness.cpp:143               plugin_startup       ] No witnesses configured! Please add witness IDs and private keys to configuration.[/b]
3312292ms th_a       main.cpp:165                  main                 ] Started witness node on a chain with 0 blocks.
3312292ms th_a       main.cpp:166                  main                 ] Chain ID is cefacd8adb8bee2bf3b757e882d2828297ceb67b1882982cbde882688ecb46a8
3312395ms ntp        ntp.cpp:147                   read_loop            ] received ntp reply from 172.82.134.52:123
3312395ms ntp        ntp.cpp:161                   read_loop            ] ntp offset: 1679989, round_trip_delay 106243
3312395ms ntp        ntp.cpp:177                   read_loop            ] ntp_delta_time updated to 1679989

Any thoughts ?

Note: I am doing this in between family time, hence the delay on the postings

I had the same errors.  I ended up fixing it by changing test_net/config.in I to
Code: [Select]
# ID of witness controlled by this node (e.g. "1.6.0", quotes are required, may specify multiple times)
witness-id = "1.6.1435"

# Tuple of [PublicKey, WIF private key] (may specify multiple times)
private-key = ["GPHxxxxxxxxxx", "privatexxxxxxx"]
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline clayop

  • Hero Member
  • *****
  • Posts: 2033
    • View Profile
    • Bitshares Korea
  • BitShares: clayop
Thanks clayop.. your brackets on the other post hinted the answer. Xeroc don't worry your instructions are really good.

Another problem, now when I try to start the witness, I get a decimal parse error for --witness-id "1.6.5155"

Code: [Select]
parse_error_exception: Parse Error
Can't parse a number with two decimal places
    {}
    th_a  json.cpp:277 number_from_stream

    {"str":"1.6.5155"}
    th_a  json.cpp:478 from_string
rethrow
    {}
    th_a  witness.cpp:88 plugin_initialize

I have tried to configure the witness-id in the config.ini but I get this warning:

Code: [Select]
3312033ms th_a       witness.cpp:70                plugin_initialize    ] key_id_to_wif_pair: ["GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV","wif key"]
3312121ms th_a       thread.cpp:95                 thread               ] name:ntp tid:139624819738368
3312121ms ntp        ntp.cpp:77                    request_now          ] resolving... ["pool.ntp.org",123]
3312121ms th_a       thread.cpp:95                 thread               ] name:p2p tid:139624800855808
3312289ms ntp        ntp.cpp:81                    request_now          ] sending request to 172.82.134.52:123
3312289ms th_a       application.cpp:116           reset_p2p_node       ] Adding seed node 104.200.28.117:61705
3312290ms th_a       application.cpp:128           reset_p2p_node       ] Configured p2p node to listen on 0.0.0.0:53031
3312292ms th_a       application.cpp:178           reset_websocket_serv ] Configured websocket rpc to listen on 127.0.0.1:8090
[b]3312292ms th_a       witness.cpp:143               plugin_startup       ] No witnesses configured! Please add witness IDs and private keys to configuration.[/b]
3312292ms th_a       main.cpp:165                  main                 ] Started witness node on a chain with 0 blocks.
3312292ms th_a       main.cpp:166                  main                 ] Chain ID is cefacd8adb8bee2bf3b757e882d2828297ceb67b1882982cbde882688ecb46a8
3312395ms ntp        ntp.cpp:147                   read_loop            ] received ntp reply from 172.82.134.52:123
3312395ms ntp        ntp.cpp:161                   read_loop            ] ntp offset: 1679989, round_trip_delay 106243
3312395ms ntp        ntp.cpp:177                   read_loop            ] ntp_delta_time updated to 1679989

Any thoughts ?

Note: I am doing this in between family time, hence the delay on the postings

Maybe a minor bug. I resolved the same problem by using cookbook

Code: [Select]
--witness-id \""1.6.xxxx"\
If it does not work, change quote marks in the private key section together.
Bitshares Korea - http://www.bitshares.kr
Vote for me and see Korean Bitshares community grows
delegate-clayop