406
Technical Support / Re: 12.04 compiling woes. PLEASE HELP!
« on: July 19, 2014, 11:04:01 pm »
I had no problems compiling on Ubuntu 14.04. How about upgrading first?
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
My local time on the forum is showing as 7 hours ahead actual local time. How do I correct it?
Click on Profile, when point "Modify Profile", select "Look and Layout", change "Time Offset" according your time zone.
>>> get_info
{
"blockchain_head_block_num": 3939,
"blockchain_head_block_age": "11 hours old",
default (unlocked) >>> quit
[Thread 0x7fffeeffd700 (LWP 8931) exited]
[Thread 0x7fffcbde4700 (LWP 8936) exited]
Program received signal SIGSEGV, Segmentation fault.
bts::blockchain::chain_database::get_head_block_id (this=0x17c15a8) at /home/bitcoiner/local/bitshares_toolkit/libraries/blockchain/chain_database.cpp:2230
2230 return my->_head_block_id;
(gdb) bt
#0 bts::blockchain::chain_database::get_head_block_id (this=0x17c15a8) at /home/bitcoiner/local/bitshares_toolkit/libraries/blockchain/chain_database.cpp:2230
#1 0x00000000005f5743 in bts::client::detail::client_impl::handle_message (this=0x1783680, message_to_handle=..., sync_mode=<optimized out>) at /home/bitcoiner/local/bitshares_toolkit/libraries/client/client.cpp:949
#2 0x00000000006e612f in operator() (__closure=<optimized out>) at /home/bitcoiner/local/bitshares_toolkit/libraries/net/node.cpp:3494
#3 fc::detail::functor_run<bts::net::detail::thread_switching_node_delegate_wrapper::handle_message(const bts::net::message&, bool)::__lambda44>::run(void *, void *) (functor=<optimized out>, prom=0x7fffd8126840)
at /home/bitcoiner/local/bitshares_toolkit/libraries/fc/include/fc/thread/task.hpp:48
#4 0x000000000064e873 in fc::task_base::run_impl (this=this@entry=0x7fffd8126790) at /home/bitcoiner/local/bitshares_toolkit/libraries/fc/src/thread/task.cpp:39
#5 0x000000000064ef25 in fc::task_base::run (this=this@entry=0x7fffd8126790) at /home/bitcoiner/local/bitshares_toolkit/libraries/fc/src/thread/task.cpp:29
#6 0x000000000064d0db in run_next_task (this=0x1784e60) at /home/bitcoiner/local/bitshares_toolkit/libraries/fc/src/thread/thread_d.hpp:372
#7 fc::thread_d::process_tasks (this=this@entry=0x1784e60) at /home/bitcoiner/local/bitshares_toolkit/libraries/fc/src/thread/thread_d.hpp:395
#8 0x000000000064d326 in fc::thread_d::start_process_tasks (my=24661600) at /home/bitcoiner/local/bitshares_toolkit/libraries/fc/src/thread/thread_d.hpp:352
#9 0x0000000000cba46e in make_fcontext ()
#10 0x0000000001784e60 in ?? ()
#11 0x0000000000000000 in ?? ()
Whats going on with the test now? Im getting stuck on a block again:Code: [Select]--- there are now 8 active connections to the p2p network
(wallet closed) >>> getinfo
{
"blockchain_head_block_num": 3939,
"blockchain_head_block_age": "5 hours old",
"blockchain_head_block_timestamp": "20140717T101150",
"blockchain_average_delegate_participation": 5.6456120737842372,
"blockchain_delegate_pay_rate": 10,
"blockchain_blocks_left_in_round": 101,
"blockchain_confirmation_requirement": 1,
"blockchain_accumulated_fees": "12.89899 XTS",
"blockchain_share_supply": 199999998692024,
"blockchain_random_seed": "b5a0d967911b6a1132a74039fefaa90c4618a60b",
"blockchain_database_version": 114,
"blockchain_version": 108,
"network_num_connections": 8,
"network_num_connections_max": 200,
"network_protocol_version": 104,
"ntp_time": "20140717T145220",
"ntp_error": -0.025156000000000001,
"wallet_open": false,
"wallet_unlocked": null,
"wallet_unlocked_until": null,
"wallet_unlocked_until_timestamp": null,
"wallet_block_production_enabled": null,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null,
"wallet_version": 100
}
So as far as I can tell there are no transactions being made in this chain at all. They are accepted and not pending but all blocks look empty from here.
Sent from my iPhone using Tapatalk
>>> wallet_account_transaction_history
RECEIVED BLOCK FROM TO AMOUNT FEE MEMO BALANCE ID
=========================================================================================================================================================================================
...
2014-07-17T01:20:11 912 bitcoiners bitcoiners 500.00000 XTS 0.10000 XTS 37,472.30684 XTS 8143a93
default (unlocked) >>> blockchain_get_transaction 8143a93
null
some funds for testing please, thanks
XTS5KdjNisUJ9bWD9UGowJy2Qa8feMES3XVLuVzQ5guFTxN6osKkb
>>> wallet_market_order_list USD XTS
TYPE QUANTITY PRICE BALANCE COST COLLATERAL ID
--------------------------------------------------------------------------------------------------------------------------------
cover_order 3.75037 XTS 0.01333201790756645 USD / XTS 0.0500 USD 0.0499 USD 5.00050 XTS XTS5u2Utwb2E7AiBcG1HmjvuxSMpKPzw9KNu
>>> wallet_market_cover bitcoiners 0.1 USD XTS5u2Utwb2E7AiBcG1HmjvuxSMpKPzw9KNu
>>> wallet_account_transaction_history
...
2014-07-15T23:39:25 1048 bitcoiners ORDER-5u2Utwb2 0.1000 USD 0.10000 XTS cover ORDER-5u2Utwb2 2cbd1f18
>>> wallet_market_order_list USD XTS
No market orders found.
By popular demand, the delegate fee calculation is clearly way more volatile than I intended so we are going to reset this dryrun before we get too far into it.
New calculations:Code: [Select]delegate_pay = total_accumulated_fees / (blocks_per_day*14)
delegate_registration = delegate_pay * blocks_per_hour * 2 / 101
The effect of this change is that delegate pay will rise much slower, and registration will have a much smaller impact on delegate pay. (14 days vs 2 hours).