Author Topic: Test Net for MS Windows-based users  (Read 3675 times)

0 Members and 1 Guest are viewing this topic.

Offline cube

  • Hero Member
  • *****
  • Posts: 1404
  • Bit by bit, we will get there!
    • View Profile
  • BitShares: bitcube
Thank you all!

The dev team has updated graphene test with a relay.  Here are the updated binaries.

http://graphene.cubeconnex.com/download/gra-relay-test.zip

Follow this thread with the new instruction

https://bitsharestalk.org/index.php/topic,18349.0.html

Edit: You will need to open up a new command Window (ie third Window) to run the new nodejs javascript.
« Last Edit: September 09, 2015, 10:50:08 am by cube »
ID: bitcube
bitcube is a dedicated witness and committe member. Please vote for bitcube.

Offline betax

  • Hero Member
  • *****
  • Posts: 808
    • View Profile
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline sudo

  • Hero Member
  • *****
  • Posts: 2255
    • View Profile
  • BitShares: ags
blockchain is small
logs  is very big

Offline puppies

  • Hero Member
  • *****
  • Posts: 1659
    • View Profile
  • BitShares: puppies
then   how to setup GUI wallet on windows? command is not user friendly enough

I have not looked into it yet.  Is it ready for end-user testing?

I think theyre in the process of rewriting lots of it.  Bytemaster stated that they are trying to not test things they already know are going to change.  You can play with it pretty easily, but I am not sure that the testing would bring any utility.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline cube

  • Hero Member
  • *****
  • Posts: 1404
  • Bit by bit, we will get there!
    • View Profile
  • BitShares: bitcube
then   how to setup GUI wallet on windows? command is not user friendly enough

I have not looked into it yet.  Is it ready for end-user testing?
ID: bitcube
bitcube is a dedicated witness and committe member. Please vote for bitcube.

Offline sudo

  • Hero Member
  • *****
  • Posts: 2255
    • View Profile
  • BitShares: ags
then   how to setup GUI wallet on windows? command is not user friendly enough

Offline cube

  • Hero Member
  • *****
  • Posts: 1404
  • Bit by bit, we will get there!
    • View Profile
  • BitShares: bitcube
Glad it works for you. :)   I hope more windows-based users can participate and test out the new graphene. 
« Last Edit: September 06, 2015, 03:15:12 am by cube »
ID: bitcube
bitcube is a dedicated witness and committe member. Please vote for bitcube.

Offline sudo

  • Hero Member
  • *****
  • Posts: 2255
    • View Profile
  • BitShares: ags
cool  it works


witness_nod.exe
cli_wallet.exe
test.json

witness_node.exe --rpc-endpoint "127.0.0.1:8090" --genesis-json test.json -d testnet -s "104.236.51.238:1776" -s "176.221.43.130:33323" -s "45.55.6.216:1776" -s "114.92.254.159:62015"

cli_wallet.exe -w testwallet  --chain-id ecbde738ba0b319cb4d266e613b200d010da8b37313c20aec03f9c8e2d9b35e3

new >>> set_password my_password
locked >>> unlock my_password

info

Offline sudo

  • Hero Member
  • *****
  • Posts: 2255
    • View Profile
  • BitShares: ags
https://github.com/cryptonomex/graphene/releases/download/test2b/aug-31-testnet-genesis.json


witness_node.exe --rpc-endpoint "127.0.0.1:8090"  --genesis-json aug-31-test-genesis.json aug-31-testnet-genesis.json -d testnet -s "104.236.51.238:1776" -s "176.221.43.130:33323" -s "45.55.6.216:1776" -s "114.92.254.159:62015" 


I run cli only  at first



github
Vital information
Chain ID: ecbde738ba0b319cb4d266e613b200d010da8b37313c20aec03f9c8e2d9b35e3
Seed node: 104.236.118.105:1776
« Last Edit: September 06, 2015, 02:37:38 am by sudo »

Offline cube

  • Hero Member
  • *****
  • Posts: 1404
  • Bit by bit, we will get there!
    • View Profile
  • BitShares: bitcube
I tried it and it worked.

Code: [Select]
D:\graphene>cli_wallet -w testwallet  --chain-id ecbde738ba0b319cb4d266e613b200d010da8b37313c20aec03f9c8e2d9b35e3  -H 127.0.0.1:8092
Logging RPC to file: logs\rpc\rpc.log
385911ms th_a       main.cpp:111                  main                 ] key_to_wif( committee_private_key ): 5KCBDTcyDqzsqehcb52tW5nU6pXife6V2rX9Yf7c3saYSzbDZ5W
385912ms th_a       main.cpp:115                  main                 ] nathan_pub_key: GPH6MRyAjQq8ud7hVNYcfnVPJxxxxxxxxGDW5CV
385926ms th_a       main.cpp:116                  main                 ] key_to_wif( nathan_private_key ): 5KQwrPbwxxxxxxxxxxxxxxxxxxxxvFD3
Starting a new wallet with chain ID ecbde738ba0b319cb4d266e613b200d010da8b37313c20aec03f9c8e2d9b35e3 (from CLI)
386040ms th_a       main.cpp:163                  main                 ] wdata.ws_server: ws://localhost:8090
387055ms th_a       main.cpp:168                  main                 ] wdata.ws_user:  wdata.ws_password:
Please use the set_password method to initialize a new wallet before continuing
387082ms th_a       main.cpp:233                  main                 ] Listening for incoming HTTP RPC requests on 127.0.0.1:8092
387112ms th_a       thread.cpp:95                 thread               ] name:cin tid:456

