Author Topic: Delegates, please response to this thread if your delegate updated to 0.4.9  (Read 19486 times)

0 Members and 1 Guest are viewing this topic.

Offline bitcoinerS

  • Hero Member
  • *****
  • Posts: 592
    • View Profile
>>> approve bitcoiners

Offline emski

  • Hero Member
  • *****
  • Posts: 1282
    • View Profile
    • http://lnkd.in/nPbhxG
Seed node and delegates updated.
* angel and lotto included

Offline svk

*.svk31 updated and running 0.4.9

Seednode currently indexing.
Worker: dev.bitsharesblocks

Offline betax

  • Hero Member
  • *****
  • Posts: 808
    • View Profile
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline tonyk

  • Hero Member
  • *****
  • Posts: 3308
    • View Profile
maybe try syncing from the chain server: https://github.com/BitShares/bitshares_toolkit/wiki/Using-Chain-Servers
I'll sync somehow...
But what about any new user?

UPDATE: I reindexed 0.4.8 datadir and it seems OK.

Yee I am syncing too...finally, but I do not think, I am giving back anything... I expect 700 new threads of the 'Wallet won't sync'/'Severe network problem' variety as everybody is going through the same process/again/at once.

It would very good, if everybody is using some more resource sparing method like the one in bold above.
« Last Edit: August 28, 2014, 07:08:13 am by TheOnion »
Lack of arbitrage is the problem, isn't it. And this 'should' solves it.

Offline Webber

  • Sr. Member
  • ****
  • Posts: 223
    • View Profile
Bitshares2.0 witness node:delegate.webber
Bitshares2.0 API:ws://114.215.116.57:8090

Offline dcchong

  • Sr. Member
  • ****
  • Posts: 203
    • View Profile
wallet_approve_delegate dc-delegate true
wallet_approve_delegate bitsharesx-delegate true

Offline emski

  • Hero Member
  • *****
  • Posts: 1282
    • View Profile
    • http://lnkd.in/nPbhxG
maybe try syncing from the chain server: https://github.com/BitShares/bitshares_toolkit/wiki/Using-Chain-Servers
I'll sync somehow...
But what about any new user?

UPDATE: I reindexed 0.4.8 datadir and it seems OK.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc

Offline emski

  • Hero Member
  • *****
  • Posts: 1282
    • View Profile
    • http://lnkd.in/nPbhxG
I run an instance of the client on 0.4.9.
It failed to synchronize (new data dir):

Code: [Select]
I am disconnecting peer 61.164.87.130:14953 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 93.48.104.46:61603 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 106.185.26.162:1776 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 69.90.132.209:1028 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 201.145.195.188:57116 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 84.238.140.192:42577 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 75.128.156.59:63559 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 68.189.49.243:55044 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 222.244.50.180:62998 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 54.84.33.170:1776 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 183.29.176.165:58582 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 106.187.42.214:1700 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 209.141.206.195:37960 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 61.194.2.252:57304 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 71.231.63.172:61488 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 23.102.66.61:1344 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 54.197.203.51:1700 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 50.206.156.115:51949 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 217.14.49.100:3137 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 61.194.2.252:54546 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 123.110.16.111:51728 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 61.164.87.130:18211 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 76.91.0.24:62318 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 65.93.177.125:51319 for reason: You offered us a block that we reject as invalid
--- there are now 14 active connections to the p2p network
--- there are now 13 active connections to the p2p network
--- there are now 12 active connections to the p2p network
--- there are now 11 active connections to the p2p network
--- there are now 10 active connections to the p2p network
(wallet closed) >>> info
{
  "blockchain_head_block_num": 275171,
  "blockchain_head_block_age": "7 days old",
  "blockchain_head_block_timestamp": "2014-08-21T01:42:30",
  "blockchain_average_delegate_participation": "0.16 %",
  "blockchain_confirmation_requirement": 303,
  "blockchain_accumulated_fees": "222,946.50184 BTSX",
  "blockchain_delegate_pay_rate": "1.84314 BTSX",
  "blockchain_share_supply": "1,999,946,838.10086 BTSX",
  "blockchain_blocks_left_in_round": 54,
  "blockchain_next_round_time": "at least 9 minutes in the future",
  "blockchain_next_round_timestamp": "2014-08-28T06:41:20",
  "blockchain_random_seed": "b4800b285ee2b68ea13596bb7ba93fb8726d763c",
  "client_version": "0.4.9",
  "network_num_connections": 10,
  "network_num_connections_max": 100,
  "ntp_time": "2014-08-28T06:32:20",
  "ntp_time_error": 0.016278999999999998,
  "wallet_open": false,
  "wallet_unlocked": null,
  "wallet_unlocked_until": null,
  "wallet_unlocked_until_timestamp": null,
  "wallet_last_scanned_block_timestamp": null,
  "wallet_scan_progress": null,
  "wallet_block_production_enabled": null,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null
}


(wallet closed) >>> blockchain_list_forks
   FORKED BLOCK              FORKING BLOCK ID              SIGNING DELEGATE      TXN COUNT      SIZE           TIMESTAMP   LATENCY   VALID    IN CURRENT CHAIN
--------------------------------------------------------------------------------------------------------------------------------------------------------------
         275164
     11af0ac74dfd49f23e6e855d2ecd09c7ba263819                        btsnow              5      1727 2014-08-20T22:54:10    632274     YES                 YES
     abd972bc55db249c13e09640fc2d5f653e0c2b8e                      d.dacsun              1      1463 2014-08-20T22:42:30    632974     N/A                  NO

blockchain_list_balances  blockchain_list_blocks
(wallet closed) >>> blockchain_list_blocks
6 key_not_found_exception: Key Not Found
unable to find key 275171
    {"key":275171}
    th_a  level_map.hpp:95 fetch
error fetching key 275171
    {"key":275171}
    th_a  level_map.hpp:105 fetch

    {"block_num":275171}
    th_a  chain_database.cpp:1267 get_block_id

    {"block_num":275171}
    th_a  chain_database.cpp:1262 get_block_record

    {}
    th_a  common_api_client.cpp:451 blockchain_list_blocks

    {"command":"blockchain_list_blocks"}
    th_a  cli.cpp:471 execute_command
Peer 223.3.87.78:61542 disconnected us: You offered us a block that we reject as invalid


After this message there is no further synchronization.
I'll try to use the datadir of 0.4.8 and post results. However I consider this serious issue.
« Last Edit: August 28, 2014, 06:37:50 am by emski »

Offline CalabiYau

calabiyau & neuronics up & running, thank you for voting back in.
« Last Edit: August 28, 2014, 07:02:01 am by CalabiYau »


Offline toast

  • Hero Member
  • *****
  • Posts: 4001
    • View Profile
  • BitShares: nikolai
delegate.adam
delegate2.adam
daslab
delegate.kettenblog
Do not use this post as information for making any important decisions. The only agreements I ever make are informal and non-binding. Take the same precautions as when dealing with a compromised account, scammer, sockpuppet, etc.

Offline Riverhead

« Last Edit: August 28, 2014, 06:46:57 am by Riverhead »

Xeldal

  • Guest
Active:
delegate.xeldal
delegate2.xeldal

standby
delegate3.xeldal
and all others

upgraded to 0.4.9