Test Net for Advanced Users

[bytemaster]

No reason to hold back on aug-17 network.  Those who know about it, please provide instructions for others to join it. 

Note that the aug 17 network does not currently have the fixes I introduced today for the out-of-order block pushing.  I will ask Vikram to update his node when he comes in this afternoon.

[puppies]

I have pushed an update that will hopefully resolve the out-of-order syncing issues. 

Those of you who have gotten good at these test networks can probably test it out for me and let me know if you still have problems.

Is there a seed node or should I just build from master and make one?

[puppies]

I am getting

Code: [Select]

user@user-desktop:~/src/graphene/programs/cli_wallet$ ./cli_wallet -w wallet -s 104.200.28.117:61705Logging RPC to file: logs/rpc/rpc.log
3362460ms th_a       main.cpp:111                  main                 ] key_to_wif( committee_private_key ): 5KCBDTcyDqzsqehcb52tW5nU6pXife6V2rX9Yf7c3saYSzbDZ5W
3362460ms th_a       main.cpp:115                  main                 ] nathan_pub_key: GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV
3362460ms th_a       main.cpp:116                  main                 ] key_to_wif( nathan_private_key ): 5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3
3362564ms th_a       main.cpp:163                  main                 ] wdata.ws_server: 104.200.28.117:61705
10 assert_exception: Assert Exception
uri.substr(0,3) == "ws:":
    {}
    th_a  websocket.cpp:585 connect

    {"uri":"104.200.28.117:61705"}
    th_a  websocket.cpp:606 connect
user@user-desktop:~/src/graphene/programs/cli_wallet$ ./cli_wallet -w wallet -s 104.200.28.117:8090
Logging RPC to file: logs/rpc/rpc.log
3372945ms th_a       main.cpp:111                  main                 ] key_to_wif( committee_private_key ): 5KCBDTcyDqzsqehcb52tW5nU6pXife6V2rX9Yf7c3saYSzbDZ5W
3372946ms th_a       main.cpp:115                  main                 ] nathan_pub_key: GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV
3372946ms th_a       main.cpp:116                  main                 ] key_to_wif( nathan_private_key ): 5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3
3373048ms th_a       main.cpp:163                  main                 ] wdata.ws_server: 104.200.28.117:8090
10 assert_exception: Assert Exception
uri.substr(0,3) == "ws:":
    {}
    th_a  websocket.cpp:585 connect

    {"uri":"104.200.28.117:8090"}
    th_a  websocket.cpp:606 connect
I will start working on getting an aug 17th seed node up, unless someone else wants to volunteer

[bytemaster]

I have pushed an update that will hopefully resolve the out-of-order syncing issues. 

Those of you who have gotten good at these test networks can probably test it out for me and let me know if you still have problems.   

[Riverhead]

It would make sense to test on the latest release of both clients and chain. I'm building aug-17 (18ed468c6f0b19bb1e322548d8be64d7faafe4e5) now which will put me back in 9c unless I get something different from the graphene.bitshares.org node.

[xeroc]

The seed node published in the op should have a websocket open at port 9080
If you connect your cli wallet to that ip directly it will tell you the chainid ..

Edit: afaik devs are working on that network already
I told them yesterday that nobody knows about that network yet .. no idea why they are holding it back .. maybe not on purpose

Anyway I will have to leave for now and will be back tomorrow ..

[betax]

Puppies can you keep it up for a while until xeroc is back.

[betax]

aug-17-testnet has 100 witnesses and will hopefull be more resistant to whatever caused the death of aug-14-testnet

So are we all going here now? or  still on the 14th.. mine has just crashed.

[puppies]

aug-17-testnet has 100 witnesses and will hopefull be more resistant to whatever caused the death of aug-14-testnet

So is 9c the correct chain then? I wasn't able to sync - but that could be a network issue on my VM.


Update: Aug-14 is syncing now. However, I should probably get Aug-17 working instead.

there's no server node for the August 17th test_net.  I can try to start one, if everyone is interested.

[xeroc]

Try connect to graphene.bitshares.org:8090 with the cli wallet .. i think there is a witness runnig which will tell you the chain id on connect .. not sure

Cant give you any more info as I am currently mobile

[Riverhead]

aug-17-testnet has 100 witnesses and will hopefull be more resistant to whatever caused the death of aug-14-testnet

So is 9c the correct chain then? I wasn't able to sync - but that could be a network issue on my VM.


Update: Aug-14 is syncing now. However, I should probably get Aug-17 working instead.

[puppies]

aug-17-testnet has 100 witnesses and will hopefull be more resistant to whatever caused the death of aug-14-testnet

I am down to switch whenever everyone else is.  Please don't keep this alive on my account.  I just wanted to continue testing till we got another official test net.

[xeroc]

aug-17-testnet has 100 witnesses and will hopefull be more resistant to whatever caused the death of aug-14-testnet

[Riverhead]

Code: [Select]

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

[codegit checkout origin/aug-17-testnet
building now

aug-17-testnet will give you chain id a629fd737e0b4d8becc25e33b90984840723b38cd4430049693059f6e396b89c (at least it did for me)
git checkout bf47a1610c4aef7e25592aa42ecd4d4ae83a2b5f
is what worked for me.

Thanks puppies. Building 2b5f now.

[puppies]

Code: [Select]

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

[codegit checkout origin/aug-17-testnet
building now

aug-17-testnet will give you chain id a629fd737e0b4d8becc25e33b90984840723b38cd4430049693059f6e396b89c (at least it did for me)
git checkout bf47a1610c4aef7e25592aa42ecd4d4ae83a2b5f
is what worked for me.