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.


Topics - Webber

Pages: [1]
1
Stakeholder Proposals / Please vote for delegate.webber witness node
« on: December 04, 2015, 01:25:41 pm »
Hello,everyone~

I'm webber :) :)

I had run a delegate in Bitshares0.x, my server was efficient and stable and very low loss rate.

Now ,I'am back~ :P :P :P :P

I have been running a witness node :delegate.webber, please vote for me~!

And,I have been running another server as API server:ws://114.215.116.57:8090,friends in china will be very convenient to use this API ~!

Thank you for everyone~! ;) ;) ;)

2
中文 (Chinese) / 请为delegate.webber投票~
« on: December 04, 2015, 01:07:24 pm »
 大家好,我是webber ;) ;) ;) ;)  我在bts 1.0时代运行了一个delegate,期间服务器稳定、可靠

由于前段时间比较忙错过了2.0令人激动的启航时间 :P :P :P

现在,我回来了~!~ ;D ;D ;D

我目前已运行了一个witness node,  名字还是 delegate.webber ,欢迎大家为我投票~!

另外我还运行了一个ws节点:ws://114.215.116.57:8090,欢迎使用~~!

嘿嘿,我能为bts做的,就是默默地当一个搬运工 8) 8) 8)

3
General Discussion / How to use mail sub-system?
« on: October 26, 2014, 02:58:02 pm »
Default mail server is timeout,I don't think nathanhourt.com or 69.90.132.209:1376 is a mail server port. can someone tell me how to use mail system ?
I want to build a mail server,what should I do? use nginx or any other software?

Code: [Select]
mywallet (unlocked) >>> mail_get_message "cde9a59a364ad29e2d6607a6d145c52e591e8957"
=== Email Message ===
From:         webber-delegate
To:           mail-test
Date:         2014-10-26T12:39:46
Subject:      test mail

this is a test mail.

===  End  Message ===

Message Failed to Send: Timed out while transmitting message.
Attempted to send to these servers:
[[
    "nathanhourt.com",
    "69.90.132.209:1376"
  ]
]
mywallet (unlocked) >>> blockchain_get_account nathanhourt.com
Name: nathanhourt.com
Registered: 2014-07-24T01:50:10
Last Updated: 66 hours ago
Owner Key: BTSX5Z1WFVTCmvwzGDc755XhLQhe6hTqsUWEgRBRNZvUSUTA4ewvyk
Active Key History:
- BTSX5Z1WFVTCmvwzGDc755XhLQhe6hTqsUWEgRBRNZvUSUTA4ewvyk, last used 14 weeks ago
Not a delegate.
Public Data:
{
  "mail_server_endpoint": "69.90.132.209:1376"
}

4
DAC 委托人 / KeyID delegates ready on~!
« on: October 03, 2014, 02:46:39 am »
KeyID webber个人代表已经正式上线,一如既往第一时间支持3i.本人也是小散,筹码有限,欢迎各位DNS支持者参与投票~~在这里谢谢各位兄弟了~ :) :) :) :)
webber-delegate
webber-delegate1
webber-delegate2

