Test Net for Advanced Users

[iHashFury]

So do I need to checkout aug-17-testnet on git

Code: [Select]

git checkout origin/aug-17-testnet
building now

[puppies]

Is this command useful? @Riverhead

Code: [Select]

rm -rf object_database*


A good suggestion but it did not take me off 9c. It did however widen my scope outside of the data directory for my reset script so thanks for that .

Is your wallet launched with this command?

Code: [Select]

./cli_wallet -w wallet-testnet-puppies.json --chain-id 081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6


I'm not running the wallet currently - just the witness_node.

Code: [Select]


 ./witness_node -d .graphene --genesis-json '"aug-14-test-genesis.json"'
2125632ms th_a       witness.cpp:70                plugin_initialize    ] key_id_to_wif_pair: ["GPH7kNZtp64ZR1R4yC2w9.","5J.Qw8pmqgsK"]
2131814ms th_a       thread.cpp:95                 thread               ] name:ntp tid:140335251613440
2131815ms ntp        ntp.cpp:77                    request_now          ] resolving... ["pool.ntp.org",123]
2131815ms th_a       thread.cpp:95                 thread               ] name:p2p tid:140335228999424
2131860ms ntp        ntp.cpp:81                    request_now          ] sending request to 50.116.36.122:123
2131860ms th_a       application.cpp:117           reset_p2p_node       ] Adding seed node 45.55.6.216:1776
2131862ms th_a       application.cpp:129           reset_p2p_node       ] Configured p2p node to listen on 127.0.0.1:8090
2131863ms th_a       application.cpp:179           reset_websocket_serv ] Configured websocket rpc to listen on 127.0.0.1:8091
2131863ms th_a       witness.cpp:143               plugin_startup       ] No witnesses configured! Please add witness IDs and private keys to configuration.
2131863ms th_a       main.cpp:165                  main                 ] Started witness node on a chain with 0 blocks.
2131863ms th_a       main.cpp:166                  main                 ] Chain ID is a629fd737e0b4d8becc25e33b90984840723b38cd4430049693059f6e396b89c
2131885ms ntp        ntp.cpp:147                   read_loop            ] received ntp reply from 50.116.36.122:123
2131885ms ntp        ntp.cpp:161                   read_loop            ] ntp offset: -2120353, round_trip_delay 25204
2131886ms ntp        ntp.cpp:177                   read_loop            ] ntp_delta_time updated to -2120353


I was building on another computer yesterday, and had to switch back to a git head from the 14th in order to get it to connect with the correct chain-id.  Checking out and building bf47a1610c4aef7e25592aa42ecd4d4ae83a2b5f worked, but I still don't know how the chain-id is derived https://github.com/cryptonomex/graphene/wiki/chain-locked-tx explains why they are important, but not sure how they are generated.

[Riverhead]

Is this command useful? @Riverhead

Code: [Select]

rm -rf object_database*


A good suggestion but it did not take me off 9c. It did however widen my scope outside of the data directory for my reset script so thanks for that .

Is your wallet launched with this command?

Code: [Select]

./cli_wallet -w wallet-testnet-puppies.json --chain-id 081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6


I'm not running the wallet currently - just the witness_node.

Code: [Select]


 ./witness_node -d .graphene --genesis-json '"aug-14-test-genesis.json"'
2125632ms th_a       witness.cpp:70                plugin_initialize    ] key_id_to_wif_pair: ["GPH7kNZtp64ZR1R4yC2w9.","5J.Qw8pmqgsK"]
2131814ms th_a       thread.cpp:95                 thread               ] name:ntp tid:140335251613440
2131815ms ntp        ntp.cpp:77                    request_now          ] resolving... ["pool.ntp.org",123]
2131815ms th_a       thread.cpp:95                 thread               ] name:p2p tid:140335228999424
2131860ms ntp        ntp.cpp:81                    request_now          ] sending request to 50.116.36.122:123
2131860ms th_a       application.cpp:117           reset_p2p_node       ] Adding seed node 45.55.6.216:1776
2131862ms th_a       application.cpp:129           reset_p2p_node       ] Configured p2p node to listen on 127.0.0.1:8090
2131863ms th_a       application.cpp:179           reset_websocket_serv ] Configured websocket rpc to listen on 127.0.0.1:8091
2131863ms th_a       witness.cpp:143               plugin_startup       ] No witnesses configured! Please add witness IDs and private keys to configuration.
2131863ms th_a       main.cpp:165                  main                 ] Started witness node on a chain with 0 blocks.
2131863ms th_a       main.cpp:166                  main                 ] Chain ID is a629fd737e0b4d8becc25e33b90984840723b38cd4430049693059f6e396b89c
2131885ms ntp        ntp.cpp:147                   read_loop            ] received ntp reply from 50.116.36.122:123
2131885ms ntp        ntp.cpp:161                   read_loop            ] ntp offset: -2120353, round_trip_delay 25204
2131886ms ntp        ntp.cpp:177                   read_loop            ] ntp_delta_time updated to -2120353


[abit]

Is this command useful? @Riverhead

Code: [Select]

rm -rf object_database*


A good suggestion but it did not take me off 9c. It did however widen my scope outside of the data directory for my reset script so thanks for that .

Is your wallet launched with this command?

Code: [Select]

./cli_wallet -w wallet-testnet-puppies.json --chain-id 081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6


