106
General Discussion / Re: segfault in 0.4.19
« on: October 02, 2014, 09:20:13 am »
0.4.19 is not safe to run. It keeps crashing. I am switching back to 0.4.18
Show Posts
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.
107
General Discussion / Re: segfault in 0.4.19
« on: October 02, 2014, 07:29:49 am »
my node just crashed on 0.4.19
Code: [Select]
>>>
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff87fff700 (LWP 4915)]
std::_Hashtable<bts::net::item_id, bts::net::item_id, std::allocator<bts::net::item_id>, std::__detail::_Identity, std::equal_to<bts::net::item_id>, std::hash<bts::net::item_id>, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits<true, true, true> >::find (
this=this@entry=0x45944, __k=...) at /usr/include/c++/4.8/bits/hashtable.h:1024
1024 std::size_t __n = _M_bucket_index(__k, __code);
(gdb) bt
#0 std::_Hashtable<bts::net::item_id, bts::net::item_id, std::allocator<bts::net::item_id>, std::__detail::_Identity, std::equal_to<bts::net::item_id>, std::hash<bts::net::item_id>, std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits<true, true, true> >::find (
this=this@entry=0x45944, __k=...) at /usr/include/c++/4.8/bits/hashtable.h:1024
#1 0x0000000000a4ede5 in find (__x=..., this=0x45944) at /usr/include/c++/4.8/bits/unordered_set.h:517
#2 bts::net::detail::node_impl::process_block_during_normal_operation (this=this@entry=0x5a7c2920, originating_peer=originating_peer@entry=0x7fff659dd210,
block_message_to_process=..., message_hash=...) at /root/bitsharesx/libraries/net/node.cpp:2828
#3 0x0000000000a5068b in bts::net::detail::node_impl::process_block_message (this=this@entry=0x5a7c2920, originating_peer=originating_peer@entry=0x7fff659dd210,
message_to_process=..., message_hash=...) at /root/bitsharesx/libraries/net/node.cpp:2880
#4 0x0000000000a51d03 in bts::net::detail::node_impl::on_message (this=0x5a7c2920, originating_peer=0x7fff659dd210, received_message=...)
at /root/bitsharesx/libraries/net/node.cpp:1598
#5 0x0000000000ac034a in bts::net::detail::message_oriented_connection_impl::read_loop (this=0x7fff65a19490) at /root/bitsharesx/libraries/net/message_oriented_connection.cpp:157
#6 0x0000000000ac271c in operator() (__closure=<optimized out>) at /root/bitsharesx/libraries/net/message_oriented_connection.cpp:100
#7 fc::detail::void_functor_run<bts::net::detail::message_oriented_connection_impl::accept()::__lambda0>::run(void *, void *) (functor=<optimized out>, prom=0x7fff65ab2120)
at /root/bitsharesx/libraries/fc/include/fc/thread/task.hpp:83
#8 0x00000000006bf323 in fc::task_base::run_impl (this=this@entry=0x7fff65ab2130) at /root/bitsharesx/libraries/fc/src/thread/task.cpp:43
#9 0x00000000006bf9d5 in fc::task_base::run (this=this@entry=0x7fff65ab2130) at /root/bitsharesx/libraries/fc/src/thread/task.cpp:32
#10 0x00000000006bd95b in run_next_task (this=0x7fff7c0008c0) at /root/bitsharesx/libraries/fc/src/thread/thread_d.hpp:415
#11 fc::thread_d::process_tasks (this=this@entry=0x7fff7c0008c0) at /root/bitsharesx/libraries/fc/src/thread/thread_d.hpp:439
#12 0x00000000006bdbe6 in fc::thread_d::start_process_tasks (my=140735273765056) at /root/bitsharesx/libraries/fc/src/thread/thread_d.hpp:395
#13 0x0000000000f4628e in make_fcontext ()
#14 0x00007fff7c0008c0 in ?? ()
#15 0x00007fff7c068be0 in ?? ()
#16 0x0000000000000000 in ?? ()
108
General Discussion / 0.4.19 issues
« on: October 02, 2014, 06:45:31 am »Still can't place short orders, even after upgrade to 0.4.19
Getting error: unknown asset symbol (35008)
109
General Discussion / Re: 0.4.19-RC1 issues
« on: October 01, 2014, 10:35:24 pm »
Getting more errors after latest git pull..
Code: [Select]
default (unlocked) >>> get_info
6 key_not_found_exception: Key Not Found
{"key":6}
th_a cached_level_map.hpp:68 fetch
{"key":6}
th_a cached_level_map.hpp:69 fetch
{"property_id":"confirmation_requirement"}
th_a chain_database.cpp:2149 get_property
{}
th_a common_api_client.cpp:2259 get_info
{"command":"get_info"}
th_a cli.cpp:556 execute_command
Code: [Select]
default (unlocked) >>> about
{
"blockchain_name": "BitShares X",
"blockchain_description": "Decentralized Autonomous Exchange",
"client_version": "v0.4.19-RC1-20-gc844ba8",
"bitshares_toolkit_revision": "c844ba8b02fb9952e32b0e2cb2378b2180cf1703",
"bitshares_toolkit_revision_age": "26 minutes ago",
"fc_revision": "c4e814d7ded6099dc4297aa843d4be7afa98b3ed",
"fc_revision_age": "32 hours ago",
"compile_date": "compiled on Oct 1 2014 at 15:22:28",
"boost_version": "1.55",
"openssl_version": "OpenSSL 1.0.1f 6 Jan 2014",
"build": "linux 64-bit"
}
Code: [Select]
default (unlocked) >>> debug_list_errors
10 assert_exception: Assert Exception
is_open(): Database is not open!
{}
th_a level_map.hpp:152 begin
error seeking to first
{}
th_a level_map.hpp:171 begin
{}
th_a common_api_client.cpp:2819 debug_list_errors
{"command":"debug_list_errors"}
th_a cli.cpp:556 execute_command
110
General Discussion / Re: Proposal: Add ability to publish IP to registered accounts
« on: October 01, 2014, 09:16:22 pm »
I would like to be able to offer service(s) from a website authenticated with my delegate account. One way this can be done is to build such ability into BitShares X client, as I proposed earlier.
If someone opens page
/#/accounts/<account>
Currently one can see date of account registration and recent transactions. Some extra info about delegates.
If my proposal is implemented users would be able to integrate external web-content inside their account pages authenticated with BitShares X.
We would have benefits of BitSharesX account reputation and web of trust features + extra services.
If someone opens page
/#/accounts/<account>
Currently one can see date of account registration and recent transactions. Some extra info about delegates.
If my proposal is implemented users would be able to integrate external web-content inside their account pages authenticated with BitShares X.
We would have benefits of BitSharesX account reputation and web of trust features + extra services.
112
General Discussion / Re: Dry Run 18 - Return of the Dry Runs $1000 BitUSD bounty
« on: October 01, 2014, 02:49:13 pm »
Transactions get stuck in pending.
Code: [Select]
>>> about
{
"blockchain_name": "BitShares XTS",
"blockchain_description": "BitShares X Test Network",
"client_version": "dryrun-18-16-ga44e378-testnet-32",
"bitshares_toolkit_revision": "a44e378203a0d55bbd80abf28200b3b83d8e7bfd",
"bitshares_toolkit_revision_age": "17 hours ago",
"fc_revision": "c4e814d7ded6099dc4297aa843d4be7afa98b3ed",
"fc_revision_age": "24 hours ago",
"compile_date": "compiled on Sep 30 2014 at 15:05:48",
"boost_version": "1.55",
"openssl_version": "OpenSSL 1.0.1f 6 Jan 2014",
"build": "linux 64-bit"
}
Code: [Select]
>>> wallet_account_transaction_history
TIMESTAMP BLOCK FROM TO AMOUNT MEMO BALANCE FEE ID
==============================================================================================================================================================================================
2014-09-30T00:00:00 0 GENESIS tester 499,934.79111 XTS claim 1HddTkBSaxVnRL2XPpgFMVChj8BSWWC5mN 499,934.79111 XTS 0.00000 XTS [c35487]
2014-10-01T14:22:24 PENDING tester tester 0.00000 XTS register tester as a delegate N/A 0.75755 XTS 0206e8f0
2014-10-01T14:25:51 PENDING tester ASK-f50b8581 30.32150 XTS sell XTS @ 0.03297989875171083 USD / XTS N/A 0.50000 XTS 5883bf57
113
Русский (Russian) / Re: От Мастера Байтов: BitUSD на данный момент приносит 1.5 % годового дохода
« on: October 01, 2014, 11:31:38 am »где можно посмотреть изменение курса bitUSD/BTSX. Хотелось бы увидеть график с момента начала торгов
http://www.bitsharesblocks.com/assets/asset?id=USD
114
Русский (Russian) / От Мастера Байтов: BitUSD на данный момент приносит 1.5 % годового дохода
« on: October 01, 2014, 08:45:19 am »
https://bitsharestalk.org/index.php?topic=9523.0;topicseen
Основываясь на количестве предложения BitUSD и размере резервного фонда, BitUSD платит в среднем 1,5% годовых, * ЕСЛИ БЫ* никаких новых сделок заключено не было, и все BitUSD лежали на счету в течении года.
Очевидно, что некоторые из этих BitUSD связаны в рыночных заказах, некоторые продадутся до того как может накопиться доходность, и некоторые доходы заберут прежде чем они полностью созреют оставляя больше дохода другим, и скорее всего, обеспечит больше сборов до конца года ... . * так что* если предложение BitUSD останется постоянным, вы можете ожидать более 1,5% годовых.
Если предложение BitUSD будет расти то это означает, что привязка работает и рынок работает и вам не нужно сильно беспокоиться о привязке.
(прим от bitcoinerS: автор имел ввиду ценовую привязку USD/BitUSD = 1)
Основываясь на количестве предложения BitUSD и размере резервного фонда, BitUSD платит в среднем 1,5% годовых, * ЕСЛИ БЫ* никаких новых сделок заключено не было, и все BitUSD лежали на счету в течении года.
Очевидно, что некоторые из этих BitUSD связаны в рыночных заказах, некоторые продадутся до того как может накопиться доходность, и некоторые доходы заберут прежде чем они полностью созреют оставляя больше дохода другим, и скорее всего, обеспечит больше сборов до конца года ... . * так что* если предложение BitUSD останется постоянным, вы можете ожидать более 1,5% годовых.
Если предложение BitUSD будет расти то это означает, что привязка работает и рынок работает и вам не нужно сильно беспокоиться о привязке.
(прим от bitcoinerS: автор имел ввиду ценовую привязку USD/BitUSD = 1)
115
General Discussion / 0.4.19-RC1 issues
« on: October 01, 2014, 05:39:51 am »
Having troubles placing a short order. Getting error:
116
General Discussion / Re: BIPs as a BitAsset
« on: September 30, 2014, 11:01:48 pm »@Frodo
You look like my evil twin
117
General Discussion / Re: Feature request: Automatic Crypto-coin <=> BitAsset gateway
« on: September 30, 2014, 10:11:02 pm »There is a thread already discussing this .. search for "huge market" and author: xeroc
I believe seeing something similar discussed earlier, just can't find that post. Also, this proposal is for BitShares X to act as automatic-gateway vs other proposal, if I am correct, talked about 3rd party doing it.
118
General Discussion / Re: Feature request: Automatic Crypto-coin <=> BitAsset gateway
« on: September 30, 2014, 10:07:57 pm »Wouldn't you need to be tightly integrated with an exchange on the backend to offer this? You'd need to find someone willing to trade BTC for bitBTC.
I'm pretty sure this would require at least an escrow/trusted 3rd party, because you're talking about trading across different blockchains.
BitBTC should be
BitShares X would need to be able to act as Bitcoin client to receive/store/payout BTC on request.
119
General Discussion / Re: Proposal: Add ability to publish IP to registered accounts
« on: September 30, 2014, 09:51:06 pm »You can authenticate to a BTSX name already (login feature). You're just asking to have URL lookup + auth as one step. This sort of stuff is the purpose of KeyID+DNS though. I don't want to give people even more of a reason to complain about names being non-transferrable.
haha
I've been complaining about names being non-transferable for a while..
I believe sooner or later they will have to become transferable.
120
General Discussion / Re: Block Explorer and Delegates Listing
« on: September 30, 2014, 09:48:35 pm »there are no downvotes, only net votes, the negative ones you're seeing are simply votes for someone being removed cause they were unapproved.
My understanding is a delegate can lose votes in two cases:
1. Due to shares voting for that delegate being transferred to a different account with different voting preferences or to a market order.
2. Due to account owner un-approving that delegate.
First is unintentional and second is intentional. Distinguishing between them would be useful.
