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.


Messages - HackFisher

Pages: 1 ... 8 9 10 11 12 13 14 [15] 16 17 18 19 20 21 22 ... 59
211
Technical Support / Re: Bitshares X 0.4.5 available
« on: August 22, 2014, 01:31:26 am »
RPC Server Error: In method 'wallet_transfer': AES error (18)

I also have transactions that have been pending forever?

Try rescan, It may indicates that the wallet is in a dirty state that miss the cached key for your balance.

Did you have crash issues before?

212
my delegate just crashed and missed a block.
Code: [Select]
(gdb) bt
#0  get_tail (next=<synthetic pointer>, h=0x907676b313d3a84b) at /home/user/bitsharesx/libraries/fc/src/thread/mutex.cpp:33
#1  fc::mutex::unlock (this=this@entry=0x302fe4c) at /home/user/bitsharesx/libraries/fc/src/thread/mutex.cpp:160
#2  0x00000000007b5226 in ~scoped_lock (this=<synthetic pointer>, __in_chrg=<optimized out>) at /home/user/bitsharesx/libraries/fc/include/fc/thread/scoped_lock.hpp:8
#3  bts::net::detail::message_oriented_connection_impl::send_message (this=0x83b8f563388ca909, message_to_send=...) at /home/user/bitsharesx/libraries/net/message_oriented_connection.cpp:195
#4  0x00000000007b5928 in bts::net::message_oriented_connection::send_message (this=this@entry=0x10f8ef98, message_to_send=...)
    at /home/user/bitsharesx/libraries/net/message_oriented_connection.cpp:267
#5  0x00000000007ab220 in bts::net::peer_connection::send_queued_messages_task (this=0x10f8ef30) at /home/user/bitsharesx/libraries/net/peer_connection.cpp:178
#6  0x00000000007ab91c in operator() (__closure=<optimized out>) at /home/user/bitsharesx/libraries/net/peer_connection.cpp:222
#7  fc::detail::void_functor_run<bts::net::peer_connection::send_message(const bts::net::message&)::__lambda2>::run(void *, void *) (functor=<optimized out>, prom=0xed599f0)
    at /home/user/bitsharesx/libraries/fc/include/fc/thread/task.hpp:56
#8  0x000000000066c483 in fc::task_base::run_impl (this=this@entry=0xed59a00) at /home/user/bitsharesx/libraries/fc/src/thread/task.cpp:42
#9  0x000000000066cb35 in fc::task_base::run (this=this@entry=0xed59a00) at /home/user/bitsharesx/libraries/fc/src/thread/task.cpp:31
#10 0x000000000066acbb in run_next_task (this=0x184f350) at /home/user/bitsharesx/libraries/fc/src/thread/thread_d.hpp:379
#11 fc::thread_d::process_tasks (this=this@entry=0x184f350) at /home/user/bitsharesx/libraries/fc/src/thread/thread_d.hpp:402
#12 0x000000000066af06 in fc::thread_d::start_process_tasks (my=25490256) at /home/user/bitsharesx/libraries/fc/src/thread/thread_d.hpp:359
#13 0x0000000000d4a85e in make_fcontext ()
#14 0x000000000184f350 in ?? ()
#15 0x0000000000000000 in ?? ()
(gdb)

Did you try
Code: [Select]
git submodule update ?