[Riverhead]

Is this command useful? @Riverhead

Code: [Select]

rm -rf object_database*


A good suggestion but it did not take me off 9c. It did however widen my scope outside of the data directory for my reset script so thanks for that .

[abit]

Is this command useful? @Riverhead

Code: [Select]

rm -rf object_database*


[iHashFury]

Just fired up my cubox and it on puppies chain straight away

Chain ID is 081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6

[iHashFury]

Glad I'm not alone

Will try again with a home computer this time.

[Riverhead]

Code: [Select]

Chain ID is a629fd737e0b4d8becc25e33b90984840723b38cd4430049693059f6e396b89ccli_wallet will not load as its a different chain

Right there with you. I've deleted/changed the data directory, recompiled the latest pull, updated the config.ini file, and tried different seed IP's. I cannot get it to join any other chain than 9c. This was not an issue yesterday so there must be some bit left that I haven't reset.

[abit]

I'm there and producing.
Try deleting your witness data directory (i called mine something like testnet_puppies), and restart, that might help.

You are correct, there are not many people at the moment,  consider this as the trial and error setting yourself up before the big testnet.

Got it resynced an am producing blocks again. One of my remaining questions is:
Does a NAT-Situation hinder smooth operation? I can set P2P-Bind in config, is there such thing as a public address? (It's clear that running a node "at home" is not for production use but this was my first try - will prepare a VPS for next version) As I see nodes being connected on my p2p-incoming port I assume it somehow works anyway but I would like to get a better understanding...

Is there a wallet-command for listing Nodes in detail? I did netstat to get an overall status...

Another way to specify incoming port is adding parameter --rpc-endpoint 0.0.0.0:your_port.
Doesn't like bitshares_client, the witness node doesn't enable UPNP by default. I'm currently running at home as well, I have to manually configure NAT port forwarding in my router and it works, I can see incoming connection in p2p.log.

[iHashFury]

Having trouble get on the puppies chain

Code: [Select]

witness_node --rpc-endpoint "127.0.0.1:8090" --p2p-endpoint "127.0.0.1:61705" --genesis-json aug-14-test-genesis.json -d test_net_puppies -s 45.55.6.216:1776
I only get this chain after several retries

Code: [Select]

rm test_net_puppies/ -fr

Code: [Select]

Chain ID is a629fd737e0b4d8becc25e33b90984840723b38cd4430049693059f6e396b89c
cli_wallet will not load as its a different chain

[mudshark79]

Everyone who has participated in one of these test network and successfully registered a witness, please post your witness ID and BTS account to this thread and I'll send you 1000 brownie pts.   

This testing has been very helpful.   I am actively working on a potential fix for the issues found.

get_witness mudshark79
{
  "id": "1.6.5157",
  "witness_account": "1.2.52558",

[twitter]

OK. I am rebuilding it from source and give itvanother try

[mudshark79]

I'm there and producing.
Try deleting your witness data directory (i called mine something like testnet_puppies), and restart, that might help.

You are correct, there are not many people at the moment,  consider this as the trial and error setting yourself up before the big testnet.

Got it resynced an am producing blocks again. One of my remaining questions is:
Does a NAT-Situation hinder smooth operation? I can set P2P-Bind in config, is there such thing as a public address? (It's clear that running a node "at home" is not for production use but this was my first try - will prepare a VPS for next version) As I see nodes being connected on my p2p-incoming port I assume it somehow works anyway but I would like to get a better understanding...

Is there a wallet-command for listing Nodes in detail? I did netstat to get an overall status...

[Riverhead]

My witness_node seems to be enamored with chain-id: a629fd737e0b4d8becc25e33b90984840723b38cd4430049693059f6e396b89c

Code: [Select]

2295235ms th_a       main.cpp:117                  main                 ] Writing new config file at /home/james/data/github/graphene/programs/witness_node/.graphene/config.ini
2295236ms th_a       witness.cpp:70                plugin_initialize    ] key_id_to_wif_pair: ["GPH6MRyAjQqweee","5KwrPbwdL6PhXuwoho"]
2295237ms th_a       application.cpp:228           operator()           ] Initializing database...
2321896ms th_a       thread.cpp:95                 thread               ] name:ntp tid:139671886788352
2321900ms ntp        ntp.cpp:77                    request_now          ] resolving... ["pool.ntp.org",123]
2321902ms th_a       thread.cpp:95                 thread               ] name:p2p tid:139671857415936
2321909ms th_a       application.cpp:129           reset_p2p_node       ] Configured p2p node to listen on 0.0.0.0:33569
2321910ms th_a       witness.cpp:143               plugin_startup       ] No witnesses configured! Please add witness IDs and private keys to configuration.
2321910ms th_a       main.cpp:165                  main                 ] Started witness node on a chain with 0 blocks.
2321910ms th_a       main.cpp:166                  main                 ] Chain ID is a629fd737e0b4d8becc25e33b90984840723b38cd4430049693059f6e396b89c
2321926ms ntp        ntp.cpp:81                    request_now          ] sending request to 96.44.142.5:123
2321971ms ntp        ntp.cpp:147                   read_loop            ] received ntp reply from 96.44.142.5:123
2321971ms ntp        ntp.cpp:161                   read_loop            ] ntp offset: -7788, round_trip_delay 45567