Author Topic: October 5 Test Network  (Read 56769 times)

0 Members and 1 Guest are viewing this topic.

Offline roadscape

Re: October 5 Test Network
« Reply #270 on: October 07, 2015, 03:10:18 pm »
roadscape updated to master
http://cryptofresh.com  |  witness: roadscape

iHashFury

  • Guest
Re: October 5 Test Network
« Reply #271 on: October 07, 2015, 03:18:26 pm »
wintness 'delegate.ihashfury' and nodes - updated to latest master

Offline bytemaster

Re: October 5 Test Network
« Reply #272 on: October 07, 2015, 03:21:47 pm »
The most recent master has a fix for failure to switch to the proper fork.   We are resolving a few other issues so there may be additional updates.

My apologies for the rapid fixes.
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 cube

  • Hero Member
  • *****
  • Posts: 1404
  • Bit by bit, we will get there!
    • View Profile
  • BitShares: bitcube
Re: October 5 Test Network
« Reply #273 on: October 07, 2015, 03:25:39 pm »
It is appraching midnight (and bedtime) here in asia.  I hope I am not going to miss any update.
ID: bitcube
bitcube is a dedicated witness and committe member. Please vote for bitcube.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12915
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Re: October 5 Test Network
« Reply #274 on: October 07, 2015, 03:34:12 pm »
My apologies for the rapid fixes.
Wait .. what ???
Give BitShares a try! Use the http://testnet.bitshares.eu provided by http://bitshares.eu powered by ChainSquad GmbH

Offline alt

  • Hero Member
  • *****
  • Posts: 2821
    • View Profile
  • BitShares: baozi
Re: October 5 Test Network
« Reply #275 on: October 07, 2015, 03:35:28 pm »
I have switched to a fork after update to master

Offline cube

  • Hero Member
  • *****
  • Posts: 1404
  • Bit by bit, we will get there!
    • View Profile
  • BitShares: bitcube
Re: October 5 Test Network
« Reply #276 on: October 07, 2015, 03:38:33 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.
« Last Edit: October 07, 2015, 03:45:26 pm by cube »
ID: bitcube
bitcube is a dedicated witness and committe member. Please vote for bitcube.

Offline puppies

  • Hero Member
  • *****
  • Posts: 1659
    • View Profile
  • BitShares: puppies
Re: October 5 Test Network
« Reply #277 on: October 07, 2015, 03:55:06 pm »
dele-puppy is now fully updated.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline spartako

  • Sr. Member
  • ****
  • Posts: 401
    • View Profile
Re: October 5 Test Network
« Reply #278 on: October 07, 2015, 04:12:08 pm »
spartako updated to last master
wallet_account_set_approval spartako

Offline twitter

  • Sr. Member
  • ****
  • Posts: 277
    • View Profile
Re: October 5 Test Network
« Reply #279 on: October 07, 2015, 04:14:18 pm »
bue  updated to last master
witness:

Offline alt

  • Hero Member
  • *****
  • Posts: 2821
    • View Profile
  • BitShares: baozi
Re: October 5 Test Network
« Reply #280 on: October 07, 2015, 04:16:57 pm »
get back after update to the latest master
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.

Offline ElMato

  • Sr. Member
  • ****
  • Posts: 288
    • View Profile
Re: October 5 Test Network
« Reply #281 on: October 07, 2015, 04:42:36 pm »
elmato updated to master.



Offline Thom

Re: October 5 Test Network
« Reply #282 on: October 07, 2015, 04:48:12 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
Code: [Select]
suggest_brain_keyI 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
Code: [Select]
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: https://bitsharestalk.org/index.php/topic,23902.0.html

Offline mindphlux

  • Sr. Member
  • ****
  • Posts: 232
    • View Profile
Re: October 5 Test Network
« Reply #283 on: October 07, 2015, 05:03:04 pm »
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.

Xeldal

  • Guest
Re: October 5 Test Network
« Reply #284 on: October 07, 2015, 05:07:13 pm »
xeldal is updated to master