Code: [Select]
(wallet closed) >>> about
{
  "bitshares_toolkit_revision": "ceffdd1b52300daf00f05e5c15d1723fd881d4df",
  "bitshares_toolkit_revision_age": "5 hours ago",
  "fc_revision": "9e75d47ba39e31e031da64e32b866903e066ecd1",
  "fc_revision_age": "7 hours ago",
  "compile_date": "compiled on Aug 21 2014 at 18:58:18"

after restart of client.  is there a newer fc?

yes, there is a change to fc, fc need to be updated.
do I need to rebuild the client or just git submodule update?

Yes, you need to rebuild after git submodule update

213
my delegate just crashed and missed a block.
Code: [Select]
(gdb) bt
#0  get_tail (next=<synthetic pointer>, h=0x907676b313d3a84b) at /home/user/bitsharesx/libraries/fc/src/thread/mutex.cpp:33
#1  fc::mutex::unlock (this=this@entry=0x302fe4c) at /home/user/bitsharesx/libraries/fc/src/thread/mutex.cpp:160
#2  0x00000000007b5226 in ~scoped_lock (this=<synthetic pointer>, __in_chrg=<optimized out>) at /home/user/bitsharesx/libraries/fc/include/fc/thread/scoped_lock.hpp:8
#3  bts::net::detail::message_oriented_connection_impl::send_message (this=0x83b8f563388ca909, message_to_send=...) at /home/user/bitsharesx/libraries/net/message_oriented_connection.cpp:195
#4  0x00000000007b5928 in bts::net::message_oriented_connection::send_message (this=this@entry=0x10f8ef98, message_to_send=...)
    at /home/user/bitsharesx/libraries/net/message_oriented_connection.cpp:267
#5  0x00000000007ab220 in bts::net::peer_connection::send_queued_messages_task (this=0x10f8ef30) at /home/user/bitsharesx/libraries/net/peer_connection.cpp:178
#6  0x00000000007ab91c in operator() (__closure=<optimized out>) at /home/user/bitsharesx/libraries/net/peer_connection.cpp:222
#7  fc::detail::void_functor_run<bts::net::peer_connection::send_message(const bts::net::message&)::__lambda2>::run(void *, void *) (functor=<optimized out>, prom=0xed599f0)
    at /home/user/bitsharesx/libraries/fc/include/fc/thread/task.hpp:56
#8  0x000000000066c483 in fc::task_base::run_impl (this=this@entry=0xed59a00) at /home/user/bitsharesx/libraries/fc/src/thread/task.cpp:42
#9  0x000000000066cb35 in fc::task_base::run (this=this@entry=0xed59a00) at /home/user/bitsharesx/libraries/fc/src/thread/task.cpp:31
#10 0x000000000066acbb in run_next_task (this=0x184f350) at /home/user/bitsharesx/libraries/fc/src/thread/thread_d.hpp:379
#11 fc::thread_d::process_tasks (this=this@entry=0x184f350) at /home/user/bitsharesx/libraries/fc/src/thread/thread_d.hpp:402
#12 0x000000000066af06 in fc::thread_d::start_process_tasks (my=25490256) at /home/user/bitsharesx/libraries/fc/src/thread/thread_d.hpp:359
#13 0x0000000000d4a85e in make_fcontext ()
#14 0x000000000184f350 in ?? ()
#15 0x0000000000000000 in ?? ()
(gdb)

Did you try
Code: [Select]
git submodule update ?

Code: [Select]
(wallet closed) >>> about
{
  "bitshares_toolkit_revision": "ceffdd1b52300daf00f05e5c15d1723fd881d4df",
  "bitshares_toolkit_revision_age": "5 hours ago",
  "fc_revision": "9e75d47ba39e31e031da64e32b866903e066ecd1",
  "fc_revision_age": "7 hours ago",
  "compile_date": "compiled on Aug 21 2014 at 18:58:18"

after restart of client.  is there a newer fc?

yes, there is a change to fc, fc need to be updated.

214
Stakeholder Proposals / Re: Delegate: technical question
« on: August 22, 2014, 01:22:54 am »
You need to build the code from https://github.com/dacsunlimited/bitsharesx

The delegate node will automatic connect to the network.

There is a document about more info
https://github.com/BitShares/bitshares_toolkit/wiki/DPOS-Registering-Names-And-Delegates

215
my delegate just crashed and missed a block.
Code: [Select]
(gdb) bt
#0  get_tail (next=<synthetic pointer>, h=0x907676b313d3a84b) at /home/user/bitsharesx/libraries/fc/src/thread/mutex.cpp:33
#1  fc::mutex::unlock (this=this@entry=0x302fe4c) at /home/user/bitsharesx/libraries/fc/src/thread/mutex.cpp:160
#2  0x00000000007b5226 in ~scoped_lock (this=<synthetic pointer>, __in_chrg=<optimized out>) at /home/user/bitsharesx/libraries/fc/include/fc/thread/scoped_lock.hpp:8
#3  bts::net::detail::message_oriented_connection_impl::send_message (this=0x83b8f563388ca909, message_to_send=...) at /home/user/bitsharesx/libraries/net/message_oriented_connection.cpp:195
#4  0x00000000007b5928 in bts::net::message_oriented_connection::send_message (this=this@entry=0x10f8ef98, message_to_send=...)
    at /home/user/bitsharesx/libraries/net/message_oriented_connection.cpp:267
#5  0x00000000007ab220 in bts::net::peer_connection::send_queued_messages_task (this=0x10f8ef30) at /home/user/bitsharesx/libraries/net/peer_connection.cpp:178
#6  0x00000000007ab91c in operator() (__closure=<optimized out>) at /home/user/bitsharesx/libraries/net/peer_connection.cpp:222
#7  fc::detail::void_functor_run<bts::net::peer_connection::send_message(const bts::net::message&)::__lambda2>::run(void *, void *) (functor=<optimized out>, prom=0xed599f0)
    at /home/user/bitsharesx/libraries/fc/include/fc/thread/task.hpp:56
#8  0x000000000066c483 in fc::task_base::run_impl (this=this@entry=0xed59a00) at /home/user/bitsharesx/libraries/fc/src/thread/task.cpp:42
#9  0x000000000066cb35 in fc::task_base::run (this=this@entry=0xed59a00) at /home/user/bitsharesx/libraries/fc/src/thread/task.cpp:31
#10 0x000000000066acbb in run_next_task (this=0x184f350) at /home/user/bitsharesx/libraries/fc/src/thread/thread_d.hpp:379
#11 fc::thread_d::process_tasks (this=this@entry=0x184f350) at /home/user/bitsharesx/libraries/fc/src/thread/thread_d.hpp:402
#12 0x000000000066af06 in fc::thread_d::start_process_tasks (my=25490256) at /home/user/bitsharesx/libraries/fc/src/thread/thread_d.hpp:359
#13 0x0000000000d4a85e in make_fcontext ()
#14 0x000000000184f350 in ?? ()
#15 0x0000000000000000 in ?? ()
(gdb)

Did you try
Code: [Select]
git submodule update ?

216
中文 (Chinese) / Re: 4.4版本钱包升级要点
« on: August 22, 2014, 01:15:22 am »
0.4.5版本已出

217
中文 (Chinese) / Re: 4.4版本钱包升级要点
« on: August 22, 2014, 01:14:41 am »
多谢LZ分享,此次升级为硬分叉,确实不能直接覆盖之前的钱包,需要重新下载区块链

重新下载区块链是可以的,但是如果不是bug应该也可以直接覆盖
硬分叉没有关系,应为Delegate的price feed没有publish,market engine还没有启动。

218
Technical Support / Re: Bitshares X 0.4.5 available
« on: August 22, 2014, 12:43:52 am »
does version 0.4.5 crash in windows?  it crashed twice when syncing.

About the crash, you mean 0.4.5 or previous version?

219
General Discussion / Re: Congrats on #3!
« on: August 21, 2014, 08:18:07 pm »
 +5%  :)

220
General Discussion / Re: alt appreciation thread
« on: August 21, 2014, 04:06:40 pm »
 :o LOL

222
General Discussion / Re: Who here wants to BUY BitUSD and at what price?
« on: August 20, 2014, 09:45:12 pm »
At the very beginning, I'll buy/sell BitUSD when it is profitable to exchange on BitShares X for BTSX or other exchanges. We need daytraders like this to make this pegging more fluid maybe.

223
A lot of Windows 7 users have this error when opening the new wallet, although it can be resolved by downloading the missing dll manually:



The address to download the missing dll file:
http://62.141.41.81/releases/0029c/

Then put it in the directory of BTSX.

This will be fixed in next version, users who have this issue can also download from this, and place it under the install path:

https://github.com/dacsunlimited/bitsharesx/raw/master/CrashRpt/bin/CrashRpt1402.dll

224
My understanding is that, BitShares Play is only part of the decentralized game assets ecosystem, It is not enough to achieve the goal only with a DAC.

To have the agents and merchants interested and join, we need to have a lot of games in our platform, in the same time, game providers have interested in BitShares Play game platform, because:

1. BitShares Play provide a good economic chips system to protect the user's game chips(assets) from being dilute. Because in BitShares Play, the platform must find way to guarantee that the new created chips must be created by providing play shares as collaterals, or according the mechanism as a game contract hardcoded in BitShares Play. It seems that games in BitShares Play should not be given the ability to issue chips as they want (As Benevolent Entity). Though I want to provide games with the flexibility, but maybe it should not be considered if it hurt the users' chips assets and thus the ecosystem.

There might be challenges for us to find ways to keep the assets rule in BitShares Play, but hopefully we will find ways, at least for a subset of the game kinds.

2. Another reason game providers would have interest in BitShares Play, is that we have agents and users base here. From another aspect, this system have agents because of the games already being there in some sense too. So the question is chicken and eggs, which will come out first?
The answer for this is that BitShares Play will first have chance games like Dice and Lottery being part of the DAC as a start for games. This will make BitShares Play looks like a gaming DAC at first glance, but with things growing, it's final goal is to be a game asset Platform, and those built-in games will retrograde just as third-party games.

225
Follow My Vote / Re: let it be beneficial to vote for the right one
« on: August 18, 2014, 06:32:09 pm »
What's the meaning of this? Adding the complexity of system I think.

It's a possible solution regarding voter apathy. (people being too lazy to vote and vote well.)

Yes, possible, but I think it only work for those who interested in luck chance, not exactly the people who are lazy to vote.
The cost is system payout and complexity but does not resolve it completely.

Pages: 1 ... 8 9 10 11 12 13 14 [15] 16 17 18 19 20 21 22 ... 59