Author Topic: 0.4.11 Release Candidate 2 Testing  (Read 13341 times)

0 Members and 1 Guest are viewing this topic.

drekrob

  • Guest
The transfer tab is still empty for me in 4.11
You should make it more clear for users, why there is overlap in the market.
It looks like the market is broken, and not everyone is reading up in here.

Offline bernard

  • Newbie
  • *
  • Posts: 17
    • View Profile
well with 0.4.11 I am actually able to open the GUI and fully sync, so its usable again which is good.

Only thing I noticed is the margin orders table is empty.

Offline tonyk

  • Hero Member
  • *****
  • Posts: 3308
    • View Profile
0.4.11 (with GUI) Running good so far.

Still getting this weird thing/bug ( present in the last 2-3 versions) - The first time ever to close the app. it freezes.
Lack of arbitrage is the problem, isn't it. And this 'should' solves it.

Offline dannotestein

  • Hero Member
  • *****
  • Posts: 760
    • View Profile
    • BlockTrades International
  • BitShares: btsnow
This segfault occurs when quitting the GUI (after it has been open for a while).

Code: [Select]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `./BitSharesX'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000000000aadcfa in boost::asio::detail::task_io_service::post_immediate_completion (this=0x18, op=op@entry=0x7ff070596450,
    is_continuation=is_continuation@entry=false) at /usr/include/boost/asio/detail/impl/task_io_service.ipp:264
264   if (one_thread_ || is_continuation)
(gdb) bt
#0  0x0000000000aadcfa in boost::asio::detail::task_io_service::post_immediate_completion (this=0x18, op=op@entry=0x7ff070596450,
    is_continuation=is_continuation@entry=false) at /usr/include/boost/asio/detail/impl/task_io_service.ipp:264
#1  0x0000000000aadf00 in boost::asio::detail::epoll_reactor::start_op (this=0x7ff070027380, op_type=op_type@entry=1, descriptor=155,
    descriptor_data=@0x7ff07048ff00: 0x7ff04c001250, op=0x7ff070596450, is_continuation=<optimized out>, allow_speculative=true)
    at /usr/include/boost/asio/detail/impl/epoll_reactor.ipp:253
#2  0x0000000000aaf268 in boost::asio::detail::reactive_socket_service_base::start_op (this=0x7ff07045d168, impl=..., op_type=1, op=<optimized out>,
    is_continuation=<optimized out>, is_non_blocking=<optimized out>, noop=false) at /usr/include/boost/asio/detail/impl/reactive_socket_service_base.ipp:214
#3  0x0000000000ab2256 in async_send<boost::asio::const_buffers_1, boost::_bi::bind_t<void, void (*)(fc::shared_ptr<fc::promise<unsigned long> > const&, boost::system::error_code const&, unsigned long), boost::_bi::list3<boost::_bi::value<fc::shared_ptr<fc::promise<unsigned long> > >, boost::arg<1>, boost::arg<2> > > > (handler=...,
    flags=0, buffers=..., impl=..., this=0x7ff07045d168) at /usr/include/boost/asio/detail/reactive_socket_service_base.hpp:216
#4  async_send<boost::asio::const_buffers_1, boost::_bi::bind_t<void, void (*)(fc::shared_ptr<fc::promise<unsigned long> > const&, boost::system::error_code const&, unsigned long), boost::_bi::list3<boost::_bi::value<fc::shared_ptr<fc::promise<unsigned long> > >, boost::arg<1>, boost::arg<2> > > > (
    handler=<unknown type in /redacted/bitsharesx/programs/qt_wallet/bin/BitSharesX, CU 0x30d2e56, DIE 0x31418e3>, flags=0, buffers=..., impl=...,
    this=0x7ff07045d140) at /usr/include/boost/asio/stream_socket_service.hpp:330
#5  async_write_some<boost::asio::const_buffers_1, boost::_bi::bind_t<void, void (*)(fc::shared_ptr<fc::promise<unsigned long> > const&, boost::system::error_code const&, unsigned long), boost::_bi::list3<boost::_bi::value<fc::shared_ptr<fc::promise<unsigned long> > >, boost::arg<1>, boost::arg<2> > > > (
    handler=<unknown type in /redacted/bitsharesx/programs/qt_wallet/bin/BitSharesX, CU 0x30d2e56, DIE 0x3115ea8>, buffers=..., this=0x7ff07048fef8)
    at /usr/include/boost/asio/basic_stream_socket.hpp:732
#6  fc::asio::write_some<boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> >, boost::asio::const_buffers_1>
    (s=..., buf=...) at /redacted/bitsharesx/libraries/fc/include/fc/asio.hpp:122
#7  0x0000000000db0399 in fc::detail::rate_limiting_group_impl::writesome (this=0x7ff070433770, socket=...,
    buffer=0x7ff049e6d7a0 "\337\362n\342\360\274\v\005\065\366LJ", length=16) at /redacted/bitsharesx/libraries/fc/src/network/rate_limiting.cpp:249
#8  0x0000000000a5ccc7 in fc::ostream::write (this=this@entry=0x7ff07048fed8, buf=buf@entry=0x7ff049e6d7a0 "\337\362n\342\360\274\v\005\065\366LJ", len=16)
    at /redacted/bitsharesx/libraries/fc/src/io/iostream.cpp:365
#9  0x0000000000be22ae in bts::net::stcp_socket::writesome (this=0x7ff07048fe80, buffer=0x7ff070001fb0 "\b", len=<optimized out>)
    at /redacted/bitsharesx/libraries/net/stcp_socket.cpp:93
#10 0x0000000000a5ccc7 in fc::ostream::write (this=this@entry=0x7ff07048fe80, buf=buf@entry=0x7ff070001fb0 "\b", len=len@entry=16)
    at /redacted/bitsharesx/libraries/fc/src/io/iostream.cpp:365
#11 0x0000000000bc30d0 in bts::net::detail::message_oriented_connection_impl::send_message (this=0x7ff07048fe70, message_to_send=...)
    at /redacted/bitsharesx/libraries/net/message_oriented_connection.cpp:251
#12 0x0000000000bc3bb8 in bts::net::message_oriented_connection::send_message (this=this@entry=0x7ff070465af8, message_to_send=...)
    at /redacted/bitsharesx/libraries/net/message_oriented_connection.cpp:328
#13 0x0000000000bbda96 in bts::net::peer_connection::send_queued_messages_task (this=0x7ff070465a90)
    at /redacted/bitsharesx/libraries/net/peer_connection.cpp:236
#14 0x0000000000bbf5dc in operator() (__closure=<optimized out>) at /redacted/bitsharesx/libraries/net/peer_connection.cpp:301
#15 fc::detail::void_functor_run<bts::net::peer_connection::send_message(const bts::net::message&)::<lambda()> >::run(void *, void *) (functor=<optimized out>,
    prom=0x7ff070466660) at /redacted/bitsharesx/libraries/fc/include/fc/thread/task.hpp:83
#16 0x0000000000a4e115 in fc::task_base::run_impl (this=0x7ff070466670) at /redacted/bitsharesx/libraries/fc/src/thread/task.cpp:43
#17 0x0000000000a4cbb3 in run_next_task (this=<optimized out>) at /redacted/bitsharesx/libraries/fc/src/thread/thread_d.hpp:398
#18 fc::thread_d::process_tasks (this=0x7ff0700008c0) at /redacted/bitsharesx/libraries/fc/src/thread/thread_d.hpp:422
#19 0x0000000000a4ce21 in fc::thread_d::start_process_tasks (my=140670647929024) at /redacted/bitsharesx/libraries/fc/src/thread/thread_d.hpp:378
#20 0x0000000000deedee in make_fcontext ()
#21 0x00007ff0700008c0 in ?? ()
#22 0x0000000000000000 in ?? ()
Please let me know if you can repeat this error in further runs. Also, before you shut down, can you check how many connections and how much memory you are using? Are you just operating with default settings, or have you increased node count or anything like that?
http://blocktrades.us Fast/Safe/High-Liquidity Crypto Coin Converter

Offline Empirical1.1

  • Hero Member
  • *****
  • Posts: 886
    • View Profile
2) Shorts can sell at up to 10% below the peg *if* there are offers to buy above the peg.  The difference is captured as fees, gives priority to shorts willing to pay the highest fee.

Is it possible and if so what do you think of the idea of - the accumulated fees that are captured from (2) being redistributed evenly as interest to BitAsset holders based on their current holdings.


Edit So while BTSX holders get the current daily burn.

(2) goes only to BitAsset holders somehow as daily interest.
(Display daily & current annualised rate on wallet opening. Considering shorting demand this interest rate will be considerable.)

Many crypto exchanges offer daily interest like bter. It shouldn't effect the peg but will maximise demand for BitAssets.

This + stable wallet = great wealth  8) 8) 8)





« Last Edit: September 03, 2014, 04:18:18 am by oasis »

Offline biophil

  • Hero Member
  • *****
  • Posts: 880
  • Professor of Computer Science
    • View Profile
    • My Academic Website
  • BitShares: biophil
Thanks tonyk and drltc for the explanations. I like it.

Sent from my SCH-S720C using Tapatalk 2

Support our research efforts to improve BitAsset price-pegging! Vote for worker 1.14.204 "201907-uccs-research-project."

Offline theoretical

Can someone give a quick back-of-the-envelope rationale for change number 2 (or point me to the discussion)? Does "the peg" mean the median price feed? So now we should expect a discontinuous market price: if we're right at the peg, as soon as someone places a bid a tiny bit above the peg, some short 10% below the peg matches him? Sounds like it could get very confusing for traders.

Confusing?  Everyone gets exactly what they asked for.  If you short Q quantity at P price, then you get a short position for Q units with 2*Q*P collateral if the order is totally filled.  If you enter a Bid for Q quantity at P' price, then you spend exactly Q*P' and get exactly Q units if the order is totally filled.

If P << P' (that is, top of Ask/Short book is much less than top of Bid book), then the system takes the difference.

As for the rationale -- basically there is so much demand to short the dollar, above and beyond the peg.  So much that they are willing to pay a premium, in the form of setting a short price below the peg and hoping BitUSD will sink even lower.  In the older version, the short-heavy Ask book was moving the price far away from the peg by pushing all the way down the Bid book which was much thinner (I think the sorts of people who are actively trading BTSX right now think BTSX is going to the moon and short dollars, trying to add leverage to their BTSX holdings).  In the new version 0.4.11, shorts are allowed to compete with each other for a limited Bid pool based on the premiums they are willing to pay, but the premium now goes to the network in the form of fees, instead of to BitUSD buyers in the form of really cheap BitUSD.
BTS- theoretical / PTS- PZxpdC8RqWsdU3pVJeobZY7JFKVPfNpy5z / BTC- 1NfGejohzoVGffAD1CnCRgo9vApjCU2viY / the delegate formerly known as drltc / Nothing said on these forums is intended to be legally binding / All opinions are my own unless otherwise noted / Take action due to my posts at your own risk

Offline tonyk

  • Hero Member
  • *****
  • Posts: 3308
    • View Profile
Can someone give a quick back-of-the-envelope rationale for change number 2 (or point me to the discussion)? Does "the peg" mean the median price feed? So now we should expect a discontinuous market price: if we're right at the peg, as soon as someone places a bid a tiny bit above the peg, some short 10% below the peg matches him? Sounds like it could get very confusing for traders.

Sent from my SCH-S720C using Tapatalk 2

Dear shorts,
you can now place your orders below the peg (up to 10% below), if you so desire. Such short orders will execute only if the bid is above the peg, thogh.
The change is justified by the simple principal - "The system does not mind getting more fees', if the free trading parties  wish to give those fees to us.
Lack of arbitrage is the problem, isn't it. And this 'should' solves it.

Offline ripplexiaoshan

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 2300
    • View Profile
  • BitShares: jademont
Can someone give a quick back-of-the-envelope rationale for change number 2 (or point me to the discussion)? Does "the peg" mean the median price feed? So now we should expect a discontinuous market price: if we're right at the peg, as soon as someone places a bid a tiny bit above the peg, some short 10% below the peg matches him? Sounds like it could get very confusing for traders.

Sent from my SCH-S720C using Tapatalk 2

I guess the "peg" means the median price published by delegates?
BTS committee member:jademont

Offline Riverhead

Chain/Node server updated and running without issue. Linux GUI is running fine and even made  few trades  :D . There is still that weird huge gap between the sections though so there is a lot of scrolling. Anyway, it's been running for a while now without issue.

Offline biophil

  • Hero Member
  • *****
  • Posts: 880
  • Professor of Computer Science
    • View Profile
    • My Academic Website
  • BitShares: biophil
Can someone give a quick back-of-the-envelope rationale for change number 2 (or point me to the discussion)? Does "the peg" mean the median price feed? So now we should expect a discontinuous market price: if we're right at the peg, as soon as someone places a bid a tiny bit above the peg, some short 10% below the peg matches him? Sounds like it could get very confusing for traders.

Sent from my SCH-S720C using Tapatalk 2

Support our research efforts to improve BitAsset price-pegging! Vote for worker 1.14.204 "201907-uccs-research-project."

Offline CLains

  • Hero Member
  • *****
  • Posts: 2606
    • View Profile
  • BitShares: clains
Thanks for all the hard work gang. :)

Offline ionx

  • Newbie
  • *
  • Posts: 19
    • View Profile
This segfault occurs when quitting the GUI (after it has been open for a while).

Code: [Select]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `./BitSharesX'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000000000aadcfa in boost::asio::detail::task_io_service::post_immediate_completion (this=0x18, op=op@entry=0x7ff070596450,
    is_continuation=is_continuation@entry=false) at /usr/include/boost/asio/detail/impl/task_io_service.ipp:264
