Author Topic: Test Net for Advanced Users  (Read 268171 times)

0 Members and 1 Guest are viewing this topic.

Offline puppies

  • Hero Member
  • *****
  • Posts: 1659
    • View Profile
  • BitShares: puppies
Thats funny because I had 100 going earlier.  I could tell because I set the genesis to 101, but set my server witness node to 100, and so 1.6.100 was missing blocks every single rotation.

There is a command in help():
Code: [Select]
graphene::chain::signed_transaction      set_desired_witness_and_committee_member_count(string, uint16_t, uint16_t, bool)
Don't know what it will do though.
I have played around with that command a little bit.  It throws an error if you set the desired number to more than what that account is currently voting for.

I would love some clarity on how the number of active witnesses is decided.  If you get_witness init92 you can see that its previous secret key is not all zeros.  It was producing blocks at some point.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
Thats funny because I had 100 going earlier.  I could tell because I set the genesis to 101, but set my server witness node to 100, and so 1.6.100 was missing blocks every single rotation.

There is a command in help():
Code: [Select]
graphene::chain::signed_transaction      set_desired_witness_and_committee_member_count(string, uint16_t, uint16_t, bool)
Don't know what it will do though.
BitShares committee member: abit
BitShares witness: in.abit

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
Here we are...



Awesome, how did you build?

Using the graphene-ui build instructions :) in github.
As I am using ubuntu in a vps I changed server.js to use 0.0.0.0, also to use prod.
My witnesses uses for rpc 0.0.0.0 instead localhost / 127.0.0.1
Do you have a URL so others could access the GUI/webwallet?
BitShares committee member: abit
BitShares witness: in.abit

Offline puppies

  • Hero Member
  • *****
  • Posts: 1659
    • View Profile
  • BitShares: puppies
My node is online now. Witness id 1.6.5247.
But number of active witnesses is still 10?
Code: [Select]
{
  "head_block_num": 11773,
  "head_block_id": "00002dfdab35043defebc42a6ae9d5a96767fd97",
  "head_block_age": "1 second old",
  "next_maintenance_time": "82 seconds in the future",
  "chain_id": "5508f5f743717fe2c78445364f62a72badd7532974d26f089af2062228b532eb",
  "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.1525",
    "1.6.4435",
    "1.6.5246",
    "1.6.5247"
  ],
  "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": "73f47170212775453a20de79b10d927e9d3b761d"
}
for some reason the info and get_global_properties screen dont show all witnesses.  There may have been something I should have changed in the genesis.  There are 101 delegate slots though.
By looking at the screen of witness_node, it's true that only the 11 witnesses are producing blocks.

//Edit: it's 11, not 10

Yeah.  You're right.

Thats funny because I had 100 going earlier.  I could tell because I set the genesis to 101, but set my server witness node to 100, and so 1.6.100 was missing blocks every single rotation.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline puppies

  • Hero Member
  • *****
  • Posts: 1659
    • View Profile
  • BitShares: puppies
Here we are...



Awesome, how did you build?

Using the graphene-ui build instructions :) in github.
As I am using ubuntu in a vps I changed server.js to use 0.0.0.0, also to use prod.
My witnesses uses for rpc 0.0.0.0 instead localhost / 127.0.0.1
I had no idea it was so easy.  I have been messing around with the light wallet instructions on the build ubuntu page with no real luck. 

CNX, you guys have really outdone yourselves with this wallet.  Its beautiful.  Key import is awesome.

One bug.  When I import my keys for puppies there are so many that the confirm button is not visible.  Even when I zoom all the way out that middle window goes way below the bottom of the page.  I was able to do it by pressing tab, and watching the JS description in the bottom left hand corner of my screen.

This is all in firefox on Xubuntu 14.04
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
My node is online now. Witness id 1.6.5247.
But number of active witnesses is still 10?
Code: [Select]
{
  "head_block_num": 11773,
  "head_block_id": "00002dfdab35043defebc42a6ae9d5a96767fd97",
  "head_block_age": "1 second old",
  "next_maintenance_time": "82 seconds in the future",
  "chain_id": "5508f5f743717fe2c78445364f62a72badd7532974d26f089af2062228b532eb",
  "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.1525",
    "1.6.4435",
    "1.6.5246",
    "1.6.5247"
  ],
  "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": "73f47170212775453a20de79b10d927e9d3b761d"
}
for some reason the info and get_global_properties screen dont show all witnesses.  There may have been something I should have changed in the genesis.  There are 101 delegate slots though.
By looking at the screen of witness_node, it's true that only the 11 witnesses are producing blocks.

//Edit: it's 11, not 10
« Last Edit: August 19, 2015, 09:29:15 pm by abit »
BitShares committee member: abit
BitShares witness: in.abit

