Sorry for the downtime guys, witness_node froze again.. bringing it back up..

Code: [Select]

798084ms th_a       application.cpp:497           handle_block         ] Got block: #2447427 time: 2016-01-07T08:13:18 latency: 85 ms from: maqifrnswa  irreversible: 2447408 (-19)
798264ms th_a       database_api.cpp:229          get_objects          ] getObjects without subscribe callback??
799293ms th_a       database_api.cpp:229          get_objects          ] getObjects without subscribe callback??
800307ms th_a       database_api.cpp:229          get_objects          ] getObjects without subscribe callback??
800407ms th_a       application.cpp:546           handle_transaction   ] Got 1 transactions from network
801321ms th_a       database_api.cpp:229          get_objects          ] getObjects without subscribe callback??
801345ms th_a       application.cpp:497           handle_block         ] Got block: #2447428 time: 2016-01-07T08:13:21 latency: 346 ms from: bitcube  irreversible: 2447408 (-20)
[stuck]
^C
Program received signal SIGINT, Interrupt.
0x0000000000e0ce10 in void fc::divide<fc::uint128>(fc::uint128 const&, fc::uint128 const&, fc::uint128&, fc::uint128&) ()
(gdb) bt
#0  0x0000000000e0ce10 in void fc::divide<fc::uint128>(fc::uint128 const&, fc::uint128 const&, fc::uint128&, fc::uint128&) ()
#1  0x0000000000e0cf74 in fc::uint128::operator/=(fc::uint128 const&) ()
#2  0x0000000000c27b7c in graphene::chain::database::clear_expired_orders() ()
#3  0x0000000000c32a0b in graphene::chain::database::_apply_block(graphene::chain::signed_block const&) ()
#4  0x0000000000c337d5 in graphene::chain::database::apply_block(graphene::chain::signed_block const&, unsigned int) ()
#5  0x0000000000c33c90 in graphene::chain::database::_push_block(graphene::chain::signed_block const&) ()
#6  0x0000000000c35894 in graphene::chain::database::push_block(graphene::chain::signed_block const&, unsigned int) ()
#7  0x0000000000a8398f in graphene::app::detail::application_impl::handle_block(graphene::net::block_message const&, bool, std::vector<fc::ripemd160, std::allocator<fc::ripemd160> >&) ()
#8  0x0000000000f71097 in fc::detail::functor_run<graphene::net::detail::statistics_gathering_node_delegate_wrapper::handle_block(graphene::net::block_message const&, bool, std::vector<fc::ripemd160, std::allocator<fc::ripemd160> >&)::{lambda()#1}>::run(void*, fc::detail::functor_run<graphene::net::detail::statistics_gathering_node_delegate_wrapper::handle_block(graphene::net::block_message const&, bool, std::vector<fc::ripemd160, std::allocator<fc::ripemd160> >&)::{lambda()#1}>) ()
#9  0x0000000000e2bbc3 in fc::task_base::run_impl() ()
#10 0x0000000000e29d2e in fc::thread_d::process_tasks() ()
#11 0x0000000000e29fa1 in fc::thread_d::start_process_tasks(long) ()
#12 0x00000000010921c1 in make_fcontext ()
#13 0x0000000000000000 in ?? ()

Is it started with --replay-blockchain? From my personal experience it won't hang by starting with this parameter.

//Edit: we have a discussion here https://bitsharestalk.org/index.php/topic,20631.0/all.html

Quote from: xeroc on January 07, 2016, 11:06:12 am

Quote from: svk on January 06, 2016, 08:05:58 pm

Unless @theoreticalbts or @bytemaster can explain the "missing" permissions that relate to bit assets I can't do much about this.

I say "missing" because they're not part of the definitions here: https://github.com/cryptonomex/graphene/blob/62c22fbf18d748531c468e0d7a88d08eddbd6f20/libraries/chain/include/graphene/chain/protocol/types.hpp#L84

and I've tried searching through the code but I can't find anything explaining how bit asset permissions.

https://github.com/cryptonomex/graphene/blob/master/libraries/wallet/wallet.cpp#L2319-L2336
It seems all that is needed is another 'bitasset"-specific json object:
https://github.com/cryptonomex/graphene/blob/master/libraries/chain/include/graphene/chain/protocol/asset_ops.hpp#L87-L110

do you mean the only way is to create another privatized smartcoin to replace TCNY, if need to get the initial issuer permissions and flags?

I guess he mean the attributes which svk didn't find are in another object, the "bitasset" object, not the "asset" object.

Quote from: xeroc on January 07, 2016, 06:29:28 am

Quote from: CoinHoarder on January 07, 2016, 04:27:02 am

Quote from: fuzzy on January 06, 2016, 07:50:39 pm

beginning to wonder if you are paid to inject toxic fumes in conversations by competitors because if i were a competitor youd be my favorite person on these forums.

I wonder this about half the posters on this forum.

I am truly embarrassed. It is like they have no idea about supply and demand, or how big of a role public perception plays into that. All of these long time "supporters" attacking every move, decision, and statement CNX makes and they don't seem to realize that this will have a negative effect on the price. They complain about everything injecting negativity into every conversation, then in turn complain about the price falling without realizing that they are playing a large role in the price falling. Bitshares has a huge PR problem in the crypto community.. I frequent Bitcointalk and it is apparent. To make things even worse, Bitshares has a huge PR problem within its own community with these forums being a never-ending horror show. Something has to give.. either the price, or the horror show. We need to come together as a community, or abandon the project and dump our coins.

