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 - king

Pages: [1] 2 3 4 5 6
1
General Discussion / BTSX wallet segmention fault
« on: October 03, 2014, 03:40:28 am »
--- there are now 52 active connections to the p2p network
--- there are now 51 active connections to the p2p network
servicewallet (unlocked) >>> Segmentation fault (core dumped)


version v0.4.19

2
General Discussion / Re: BitShares X 0.4.15 Mandatoty Update
« on: September 14, 2014, 07:51:28 am »
Mandatory Update???

3
Stakeholder Proposals / Re: Strange missed blocks
« on: September 13, 2014, 02:34:04 am »
try run:
network_set_advanced_node_parameters {"desired_number_of_connections":100, "maximum_number_of_connections":200}

5
Stakeholder Proposals / Re: About wallet_publish_version command
« on: September 12, 2014, 07:36:06 pm »
Is it not an option to lower a little bit the "Transaction Fee (BTSX)" manualy at "Preferences"(gui) ? Am I missing something?
Sure .. you are free to do so .. unless you figure out that everything <0.1 BTSX will not work properly :-)

Quote
I made it myself. Do you think it's not ethical? I think it's ok. Let me known....
not really en ethical issue .. there are different things to consider:
- every btsx fee you pay will help delegates to be profitable
- a part of that fee is burned and comes as a profit for shareholders ...

I have not decided my own if its greedy or unethical to reduce the fee .. I will stick with .5 btsx just because .. it's still just a handful of $cents .. (although I send out feeds for 3 delegates and 4 currencies every 4 hours :-) ) .. income is still > costs :-)  -- even if I had only one active delegate .. (btw:  https://bitsharestalk.org/index.php?topic=7673.msg101741#msg101741 )

People will not only feel less fees to pay, but because of reasonable pay.
delegate revenues> costs, but these revenues should be used to promote the product in place of progress,
Thanks discussion, I now think is really necessary to pay, because it avoids publish spam

6
Stakeholder Proposals / Re: About wallet_publish_version command
« on: September 12, 2014, 07:25:58 pm »
Thanks, I'm just discussing reasonable, including:
Question 1, when the delegate publish version info and update feed price, whether you need to pay?
Question 2, the delegate update, the need to manually execute the command wallet_publish_version, ability to automatically publish version?which will avoid some malicious behavior;

For Question 1, the above discussion has been very good;
I hope to discuss Question 2.

7
Stakeholder Proposals / About wallet_publish_version command
« on: September 12, 2014, 02:52:15 am »
About wallet_publish_version command, when used, will cost 0.5BTSX, I think it is not very reasonable!
version of the delegate node, can automatically publish the wallet? And without cost?

8
General Discussion / Re: BTSX 0.4.13-RC1 was just posted by DAC Sun
« on: September 09, 2014, 08:20:26 pm »
sun.delegate.service
moon.delegate.service
updated,and published version.

9
General Discussion / Re: version 0.4.12 missed blocks
« on: September 08, 2014, 01:27:25 am »
Resource usage VPS I
CPU[  1.3%]     Tasks: 33, 21 thr; 1 running
Mem[ 143/994MB]     Load average: 0.02 0.02 0.05

Uses only minimal resources, including network and IO.
and I ran blockchain_is_synced command, the result is true
But I use wallet_get_account command to view last_block_num_produced info, much smaller than the current block number
sometimes you miss block is not because of you,but the delegate after you.


I lost the 100% reliability, very bad!

10
General Discussion / Re: version 0.4.12 missed blocks
« on: September 07, 2014, 11:34:50 pm »
Resource usage VPS I
CPU[  1.3%]     Tasks: 33, 21 thr; 1 running
Mem[ 143/994MB]     Load average: 0.02 0.02 0.05

Uses only minimal resources, including network and IO.
and I ran blockchain_is_synced command, the result is true
But I use wallet_get_account command to view last_block_num_produced info, much smaller than the current block number

11
General Discussion / Re: version 0.4.12 missed blocks
« on: September 07, 2014, 02:35:32 pm »
Sorry,My operating system is 14.04, I just made ​​a mistake

12
General Discussion / version 0.4.12 missed blocks
« on: September 07, 2014, 02:30:23 pm »
0.4.12 version I think there is a bug, the client is running about 12 hours later, will be missed blocks, and without any exception, the previous version is very stable, does not appear in this case!
My operating system is ubuntu 14.04

13
sun.delegate.service
moon.delegate.service
@ v0.4.12
and public data update
{"version","0.4.12"}

14
DAC 委托人 / Re: 为代理拉票2014年8月30日凌晨0点整理
« on: September 04, 2014, 06:48:44 pm »
携两孩子
sun.delegate.service
moon.delegate.service
感谢楼主!
我原来运行mister,也有近2000块无丢块记录(块主要是初期丢的)
service虽然团队销毁率为0%,但团队将付出更多的时间成本,并使用备用VPS,以最大限度保证更新不丢块,以提供最稳定的服务,
团队将持续做好服务,后期将逐步增加销毁率!

15
General Discussion / Re: Delegates can now Publish their Version
« on: September 04, 2014, 05:19:16 am »
sun.delegate.service
moon.delegate.service

updrage : {version:0.4.10}

Pages: [1] 2 3 4 5 6