Offline puppies

  • Hero Member
  • *****
  • Posts: 1659
    • View Profile
  • BitShares: puppies
My node is online now. Witness id 1.6.5247.
But number of active witnesses is still 10?
Code: [Select]
{
  "head_block_num": 11773,
  "head_block_id": "00002dfdab35043defebc42a6ae9d5a96767fd97",
  "head_block_age": "1 second old",
  "next_maintenance_time": "82 seconds in the future",
  "chain_id": "5508f5f743717fe2c78445364f62a72badd7532974d26f089af2062228b532eb",
  "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.1525",
    "1.6.4435",
    "1.6.5246",
    "1.6.5247"
  ],
  "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": "73f47170212775453a20de79b10d927e9d3b761d"
}
for some reason the info and get_global_properties screen dont show all witnesses.  There may have been something I should have changed in the genesis.  There are 101 delegate slots though.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
My node is online now. Witness id 1.6.5247.
But number of active witnesses is still 11?
Code: [Select]
{
  "head_block_num": 11773,
  "head_block_id": "00002dfdab35043defebc42a6ae9d5a96767fd97",
  "head_block_age": "1 second old",
  "next_maintenance_time": "82 seconds in the future",
  "chain_id": "5508f5f743717fe2c78445364f62a72badd7532974d26f089af2062228b532eb",
  "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.1525",
    "1.6.4435",
    "1.6.5246",
    "1.6.5247"
  ],
  "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": "73f47170212775453a20de79b10d927e9d3b761d"
}

//Edit: it's 11, not 10
« Last Edit: August 19, 2015, 09:28:51 pm by abit »
BitShares committee member: abit
BitShares witness: in.abit

Offline clayop

  • Hero Member
  • *****
  • Posts: 2033
    • View Profile
    • Bitshares Korea
  • BitShares: clayop
Great works all you guys. I will be in later tonight.
Bitshares Korea - http://www.bitshares.kr
Vote for me and see Korean Bitshares community grows
delegate-clayop

Offline betax

  • Hero Member
  • *****
  • Posts: 808
    • View Profile
Well...

Uhhhhh, Probably first Windows witness up and running  :)
Witness id: 1.6.4435 or simple testz
Please vote this witness in.

PS: Tomorrow I will try to summarize what I done and maybe will come with small instruction how to build and run witness under Windows

Voted and looking forward those instructions
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline betax

  • Hero Member
  • *****
  • Posts: 808
    • View Profile
Here we are...



Awesome, how did you build?

Using the graphene-ui build instructions :) in github.
As I am using ubuntu in a vps I changed server.js to use 0.0.0.0, also to use prod.
My witnesses uses for rpc 0.0.0.0 instead localhost / 127.0.0.1
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
Well...

Until we get something official, I have a new version up and running with 100 init witnessess.  I manually edited the genesis, and everything seems to be working, but I really had no idea what I was doing.  https://www.dropbox.com/s/xzlnoyn4tdpdede/aug-19-puppies-test-genesis.json?dl=0

The specific tag I built was 15c99bd65b0c90854d430126582fee49ec645fe6, so if you are having a hard time getting on the same chain-id I would suggest a
Code: [Select]
git checkout 15c99bd65b0c90854d430126582fee49ec645fe6
git submodule update --init --recursive
cmake -DBOOST_ROOT="$BOOST_ROOT" -DCMAKE_BUILD_TYPE=Debug .
make

I was also having a hard time getting the genesis.json to load.  Using the entire path in the command seems to work so for example
Code: [Select]
./witness_node -d test_net --genesis-json /home/user/src/8.19/graphene/programs/witness_node/aug-19-puppies-test-genesis.json
my server is still 45.55.6.216:1776

As always I am running on Ubuntu 14.04.  I also have exactly 0 formal computer science training, so if I am doing something wrong please let me know.  I am a learn by doing type of guy, and that includes making lots of mistakes.

and the chain id is 5508f5f743717fe2c78445364f62a72badd7532974d26f089af2062228b532eb but its kinda a pain to get the genesis.json to load and give you that chain-id
Great thanks.  +5% Building..
BitShares committee member: abit
BitShares witness: in.abit

Offline bytemaster

Well...

Uhhhhh, Probably first Windows witness up and running  :)
Witness id: 1.6.4435 or simple testz
Please vote this witness in.

PS: Tomorrow I will try to summarize what I done and maybe will come with small instruction how to build and run witness under Windows

Nice work!
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline puppies

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

Offline betax

  • Hero Member
  • *****
  • Posts: 808
    • View Profile
« Last Edit: August 19, 2015, 08:40:51 pm by betax »
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads