Dry Run 2: The Real Deal

[JoeyD]

Oops, sorry about forgetting to update the submodules.

Still can't manage to compile a working binary outside of ubuntu however, I'm now stuck on a linking error with an undefined reference to 'main' with bitshares_client_tests and deterministic_signature_test.

Any steps I could take to figure out what's going wrong there?

[bitcoinerS]

list_errors?

Unfortunately my terminal screen gets cut off

Code: [Select]

"line": 818,
            "method": "",
            "hostname": "",
            "thread_name": "th_a",
            "timestamp": "20140616T033824.967829"
          },
          "format": "I am disconnecting peer 107.170.170.214:39219 for reason: You offered us a block that we reject as invalid",
          "data": {}
        }
      ]
    }
  ],[
    "20140616T033824.971040",{
      "code": 0,
      "name": "exception",
      "message": "unspecified",
      "stack": [{
          "context": {
            "level": "error",
            "file": "client.cpp",
            "line": 818,
            "method": "",
            "hostname": "",
            "thread_name": "th_a",
            "timestamp": "20140616T033824.971038"
          },
          "format": "I am disconnecting peer 128.199.180.112:58344 for reason: You offered us a block that we reject as invalid",
          "data": {}
        }
      ]
    }
  ],[
    "20140616T033824.972200",{
      "code": 0,
      "name": "exception",
      "message": "unspecified",
      "stack": [{
          "context": {
            "level": "error",
            "file": "client.cpp",
            "line": 818,
            "method": "",
            "hostname": "",
            "thread_name": "th_a",
            "timestamp": "20140616T033824.972198"
          },
          "format": "I am disconnecting peer 107.170.30.182:8764 for reason: You offered us a block that we reject as invalid",
          "data": {}
        }
      ]
    }
  ],[
    "20140616T173520.297257",{
      "code": 0,
      "name": "exception",
      "message": "unspecified",
      "stack": [{
          "context": {
            "level": "error",
            "file": "node.cpp",
            "line": 2046,
            "method": "",
            "hostname": "",
            "thread_name": "th_a",
            "timestamp": "20140616T173839.826219"
          },
          "format": "You sent me a sync block that I didn't ask for, block_id: ${block_id}",
          "data": {
            "block_id": "b6bab87fac3fec2519020c0202c58abbdd2acdb4"
          }
        }
      ]
    }
  ]
]


[toast]

Second issue is known.

Regarding keyhotee, I just wouldn't worry about it - the whole thing is really screwy and we need to figure out what we're doing about that

[Xeldal]

Something stange.

I generated a list of 162 different brainkey combinations and pasted the whole thing into the client.

something like the following:

Code: [Select]

wallet_import_keyhotee John Middle Lastname "My secret brainkey challenge." EasyBTC
wallet_import_keyhotee John Middle Lastname "My secret 1brainkey challenge." EasyBTC
wallet_import_keyhotee John Middle Lastname "My secret 2brainkey challenge." EasyBTC
wallet_import_keyhotee John Middle Lastname "My secret 3brainkey challenge." EasyBTC
wallet_import_keyhotee John Middle Lastname "My secret 4brainkey challenge." EasyBTC
... etc.

When it was done i got this

xeldal-w (unlocked) >>> wallet_list_receive_accounts
--- there are now 12 active connections to the p2p network
NAME (* delegate)                  KEY                                                             REGISTERED            TRUST LEVEL
xeldal-del                         XTS8YWXDVj8qGtyJvNYGXENqgVZEnrvFY7nUfegi1VrSyZCtgp5dD           2014-06-16T02:00:30   0
easybtcchallenge.                  XTS8WoPWWvktGEcHXBiSonjkupzBcv69ruQzWeiebcLVFQSgMM1Yf           NO                    0
init-delegate-45 *                 XTS5ttrjXKJPiWYm6EL7LAYRWV4GWnAaBPjGvkydy86yaKQdxTcHg           2014-06-01T00:00:00   0
init-delegate-44 *                 XTS8QLeHvaYQqFRdTP46EZq4GVdvj65Fp9wbKBGhBx5kvDnNFTDtM           2014-06-01T00:00:00   0
init-delegate-43 *                 XTS6whTVdWVb4KFvBDfKeawRjWPa6rsG5etsMvmg1MuybWhpVTf2u           2014-06-01T00:00:00   0
init-delegate-42 *                 XTS5iNWht2kEmdWNDf6cRz6HiVEs2zk3X61GpQvrQT1wQf66xucit           2014-06-01T00:00:00   0

