Test Net for Advanced Users

[Riverhead]

Maybe I made myself a little unclear .. you need to run a witness_node and a cli_node ..
The setup would look like:


Witness (port 8090)   <--->   cli_wallet (port:8092)  <-----> python

A bit. The directions say not to connect to a witness_node . I see now you meant not to fire your script against the witness node.

[betax]

I am joining in the testing.

ID: 1.6.624
Witness Account: 1.2.8112
Account: bitcube

Can someone send me some CORE and vote me in?

how to join? is there any guide?

Check this guide for Ubuntu and test2b https://github.com/cryptonomex/graphene/wiki/How-to-setup-your-witness-for-test-net-(Ubuntu-14.04)

[xeroc]

The only other thing I can think of is in the witness config.ini file there is a parameter called enable-stale-production which needs to be false. I think that's the default now so that's probably not the issue.

I am using 'enable-stale-production' as described in xeroc's guide.  I am going to try without it.

Sorry for that .. I removed it from the wiki

[cube]

The only other thing I can think of is in the witness config.ini file there is a parameter called enable-stale-production which needs to be false. I think that's the default now so that's probably not the issue.

I am using 'enable-stale-production' as described in xeroc's guide.  I am going to try without it.

[xeroc]

you have to run the cli_wallet(!!!) with
-H 127.0.0.1:8092
and unlock your wallet.

My wallet will not run with this flag. Is there anything else needed? My two attempts:

Code: [Select]

cli_wallet -w test2b --chain-id ecbde738ba0b319cb4d266e613b200d010da8b37313c20aec03f9c8e2d9b35e3 -H 127.0.0.1:8092
Logging RPC to file: logs/rpc/rpc.log
2022756ms th_a       main.cpp:111                  main                 ] key_to_wif( committee_private_key ): 5KCBDTcyDqzsqehcb52tW5nU6pXife6V2rX9Yf7c3saYSzbDZ5W
2022757ms th_a       main.cpp:115                  main                 ] nathan_pub_key: GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV
2022757ms th_a       main.cpp:116                  main                 ] key_to_wif( nathan_private_key ): 5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3
2022760ms th_a       main.cpp:163                  main                 ] wdata.ws_server: ws://localhost:8090
0 exception: unspecified
Underlying Transport Error
    {"message":"Underlying Transport Error"}
    asio  websocket.cpp:431 operator()

    {"uri":"ws://localhost:8090"}
    th_a  websocket.cpp:616 connect


Code: [Select]

./cli_wallet -H 127.0.0.1:8092
Logging RPC to file: logs/rpc/rpc.log
2052250ms th_a       main.cpp:111                  main                 ] key_to_wif( committee_private_key ): 5KCBDTcyDqzsqehcb52tW5nU6pXife6V2rX9Yf7c3saYSzbDZ5W
2052250ms th_a       main.cpp:115                  main                 ] nathan_pub_key: GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV
2052250ms th_a       main.cpp:116                  main                 ] key_to_wif( nathan_private_key ): 5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3
Starting a new wallet with chain ID 6d2141a7a5577221d3681a4b6296e330f77a4668ddcd78fbbe4fbe966e54bccc (from egenesis)
2052251ms th_a       main.cpp:163                  main                 ] wdata.ws_server: ws://localhost:8090
0 exception: unspecified
Underlying Transport Error
    {"message":"Underlying Transport Error"}
    asio  websocket.cpp:431 operator()

    {"uri":"ws://localhost:8090"}
    th_a  websocket.cpp:616 connect


Maybe I made myself a little unclear .. you need to run a witness_node and a cli_node ..
The setup would look like:


Witness (port 8090)   <--->   cli_wallet (port:8092)  <-----> python

[Riverhead]

The only other thing I can think of is in the witness config.ini file there is a parameter called enable-stale-production which needs to be false. I think that's the default now so that's probably not the issue.

[cube]

What is your Chain ID? ecbde738ba0b319cb4d266e613b200d010da8b37313c20aec03f9c8e2d9b35e3

I show a different vote count for you:

Code: [Select]

get_witness bitcube
{
  "id": "1.6.624",
  "witness_account": "1.2.8112",
  "last_aslot": 0,
  "signing_key": "GPH7qbi1...y..sn",
  "vote_id": "1:623",
  "total_votes": "64885994140",
  "url": ""
}


Chain ID matches.

Code: [Select]

