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

0 Members and 1 Guest are viewing this topic.

Offline puppies

  • Hero Member
  • *****
  • Posts: 1659
    • View Profile
  • BitShares: puppies
I fixed some crashes with the RPC code today.   In case anyone has experienced witness node crashes.

Will we need a new test net or should this sync with current network?
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline bytemaster

I fixed some crashes with the RPC code today.   In case anyone has experienced witness node crashes.
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 Akado

  • Hero Member
  • *****
  • Posts: 2752
    • View Profile
  • BitShares: akado
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
Thanks @abit, it is still not showing up so maybe you are right, I'll watch that issue. Sadly I didn't have the foresight to copy it down   :-\

As there isn't a destroy_witness command I guess I'd have to start with a new account to generate a new witness - not sure I can face that right now!

Many thanks for your help anyhow
I'd like to suggest that you could try start a new chain or maybe a new witness_node (don't sync with current network) and create the witness again, maybe you'll get the keys. I noticed that my keys are same every time in the past 4 test networks.

Good plan, will try that
Hmm maybe registering a new witness account is much easier.
BitShares committee member: abit
BitShares witness: in.abit

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore

Is there a way to claim witness pay yet? It would help to fund testing :).

get_object "1.13.178"
[{
    "id": "1.13.178",
    "owner": "1.2.67159",
    "balance": {
      "amount": 437000000,
      "asset_id": "1.3.0"

Yes, commands here:
Code: [Select]
get_vesting_balances in.abit
withdraw_vesting in.abit 100 CORE true

I think you're allowed to withdraw 4370 CORE.
« Last Edit: September 07, 2015, 07:54:20 pm by abit »
BitShares committee member: abit
BitShares witness: in.abit

Offline bulletproof

Thanks @abit, it is still not showing up so maybe you are right, I'll watch that issue. Sadly I didn't have the foresight to copy it down   :-\

As there isn't a destroy_witness command I guess I'd have to start with a new account to generate a new witness - not sure I can face that right now!

Many thanks for your help anyhow
I'd like to suggest that you could try start a new chain or maybe a new witness_node (don't sync with current network) and create the witness again, maybe you'll get the keys. I noticed that my keys are same every time in the past 4 test networks.

Good plan, will try that
Everything is awesome, or if it isn't it ought to be.

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
Thanks @abit, it is still not showing up so maybe you are right, I'll watch that issue. Sadly I didn't have the foresight to copy it down   :-\

As there isn't a destroy_witness command I guess I'd have to start with a new account to generate a new witness - not sure I can face that right now!

Many thanks for your help anyhow
I'd like to suggest that you could try start a new chain or maybe a new witness_node (don't sync with current network) and create the witness again, maybe you'll get the keys. I noticed that my keys are same every time in the past 4 test networks.
BitShares committee member: abit
BitShares witness: in.abit

Offline bulletproof

Thanks @abit, it is still not showing up so maybe you are right, I'll watch that issue. Sadly I didn't have the foresight to copy it down   :-\

As there isn't a destroy_witness command I guess I'd have to start with a new account to generate a new witness - not sure I can face that right now!

Many thanks for your help anyhow
Everything is awesome, or if it isn't it ought to be.

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
Almost there with my witness - just having trouble finding/adding my witness private key. My witness signing key (starting GPH5..) isn't listed in array output from:

Code: [Select]
dump_private_keys
[[
    "GPH6xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxV",
    "5xxx<private>"
  ],[
    "GPH6xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxj",
    "5xxx<private>"
  ],[
    "GPH7xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxa",
    "5xxx<private>"
  ]
]

Is this simply because I don't have any/enough votes yet?

Code: [Select]
get_witness "e-v"
{
  "id": "1.6.5249",
  "witness_account": "1.2.25428",
  "last_aslot": 0,
  "signing_key": "GPH5xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxX",
  "vote_id": "1:5465",
  "total_votes": 0,
  "url": "url-to-proposal"
}

If so I'd be grateful for some, as I'd like to see if my witness can sign blocks on the AWS free-tier VPS - all running fine on 1GB RAM so far  :)
Voted in.
But I think there is a bug which caused the lost of your signing key. Maybe this issue https://github.com/cryptonomex/graphene/issues/259
I can't find my signing key as well when I re-unlock the wallet. Fortunately I copied it out when I created my witness at first.
BitShares committee member: abit
BitShares witness: in.abit