No idea where that came from.  I certainly didn't create it.
At first I thought maybe I had found my Keyhotee Key and the name just got fuddled but unfortunately the key is different.

At any rate I'm sure its not supposed to do whatever it did.

[bytemaster]

Still no blocks produced by my delegate node.. It is stuck on

    "blocks_produced": 7,

Code: [Select]

>>> blockchain_get_account_record bitcoiners
{
  "id": 299,
  "name": "bitcoiners",
  "public_data": null,
  "owner_key": "XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk",
  "active_key_history": [[
      "20140613T030845",
      "XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk"
    ]
  ],
  "delegate_info": {
    "votes_for": 83109630849,
    "votes_against": 0,
    "blocks_produced": 7,
    "blocks_missed": 130,
    "pay_balance": 576553,
    "next_secret_hash": "a2d0bdf2ef998a9efb0821786b243d146c7a075b",
    "last_block_num_produced": 9758
  },
  "registration_date": "20140613T030845",
  "last_update": "20140613T031130",
  "meta_data": null
}



Code: [Select]

default (unlocked) >>> get_info
{
  "blockchain_head_block_num": 12387,
  "blockchain_head_block_time": "20140616T212245",
  "blockchain_head_block_time_rel": "2 seconds old",
  "blockchain_confirmation_requirement": 201,
  "blockchain_average_delegate_participation": 66.988950276243088,
  "network_num_connections": 10,


Code: [Select]

>>> about
{
  "bitshares_toolkit_revision": "cc3d866a984c0117932ed407a4183bab4e69cc10",
  "bitshares_toolkit_revision_age": "5 hours ago",
  "fc_revision": "689848432106a52c9c1656611727745ba8a5ac0d",
  "fc_revision_age": "5 hours ago",
  "compile_date": "compiled on Jun 16 2014 at 18:11:46"


list_errors?

[alt]

There are 5 pages of comments that I haven't caught up on, but I wanted to post an update on where we are:

1) Clock drift is causing some nodes to fail to validate blocks.  Apparently it can drift by as much as 5 seconds or more per day and we only do NTP sync on launch.   Blocks were failing because their time was 'in the future' and this would cause forks.

2) We found a bug where transactions on forks are not saved and thus we fail to switch to the fork.  This would exasperate #1

3) If your client is the one with the bad clock then you can get stuck because once block is 'failed' it will never retry.  This will leave you stuck until you re-sync.

We are preparing fixes for these issues now which should be relatively straight forward and should have it all resolved today.

woderfull

来自我的 HUAWEI P7-L00 上的 Tapatalk

[bitcoinerS]

Still no blocks produced by my delegate node.. It is stuck on

    "blocks_produced": 7,

Code: [Select]

>>> blockchain_get_account_record bitcoiners
{
  "id": 299,
  "name": "bitcoiners",
  "public_data": null,
  "owner_key": "XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk",
  "active_key_history": [[
      "20140613T030845",
      "XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk"
    ]
  ],
  "delegate_info": {
    "votes_for": 83109630849,
    "votes_against": 0,
    "blocks_produced": 7,
    "blocks_missed": 130,
    "pay_balance": 576553,
    "next_secret_hash": "a2d0bdf2ef998a9efb0821786b243d146c7a075b",
    "last_block_num_produced": 9758
  },
  "registration_date": "20140613T030845",
  "last_update": "20140613T031130",
  "meta_data": null
}



Code: [Select]

