Delegates and seed nodes, upgrade your client version to 0.2.3

[puppies]

Thanks vikram.  That's exactly what I was looking for.

[vikram]

Is there perhaps a cmake command that will turn off building all the test stuff, and other stuff not needed on a cli delegate node?

You can do 'make bitshares_client' to build only the client.

[xeroc]

My backup nodes is updated .. main node for delegates will follow when non mobile again

[liondani]

Upgraded to 0.2.3 and feels so good  8)

[Riverhead]

Upgraded to 0.2.2.  No issues.

[testz]

Updated to 0.2.2, working fine

[spartako]

All spartako active delegates are updated to 0.2.2 version without problem.

Code Select Expand


default (unlocked) >>> about
{
  "bitshares_toolkit_revision": "7c3645e760305fce559ecfe05941c6d4c666f356",
  "bitshares_toolkit_revision_age": "11 hours ago",
  "fc_revision": "a254e5ff280cf88814730556c656254919bf53b6",
  "fc_revision_age": "19 hours ago",
  "compile_date": "compiled on Jul 24 2014 at 09:40:55"
}


[puppies]

Is there perhaps a cmake command that will turn off building all the test stuff, and other stuff not needed on a cli delegate node?

[GaltReport]

That was fun....not so much  ;D Hopefully it was tested somewhere by someone... :)

(sleeps now and assumes everything went well)

[HackFisher]

Is it recommended to build this from scratch in a new directory or update from repo into existing directory and rebuild?

it's ok to run on existing directory, but need about 2 minutes re–indexing

来自我的 GT-N7100 上的 Tapatalk

[GaltReport]

Thanks, how do you check next block produce time?  get_info?

{
"wallet_next_block_production_time": "4 minutes in the future",
}

Got it, TY.

[GaltReport]

Is it recommended to build this from scratch in a new directory or update from repo into existing directory and rebuild?

[muse-umum]

Thanks, how do you check next block produce time?  get_info?

Yes, get_info

{

"wallet_next_block_production_time": "4 minutes in the future",

}

[GaltReport]

System does not care about IP.

That's good.  TY.

[bytemaster]

System does not care about IP.

[GaltReport]

How do you do this:

"be careful and make sure you are producing blocks during upgrading."

Run two nodes, build another when running current one.

Check the next block produce time before you switch different delegate nodes.

Do not forget to open and unlock for enough long time.

Thanks, how do you check next block produce time?  get_info?

Is it okay if the IP is different if you are not a seed node?

[DACSunlimited]

How do you do this:

"be careful and make sure you are producing blocks during upgrading."

Run two nodes, build another when running current one.

Check the next block produce time before you switch different delegate nodes.

Do not forget to open and unlock for enough long time.

[GaltReport]

How do you do this:

"be careful and make sure you are producing blocks during upgrading."

[alt]

 +5% +5% +5%

[Overthetop]

 +5%

[bytemaster]

It will take about 1 minute to rebuild the blockchain database the first time you launch it so be prepared for that.

[DACSunlimited]

Download and build from:

https://github.com/dacsunlimited/bitsharesx/releases/tag/0.2.3

Binaries will be provided to users later

Suggestions:

1. Active Delegate, be careful and make sure you are producing blocks during upgrading.
2. BACKUP YOUR WALLET USING THE COMMAND wallet_export_to_json BEFORE UPGRADING
3. New version added lots of new seed nodes, you can connect to them by delegate config.json in your data dir.