Offline clayop

  • Hero Member
  • *****
  • Posts: 2033
    • View Profile
    • Bitshares Korea
  • BitShares: clayop
Almost there with my witness - just having trouble finding/adding my witness private key. My witness signing key (starting GPH5..) isn't listed in array output from:

Code: [Select]
dump_private_keys
[[
    "GPH6xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxV",
    "5xxx<private>"
  ],[
    "GPH6xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxj",
    "5xxx<private>"
  ],[
    "GPH7xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxa",
    "5xxx<private>"
  ]
]

Is this simply because I don't have any/enough votes yet?

Code: [Select]
get_witness "e-v"
{
  "id": "1.6.5249",
  "witness_account": "1.2.25428",
  "last_aslot": 0,
  "signing_key": "GPH5xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxX",
  "vote_id": "1:5465",
  "total_votes": 0,
  "url": "url-to-proposal"
}

If so I'd be grateful for some, as I'd like to see if my witness can sign blocks on the AWS free-tier VPS - all running fine on 1GB RAM so far  :)

I think you need at least 1 vote.
Bitshares Korea - http://www.bitshares.kr
Vote for me and see Korean Bitshares community grows
delegate-clayop

Offline bulletproof

Almost there with my witness - just having trouble finding/adding my witness private key. My witness signing key (starting GPH5..) isn't listed in array output from:

Code: [Select]
dump_private_keys
[[
    "GPH6xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxV",
    "5xxx<private>"
  ],[
    "GPH6xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxj",
    "5xxx<private>"
  ],[
    "GPH7xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxa",
    "5xxx<private>"
  ]
]

Is this simply because I don't have any/enough votes yet?

Code: [Select]
get_witness "e-v"
{
  "id": "1.6.5249",
  "witness_account": "1.2.25428",
  "last_aslot": 0,
  "signing_key": "GPH5xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxX",
  "vote_id": "1:5465",
  "total_votes": 0,
  "url": "url-to-proposal"
}

If so I'd be grateful for some, as I'd like to see if my witness can sign blocks on the AWS free-tier VPS - all running fine on 1GB RAM so far  :)
Everything is awesome, or if it isn't it ought to be.

Offline spartako

  • Sr. Member
  • ****
  • Posts: 401
    • View Profile
I will not available for some hours, so I will send CORE when I back at home.

Moreover I'm creating a nodejs library for graphene:
https://github.com/spartako82/node-graphene

I have two command now (see the README in github for usage):

* lastBlocks.js -> see the last blocks with delegate name and number of tx x block
* flood.js -> spam the network creating new accounts


It is very new code and it could have some bugs but feel free to try ;)
« Last Edit: September 07, 2015, 04:35:04 pm by spartako »
wallet_account_set_approval spartako

Offline betax

  • Hero Member
  • *****
  • Posts: 808
    • View Profile
You need to be synced before you can produce blocks. It normally (all the time for me) requires a restart.

Also make sure you have ntp intalled

Code: [Select]
apt-get install ntp
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline spartako

  • Sr. Member
  • ****
  • Posts: 401
    • View Profile
Code: [Select]
199164ms th_a       thread.cpp:95                 thread               ] name:p2p tid:4535488512
199164ms ntp        ntp.cpp:77                    request_now          ] resolving... ["pool.ntp.org",123]
199199ms ntp        ntp.cpp:81                    request_now          ] sending request to 213.136.0.252:123
199199ms th_a       application.cpp:117           reset_p2p_node       ] Adding seed node 104.236.118.105:1776
199200ms th_a       application.cpp:129           reset_p2p_node       ] Configured p2p node to listen on 0.0.0.0:51700
199202ms th_a       application.cpp:179           reset_websocket_serv ] Configured websocket rpc to listen on 127.0.0.1:8090
199203ms th_a       witness.cpp:117               plugin_startup       ] witness plugin:  plugin_startup() begin
199203ms th_a       witness.cpp:124               plugin_startup       ] Launching block production for 1 witnesses.
199203ms th_a       witness.cpp:146               schedule_production_ ] now.time_since_epoch().count(): 1441638199203280 next_second: 2015-09-07T15:03:20
199203ms th_a       witness.cpp:131               plugin_startup       ] witness plugin:  plugin_startup() end
199203ms th_a       main.cpp:165                  main                 ] Started witness node on a chain with 0 blocks.
199203ms th_a       main.cpp:166                  main                 ] Chain ID is 57a6462f35bb7fe448d22b3a8b61dd67663bfdd00b4e4e969f0f5b502813b6c5
199313ms th_a       api.cpp:40                    database_api         ] creating database api 4527827232
199314ms th_a       api.cpp:40                    database_api         ] creating database api 4527828384
200000ms th_a       witness.cpp:176               block_production_loo ] Not producing block because production is disabled until we receive a recent block (see: --enable-stale-production)
200000ms th_a       witness.cpp:146               schedule_production_ ] now.time_since_epoch().count(): 1441638200000180 next_second: 2015-09-07T15:03:21
200574ms ntp        ntp.cpp:147                   read_loop            ] received ntp reply from 213.136.0.252:123
200574ms ntp        ntp.cpp:161                   read_loop            ] ntp offset: -670347, round_trip_delay 1375349
200575ms ntp        ntp.cpp:166                   read_loop            ] received stale ntp reply requested at 2015-09-07T15:03:19, send a new time request
200575ms ntp        ntp.cpp:77                    request_now          ] resolving... ["pool.ntp.org",123]
200576ms ntp        ntp.cpp:81                    request_now          ] sending request to 129.250.35.250:123
200601ms ntp        ntp.cpp:147                   read_loop            ] received ntp reply from 129.250.35.250:123
200601ms ntp        ntp.cpp:161                   read_loop            ] ntp offset: 3814, round_trip_delay 25671
200601ms ntp        ntp.cpp:177                   read_loop            ] ntp_delta_time updated to 3814

hey when trying to start witness node after registered etc .. i'm getting this message .. do i'm anything wrong here?

graphene should be registered as a witness now!

You started your witness with the chain not in sync.
Usually I start the witness without the commands for creating blocks (--witness-id and --private-key params) then when I am in sync I stop and relaunch with params for creating blocks and you should see logs similar to this:

when you are not producing blocks:
Code: [Select]
923000ms th_a       witness.cpp:223               block_production_loo ] Not producing block because slot has not yet arrived
923000ms th_a       witness.cpp:187               schedule_production_ ] now.time_since_epoch().count(): 1441638922998106 next_second: 2015-09-07T15:15:24
924000ms th_a       witness.cpp:223               block_production_loo ] Not producing block because slot has not yet arrived
924001ms th_a       witness.cpp:187               schedule_production_ ] now.time_since_epoch().count(): 1441638923999016 next_second: 2015-09-07T15:15:25
925000ms th_a       witness.cpp:220               block_production_loo ] Not producing block because it isn't my turn
925000ms th_a       witness.cpp:187               schedule_production_ ] now.time_since_epoch().count(): 1441638924998096 next_second: 2015-09-07T15:15:26
925122ms th_a       application.cpp:356           handle_block         ] Got block #101560 from network
926000ms th_a       witness.cpp:223               block_production_loo ] Not producing block because slot has not yet arrived
926001ms th_a       witness.cpp:187               schedule_production_ ] now.time_since_epoch().count(): 1441638925998416 next_second: 2015-09-07T15:15:27

