October 2nd Test Network

[puppies]

@Thom

For this test net you will need to upgrade a lifetime member account to a witness with the create_witness command. 

This will give you a new public private signing key to put in your config.ini.

After create_ witness get_witness well give you your witness ID number.

[Thom]

My memory isn't what it used to be.  I have the code built and I can launch as a seed, but I can't recall the minimal steps required to become an active witness that produces blocks on graphene.

I have the keys for delegate.verbaltech I used for the early testnet, and a config.ini file I've edited with current info from https://github.com/cryptonomex/graphene/releases/tag/test5. I presume they're still valid now as they were for the early testnet (Is that dictated by the genesis.json file? Why does that need to change each test cycle, is it so that the current state of the BTS 1.0 chain serves as the starting point?).

The witness_id is where I get lost.

Is obtaining a new witness_id for delegate.verbaltech a matter of importing the keys using import_key <accountname> <owner wif key> and requesting to be voted in? Can the wallet .json file exported from 0.9.3c be imported into the graphene cli_wallet? I tried using import_accounts "filename.json" "password" but it fails with "fc::exists( filename ):", tho I tried both full pathname and putting the file where the wallets & config.ini are.

I see several posts requesting CORE to get registered as a witness and for spamming. The spamming I can understand, it takes assets to run tests. For registration though? Don't all 1.0 delegate accounts exist in 2.0 through the genesis block? If people are requesting CORE to get registered is that to avoid the need to import a balance from 1.0?

This wiki page says to use "get_witness <delegatename>" to obtain the witnessID from the cli wallet. When I do that it says "No account or witness named delegate.verbaltech"

[CalabiYau]

Code: [Select]

2079000ms th_a       witness.cpp:182               block_production_loo ] Not producing block because it isn't my turn
2079004ms th_a       application.cpp:432           handle_transaction   ] Got transaction from network
2079264ms th_a       application.cpp:432           handle_transaction   ] Got transaction from network
witness_node: /home/calabiyau/graphene/libraries/fc/src/thread/thread_d.hpp:370: bool fc::thread_d::start_next_fiber(bool): Assertion `std::current_exception() == std::exception_ptr()' failed.
Aborted (core dumped)

witness crashed - restart

[rnglab]

Thank you spartako for the CORES, bitshares-argentina ready to be voted in

[Bhuz]

I am one of those witnessed id...Is there something wrong?

A question:
I set up and ran a witness in the testnet of the 1st october (sadly with latency problems).
Now I would like to put this witness in another vps... Do I need to re-create the wallet, re-import the private keys and so on, or there is a faster way?

I would also know how much does it cost to become a delegate now (so upgrade to lifetime) and how much will it cost once BTS 2.0 is out.
Thanks and sorry for the little OT

Edit: I think I misunderstood the 5 digit id thing, nevermind I was in the active ones

[clayop]

Voting bias detected: witnesses with the digit 5 in their ID are not in active witness group:

Code: [Select]

info
{
...
  "active_witnesses": [
    "1.6.2",
...
   "1.6.14",
    "1.6.16",
...
    "1.6.24",
    "1.6.26",
...
    "1.6.31",
...
  ],
Who are these digit 5 witnesses?

Code: [Select]

get_witness fox
{
  "id": "1.6.25",
  "witness_account": "1.2.30566",
  "last_aslot": 23934,
...
  "total_votes": "9178845900",
...
  "last_confirmed_block_num": 7460
}

get_witness delegate-clayop
{
  "id": "1.6.15",
  "witness_account": "1.2.22404",
  "last_aslot": 23969,
...
  "total_votes": "9178845900",
...
  "last_confirmed_block_num": 7490
}

Both witnesses have votes, have produced in the past, but neither are in the active witness group at this time.  I recall Bytemaster voted out the witness lot, then stated he would vote them all back in, so maybe these were just missed and/or not meeting the minimum vote threshold (I'm not sure how to determine the threshold). 

Thanks for looking into this.

Disclaimer: I am one of the digit 5 witnesses

 
Disclaimer: I am another digit 5 witness 

[Fox]

Voting bias detected: witnesses with the digit 5 in their ID are not in active witness group:

Code: [Select]

info
{
...
  "active_witnesses": [
    "1.6.2",
...
   "1.6.14",
    "1.6.16",
...
    "1.6.24",
    "1.6.26",
...
    "1.6.31",
...
  ],
Who are these digit 5 witnesses?

Code: [Select]

get_witness fox
{
  "id": "1.6.25",
  "witness_account": "1.2.30566",
  "last_aslot": 23934,
...
  "total_votes": "9178845900",
...
  "last_confirmed_block_num": 7460
}

get_witness delegate-clayop
{
  "id": "1.6.15",
  "witness_account": "1.2.22404",
  "last_aslot": 23969,
...
  "total_votes": "9178845900",
...
  "last_confirmed_block_num": 7490
}

Both witnesses have votes, have produced in the past, but neither are in the active witness group at this time.  I recall Bytemaster voted out the witness lot, then stated he would vote them all back in, so maybe these were just missed and/or not meeting the minimum vote threshold (I'm not sure how to determine the threshold). 

Thanks for looking into this.

Disclaimer: I am one of the digit 5 witnesses

[clayop]

1000 TPS

https://graphene.bitshares.org/#/block/26232

[mindphlux]

Hello,

I recompiled master and re-setup my witness. I was participating in testnet3,4 and now 5. I already was a witness in testnet 4 :-)

please vote for my witness:


get_witness mindphlux.witness
{
  "id": "1.6.33",
  "witness_account": "1.2.92028",
  "last_aslot": 0,
  "signing_key": "GPH63kshJb47VhEYyJJiWBWKYjPQuQ7bBm2UvTTYhcme2nvsMWCj7",
  "vote_id": "1:54",
  "total_votes": 0,
  "url": "true",
  "total_missed": 0,
  "last_confirmed_block_num": 0
}

Thanks!

[betax]

Sorry about the missed blocks

witness 'delegate.ihashfury' and nodes updated with xeroc's feed script running every hour

We all entered a fork, don't worry.

[iHashFury]

Sorry about the missed blocks

witness 'delegate.ihashfury' and nodes updated with xeroc's feed script running every hour

[pc]

Updated and producing blocks again

[rnglab]

Hi there, still need some CORE for bitshares-argentina to create_witness

Code: [Select]

{
  "id": "2.1.0",
  "head_block_number": 20005,
  "head_block_id": "00004e254509b96a5c08d4839a4b19a811759d59",
  "time": "2015-10-03T07:52:30",
  "current_witness": "1.6.29",
  "next_maintenance_time": "2015-10-03T08:00:00",
  "witness_budget": 387000000,
  "accounts_registered_this_interval": 0,
  "recently_missed_count": 0,
  "current_aslot": 38193,
  "recent_slots_filled": "317659448096336101568232559415746362303",
  "dynamic_flags": 0
}

[xeroc]

My dedicated machine crashed this night and too most domains offline including stats.bitshares.eu. I will investigate and put them back online later this day (including the witness node)

[CalabiYau]

back on track

Code: [Select]

"head_block_num": 19314,
  "head_block_id": "00004b7263c523b80ea7467f5c080998de40d4dc",
  "head_block_age": "3 seconds old",