Test Net for Advanced Users

[betax]

Thanks..
I have send some CORE around for testing.

I am trying to create an asset (as per our first testnets which was more fun), any idea on how to create the common options parameters in the cli?
From unit tests https://github.com/cryptonomex/graphene/blob/0295f103876afe199a5639c1a12b494f2cb59c98/tests/tests/uia_tests.cpp

Code: [Select]

   asset_id_type test_asset_id = db.get_index<asset_object>().get_next_id();
40       asset_create_operation creator;
41       creator.issuer = account_id_type();
42       creator.fee = asset();
43       creator.symbol = "ADVANCED";
44       creator.common_options.max_supply = 100000000;
45       creator.precision = 2;
46       creator.common_options.market_fee_percent = GRAPHENE_MAX_MARKET_FEE_PERCENT/100; /*1%*/
47       creator.common_options.issuer_permissions = ASSET_ISSUER_PERMISSION_MASK & ~(disable_force_settle|global_settle);
48       creator.common_options.flags = ASSET_ISSUER_PERMISSION_MASK & ~(disable_force_settle|global_settle|transfer_restricted);
49       creator.common_options.core_exchange_rate = price({asset(2),asset(1,1)});
50       creator.common_options.whitelist_authorities = creator.common_options.blacklist_authorities = {account_id_type()};


[abit]

Do you have the p2p logs for this?

See comment in github: https://github.com/cryptonomex/graphene/issues/247#issuecomment-132349244.

[puppies]

great compilation of what we learned betax

[maqifrnswa]

betax awesome write up! Thank you

First RPi tests: the old 256 MB pi runs out of memory and ends up using lots of swap (no surprise there...) I have a new quad core rpi2 with 1 GB ram to try next, I just need a microsd card.

[betax]

I don't know if this is an issue, but my balances were not imported / showing until I listed accounts.

[betax]

Another attempt for end to end instructions if anybody is interested.

1. Follow instructions for ubuntu build here https://github.com/cryptonomex/graphene/wiki/build-ubuntu
2. Go to the witness directory:

Code: [Select]

cd ~/graphene/programs/witness_node
3. Download genesis

Code: [Select]

wget https://www.dropbox.com/s/zxp2qg0rc9sk1kc/aug-14-test-genesis.json
4.Start a new terminal screen

Code: [Select]

screen5. Run the witness

Code: [Select]

./witness_node --rpc-endpoint "127.0.0.1:8090"  --genesis-json aug-14-test-genesis.json -d test_net_puppies -s 45.55.6.216:1776
Note:
-d parameter is for the directory you want the witness data to be stored
-s is the node you want to connect
6. Detach from screen

Code: [Select]

Ctrl A Ctrl D7. Extract your wif keys for user and balances as per xeroc's instructions https://github.com/cryptonomex/graphene/wiki/Howto-become-an-active-witness-in-BitShares-2.0
8. Navigate to cli_wallet

Code: [Select]

cd ~/graphene/programs/cli_wallet9. Run cli

Code: [Select]

./cli_wallet -w test_wallet_puppies  --chain-id 081401ede64c8fe30b23c91d7ab8750103acb1a39548a866fb562f2edf4627d6Note:
-w is your directory wallet
10. Setup witness as per xerocs instructions https://github.com/cryptonomex/graphene/wiki/Howto-become-an-active-witness-in-BitShares-2.0
(If you don't see any balances after import remember to list accounts) and copy your keys, witness id
11. Exit
12. Go back to your witness terminal

Code: [Select]

screen -r 13. Exit your witness ctrl c
14. Restart with parameters to start block producing (block producing needs your witness id and private keys)

Code: [Select]

./witness_node --rpc-endpoint "127.0.0.1:8090"  --genesis-json aug-14-test-genesis.json -d test_net_puppies -s 45.55.6.216:1776  --witness-id '"1.6.5156"' --private-key '["GPH6JhL..your.signing.key..bc5mWyCvERV3coy","5K..your.secret..a"]'15. See your witness producing blocks and
you can Ctrl A Ctrl D to detach from screen.

[abit]

Well done puppies. I think we are not that bad bad test witnesses 

  You guys have done a great job.   If we could find a way to reliably reproduce this with just a few nodes that would be very helpful.

Try run a node in a unstable network? With limited bandwidth, or heavy networking load, high latency etc.

[abit]

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.

witness ID in OP's chain: "1.6.5156"
witness ID in puppies' chain: "1.6.5155"
bts account: abit
Thanks!

[clayop]

Sweet.

Witness ID: "1.6.1446"
BTS ID: clayop

[betax]

"1.6.5155" betaxtrade thanks

[puppies]

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.

1.6.1435 puppies

[bytemaster]

Well done puppies. I think we are not that bad bad test witnesses 

  You guys have done a great job.   If we could find a way to reliably reproduce this with just a few nodes that would be very helpful.

[bytemaster]

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.

[clayop]

Well done puppies. I think we are not that bad bad test witnesses 

[bytemaster]

slightly off topic, but is there a good resource on proper protocol to post these issues directly to github?  I could post directly to github, but I'm such a github noob that I'm not sure I wouldn't be making things worse than just posting here.

No real protocol.  I suppose you should confirm that it is an actual issue before posting to github.