Author Topic: [URGENT] Delegates Please Upgrade to v0.4.26!  (Read 17771 times)

0 Members and 1 Guest are viewing this topic.

Offline alt

  • Hero Member
  • *****
  • Posts: 2821
    • View Profile
  • BitShares: baozi
the other client is in the main chain, but just refuse to sync continue,
here is the message from p2p.log
Code: [Select]
2014-12-14T02:12:47 th_a:invoke handle_message evaluate_transaction ] Transaction 921f8f9e253253994ac068e5b2824be7ee8bd079 needed relay fee 90000 but only had 10000   
                chain_database.cpp:1548
2014-12-14T02:12:47 th_a:invoke handle_message                store ] storing error in database: {"code":36005,"name":"insufficient_relay_fee","message":"insufficient r
elay fee","stack":[{"context":{"level":"error","file":"chain_database.cpp","line":1549,"method":"evaluate_transaction","hostname":"","thread_name":"th_a","timestamp":"2
014-12-14T02:12:47"},"format":"","data":{"fees":10000,"required_fees":90000}},{"context":{"level":"warn","file":"chain_database.cpp","line":1555,"method":"evaluate_tran
saction","hostname":"","thread_name":"th_a","timestamp":"2014-12-14T02:12:47"},"format":"","data":{"trx":{"expiration":"2014-12-14T03:20:06","delegate_slate_id":null,"o
perations":[{"type":"ask_op_type","data":{"amount":25002540,"ask_index":{"order_price":{"ratio":"1.8907165815844","quote_asset_id":3,"base_asset_id":0},"owner":"BTSFTpA
1iwRTLjpzy97pJP5StB4vFRiRU6a6"}}},{"type":"withdraw_op_type","data":{"balance_id":"BTSH5rE3GwXQCcVUENejXdf2QehqFSh1UCbj","amount":25012540,"claim_input_data":""}}],"sig
natures":["200a2f8807a6f74471f1db5d966d0259b8a277079728d15a3d62d2b1898b358e3b5161f74fef73cbe7913a724354c63885c5c2eb1a5fc529d63225fef54467856e","1f0efb2bdb393d65181cd984
1b87698a1dae48dc060dba469bff116e778b41827653996aceeb8e535d2e196362e99d9588f72dfb760fbc9a1c2a4acf4ae2536cc4"]}}},{"context":{"level":"warn","file":"chain_database.cpp","
line":2218,"method":"store_pending_transaction","hostname":"","thread_name":"th_a","timestamp":"2014-12-14T02:12:47"},"format":"","data":{"trx":{"expiration":"2014-12-1
4T03:20:06","delegate_slate_id":null,"operations":[{"type":"ask_op_type","data":{"amount":25002540,"ask_index":{"order_price":{"ratio":"1.8907165815844","quote_asset_id
":3,"base_asset_id":0},"owner":"BTSFTpA1iwRTLjpzy97pJP5StB4vFRiRU6a6"}}},{"type":"withdraw_op_type","data":{"balance_id":"BTSH5rE3GwXQCcVUENejXdf2QehqFSh1UCbj","amount"
:25012540,"claim_input_data":""}}],"signatures":["200a2f8807a6f74471f1db5d966d0259b8a277079728d15a3d62d2b1898b358e3b5161f74fef73cbe7913a724354c63885c5c2eb1a5fc529d63225fef54467856e","1f0efb2bdb393d65181cd9841b87698a1dae48dc060dba469bff116e778b41827653996aceeb8e535d2e196362e99d9588f72dfb760fbc9a1c2a4acf4ae2536cc4"]}}}]}                        client_impl.hpp:47
2014-12-14T02:12:47 th_a:invoke handle_messa

Offline alt

  • Hero Member
  • *****
  • Posts: 2821
    • View Profile
  • BitShares: baozi