5
General Discussion / chain database is in an inconsistent state.
« on: September 13, 2014, 01:01:28 pm »
I build a new linux wallet today,but can't sync.Wallet version is 0.4.15-RC1.
Code: [Select]
--- there are now 13 active connections to the p2p network
I am disconnecting peer 80.240.133.79:1776 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 104.131.35.149:1776 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 178.62.50.61:1776 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 178.62.50.61:1779 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 180.153.142.120:1777 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 5.101.106.138:1777 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 80.240.133.79:1778 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 95.85.33.16:8764 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 84.238.140.192:42577 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 5.101.106.138:1778 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 5.101.106.138:1776 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 80.240.133.79:1777 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 54.79.27.224:1776 for reason: You offered us a block that we reject as invalid
--- in sync with p2p network
Error: your chain database is in an inconsistent state.  Please shut down and relaunch using --rebuild-index or --resync-blockchain to repair the database
Error: your chain database is in an inconsistent state.  Please shut down and relaunch using --rebuild-index or --resync-blockchain to repair the database
Error: your chain database is in an inconsistent state.  Please shut down and relaunch using --rebuild-index or --resync-blockchain to repair the database
Error: your chain database is in an inconsistent state.  Please shut down and relaunch using --rebuild-index or --resync-blockchain to repair the database
Error: your chain database is in an inconsistent state.  Please shut down and relaunch using --rebuild-index or --resync-blockchain to repair the database
--- there are now 0 active connections to the p2p network
Error: your chain database is in an inconsistent state.  Please shut down and relaunch using --rebuild-index or --resync-blockchain to repair the database
Error: your chain database is in an inconsistent state.  Please shut down and relaunch using --rebuild-index or --resync-blockchain to repair the database
(wallet closed) >>>
(wallet closed) >>> info
{
  "blockchain_head_block_num": 451571,
  "blockchain_head_block_age": "66 hours old",
  "blockchain_head_block_timestamp": "2014-09-10T19:10:00",
  "blockchain_average_delegate_participation": "0.42 %",
  "blockchain_confirmation_requirement": 125,
  "blockchain_accumulated_fees": "209,705.88885 BTSX",
  "blockchain_delegate_pay_rate": "1.73367 BTSX",
  "blockchain_share_supply": "1,999,890,025.95776 BTSX",
  "blockchain_blocks_left_in_round": 101,
  "blockchain_next_round_time": "at least 17 minutes in the future",
  "blockchain_next_round_timestamp": "2014-09-13T13:17:50",
  "blockchain_random_seed": "b31cd4240040e986124f7235d2f8a4e6ae14b9ca",
  "client_data_dir": "/root/.BitSharesX",
  "client_version": "v0.4.15-RC1",
  "network_num_connections": 0,
  "network_num_connections_max": 200,
  "ntp_time": "2014-09-13T13:01:06",
  "ntp_time_error": -0.022821999999999999,
  "wallet_open": false,
  "wallet_unlocked": null,
  "wallet_unlocked_until": null,
  "wallet_unlocked_until_timestamp": null,
  "wallet_last_scanned_block_timestamp": null,
  "wallet_scan_progress": null,
  "wallet_block_production_enabled": null,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null
}

6
中文 (Chinese) / btc38h和bter有无开通bitcny/cny杠杆的可能
« on: September 11, 2014, 10:42:50 am »
目前bitcny、bitusd走向大规模应用的最大障碍是对法币的市场深度问题,Bitcny、bitusd天生就是价值稳定的东西,价值稳定意味着交易不会太活跃。如果仅靠承兑商将bitcny、bitusd换成btsx在换成法币,看起来绕了一个圈圈。bitcny、bitusd是最适合开通杠杆的交易的虚拟币,平台既然开通了bitcny/cny的交易对,开杠杆也有利于市场深度加深。貌似也是平台未来的盈利点。

7
I think 0.4.5 0.4.6 0.4.7 0.4.8 have same issues.I imported private key into those version wallet .one issue is my account income sum is about (1+533+1100+170+403+500)=2707btsx,but wallet_account_balance only  2,280.09952 BTSX. 4a3f18e0 is my short order,then I cancled it ,but this order disappeared.
Another issue is BALANCE is not correct begin from this order:
2014-08-21T00:06:13 126381    delegate.webber     delegate.webber     170.00000 BTSX          payday                                      1,633.69952 BTSX        0.10000 BTSX        f372c93f