264   if (one_thread_ || is_continuation)
(gdb) bt
#0  0x0000000000aadcfa in boost::asio::detail::task_io_service::post_immediate_completion (this=0x18, op=op@entry=0x7ff070596450,
    is_continuation=is_continuation@entry=false) at /usr/include/boost/asio/detail/impl/task_io_service.ipp:264
#1  0x0000000000aadf00 in boost::asio::detail::epoll_reactor::start_op (this=0x7ff070027380, op_type=op_type@entry=1, descriptor=155,
    descriptor_data=@0x7ff07048ff00: 0x7ff04c001250, op=0x7ff070596450, is_continuation=<optimized out>, allow_speculative=true)
    at /usr/include/boost/asio/detail/impl/epoll_reactor.ipp:253
#2  0x0000000000aaf268 in boost::asio::detail::reactive_socket_service_base::start_op (this=0x7ff07045d168, impl=..., op_type=1, op=<optimized out>,
    is_continuation=<optimized out>, is_non_blocking=<optimized out>, noop=false) at /usr/include/boost/asio/detail/impl/reactive_socket_service_base.ipp:214
#3  0x0000000000ab2256 in async_send<boost::asio::const_buffers_1, boost::_bi::bind_t<void, void (*)(fc::shared_ptr<fc::promise<unsigned long> > const&, boost::system::error_code const&, unsigned long), boost::_bi::list3<boost::_bi::value<fc::shared_ptr<fc::promise<unsigned long> > >, boost::arg<1>, boost::arg<2> > > > (handler=...,
    flags=0, buffers=..., impl=..., this=0x7ff07045d168) at /usr/include/boost/asio/detail/reactive_socket_service_base.hpp:216