default (unlocked) >>> get_info
{
  "blockchain_head_block_num": 12387,
  "blockchain_head_block_time": "20140616T212245",
  "blockchain_head_block_time_rel": "2 seconds old",
  "blockchain_confirmation_requirement": 201,
  "blockchain_average_delegate_participation": 66.988950276243088,
  "network_num_connections": 10,


Code: [Select]

>>> about
{
  "bitshares_toolkit_revision": "cc3d866a984c0117932ed407a4183bab4e69cc10",
  "bitshares_toolkit_revision_age": "5 hours ago",
  "fc_revision": "689848432106a52c9c1656611727745ba8a5ac0d",
  "fc_revision_age": "5 hours ago",
  "compile_date": "compiled on Jun 16 2014 at 18:11:46"


[bytemaster]

Good news, we appear to have solved the hang on block 173 issue (stack overflow due to default stack size chosen by boost::context being too small).   

Those of you who are lucky enough to experience this particular bug can checkout the latest (be sure to do submodule update) and you should be able to get past block 173.

[bytemaster]

Has anyone managed to get the client to compile on a different linux distribution?

On both OpenSuse and Gentoo I get stuck in the same place,  apparently because of a problem in time.hpp/cpp. I've quoted the error message below. Any clues on how to get beyond this point would be appreciated, because I'm personally not a big fan of Ubuntu.

[ 95%] Building CXX object libraries/client/CMakeFiles/bts_client.dir/client.cpp.o
/home/joey/bitshares_toolkit/libraries/client/client.cpp: In member function 'virtual fc::variant_object bts::client::detail::client_impl::get_info() const':
/home/joey/bitshares_toolkit/libraries/client/client.cpp:1954:149: error: no matching function for call to 'get_approximate_relative_time_string(fc::time_point_sec, fc::time_point_sec, const char [5])'
       info["blockchain_head_block_time_rel"]             = fc::get_approximate_relative_time_string(_chain_db->now(), bts::blockchain::now(), " old");
                                                                                                                                                     ^
/home/joey/bitshares_toolkit/libraries/client/client.cpp:1954:149: note: candidates are:
In file included from /home/joey/bitshares_toolkit/libraries/fc/include/fc/log/logger.hpp:3:0,
                 from /home/joey/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp:6,
                 from /home/joey/bitshares_toolkit/libraries/blockchain/include/bts/blockchain/types.hpp:6,
                 from /home/joey/bitshares_toolkit/libraries/blockchain/include/bts/blockchain/chain_database.hpp:2,
                 from /home/joey/bitshares_toolkit/libraries/client/include/bts/client/client.hpp:2,
                 from /home/joey/bitshares_toolkit/libraries/client/client.cpp:1:
/home/joey/bitshares_toolkit/libraries/fc/include/fc/time.hpp:120:10: note: fc::string fc::get_approximate_relative_time_string(const fc::time_point_sec&)
   string get_approximate_relative_time_string(const time_point_sec& event_time);
          ^
/home/joey/bitshares_toolkit/libraries/fc/include/fc/time.hpp:120:10: note:   candidate expects 1 argument, 3 provided
/home/joey/bitshares_toolkit/libraries/fc/include/fc/time.hpp:121:10: note: fc::string fc::get_approximate_relative_time_string(const fc::time_point&)
   string get_approximate_relative_time_string(const time_point& event_time);
          ^
/home/joey/bitshares_toolkit/libraries/fc/include/fc/time.hpp:121:10: note:   candidate expects 1 argument, 3 provided
libraries/client/CMakeFiles/bts_client.dir/build.make:57: recipe for target 'libraries/client/CMakeFiles/bts_client.dir/client.cpp.o' failed
make[2]: *** [libraries/client/CMakeFiles/bts_client.dir/client.cpp.o] Error 1
CMakeFiles/Makefile2:685: recipe for target 'libraries/client/CMakeFiles/bts_client.dir/all' failed
make[1]: *** [libraries/client/CMakeFiles/bts_client.dir/all] Error 2
Makefile:116: recipe for target 'all' failed
make: *** [all] Error 2

git submodule update ... your fc branch is out of date.

[JoeyD]

Has anyone managed to get the client to compile on a different linux distribution?

On both OpenSuse and Gentoo I get stuck in the same place,  apparently because of a problem in time.hpp/cpp. I've quoted the error message below. Any clues on how to get beyond this point would be appreciated, because I'm personally not a big fan of Ubuntu.

[ 95%] Building CXX object libraries/client/CMakeFiles/bts_client.dir/client.cpp.o
/home/joey/bitshares_toolkit/libraries/client/client.cpp: In member function 'virtual fc::variant_object bts::client::detail::client_impl::get_info() const':
/home/joey/bitshares_toolkit/libraries/client/client.cpp:1954:149: error: no matching function for call to 'get_approximate_relative_time_string(fc::time_point_sec, fc::time_point_sec, const char [5])'
       info["blockchain_head_block_time_rel"]             = fc::get_approximate_relative_time_string(_chain_db->now(), bts::blockchain::now(), " old");
                                                                                                                                                     ^
/home/joey/bitshares_toolkit/libraries/client/client.cpp:1954:149: note: candidates are:
In file included from /home/joey/bitshares_toolkit/libraries/fc/include/fc/log/logger.hpp:3:0,
                 from /home/joey/bitshares_toolkit/libraries/fc/include/fc/exception/exception.hpp:6,
                 from /home/joey/bitshares_toolkit/libraries/blockchain/include/bts/blockchain/types.hpp:6,
                 from /home/joey/bitshares_toolkit/libraries/blockchain/include/bts/blockchain/chain_database.hpp:2,
                 from /home/joey/bitshares_toolkit/libraries/client/include/bts/client/client.hpp:2,
                 from /home/joey/bitshares_toolkit/libraries/client/client.cpp:1:
/home/joey/bitshares_toolkit/libraries/fc/include/fc/time.hpp:120:10: note: fc::string fc::get_approximate_relative_time_string(const fc::time_point_sec&)
   string get_approximate_relative_time_string(const time_point_sec& event_time);
          ^
/home/joey/bitshares_toolkit/libraries/fc/include/fc/time.hpp:120:10: note:   candidate expects 1 argument, 3 provided
/home/joey/bitshares_toolkit/libraries/fc/include/fc/time.hpp:121:10: note: fc::string fc::get_approximate_relative_time_string(const fc::time_point&)
   string get_approximate_relative_time_string(const time_point& event_time);
          ^
/home/joey/bitshares_toolkit/libraries/fc/include/fc/time.hpp:121:10: note:   candidate expects 1 argument, 3 provided
libraries/client/CMakeFiles/bts_client.dir/build.make:57: recipe for target 'libraries/client/CMakeFiles/bts_client.dir/client.cpp.o' failed
make[2]: *** [libraries/client/CMakeFiles/bts_client.dir/client.cpp.o] Error 1
CMakeFiles/Makefile2:685: recipe for target 'libraries/client/CMakeFiles/bts_client.dir/all' failed
make[1]: *** [libraries/client/CMakeFiles/bts_client.dir/all] Error 2
Makefile:116: recipe for target 'all' failed
make: *** [all] Error 2

[clout]

Are there any howto about running web wallet?

just follow the README.md on https://github.com/BitShares/web_wallet

[bitcoinerS]

Seems my delegate node is not producing blocks.. It has been showing

   "blocks_produced": 7,

for several hours

Code: [Select]

get_info
{
  "blockchain_head_block_num": 12019,
  "blockchain_head_block_time": "20140616T190730",
  "blockchain_head_block_time_rel": "2 seconds old",
  "blockchain_confirmation_requirement": 223,
  "blockchain_average_delegate_participation": 66.529492455418378,
  "network_num_connections": 11,
..
--- there are now 10 active connections to the p2p network
default (unlocked)


Code: [Select]

>>> blockchain_get_account_record bitcoiners
{
  "id": 299,
  "name": "bitcoiners",
  "public_data": null,
  "owner_key": "XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk",
  "active_key_history": [[
      "20140613T030845",
      "XTS8eoFWByxKtGYzBrNF4diAhv1zjY7jGNTUv6PSqVGbQs8yi7nqk"
    ]
  ],
  "delegate_info": {
    "votes_for": 83109630849,
    "votes_against": 0,
    "blocks_produced": 7,
    "blocks_missed": 125,
    "pay_balance": 576553,
    "next_secret_hash": "a2d0bdf2ef998a9efb0821786b243d146c7a075b",
    "last_block_num_produced": 9758
  },

[emski]

If you haven't updated recently then your client will not be able to switch to the correct fork when it tries without deleting the chain (unless there were no transactions during the fork).

We have fixed several significant issues today so I encourage everyone to update.

Why dont you create a separate thread where you state the recommended git revision(s).
This could avoid compile error(s) and will keep everyone on same version(s) (hopefully).

[Xeldal]

Is there an alternative way to check the brainkey on keyhotee ID. 

I'm convinced, of the 200 iterations of my brainkey at least one of them is correct but it has not imported into this wallet.

[bytemaster]

Whats wrong with current test networks in latest git build? It cannot sync after

Code: [Select]

{
  "blockchain_head_block_num": 10252,
  "blockchain_head_block_time": "20140616T161845",
  "blockchain_head_block_time_rel": "2 minutes old",
  "blockchain_confirmation_requirement": 291,
  "blockchain_average_delegate_participation": 28.429073856975382,

Seems we have 2 major forks =\

I am on the block 10256.

"blockchain_head_block_num": 11958,
  "blockchain_head_block_time": "20140616T184500",

If you haven't updated recently then your client will not be able to switch to the correct fork when it tries without deleting the chain (unless there were no transactions during the fork).

We have fixed several significant issues today so I encourage everyone to update.