Code: [Select]
mywallet (unlocked) >>> wallet_account_transaction_history delegate.webber
RECEIVED            BLOCK     FROM                TO                  AMOUNT                  MEMO                                        BALANCE                 FEE                 ID     
==============================================================================================================================================================================================
2014-08-21T04:05:41 38975     webber              delegate.webber     1.00000 BTSX                                                        1.00000 BTSX            0.00000 BTSX        bdc23380
2014-08-21T04:05:41 39083     delegate.webber     delegate.webber     0.00000 BTSX            update delegate.webber                      0.89952 BTSX            0.10048 BTSX        8f6597a5
2014-08-21T04:05:41 97968     webber-delegate     delegate.webber     533.00000 BTSX          payday                                      533.89952 BTSX          0.00000 BTSX        204955b8
2014-08-21T04:05:41 117492    delegate.webber     delegate.webber     1,100.00000 BTSX        payday                                      1,633.79952 BTSX        0.10000 BTSX        3a45fc02
2014-08-21T04:05:41 126381    delegate.webber     delegate.webber     170.00000 BTSX          payday                                      1,633.69952 BTSX        0.10000 BTSX        f372c93f
2014-08-21T04:05:41 165494    delegate.webber     delegate.webber     403.00000 BTSX          payday                                      1,633.59952 BTSX        0.10000 BTSX        ea6884c5
2014-08-21T04:05:41 221545    bitrose             delegate.webber     1. ROSE                 B_rose                                      1. ROSE                 0.00000 BTSX        24eca507
2014-08-21T04:05:41 227314    delegate.webber     delegate.webber     574.00000 BTSX          XTS                                         1,633.49952 BTSX        0.10000 BTSX        171b539b
2014-08-21T04:05:41 241989    delegate.webber     delegate.webber     0.00000 BTSX            update delegate.webber                      1,633.39952 BTSX        0.10000 BTSX        55c8306b
2014-08-21T04:05:41 241992    delegate.webber     webber-delegate     0.00000 BTSX            update webber-delegate                      1,633.29952 BTSX        0.10000 BTSX        ccd988f2
2014-08-24T11:13:48 254260    delegate.webber     UNKNOWN             1,000.00000 BTSX                                                    633.19952 BTSX          0.10000 BTSX        4a3f18e0
2014-08-21T04:05:41 263980    delegate.webber     delegate.webber     200.00000 BTSX                                                      632.69952 BTSX          0.50000 BTSX        c27d3339
2014-08-21T04:05:41 267096    delegate.webber     delegate.webber     500.00000 BTSX          payday                                      632.19952 BTSX          0.50000 BTSX        60fe30ff
2014-08-25T14:37:30 313657    delegate.webber     UNKNOWN             0.00000 BTSX            withdraw pay                                631.69952 BTSX          0.50000 BTSX        12868453
2014-08-25T14:41:20 313680    delegate.webber     UNKNOWN             0.00000 BTSX            withdraw pay                                631.19952 BTSX          0.50000 BTSX        fdb96126
mywallet (unlocked) >>> wallet_account_balance delegate.webber
ACCOUNT                         BALANCE                     
============================================================
delegate.webber                 2,280.09952 BTSX           
                                1. ROSE                     
                                877.17370 BTSX (pay)

8
Code: [Select]
>> blockchain_get_security_state

{
  "alert_level": "yellow",
  "estimated_confirmation_seconds": 70,
  "participation_rate": 75.939849624060145
}

xeroc-delegate     charity-delegate  这两个人每人维护了9个受托人,貌似这俩人的服务器都挂掉了,出块率直接掉到了75%

单服务器维护超过5个受托人就感觉有点集中了,在好的承诺也会有意外发生,所以建议不要在给他们投票了,或者只给他们的部分受托人投票。

9
General Discussion / TITAN is not required every times
« on: July 14, 2014, 09:53:18 am »
As we all know TITAN is real anonymous on blockchain,so no one can know receiver and sender of one trasaction by default.But I think set TITAN become optional is reasonable.For example,I make a deal with A ,and I want to open to pay 100XTS to A ,so A can't not to admit this deal because this transaction is open to everyone.
Moreover,sometimes we need to create a open account that every receive and send can open to everyone. I think TITAN is redundant for some  account that need to monitor by public .Like bts from AGS before 2.28.
So,receiver/sender anonymous or account anonymous optional function is very pratical. 

Pages: [1]