Quote from: sumantso on July 25, 2014, 10:41:01 AM
Can I just copy the wallet folder for backup too?

Yes bytemaster confirmed that that works.  I do both that and .json just to be safe.

updated  ;)

Can I just copy the wallet folder for backup too?

active spartako delegates updated:


default (unlocked) >>> about
{
  "bitshares_toolkit_revision": "554f588a931f9340aff2b27261392b57858d7300",
  "bitshares_toolkit_revision_age": "7 hours ago",
  "fc_revision": "a254e5ff280cf88814730556c656254919bf53b6",
  "fc_revision_age": "30 hours ago",
  "compile_date": "compiled on Jul 24 2014 at 23:22:40"
}


I think it's only possible to check by ip.

Quote from: GaltReport on July 24, 2014, 07:46:26 PM

Quote from: Xeldal on July 24, 2014, 05:22:48 PM
Done.

Is there yet a way to see which version delegates are running?

I think you can use the command about


mywallet (unlocked) >>> about
{
  "bitshares_toolkit_revision": "7c3645e760305fce559ecfe05941c6d4c666f356",
  "bitshares_toolkit_revision_age": "20 hours ago",
  "fc_revision": "a254e5ff280cf88814730556c656254919bf53b6",
  "fc_revision_age": "28 hours ago",
  "compile_date": "compiled on Jul 24 2014 at 02:51:35"
}

but it's kinda hard to interpret.

I will have to  do this  recent update later tonight.

I meant whether it's possible to check what version other delegates are running.

Quote from: Xeldal on July 24, 2014, 05:22:48 PM
Done.

Is there yet a way to see which version delegates are running?

I think you can use the command about


mywallet (unlocked) >>> about
{
  "bitshares_toolkit_revision": "7c3645e760305fce559ecfe05941c6d4c666f356",
  "bitshares_toolkit_revision_age": "20 hours ago",
  "fc_revision": "a254e5ff280cf88814730556c656254919bf53b6",
  "fc_revision_age": "28 hours ago",
  "compile_date": "compiled on Jul 24 2014 at 02:51:35"
}

but it's kinda hard to interpret.

I will have to  do this  recent update later tonight.

Done

Done.

Is there yet a way to see which version delegates are running?

Quote from: emski on July 24, 2014, 03:47:32 PM
What causes the frequency of the updates ?

Will be explained later, basicly due to potential security concerns.

Quote from: emski on July 24, 2014, 03:47:32 PM
What causes the frequency of the updates ?

We found a source of potential forks... otherwise our targeted release schedule is about once per week until we get a stable build out there that addresses potential security concerns, bugs, and ease of use issues.

What causes the frequency of the updates ?

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.