Test Net for Advanced Users

[clayop]

Aug 17 testnet is coming

[puppies]

With the witness ran as I indicated in my last post I still can't get the cli to run using the info in the OP:

Code: [Select]

./cli_wallet -w wallet_name  --chain-id 081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6
Logging RPC to file: logs/rpc/rpc.log
1677766ms th_a       main.cpp:111                  main                 ] key_to_wif( committee_private_key ): 5KCBDTcyDqzsqehcb52tW5nU6pXife6V2rX9Yf7c3saYSzbDZ5W
1677766ms th_a       main.cpp:115                  main                 ] nathan_pub_key: GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV
1677766ms th_a       main.cpp:116                  main                 ] key_to_wif( nathan_private_key ): 5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3
Starting a new wallet with chain ID 081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6 (from CLI)
1677766ms th_a       main.cpp:163                  main                 ] wdata.ws_server: ws://localhost:8090
1677769ms th_a       main.cpp:168                  main                 ] wdata.ws_user:  wdata.ws_password: 
0 exception: unspecified
Remote server gave us an unexpected chain_id
    {"remote_chain_id":"a629fd737e0b4d8becc25e33b90984840723b38cd4430049693059f6e396b89c","chain_id":"081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6"}
    th_a  wallet.cpp:375 wallet_api_impl

Does the chain-id in the OP still correct against your seed?

Yeah.  I've still got.
[Codeunlocked >>> info
info
{
  "head_block_num": 58249,
  "head_block_id": "0000e389b37fdc0d2a5879c7b32f5154893bdf0b",
  "head_block_age": "1 second old",
  "next_maintenance_time": "4 minutes in the future",
  "chain_id": "081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6",
  "active_witnesses": [
    "1.6.0",
    "1.6.1",
    "1.6.2",
    "1.6.3",
    "1.6.4",
    "1.6.5",
    "1.6.6",
    "1.6.1435",
    "1.6.1439",
    "1.6.5155"
  ],
  "active_committee_members": [
    "1.5.0",
    "1.5.1",
    "1.5.2",
    "1.5.3",
    "1.5.4",
    "1.5.5",
    "1.5.6",
    "1.5.7",
    "1.5.8",
    "1.5.9"
  ],
  "entropy": "0673bf1ccd60a996958985b9e956657c6c9edc3e"
}
unlocked >>>[/code]]

[Thom]

With the witness ran as I indicated in my last post I still can't get the cli to run using the info in the OP:

Code: [Select]

./cli_wallet -w wallet_name  --chain-id 081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6
Logging RPC to file: logs/rpc/rpc.log
1677766ms th_a       main.cpp:111                  main                 ] key_to_wif( committee_private_key ): 5KCBDTcyDqzsqehcb52tW5nU6pXife6V2rX9Yf7c3saYSzbDZ5W
1677766ms th_a       main.cpp:115                  main                 ] nathan_pub_key: GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV
1677766ms th_a       main.cpp:116                  main                 ] key_to_wif( nathan_private_key ): 5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3
Starting a new wallet with chain ID 081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6 (from CLI)
1677766ms th_a       main.cpp:163                  main                 ] wdata.ws_server: ws://localhost:8090
1677769ms th_a       main.cpp:168                  main                 ] wdata.ws_user:  wdata.ws_password: 
0 exception: unspecified
Remote server gave us an unexpected chain_id
    {"remote_chain_id":"a629fd737e0b4d8becc25e33b90984840723b38cd4430049693059f6e396b89c","chain_id":"081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6"}
    th_a  wallet.cpp:375 wallet_api_impl

Does the chain-id in the OP still correct against your seed?

[Thom]