When you produce a block:
Code: [Select]
999000ms th_a       witness.cpp:223               block_production_loo ] Not producing block because slot has not yet arrived
999000ms th_a       witness.cpp:187               schedule_production_ ] now.time_since_epoch().count(): 1441638998998117 next_second: 2015-09-07T15:16:40
1000004ms th_a       witness.cpp:214               block_production_loo ] Generated block #{"n":101574,"t":"2015-09-07T15:16:40","c":"2015-09-07T15:16:40"} with timestamp {"n":101574,"t":"2
015-09-07T15:16:40","c":"2015-09-07T15:16:40"} at time {"n":101574,"t":"2015-09-07T15:16:40","c":"2015-09-07T15:16:40"}
1000004ms th_a       witness.cpp:187               schedule_production_ ] now.time_since_epoch().count(): 1441639000001898 next_second: 2015-09-07T15:16:41
wallet_account_set_approval spartako

Offline cass

  • Hero Member
  • *****
  • Posts: 4311
  • /(┬.┬)\
    • View Profile
Code: [Select]
199164ms th_a       thread.cpp:95                 thread               ] name:p2p tid:4535488512
199164ms ntp        ntp.cpp:77                    request_now          ] resolving... ["pool.ntp.org",123]
199199ms ntp        ntp.cpp:81                    request_now          ] sending request to 213.136.0.252:123
199199ms th_a       application.cpp:117           reset_p2p_node       ] Adding seed node 104.236.118.105:1776
199200ms th_a       application.cpp:129           reset_p2p_node       ] Configured p2p node to listen on 0.0.0.0:51700
199202ms th_a       application.cpp:179           reset_websocket_serv ] Configured websocket rpc to listen on 127.0.0.1:8090
199203ms th_a       witness.cpp:117               plugin_startup       ] witness plugin:  plugin_startup() begin
199203ms th_a       witness.cpp:124               plugin_startup       ] Launching block production for 1 witnesses.
199203ms th_a       witness.cpp:146               schedule_production_ ] now.time_since_epoch().count(): 1441638199203280 next_second: 2015-09-07T15:03:20
199203ms th_a       witness.cpp:131               plugin_startup       ] witness plugin:  plugin_startup() end
199203ms th_a       main.cpp:165                  main                 ] Started witness node on a chain with 0 blocks.
199203ms th_a       main.cpp:166                  main                 ] Chain ID is 57a6462f35bb7fe448d22b3a8b61dd67663bfdd00b4e4e969f0f5b502813b6c5
199313ms th_a       api.cpp:40                    database_api         ] creating database api 4527827232
199314ms th_a       api.cpp:40                    database_api         ] creating database api 4527828384
200000ms th_a       witness.cpp:176               block_production_loo ] Not producing block because production is disabled until we receive a recent block (see: --enable-stale-production)
200000ms th_a       witness.cpp:146               schedule_production_ ] now.time_since_epoch().count(): 1441638200000180 next_second: 2015-09-07T15:03:21
200574ms ntp        ntp.cpp:147                   read_loop            ] received ntp reply from 213.136.0.252:123
200574ms ntp        ntp.cpp:161                   read_loop            ] ntp offset: -670347, round_trip_delay 1375349
200575ms ntp        ntp.cpp:166                   read_loop            ] received stale ntp reply requested at 2015-09-07T15:03:19, send a new time request
200575ms ntp        ntp.cpp:77                    request_now          ] resolving... ["pool.ntp.org",123]
200576ms ntp        ntp.cpp:81                    request_now          ] sending request to 129.250.35.250:123
200601ms ntp        ntp.cpp:147                   read_loop            ] received ntp reply from 129.250.35.250:123
200601ms ntp        ntp.cpp:161                   read_loop            ] ntp offset: 3814, round_trip_delay 25671
200601ms ntp        ntp.cpp:177                   read_loop            ] ntp_delta_time updated to 3814

hey when trying to start witness node after registered etc .. i'm getting this message .. do i'm anything wrong here?

my account: graphene should be registered as a witness now!
« Last Edit: September 07, 2015, 03:10:38 pm by cass »
█║▌║║█  - - -  The quieter you become, the more you are able to hear  - - -  █║▌║║█