All I can say is that I'm happy 3/4 of my Bitshares are in bitBTC, bitGOLD, and bitSILVER... call me a bear, but there is so much negative energy around here that I am not sure I can stand to support this train wreck much longer.

This!

lol in combine with tony's signature:

- cause a 100% idiotic is hardly ever enough!

Quote from: abit on January 05, 2016, 11:07:48 pm

@xeroc latest version (commit 3c7b2ca1b68e33fbf47aa9d66005613b83ca1f51) with Btc38's BTS/BTC market enabled by default causes a 10% off on BTS/CNY price.

Code: [Select]

|  CNY   | 0.02429415 | 0.02342230 (+3.72%) | 0.02433542 (-0.17%) | 0.02429415 (+0.00%) |  0.03% ( 5)  | 0.02209000 (+9.98%) | 0.02209988 (+9.93%) | 1:48:02.671795 ago |    X    |
blame file here: https://drive.google.com/open?id=0B3xrm70jSHn4V2dBX1duaEZ5OEE

Another minor error on my server:

Code: [Select]

Error fetching results from Ccedk! ('bool' object is not subscriptable)


The script is a deterministic one, so it does not "cause" a wrong price. I will investigate what the reason for this is, but I assume some exchange may have published an "off"-price .. We do see some volatility right now..

It's sure caused by Btc38's BTS/BTC market, but I don't think there is enough volume to cause a 10% change on weighted average price. Maybe I'm wrong.. However I disabled that market in my production script.

我个人并未觉得中国用户投票意识比国外用户明显淡，不然我也不会在未获BM投票的情况下被投进去。似乎不见得中国用户放在交易所里的BTS比例更大。

BM现在领导着CNX，需要不断给他的团队找活干，总有新想法是可以理解的，问题在于社区要发挥作用，要掌握应该掌握的，没有人愿意给自己戴上镣铐，拿着镣铐的人要想办法去拷上，这次寻求交易所投票可以看做一次尝试，如果能借此建立一个真正的多元化/去中心的理事会，那么也许还有的玩，如果社区连一个理事会都搞不定，那就趁早散了吧。

我有点奇怪，为什么跟帖赞同交易所投票的多，可却有那么多投票反对交易所投票的？

发起投票的人，能不能看到谁投了什么票？

Quote from: yvv on January 06, 2016, 03:14:33 am

Buy back is not distributing a revenue. It is a convenient method to pay debt for issuer of debt token, like obits. Obits borrowed worth of $200K loan from people (4M obits), and made $3K profit in one month. If they claim that they are going to spend all their profit to pay their debt, it will take them about 5 years to pay their debt at this pace.

Apple's stock price is currently $102.71. It's dividend in the past year was $2.03.  If Apple's means of paying off the loan of investing in it was a buy back it would take 50 years at this pace.

Using the buy back model are mostly because of concerns of legal issues. Issuing a asset and paying dividends without a proper license is illegal in many countries.
On the other hand, with the buy back model, the company may have more control of it's operation.

Instead of pushing dividends, couldn't the process be a pull. When a dividend is available, a claim button is enabled in the gui that shows amount available to claim.  The holder of the asset can decide when to claim the dividend. This way the process can happen over a period on time instead of one interval.

Yes, it's what we've discussed in that post.

FYI we had some discussions about how to efficiently pay dividends long time ago, a claim model.
https://bitsharestalk.org/index.php?topic=14785.msg191711#msg191711

Quote from: abit on January 05, 2016, 11:19:27 pm

@iHashFury some questions:
* did you start it with --replay-blockchain?
* was your witness_node running in gdb? if yes, a backtrace would be helpful.

--replay-blockchain run automatically after the update.

I believe it's different.

I just found that my backup node has been in stuck status for quite some time, and CPU is 100%. It's a debug build of version 2.0.160103b, running in gdb, started without --replay-blockchain, however no automatically replay when it was started (database was considered clean).

1701380ms th_a       application.cpp:497           handle_block         ] Got block: #2367989 time: 2016-01-04T12:28:21 latency: 380 ms from: verbaltech2  irreversible: 2367972 (-17)
1702000ms th_a       witness.cpp:194               block_production_loo ] Not producing block because slot has not yet arrived
1703000ms th_a       witness.cpp:194               block_production_loo ] Not producing block because slot has not yet arrived
1704000ms th_a       witness.cpp:191               block_production_loo ] Not producing block because it isn't my turn
1704347ms th_a       application.cpp:497           handle_block         ] Got block: #2367990 time: 2016-01-04T12:28:24 latency: 347 ms from: spectral  irreversible: 2367972 (-18)
1152420ms ntp        ntp.cpp:177                   read_loop            ] ntp_delta_time updated to 88 us
258788ms ntp        ntp.cpp:177                   read_loop            ] ntp_delta_time updated to 36647 us
1164747ms ntp        ntp.cpp:177                   read_loop            ] ntp_delta_time updated to -109792 us
2070280ms ntp        ntp.cpp:177                   read_loop            ] ntp_delta_time updated to -216 us
3570604ms ntp        ntp.cpp:177                   read_loop            ] ntp_delta_time updated to -1283 us
Instructions needed. Wish I can help.

//Edit:
Both my primary witness node and seed node work fine, both were started with --replay-blockchain.