Using this to launch the witness node, wiped the _data_dir (there doesn't seem to be a wallet yet, probably b/c it is crashing):

Code: [Select]

./witness_node --rpc-endpoint "127.0.0.1:8090"  --genesis-json ../Downloads/aug-14-test-genesis.json -d test_net -s 45.55.6.216:1776 --enable-stale-production -w \""1.6.0"\" \""1.6.1"\" \""1.6.2"\" \""1.6.3"\" \""1.6.4"\"

Is that correct? I'm have a little difficulty following the permutations between the instructions in the OP of this thread and xeroc's instructions for importing balances from 0.9.2. The OP doesn't appear to address importing from 0.9.2, which xeroc's instructions do. I'm just a bit confused by the mixture of accounts in this predefined genesis block and using balances imported from 0.9.2.

Not even sure if I should be trying to import a balance from 0.9.2. Is that what most of you testing now are doing or just using the balance from nathan's account mentioned in the OP?

[puppies]

Thanks puppies.

I'll go back to the OP here, thought was was really old & outdated by now, but I guess not.

I'll use the 45.55.6.216:1776 seed node you mentioned.

I started the witness on the unedited config.ini file with the seed from xeroc's write up. It runs, but the cli crashes:

Code: [Select]

deletech@Jessie:~/bts2.0$ ./cli_wallet -s ws://127.0.0.1:8090
Logging RPC to file: logs/rpc/rpc.log
3273995ms th_a       main.cpp:111                  main                 ] key_to_wif( committee_private_key ): 5KCBDTcyDqzsqehcb52tW5nU6pXife6V2rX9Yf7c3saYSzbDZ5W
3273995ms th_a       main.cpp:115                  main                 ] nathan_pub_key: GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV
3273995ms th_a       main.cpp:116                  main                 ] key_to_wif( nathan_private_key ): 5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3
Starting a new wallet with chain ID 3fda83797955b6d7c3916a08bab36f9a86169c23298a5f519e48dff1d4e6475a (from egenesis)
3273995ms th_a       main.cpp:163                  main                 ] wdata.ws_server: ws://127.0.0.1:8090
3273997ms th_a       main.cpp:168                  main                 ] wdata.ws_user:  wdata.ws_password: 
0 exception: unspecified
Remote server gave us an unexpected chain_id
    {"remote_chain_id":"a629fd737e0b4d8becc25e33b90984840723b38cd4430049693059f6e396b89c","chain_id":"3fda83797955b6d7c3916a08bab36f9a86169c23298a5f519e48dff1d4e6475a"}
    th_a  wallet.cpp:375 wallet_api_impl

That's probably expected. I review the OP and see if I can get up to speed...

Yeah you're on the wrong chain.  You will need to launch with --genesis-json and --resync-blockchain.

Alternately you can add the genesis to your config.ini and delete the chain folder, or change the data directory with -d

[Thom]

Thanks puppies.

I'll go back to the OP here, thought was was really old & outdated by now, but I guess not.

I'll use the 45.55.6.216:1776 seed node you mentioned.

I started the witness on the unedited config.ini file with the seed from xeroc's write up. It runs, but the cli crashes:

Code: [Select]

deletech@Jessie:~/bts2.0$ ./cli_wallet -s ws://127.0.0.1:8090
Logging RPC to file: logs/rpc/rpc.log
3273995ms th_a       main.cpp:111                  main                 ] key_to_wif( committee_private_key ): 5KCBDTcyDqzsqehcb52tW5nU6pXife6V2rX9Yf7c3saYSzbDZ5W
3273995ms th_a       main.cpp:115                  main                 ] nathan_pub_key: GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV
3273995ms th_a       main.cpp:116                  main                 ] key_to_wif( nathan_private_key ): 5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3
Starting a new wallet with chain ID 3fda83797955b6d7c3916a08bab36f9a86169c23298a5f519e48dff1d4e6475a (from egenesis)
3273995ms th_a       main.cpp:163                  main                 ] wdata.ws_server: ws://127.0.0.1:8090
3273997ms th_a       main.cpp:168                  main                 ] wdata.ws_user:  wdata.ws_password: 
0 exception: unspecified
Remote server gave us an unexpected chain_id
    {"remote_chain_id":"a629fd737e0b4d8becc25e33b90984840723b38cd4430049693059f6e396b89c","chain_id":"3fda83797955b6d7c3916a08bab36f9a86169c23298a5f519e48dff1d4e6475a"}
    th_a  wallet.cpp:375 wallet_api_impl

That's probably expected. I review the OP and see if I can get up to speed...

[puppies]

I was producing blocks, but every so often I had the ntp error.

I have seen that NTP error from time to time myself.  We will look into it.

Vikram and I have reviewed the testnet and have identified a patch that would allow us to revive the existing test net by specifying a checkpoint.  Once we are sure we can revive the testnet we will start a new network with at least 100 witness slots so that it is less likely for a few bad apples to result in this issue.