{
  "head_block_num": 56624,
  "head_block_id": "0000dd308073d87ccb3b0d739f07ebfb6842e95c",
  "head_block_age": "0 second old",
  "next_maintenance_time": "4 minutes in the future",
  "chain_id": "ecbde738ba0b319cb4d266e613b200d010da8b37313c20aec03f9c8e2d9b35e3",
,,,


Code: [Select]

  "total_votes": "64885994140",

Vote count matches too. Yet I am not in the active list.  What's wrong?

[Riverhead]

Is there a way to withdraw witness pay? Would be a good source of testing funds.

[Riverhead]

What is your Chain ID? ecbde738ba0b319cb4d266e613b200d010da8b37313c20aec03f9c8e2d9b35e3

I show a different vote count for you:

Code: [Select]

get_witness bitcube
{
  "id": "1.6.624",
  "witness_account": "1.2.8112",
  "last_aslot": 0,
  "signing_key": "GPH7qbi1...y..sn",
  "vote_id": "1:623",
  "total_votes": "64885994140",
  "url": ""
}


[cube]

You have way more votes than me - not sure why you don't show up in the list. You still don't have an assigned slot either. Are you sure your witness_node recognizes your keys?

How to be really sure?

I got the public key from the signing key in the command 'get_witness bitcube'.

Code: [Select]

get_witness bitcube
{
  "id": "1.6.624",
  "witness_account": "1.2.8112",
  "last_aslot": 0,
  "signing_key": "GPxxxx-PUBLICKEY",
  "vote_id": "1:623",
  "total_votes": "64884389452",
  "url": ""
}


 I looked up the public-private key pair in dump_private_keys

Code: [Select]

dump_private_keys
[[
    "GPxxxx-PUBLICKEY",
    "5Jxxx-PRIVATEKEY"
  ],[
    "GPxxxx-PUBLICKEY2",
    "5Jxxx-PRIVATEKEY2"
  ]
]

I entered the key pair into config.ini

Code: [Select]

# ID of witness controlled by this node (e.g. "1.6.5", quotes are required, may specify multiple times)
witness-id = "1.6.624"

# Tuple of [PublicKey, WIF private key] (may specify multiple times)
private-key = ["GPxxxx-PUBLICKEY","5Jxxx-PRIVATEKEY"]

When I run the witness_node, the log says:

Code: [Select]

57981ms th_a       witness.cpp:84                plugin_initialize    ] witness plugin:  plugin_initialize() begin
57981ms th_a       witness.cpp:94                plugin_initialize    ] key_id_to_wif_pair: ["GPxxxx-PUBLICKEY","5Jxxx-PRIVATEKEY"]
57982ms th_a       witness.cpp:112               plugin_initialize    ] witness plugin:  plugin_initialize() end
58201ms th_a       application.cpp:228           operator()           ] Initializing database...


[Riverhead]

When you first start your witness node does it give you any errors (in blue) about the pub/priv key pair you specified for your witness?

Your slots being 0 probably means you aren't actually signing blocks however you have votes so your witness is good to go.

I think I found the answer.  It is not voted in yet.  Please help vote it in.

You have way more votes than me - not sure why you don't show up in the list. You still don't have an assigned slot either. Are you sure your witness_node recognizes your keys?

[cube]

When you first start your witness node does it give you any errors (in blue) about the pub/priv key pair you specified for your witness?

Your slots being 0 probably means you aren't actually signing blocks however you have votes so your witness is good to go.

I think I found the answer.  It is not voted in yet.  Please help vote it in.

[Riverhead]

When you first start your witness node does it give you any errors (in blue) about the pub/priv key pair you specified for your witness?

Your slots being 0 probably means you aren't actually signing blocks however you have votes so your witness is good to go.

[cube]

The pay_vb shows the vesting balance object ID. If that is accruing funds you're producing blocks.

I think I am connecting to the correct test net but I do not see the 'pay_vb' object.   What did I miss?

Code: [Select]

info
{
  "head_block_num": 56624,
  "head_block_id": "0000dd308073d87ccb3b0d739f07ebfb6842e95c",
  "head_block_age": "0 second old",
  "next_maintenance_time": "4 minutes in the future",
  "chain_id": "ecbde738ba0b319cb4d266e613b200d010da8b37313c20aec03f9c8e2d9b35e3",
,,,


Code: [Select]

get_witness bitcube
{
  "id": "1.6.624",
  "witness_account": "1.2.8112",
  "last_aslot": 0,
  "signing_key": "GPxxxxxxaaaaxxxx",
  "vote_id": "1:623",
  "total_votes": "64885994140",
  "url": ""
}

Edit: I think I found the answer.  It is not voted in yet.  Please help vote it in.

[bulletproof]

Download this Aug-14 snapshot of BitShares:

https://drive.google.com/open?id=0B_GVo0GoC_v_S3lPOWlUbFJFWTQ

If you have a mac, download the draft version of BitShares 0.9.2 which has a new api call
https://github.com/bitshares/bitshares/releases/tag/untagged-4166986045ff28284dc4

This bit in the OP had a link to a new 0.9.2 release with an API call to export all keys. The link is dead and there are no releases since May - is this a red herring?