Edit:

Did you run witness_node.exe in another Command-prompt Window?   witness_node.exe needs to be run all the time or your cli_wallet will not work.
« Last Edit: September 06, 2015, 02:25:12 am by cube »
ID: bitcube
bitcube is a dedicated witness and committe member. Please vote for bitcube.

Offline sudo

  • Hero Member
  • *****
  • Posts: 2255
    • View Profile
  • BitShares: ags
>cli_wallet -w test_wallet  --chain-id ecbde738ba0b319cb4d266e613b200d010da8b37313c20aec03f9c8e2d9b35e3 -H 127.0.0.1:8092
Logging RPC to file: logs\rpc\rpc.log
2364643ms th_a       main.cpp:111                  main                 ] key_to_wif( committee_private_key ): 5KCBDTcyDqzsqehcb52tW5nU6pXife6V2rX9Yf7c3saYSzbDZ5W
2364647ms th_a       main.cpp:115                  main                 ] nathan_pub_key: GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV
2364648ms th_a       main.cpp:116                  main                 ] key_to_wif( nathan_private_key ): 5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3
Starting a new wallet with chain ID ecbde738ba0b319cb4d266e613b200d010da8b37313c20aec03f9c8e2d9b35e3 (from CLI)
2364657ms th_a       main.cpp:163                  main                 ] wdata.ws_server: ws://localhost:8090
0 exception: unspecified
Underlying Transport Error
    {"message":"Underlying Transport Error"}
    asio  websocket.cpp:431 fc::http::detail::websocket_client_impl::{ctor}::<lambda_65314a0dba1a739cff07d8c8ddd38767>::operator ()

    {"uri":"ws://localhost:8090"}
    th_a  websocket.cpp:616 fc::http::websocket_client::connect

 

Offline puppies

  • Hero Member
  • *****
  • Posts: 1659
    • View Profile
  • BitShares: puppies
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline sudo

  • Hero Member
  • *****
  • Posts: 2255
    • View Profile
  • BitShares: ags
 +5% +5% +5% great job

x64 version  only
« Last Edit: September 06, 2015, 01:32:25 am by sudo »

Offline cube

  • Hero Member
  • *****
  • Posts: 1404
  • Bit by bit, we will get there!
    • View Profile
  • BitShares: bitcube
Some users are asking for a Windows version of the graphene test net. I have uploaded a copy here

http://graphene.cubeconnex.com/download/gra-test2b.zip

You would need to install the Microsoft redistributable from below before running the witness_node and cli_wallet.

http://www.microsoft.com/en-us/download/details.aspx?id=40784

Have fun! :)

============
Edit: Added brief instruction

The following will only work on MS Windows 64bit computers (tested on Windows 8).

There are two command-line programs that need to be

Installation of Microsft Re-distributables

Download and install vcredist_x64.exe from http://www.microsoft.com/en-us/download/details.aspx?id=40784


Download Graphene test programs and testnet genesis file

Download http://graphene.cubeconnex.com/download/gra-test2b.zip

Create a folder called 'c:\graphene'

Extract out the two command-line programs, cli-wallet.exe and witness_node.exe into this folder

Download genesis file with a web browser
Code: [Select]
https://github.com/cryptonomex/graphene/releases/download/test2b/aug-31-testnet-genesis.json


Open a Command-Prompt Window for witness_node.exe. Run it as an observer first.

CD to c:\graphene and run the witness node program - witness_node.exe

Code: [Select]
witness_node.exe --rpc-endpoint "127.0.0.1:8090"  --genesis-json aug-31-testnet-genesis.json -d testnet -s "104.236.51.238:1776" -s "176.221.43.130:33323" -s "45.55.6.216:1776" -s "114.92.254.159:62015" 

Note:
-d parameter is for the directory you want the witness data to be stored
-s is the node you want to connect

Retrieve 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

Go to your old bitshares wallet 0.9.x to retrieve your old bts keys. Skip this step if you intend to create a new account in graphene.

Get your owner private key. Copy down.
Code: [Select]
wallet_dump_account_private_key bitcube "owner_key"
Get your balance public keys for your owner key. There is a number of it.  Copy down.
Code: [Select]

