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

0 Members and 1 Guest are viewing this topic.

Offline GaltReport

A little confused as their are warnings not to upgrade and some download and build instructions have strikethroughs.  Can you clarify please?

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
hm .. my backup system successfully upgraded and produced blocks .. when switching to the main system with 0.4.0 he missed blocks ... wlthough all seemed fine ..
strange .. looking into ito

//edit: seems I needed to reanble block production
« Last Edit: August 15, 2014, 09:14:32 am by xeroc »

Offline Riverhead

Not sure if this is related to 0.4.0 delegates vs 0.3.1 but I'm see this. Note that I haven't missed a block because of this. I have not published a feed yet.


Code: [Select]

Peer 104.131.134.181:51145 disconnected us: You offered us a block that we reject as invalid
Peer 106.185.24.234:39314 disconnected us: You offered us a block that we reject as invalid

Offline emski

  • Hero Member
  • *****
  • Posts: 1282
    • View Profile
    • http://lnkd.in/nPbhxG
What if the delegate in the round just after me hasn't updated?
When we are required to publish price feeds?
Should we do it for all currencies ?

Offline emski

  • Hero Member
  • *****
  • Posts: 1282
    • View Profile
    • http://lnkd.in/nPbhxG
I updated and everything seemed to work properly.
As soon as I published price feeds I started missing blocks.
Code: [Select]
emski (unlocked) >>> info
{
  "blockchain_head_block_num": 227738,
  "blockchain_head_block_age": "5 seconds old",
  "blockchain_head_block_timestamp": "2014-08-15T07:17:00",
  "blockchain_average_delegate_participation": "91.82 %",
  "blockchain_confirmation_requirement": 1,
  "blockchain_accumulated_fees": "153,146.14196 BTSX",
  "blockchain_delegate_pay_rate": "1.26608 BTSX",
  "blockchain_share_supply": "1,999,957,225.95763 BTSX",
  "blockchain_blocks_left_in_round": 17,
  "blockchain_next_round_time": "3 minutes in the future",
  "blockchain_next_round_timestamp": "2014-08-15T07:19:50",
  "blockchain_random_seed": "14bfd263fd0987fa90ce853b16c3461e89f4524e",
  "client_data_dir": "/home/emski/bitsharesnodeTock/bitsharesx/programs/client/dd4.0",
  "network_num_connections": 66,
  "network_num_connections_max": 200,
  "ntp_time": "2014-08-15T07:17:05",
  "ntp_time_error": -0.0043769999999999998,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "37 minutes in the future",
  "wallet_unlocked_until_timestamp": "2014-08-15T07:53:41",
  "wallet_scan_progress": "? %",
  "wallet_block_production_enabled": true,
  "wallet_next_block_production_time": "at least 3 minutes in the future",
  "wallet_next_block_production_timestamp": null
}
emski (unlocked) >>> blockchain_list_blocks
HEIGHT  TIMESTAMP           SIGNING DELEGATE                # TXS   SIZE    TOTAL FEES      LATENCY PROCESSING TIME
===================================================================================================================
227738  2014-08-15T07:17:00 dpos.crazybit                   0       166     0.00000 BTSX    0       0.004883
227737  2014-08-15T07:16:50 fox                             0       166     0.00000 BTSX    0       0.000117
MISSED  2014-08-15T07:16:40 lotto-delegate                  N/A     N/A     N/A             N/A     N/A
227736  2014-08-15T07:16:30 init34                          0       166     0.00000 BTSX    0       0.002168

And where is my console.log ?


Output from 3.1 client:
Code: [Select]
     227736
     6b6301bb71de964c1a8f759f304316a3f6417967                lotto-delegate              2       502 2014-08-15T07:16:40         0      NO                  NO
     71f889b8659ff455185586ebedca7e99a21a59bf                           fox              0       166 2014-08-15T07:16:50         0     YES                 YES
         227744
     704bd508f16573c486e8ba828026f257364cc340               delegate.webber              0       166 2014-08-15T07:18:10         0     YES                  NO
     61d53df45eebe57e9f81632dc27eb845ced89d3e               delegate.webber              0       166 2014-08-15T07:18:10         0     YES                 YES
REASONS FOR INVALID BLOCKS
6b6301bb71de964c1a8f759f304316a3f6417967: 10 assert_exception: Assert Exception
converter_itr != _converters.end():
    {}
    th_a  operations.cpp:62 to_variant

    {}
    th_a  operations.cpp:64 to_variant

    {"trx_num":0}
    th_a  chain_database.cpp:1003 apply_transactions
« Last Edit: August 15, 2014, 07:22:49 am by emski »

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
one can count the hours to release now :) exciting

Offline alt

  • Hero Member
  • *****
  • Posts: 2821
    • View Profile
  • BitShares: baozi

Ggozzo

  • Guest
What if we aren't savvy enough to build? Are you going to eventually release a compiled version for windows? And the link on price feeds didn't explain all that much on what to do.

Offline toast

  • Hero Member
  • *****
  • Posts: 4001
    • View Profile
  • BitShares: nikolai
Quote
- Market has been overhauled and market-pegged BitAssets have been added

O=

=O

||
O
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 DACSunlimited

  • Full Member
  • ***
  • Posts: 136
    • View Profile
0.4.1: Fixes missed blocks problem due to hardfork changes.

*This is a version only for delegates, exchanges, and seed nodes.*

Delegates should not upgrade unless they want to help test and are prepared to upgrade one more time before wednesday.   Delegates that want to be lazy and upgrade only once should not try this release.

Updates from bytemaster:
Quote
After discussions going on I have tweaked the bitasset FDIC system so the hardfork will be slightly different than we see in this release.  In fact, we may want to push the hard-fork back a few days so that all the issues can be worked out.

Do not publish price feeds until after hardfork and all clients are upgraded. This is a new operation that is part of the hardfork. All old clients will reject blocks containing publish price feed operation. This is the reason for missed blocks.

Large transaction and block sizes are also part of the hardfork, and could result in missed blocks.

We will release a patch ensuring all hardfork changes take effect at the same time.

Delegates are still free to upgrade but must be aware that a crashing issue has been identified. Brave delegates can upgrade and run client in a debugger to help us get a stack trace of the crash.


GUI will be provided soon. All clients must upgrade before hardfork or syncing will freeze.

Download and build from:

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

Suggestions:

1. Active Delegate, be careful and make sure you are producing blocks during upgrading.
2. Delegates, publish your price feeds.

Refer bytemaster's post about price feeds:
https://bitsharestalk.org/index.php?topic=6306.0


Change Log
- [HARDFORK] Block 274000 - Old clients will no longer sync after 2014-08-20 15:30:00 UTC
- [CHECKPOINT] Block 225000 - ID: 2e09195c3e4ef6d58736151ea22f78f08556e6a9

- [EXCHANGES] wallet_transfer API now returns a wallet_transaction_record which includes the transaction ID
- Database will re-index on launch
- Market has been overhauled and market-pegged BitAssets have been added
- Max block size increased from 2560 bytes to 51200 bytes
- Transaction size limit has been removed
- Size-based transaction fee requirement has been removed
- Wallet will no longer automatically relock if it contains any enabled delegates
- Chain server mode has been added to allow for improved initial syncing speeds
- Block and transaction broadcasting fixes
- General syncing fixes
- NTP initialization fixes
- Miscellaneous fixes and improvements
« Last Edit: August 16, 2014, 02:43:20 pm by DACSunlimited »