and the fork is create from my delegate, because of sync problem
Code: [Select]
delegate (unlocked) >>> blockchain_list_blocks  1253612 2
HEIGHT  TIMESTAMP           SIGNING DELEGATE                # TXS   SIZE    LATENCY PROCESSING TIME  RAND           
====================================================================================================================
1253612 2014-12-13T16:00:00 init43                          2       1577    0       0.037797         26b59b8a3d46a6b1682b013783e601a1fa7e384a
MISSED  2014-12-13T16:00:10 mrs.agsexplorer                 N/A     N/A     N/A     N/A              N/A           
MISSED  2014-12-13T16:00:20 moon.delegate.service           N/A     N/A     N/A     N/A              N/A           
MISSED  2014-12-13T16:00:30 delegate1-galt                  N/A     N/A     N/A     N/A              N/A           
MISSED  2014-12-13T16:00:40 bm.payroll.riverhead            N/A     N/A     N/A     N/A              N/A           
MISSED  2014-12-13T16:00:50 delegate.nathanhourt.com        N/A     N/A     N/A     N/A              N/A           
MISSED  2014-12-13T16:01:00 delegate.charity                N/A     N/A     N/A     N/A              N/A           
MISSED  2014-12-13T16:01:10 very.strong                     N/A     N/A     N/A     N/A              N/A           
MISSED  2014-12-13T16:01:20 future.dacwin                   N/A     N/A     N/A     N/A              N/A           
MISSED  2014-12-13T16:01:30 delegate2.xeldal                N/A     N/A     N/A     N/A              N/A           
MISSED  2014-12-13T16:01:40 boombastic                      N/A     N/A     N/A     N/A              N/A           
MISSED  2014-12-13T16:01:50 now.dacwin                      N/A     N/A     N/A     N/A              N/A           
MISSED  2014-12-13T16:02:00 testz                           N/A     N/A     N/A     N/A              N/A           
MISSED  2014-12-13T16:02:10 emski.bitdelegate               N/A     N/A     N/A     N/A              N/A           
MISSED  2014-12-13T16:02:20 riverhead-del-server-1          N/A     N/A     N/A     N/A              N/A           
MISSED  2014-12-13T16:02:30 crazybit                        N/A     N/A     N/A     N/A              N/A           
1253613 2014-12-13T16:02:40 delegate.baozi                  7       7330    0       0.056642         4c15a30b598899cbbcfc1ee30b6dfd463d54bc03

Offline alt

  • Hero Member
  • *****
  • Posts: 2821
    • View Profile
  • BitShares: baozi
I have 3 client, in 3 different forks.....both v0.4.26

from block 1253547, the random seed is different, but the block is same
5%
Code: [Select]
delegate (unlocked) >>> blockchain_get_block 1253547
{
  "previous": "1eb0869d7fba7402ba5017e3778d04bb2496406d",
  "block_num": 1253547,
  "timestamp": "2014-12-13T15:48:50",
  "transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
  "next_secret_hash": "af817547d1c6c287c7c3c4388fc6e0839001d44a",
  "previous_secret": "ae525bf66ce8e114a5d23827ea24fbfc6c50174f",
  "delegate_signature": "2040ee212addc5a6503b7997009afa4ffd733be14a3afaa0c74b130843a6bf952c4bac02ae48c819f223b0ecf9fdd8cf410ba4edc93fc96660379bf9674af92ee1",
  "user_transaction_ids": [],
  "signee_shares_issued": 150000,
  "signee_fees_collected": 0,
  "signee_fees_destroyed": 0,
  "random_seed": "8b9d9afdd18d92ee0ecef0997e81562620d1d5a6",
  "block_size": 166,
  "latency": 0,
  "processing_time": 2834
}
95%
Code: [Select]
delegate (unlocked) >>> blockchain_get_block 1253547
{
  "previous": "1eb0869d7fba7402ba5017e3778d04bb2496406d",
  "block_num": 1253547,
  "timestamp": "2014-12-13T15:48:50",
  "transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
  "next_secret_hash": "af817547d1c6c287c7c3c4388fc6e0839001d44a",
  "previous_secret": "ae525bf66ce8e114a5d23827ea24fbfc6c50174f",
  "delegate_signature": "2040ee212addc5a6503b7997009afa4ffd733be14a3afaa0c74b130843a6bf952c4bac02ae48c819f223b0ecf9fdd8cf410ba4edc93fc96660379bf9674af92ee1",
  "user_transaction_ids": [],
  "signee_shares_issued": 150000,
  "signee_fees_collected": 0,
  "signee_fees_destroyed": 0,
  "random_seed": "9ba0e03ae99795a91f73c233b999efdc5f68a663",
  "block_size": 166,
  "latency": 0,
  "processing_time": 29190
}