#4  async_send<boost::asio::const_buffers_1, boost::_bi::bind_t<void, void (*)(fc::shared_ptr<fc::promise<unsigned long> > const&, boost::system::error_code const&, unsigned long), boost::_bi::list3<boost::_bi::value<fc::shared_ptr<fc::promise<unsigned long> > >, boost::arg<1>, boost::arg<2> > > > (
    handler=<unknown type in /redacted/bitsharesx/programs/qt_wallet/bin/BitSharesX, CU 0x30d2e56, DIE 0x31418e3>, flags=0, buffers=..., impl=...,
    this=0x7ff07045d140) at /usr/include/boost/asio/stream_socket_service.hpp:330
#5  async_write_some<boost::asio::const_buffers_1, boost::_bi::bind_t<void, void (*)(fc::shared_ptr<fc::promise<unsigned long> > const&, boost::system::error_code const&, unsigned long), boost::_bi::list3<boost::_bi::value<fc::shared_ptr<fc::promise<unsigned long> > >, boost::arg<1>, boost::arg<2> > > > (
    handler=<unknown type in /redacted/bitsharesx/programs/qt_wallet/bin/BitSharesX, CU 0x30d2e56, DIE 0x3115ea8>, buffers=..., this=0x7ff07048fef8)
    at /usr/include/boost/asio/basic_stream_socket.hpp:732