>wallet_account_balance_ids  bitcube
    "bitcube",[
      "BTS---------------------------------A",
      "BTS---------------------------------B",
      "BTS---------------------------------C", 
...

>blockchain_get_balance BTS---------------------------------A

{
  "condition": {
    "asset_id": 39,
    "slate_id": 0,
    "type": "withdraw_signature_type",
    "data": {
      "owner": "BTS---------------------------------balanceA",


Get private key for each of the balance keys. Copy down.
Code: [Select]
wallet_dump_private_key BTS---------------------------------balanceA

With the owner private key and its balance private keys, you are ready to import them into the new graphene wallet.

Open a new Command-Prompt Window for cli_wallet.exe

CD to c:\graphene and run the wallet program - cli_wallet.exe

Code: [Select]
cli_wallet.exe -w testwallet  --chain-id d011922587473757011118587f93afcc314fbaea094fc1055574721b27975083
Note:
-w is your directory wallet

Setup witness as per xerocs instructions https://github.com/cryptonomex/graphene/wiki/Howto-become-an-active-witness-in-BitShares-2.0
Remember to copy your keys, witness id.

Set password to your wallet.
Code: [Select]
new >>> set_password <password>
null
locked >>> unlock <password>
null
unlocked >>>

Import old bts keys into your wallet.  You will be importing your owner key and its balance keys.

[Note: You can still participate in the test without this step by creating a new account. ]

Code: [Select]
>import_key bitcube 5Jxxxaaewaewaewae  true

113816ms th_a       wallet.cpp:666                save_wallet_file     ] saving wallet to file testwallet
113817ms th_a       wallet.cpp:425                copy_wallet_file     ] backing up wallet testwallet to after-import-key-7671dc37.wallet

>import_balance bitcube [5JpkL5gxxxaweaweaweaweawef] true
1300892ms th_a       wallet.cpp:2805               import_balance       ] balances:

Remember to wait for the blockchain to sync before importing your keys into this new wallet.  Type the command 'info' in your wallet to find out if you are synced.
Code: [Select]
>info
{
  "head_block_num": 79157,
  "head_block_id": "00013535c26d36de4378fd2427750b80bd334b17",
  "head_block_age": "3 seconds old",

Code: [Select]
list_my_accounts
[{
    "id": "1.2.8112",
    "annotations": [],
    "membership_expiration_date": "1969-12-31T23:59:59",
    "registrar": "1.2.8112",
    "referrer": "1.2.8112",
    "lifetime_referrer": "1.2.8112",
    "network_fee_percentage": 2000,
    "lifetime_referrer_fee_percentage": 8000,
    "referrer_rewards_percentage": 0,
    "name": "bitcube",
    "owner": {
      "weight_threshold": 1,
      "account_auths": [],
      "key_auths": [[


Find out your witness id (in this example, '1.6.624') and its public-private key pair.
Code: [Select]
>>> get_witness bitcube
get_witness bitcube
{
  "id": "1.6.624",
  "witness_account": "1.2.8112",
  "last_aslot": 0,
  "signing_key": "GPH-------------------------------------------------sn",
  "vote_id": "1:623",
  "total_votes": "64885994140",
  "url": ""
}

>>> dump_private_keys
dump_private_keys
[[
    "GPH-------------------------------------------------sn",
    "5JN-------------------------------------------------------------------------pp"
  ],[
    "GPH------------------------------------------------------------------AA",
    "5J------------------------------------------------------------"
  ]
]

GPH-------------------------------------------------sn is the public key and 5JN-------------------------------------------------------------------------pp is the private key to the witness.

Tell the world your witness id so that they can vote you in.

[Note: you need to wait for a maintenance period to be voted in.]

Go back to your witness node Command-Prompt Window. Re-run it as a witness now.
 
Exit your witness by ctrl c


Re-run witness_node.exe with additional parameters so that you can start block production (Note: your witness id and public-private key pair will be used here)

Code: [Select]
witness_node.exe --rpc-endpoint "127.0.0.1:8090"  --genesis-json aug-31-test-genesis.json -d testnet -s "104.236.51.238:1776" -s "176.221.43.130:33323" -s "45.55.6.216:1776" -s "114.92.254.159:62015"   --witness-id '"1.6.624"' --private-key '["GPH-------------------------------------------------sn","5JN-------------------------------------------------------------------------pp"]'
Alternatively, you can add the same information (your witness id and public-private key pair) to the config.ini file. By doing this, you do not need to run witness_node.exe with the additional parameters.

Code: [Select]
cd c:\graphene\testnet
notepad config.ini

Add these two lines, save and exit

witness-id = "1.6.624"
private-key= ["GPH-------------------------------------------------sn","5JN-------------------------------------------------------------------------pp"]

cd c:\graphene
witness_node.exe --rpc-endpoint "127.0.0.1:8090"  --genesis-json aug-31-test-genesis.json -d testnet -s "104.236.51.238:1776" -s "176.221.43.130:33323" -s "45.55.6.216:1776" -s "114.92.254.159:62015"


As your witness_node.exe runs, it will produce messages showing the status.
« Last Edit: September 06, 2015, 03:10:00 am by cube »
ID: bitcube
bitcube is a dedicated witness and committe member. Please vote for bitcube.