Author Topic: Delegates and seed nodes, upgrade your client version to 0.2.3  (Read 5211 times)

0 Members and 1 Guest are viewing this topic.

Offline Riverhead

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.

Offline liondani

  • Hero Member
  • *****
  • Posts: 3737
  • Inch by inch, play by play
    • View Profile
    • My detailed info
  • BitShares: liondani
  • GitHub: liondani

sumantso

  • Guest
Can I just copy the wallet folder for backup too?

Offline spartako

  • Sr. Member
  • ****
  • Posts: 401
    • View Profile
active spartako delegates updated:

Code: [Select]
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"
}
wallet_account_set_approval spartako

Offline puppies

  • Hero Member
  • *****
  • Posts: 1659
    • View Profile
  • BitShares: puppies
I think it's only possible to check by ip.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Xeldal

  • Guest
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.

Offline GaltReport

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.

Offline testz


Xeldal

  • Guest
Done.

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

Offline DACSunlimited

  • Full Member
  • ***
  • Posts: 136
    • View Profile
What causes the frequency of the updates ?

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

Offline bytemaster

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.

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 DACSunlimited

  • Full Member
  • ***
  • Posts: 136
    • View Profile
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.