from 1253613, the block is different
5%
Code: [Select]
delegate (unlocked) >>> blockchain_get_block 1253613
{
  "previous": "98527eea839fbfe7974ba0795e8e61805a2e6b7a",
  "block_num": 1253613,
  "timestamp": "2014-12-13T16:02:40",
  "transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
  "next_secret_hash": "4166c54ab052c38509ee126773b9be62ccd786f5",
  "previous_secret": "cba4a7e4709b6053a47960265c2c7c9a19255f76",
  "delegate_signature": "206150cb7badd373d189863e1b5d01eeaeeac2493e9e4d51d025ae3de043010b7b49d0c573e8145547aa68190d407cf366bc405b3d752a07d9f2d130ef237f0d30",
  "user_transaction_ids": [
    "b850db16dcb49b6e98e0790a40159e9eb3ec8156",
    "12a4b67ccbfdf9950df96f48240853e9df955a18",
    "37c997cb63b065253f41bbebb83d3428c5a75aeb",
    "7954c4d8db3d5ee63fa90334830e657970c9623f",
    "865c748a7f81dc0444e676120dea7b4bdbc0d8b6",
    "b322b06f9fe9208e21d5541119152bc30a52cc3d",
    "f55dd51a1610aff079ac1b59cede113bf959920b"
  ],
  "signee_shares_issued": 150000,
  "signee_fees_collected": 0,
  "signee_fees_destroyed": 20000,
  "random_seed": "4c15a30b598899cbbcfc1ee30b6dfd463d54bc03",
  "block_size": 7330,
  "latency": 0,
  "processing_time": 56642
}
95%
Code: [Select]
delegate (unlocked) >>> blockchain_get_block 1253613
{
  "previous": "98527eea839fbfe7974ba0795e8e61805a2e6b7a",
  "block_num": 1253613,
  "timestamp": "2014-12-13T16:00:10",
  "transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
  "next_secret_hash": "b293cae7599d6a74e8c1f415e482767a01a3c4f6",
  "previous_secret": "37279fa9266808a91eb09ab4c75b3b428b01c1ea",
  "delegate_signature": "1f38bafda9c039414cb2b85bb0d73389c4ad4463a39899cabb2b0a92c8543a08a643c19dc7e8d05519e7be741d12e0f5935eba01413e6fe34973effc741c1a5ff8",
  "user_transaction_ids": [],
  "signee_shares_issued": 150000,
  "signee_fees_collected": 0,
  "signee_fees_destroyed": 20000,
  "random_seed": "df612d4ab5f43d0c8c4f066f315480c1145a4b85",
  "block_size": 166,
  "latency": 0,
  "processing_time": 37179
}

Offline bytemaster


Delegate participation rate is over 95% now. Beautiful update speed (considering re-indexing time)

Yes, it is impressive considering not all delegates are running it as a full-timer.

i'm one of the 5%, somehow it got on a fork last night while I was asleep and was producing blocks on a chain with by itself. I have 3 machines and can't get any of them to connect to the network. I've deleted and downloaded the chain 3 times, let's see if 4 is the charm...

EDIT: by can't connect i mean they seem to get on a fork and peg the CPU at 100% while downloading blocks. Different block each time

Try deleting your peer db and manually reindex. 
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 Riverhead