#6  fc::asio::write_some<boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::stream_socket_service<boost::asio::ip::tcp> >, boost::asio::const_buffers_1>
    (s=..., buf=...) at /redacted/bitsharesx/libraries/fc/include/fc/asio.hpp:122
#7  0x0000000000db0399 in fc::detail::rate_limiting_group_impl::writesome (this=0x7ff070433770, socket=...,
    buffer=0x7ff049e6d7a0 "\337\362n\342\360\274\v\005\065\366LJ", length=16) at /redacted/bitsharesx/libraries/fc/src/network/rate_limiting.cpp:249
#8  0x0000000000a5ccc7 in fc::ostream::write (this=this@entry=0x7ff07048fed8, buf=buf@entry=0x7ff049e6d7a0 "\337\362n\342\360\274\v\005\065\366LJ", len=16)
    at /redacted/bitsharesx/libraries/fc/src/io/iostream.cpp:365
#9  0x0000000000be22ae in bts::net::stcp_socket::writesome (this=0x7ff07048fe80, buffer=0x7ff070001fb0 "\b", len=<optimized out>)
    at /redacted/bitsharesx/libraries/net/stcp_socket.cpp:93
#10 0x0000000000a5ccc7 in fc::ostream::write (this=this@entry=0x7ff07048fe80, buf=buf@entry=0x7ff070001fb0 "\b", len=len@entry=16)
    at /redacted/bitsharesx/libraries/fc/src/io/iostream.cpp:365
