Main Menu

October 5 Test Network

Started by bytemaster, October 05, 2015, 02:23:40 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

betax

upgrade latest, need votes :D
[url="https://metaexchange.info"]https://metaexchange.info[/url] | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

boombastic

mr.agsexplorer is updated to latest master, needs to be voted in, @bytemaster
[url="http://bitshares.dacplay.org/r/boombastic"]http://bitshares.dacplay.org/r/boombastic[/url]
Support My Witness: mr.agsexplorer
BTC: 1Bb6V1UStz45QMAamjaX8rDjsnQnBpHvE8

Bhuz

@puppies Thank you so much!

bhuz running on latest master

Thom

delegate.verbaltech is updated to master, running on a vew VPS and a new signing key in Singnapore. Current missed block count is 98. See lots of errors pushing blocks, but mu missed block count is not going up.

I've gotta run to an appointment now tho, so hopefully it's working as it should.

BTW, what's that msg about updating the date on the genesis.json all about?
Injustice anywhere is a threat to justice everywhere - MLK |  Verbaltech2 Witness Reports: [url="https://bitsharestalk.org/index.php/topic,23902.0.html"]https://bitsharestalk.org/index.php/topic,23902.0.html[/url]

Xeldal


mindphlux

How do I withdraw the vested balance for my witness?

The command below seems to work but I'm not seeing those 1000 CORE on any account. What am I doing wrong?

unlocked >>> withdraw_vesting mindphlux.witness 1000 CORE true
withdraw_vesting mindphlux.witness 1000 CORE true
{
  "ref_block_num": 57826,
  "ref_block_prefix": 1642589200,
  "expiration": "2015-10-07T17:01:39",
  "operations": [[
      33,{
        "fee": {
          "amount": 100000,
          "asset_id": "1.3.0"
        },
        "vesting_balance": "1.13.41",
        "owner": "1.2.91505",
        "amount": {
          "amount": 100000000,
          "asset_id": "1.3.0"
        }
      }
    ]
  ],
  "extensions": [],
  "signatures": [
    "1f578fe8df3796f443b969aaa2c2d4502d48df14b132676e29b95721fc50c2a35455745a743e388aec7fbff4b8ac1565ca6f034047b67c4889342d1a74650008f8"
  ]
}
Please consider voting for my witness mindphlux.witness and my committee user mindphlux. I will not vote for changes that affect witness pay.

Thom

Quote from: puppies on October 07, 2015, 02:49:49 PM
Quote from: Bhuz on October 07, 2015, 01:42:34 PM
Quote from: bytemaster on October 07, 2015, 01:11:40 PM
Everyone else, please update your witness to the latest master before block 58500  (about 4 hours).

Can someone please tell me how to update the witness without stop it?

Can I copy the current "graphene" folder, rename it to "current-graphene", update the copied "graphene", restart the witness in this new folder?
Do I have to use update_witness when launching the updated one? How does it works?

Thanks xD
I've used a few different strategies.  Most often what I have done is
1) build a fresh build on a different box.
2) get it set up and running with a secondary public private key pair (more on this below)
3) switch block production to this second key pair
4) build on my main box and restart witness node
5) switch block production back.
This time I am trying something new.  I have created a secondary build directory on my main box and have launched a second witness_node running with a secondary key pair.  Once the build is complete on the local box that has all of my balances I will switch over production, shut down the first build, and rebuild it.

In order to switch between witnesses you will need at least two sets of public private key pairs.  You can generate these key pairs with the wallet command
suggest_brain_key

I recommend saving the output of that command to a file so you can reference it later.  On your secondary box you will replace the current active public private key pair, with this new public private key pair.  I suggest doing this in the config.ini, but you can also do it all in command line.  Once both boxes are up and running with different key pairs, you can switch between them with the wallet command

update_witness <witness_account> <url> <public key> true

you should be able to use "" if you want an empty url. 

Hope this cleared things up and didn't just confuse you further.

I am running on a different VPS today, and I tried to start it using the above as a guide. From the looks of things I wasn't successful, as I see errors pushing blocks.

What I was unclear of is which node should the update_witness cmd be run on, the old chain or the new one?

I was running the cli directly in the bin folder so my trouble may be the wallet. I copied the wallet.json and one other file (it was created on the 5th) to the new VPS and used -w and the other file to launch the cli. When I started the cli it opened with correct password and get_witness agreeed with the same command on the old VPS.

Anyway I'm stopping the witness as it doesn't seem to be working. Before I do I will revert to the old keys, if possible. I may have to restart the old witness to do that.
Injustice anywhere is a threat to justice everywhere - MLK |  Verbaltech2 Witness Reports: [url="https://bitsharestalk.org/index.php/topic,23902.0.html"]https://bitsharestalk.org/index.php/topic,23902.0.html[/url]

ElMato


alt

get back after update to the latest master
Quote from: cube on October 07, 2015, 03:38:33 PM
Quote from: alt on October 07, 2015, 03:35:28 PM
I have switched to a fork after update to master

I realised I went into a fork too.  I am trying to resync.

Edit: resynced.

twitter

bue  updated to last master
witness:

spartako

spartako updated to last master
wallet_account_set_approval spartako

puppies

dele-puppy is now fully updated.
[url="https://metaexchange.info"]https://metaexchange.info[/url] | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

cube

#277
Quote from: alt on October 07, 2015, 03:35:28 PM
I have switched to a fork after update to master

I realised I went into a fork too.  I am trying to resync.

Edit: resynced.
ID: bitcube
bitcube is a dedicated witness and committe member. Please vote for bitcube.

alt

I have switched to a fork after update to master

xeroc