I had a similar issue. What I ended up doing was stating 0.4.26 in a completely new directory and then creating a new wallet and importing the private keys. Until then I was getting databases that be OK for a bit and then corrupt or stall.

Offline maqifrnswa

  • Hero Member
  • *****
  • Posts: 661
    • View Profile
Delegate participation rate is over 95% now. Beautiful update speed (considering re-indexing time)

Yes, it is impressive considering not all delegates are running it as a full-timer.

i'm one of the 5%, somehow it got on a fork last night while I was asleep and was producing blocks on a chain with by itself. I have 3 machines and can't get any of them to connect to the network. I've deleted and downloaded the chain 3 times, let's see if 4 is the charm...

EDIT: by can't connect i mean they seem to get on a fork and peg the CPU at 100% while downloading blocks. Different block each time


up and running!
« Last Edit: December 13, 2014, 06:03:22 pm by maqifrnswa »
maintains an Ubuntu PPA: https://launchpad.net/~showard314/+archive/ubuntu/bitshares [15% delegate] wallet_account_set_approval maqifrnswa true [50% delegate] wallet_account_set_approval delegate1.maqifrnswa true

Offline cube

  • Hero Member
  • *****
  • Posts: 1404
  • Bit by bit, we will get there!
    • View Profile
  • BitShares: bitcube
Delegate participation rate is over 95% now. Beautiful update speed (considering re-indexing time)

Yes, it is impressive considering not all delegates are running it as a full-timer.
ID: bitcube
bitcube is a dedicated witness and committe member. Please vote for bitcube.

Offline bytemaster


(considering re-indexing time)

Speaking of which, is re-indexing something that is inherently single-threaded or that could be made multi-threaded in the future? Because that could help speed upgrades a lot, even more so than just the gain from the speedup itself on the computer, eg: sometimes in the past I had only 20-30 minutes of "contiguous time" to upgrade and decided to postpone the upgrade until a bit later when I would have more time, because otherwise I wouldn't have been available to unlock my wallet after re-indexing.

Inherently sequential. 
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 wackou

(considering re-indexing time)

Speaking of which, is re-indexing something that is inherently single-threaded or that could be made multi-threaded in the future? Because that could help speed upgrades a lot, even more so than just the gain from the speedup itself on the computer, eg: sometimes in the past I had only 20-30 minutes of "contiguous time" to upgrade and decided to postpone the upgrade until a bit later when I would have more time, because otherwise I wouldn't have been available to unlock my wallet after re-indexing.
Please vote for witness wackou! More info at http://digitalgaia.io

Offline clayop

  • Hero Member
  • *****
  • Posts: 2033
    • View Profile
    • Bitshares Korea
  • BitShares: clayop
Delegate participation rate is over 95% now. Beautiful update speed (considering re-indexing time)
Bitshares Korea - http://www.bitshares.kr
Vote for me and see Korean Bitshares community grows
delegate-clayop

Offline svk

For sure, I was the only one left on the v25 chain though, haha.

How are you likein your reliability now, eh? :p

 :'( :'(
Worker: dev.bitsharesblocks

Offline liondani

  • Hero Member
  • *****
  • Posts: 3737
  • Inch by inch, play by play
    • View Profile
    • My detailed info
  • BitShares: liondani
  • GitHub: liondani
delegate.liondani producing blocks again with client version v0.4.26
...seed node also updated  ;)

Offline Riverhead


Offline monsterer

For sure, I was the only one left on the v25 chain though, haha.

How are you likein your reliability now, eh? :p
My opinions do not represent those of metaexchange unless explicitly stated.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
v0.4.26 has been released with a checkpoint to address the blockchain fork: https://bitsharestalk.org/index.php?topic=7067.msg161432#msg161432

Delegates and seed nodes should upgrade ASAP.

Really? The third update in 24 hours?
yhea .. woke up 6 hours ago .. compiling three versions every since :)
0.4.25 has a fork flaw :)