It could be that you produced blocks on a fork.  If any of you have evidence that you were on a fork (have a block that wasn't included in the main chain) then that is something I am very interested in.

If we all added a checkpoint = to our config.ini or will it require a different build?

[puppies]

So what is the state of things at this point? I'm 90% finished rebuilding fresh from src (I presume there have been many changes since 8/9) on 2 systems.

Are you guys using the procedure in the readme for "Running private testnet", or xeroc's process for importing balances from 0.9.2?

Xeroc's with the bytemaster's start up parameters, see my post.

I've been monitoring this thread all day, but I'm not sure which of your posts you're referring to, or what you mean "bytemaster's parameters" .

When I tried this on the 9th I was unable to import a balance or register a witness. I am starting to try that now. According to xeroc's instructions under git/graphene/docs, he says to start the witness with a downloaded genesis block:

Code: [Select]

programs/witness_node/witness_node -s 104.200.28.117:61705 --rpc-endpoint 127.0.0.1:8090 --genesis-json aug-14-test-genesis.json
Is this still the correct IP:port for the seed node and genesis block to use?

Download the genesis Json in the op, and follow the commands to launch witness node and cli wallet.  To import your delegate I would suggest following the link about becoming a delegate.  His python script is especially useful.

The test net died, but I started another one, so if you want to test until another official one comes up replace the url in bytemasters command with 45.55.6.216:1776

[Thom]

So what is the state of things at this point? I'm 90% finished rebuilding fresh from src (I presume there have been many changes since 8/9) on 2 systems.

Are you guys using the procedure in the readme for "Running private testnet", or xeroc's process for importing balances from 0.9.2?

Xeroc's with the bytemaster's start up parameters, see my post.

I've been monitoring this thread all day, but I'm not sure which of your posts you're referring to, or what you mean "bytemaster's parameters" .

When I tried this on the 9th I was unable to import a balance or register a witness. I am starting to try that now. According to xeroc's instructions under git/graphene/docs, he says to start the witness with a downloaded genesis block:

Code: [Select]

programs/witness_node/witness_node -s 104.200.28.117:61705 --rpc-endpoint 127.0.0.1:8090 --genesis-json aug-14-test-genesis.json
Is this still the correct IP:port for the seed node and genesis block to use?

[betax]

I was producing blocks, but every so often I had the ntp error.

I have seen that NTP error from time to time myself.  We will look into it.

Vikram and I have reviewed the testnet and have identified a patch that would allow us to revive the existing test net by specifying a checkpoint.  Once we are sure we can revive the testnet we will start a new network with at least 100 witness slots so that it is less likely for a few bad apples to result in this issue.

It could be that you produced blocks on a fork.  If any of you have evidence that you were on a fork (have a block that wasn't included in the main chain) then that is something I am very interested in.

From the comments with logs, the blocks I could see were ~ matching my current blocks so I don't think we forked.

[betax]

So what is the state of things at this point? I'm 90% finished rebuilding fresh from src (I presume there have been many changes since 8/9) on 2 systems.

Are you guys using the procedure in the readme for "Running private testnet", or xeroc's process for importing balances from 0.9.2?

Xeroc's with the bytemaster's start up parameters, see my post.

[betax]

Edit.. amazon option has more ram

FWIW -Looking at my Azure VPS for Graphine, I have the G5 machine size option: 32 cores, 448GB RAM [1]
No, I'm not currently running this size during testing.

[1] http://azure.microsoft.com/en-us/pricing/details/virtual-machines/#Linux
Not all locations have the G series instances available.

  G for Guthrie ?

[Thom]

So what is the state of things at this point? I'm 90% finished rebuilding fresh from src (I presume there have been many changes since 8/9) on 2 systems.

Are you guys using the procedure in the readme for "Running private testnet", or xeroc's process for importing balances from 0.9.2?

[Fox]

Edit.. amazon option has more ram

FWIW -Looking at my Azure VPS for Graphine, I have the G5 machine size option: 32 cores, 448GB RAM [1]
No, I'm not currently running this size during testing.

[1] http://azure.microsoft.com/en-us/pricing/details/virtual-machines/#Linux
Not all locations have the G series instances available.

[bytemaster]

I was producing blocks, but every so often I had the ntp error.

I have seen that NTP error from time to time myself.  We will look into it.

Vikram and I have reviewed the testnet and have identified a patch that would allow us to revive the existing test net by specifying a checkpoint.  Once we are sure we can revive the testnet we will start a new network with at least 100 witness slots so that it is less likely for a few bad apples to result in this issue.

It could be that you produced blocks on a fork.  If any of you have evidence that you were on a fork (have a block that wasn't included in the main chain) then that is something I am very interested in.