Author [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] Topic: 0.4.11 Release Candidate 2 Testing  (Read 2866 times)

0 Members and 1 Guest are viewing this topic.

Offline bytemaster

0.4.11 Release Candidate 2 Testing
« on: September 02, 2014, 09:55:50 PM »

0.4.11 release candidate has been posted to master at https://github.com/dacsunlimited/bitsharesx.git

https://github.com/dacsunlimited/bitsharesx/releases/tag/0.4.11-RC1


More market fixes so RC1 users still will have to upgrade:
https://github.com/dacsunlimited/bitsharesx/releases/tag/0.4.11-RC2

Changes in this update:
1) Major bugs fixes in the GUI
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.
3) Enhancements for canceling orders when managing a wallet imported from backup.
4) Deterministic key generation is now done on a per-account basis rather than per-wallet.  This should help place orders in the proper account when recovering from backups.
5) Average price gets set to the "median feed"
6) Major network bug fixes.

All hard-fork changes are currently scheduled to go into effect Friday at Noon. 

Test GUIs should be provided by DAC Sun Limited soon.



« Last Edit: September 03, 2014, 09:05:14 PM by vikram »
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline emski

  • Hero Member
  • *****
  • Posts: 1283
    • View Profile
    • http://lnkd.in/nPbhxG
Re: 0.4.11 Release Candidate Testing
« Reply #1 on: September 02, 2014, 10:06:40 PM »
Should seed nodes and delegates update to this ? (before official release I mean)

Offline bytemaster

Re: 0.4.11 Release Candidate Testing
« Reply #2 on: September 02, 2014, 10:09:45 PM »
Should seed nodes and delegates update to this ? (before official release I mean)

Well if the release testing goes well then you will be ahead of the game.   Delegates that are less pro-active can wait until the official tag is declared as 0.4.11.

No major new changes will be made between master and 0.4.11.

For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline theoretical

Re: 0.4.11 Release Candidate Testing
« Reply #3 on: September 02, 2014, 10:13:47 PM »
5) Average price gets set to the "median feed"

I think this really means "the JSON-RPC field and the spot in the GUI that previously displayed the average price now display the median feed price but have not been relabeled."   If this is, in fact, what it actually means, then I think we should relabel them before we drop the release candidate status.

BitShares has enough confusing, technical, somewhat poorly documented terminology as it is.  There's absolutely no need to go re-defining terms like "average price" to mean something completely different from what people expect it to mean!
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 bytemaster

Re: 0.4.11 Release Candidate Testing
« Reply #4 on: September 02, 2014, 10:20:31 PM »
5) Average price gets set to the "median feed"

I think this really means "the JSON-RPC field and the spot in the GUI that previously displayed the average price now display the median feed price but have not been relabeled."   If this is, in fact, what it actually means, then I think we should relabel them before we drop the release candidate status.

BitShares has enough confusing, technical, somewhat poorly documented terminology as it is.  There's absolutely no need to go re-defining terms like "average price" to mean something completely different from what people expect it to mean!

The GUI reads median price... that particular comment was based upon technical internals.   
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline emski

  • Hero Member
  • *****
  • Posts: 1283
    • View Profile
    • http://lnkd.in/nPbhxG
Re: 0.4.11 Release Candidate Testing
« Reply #5 on: September 02, 2014, 10:43:18 PM »
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.

Offline tonyk

  • Hero Member
  • *****
  • Posts: 3309
    • View Profile
Re: 0.4.11 Release Candidate Testing
« Reply #6 on: September 02, 2014, 11:28:35 PM »
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 ionx

  • Newbie
  • *
  • Posts: 19
    • View Profile
Re: 0.4.11 Release Candidate Testing
« Reply #7 on: September 02, 2014, 11:36:19 PM »
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, [email protected]=0x7ff070596450,
    [email protected]=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, [email protected]=0x7ff070596450,
    [email protected]=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, [email protected]=1, descriptor=155,
    [email protected]: 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 ([email protected]=0x7ff07048fed8, [email protected]=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 ([email protected]=0x7ff07048fe80, [email protected]=0x7ff070001fb0 "\b", [email protected]=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 ([email protected]=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 CLains

  • Hero Member
  • *****
  • Posts: 2610
    • View Profile
  • BTS: clains
Re: 0.4.11 Release Candidate Testing
« Reply #8 on: September 02, 2014, 11:41:31 PM »
Thanks for all the hard work gang. :)
Vote for BTS-2 witness: spectral (1.6.30)

Follow https://steemit.com/@clains

Offline biophil

  • Hero Member
  • *****
  • Posts: 814
  • Incentives run the world
    • View Profile
    • Sign up for a Bitshares account!
  • BTS: zebulon
Re: 0.4.11 Release Candidate Testing
« Reply #9 on: September 03, 2014, 12:28:53 AM »
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


Offline Riverhead

Re: 0.4.11 Release Candidate Testing
« Reply #10 on: September 03, 2014, 12:33:20 AM »
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 ripplexiaoshan

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 2026
    • View Profile
  • BTS: xiaoshan
Re: 0.4.11 Release Candidate Testing
« Reply #11 on: September 03, 2014, 12:42:42 AM »
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 ID:xiaoshan                   www.yoyow.org      www.btsabc.org      www.openledger.info

Offline tonyk

  • Hero Member
  • *****
  • Posts: 3309
    • View Profile
Re: 0.4.11 Release Candidate Testing
« Reply #12 on: September 03, 2014, 12:54:38 AM »
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 theoretical

Re: 0.4.11 Release Candidate Testing
« Reply #13 on: September 03, 2014, 01:28:58 AM »
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 biophil

  • Hero Member
  • *****
  • Posts: 814
  • Incentives run the world
    • View Profile
    • Sign up for a Bitshares account!
  • BTS: zebulon
Re: 0.4.11 Release Candidate Testing
« Reply #14 on: September 03, 2014, 03:21:48 AM »
Thanks tonyk and drltc for the explanations. I like it.

Sent from my SCH-S720C using Tapatalk 2


 

Google+