#11 0x0000000000bc30d0 in bts::net::detail::message_oriented_connection_impl::send_message (this=0x7ff07048fe70, message_to_send=...)
    at /redacted/bitsharesx/libraries/net/message_oriented_connection.cpp:251
#12 0x0000000000bc3bb8 in bts::net::message_oriented_connection::send_message (this=this@entry=0x7ff070465af8, message_to_send=...)
    at /redacted/bitsharesx/libraries/net/message_oriented_connection.cpp:328
#13 0x0000000000bbda96 in bts::net::peer_connection::send_queued_messages_task (this=0x7ff070465a90)
    at /redacted/bitsharesx/libraries/net/peer_connection.cpp:236
#14 0x0000000000bbf5dc in operator() (__closure=<optimized out>) at /redacted/bitsharesx/libraries/net/peer_connection.cpp:301
#15 fc::detail::void_functor_run<bts::net::peer_connection::send_message(const bts::net::message&)::<lambda()> >::run(void *, void *) (functor=<optimized out>,
    prom=0x7ff070466660) at /redacted/bitsharesx/libraries/fc/include/fc/thread/task.hpp:83
#16 0x0000000000a4e115 in fc::task_base::run_impl (this=0x7ff070466670) at /redacted/bitsharesx/libraries/fc/src/thread/task.cpp:43
#17 0x0000000000a4cbb3 in run_next_task (this=<optimized out>) at /redacted/bitsharesx/libraries/fc/src/thread/thread_d.hpp:398
#18 fc::thread_d::process_tasks (this=0x7ff0700008c0) at /redacted/bitsharesx/libraries/fc/src/thread/thread_d.hpp:422
#19 0x0000000000a4ce21 in fc::thread_d::start_process_tasks (my=140670647929024) at /redacted/bitsharesx/libraries/fc/src/thread/thread_d.hpp:378
#20 0x0000000000deedee in make_fcontext ()
#21 0x00007ff0700008c0 in ?? ()
#22 0x0000000000000000 in ?? ()

Offline tonyk

  • Hero Member
  • *****
  • Posts: 3308
    • View Profile
0.4.11 release candidate has been posted to master at https://github.com/dacsunlimited/bitsharesx.git

Changes in this update:
2) Shorts can sell at up to 10% below the peg *if* there are offers to buy above the peg.  The difference is captured as fees, gives priority to shorts willing to pay the highest fee.

Are you trying to get 200 bitBTC as fee for the system with this.  :)

But they will be unbacked by almost any BTSX... :o

OK I see, 10 % sanity check.
« Last Edit: September 02, 2014, 11:37:00 pm by tonyk »
Lack of arbitrage is the problem, isn't it. And this 'should' solves it.

Offline emski

  • Hero Member
  • *****
  • Posts: 1282
    • View Profile
    • http://lnkd.in/nPbhxG
I've tested clean synchronization - no issues except it waits for almost 1 minute before it starts synchronizing.
I've updated the seed node to this version.
I'll delay updating the delegate.
It looks OK so far. It seems like it uses far less memory (or previous version leaks). I'll monitor that.