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

Pages: 1 ... 12 13 14 15 16 17 18 [19] 20 21 22 23 24 25 26 ... 29
271
music 的代码在哪里可以看到?

272
中文 (Chinese) / Re: 竞选专用帖
« on: June 04, 2014, 01:40:55 pm »
freedom!!!

273
中文 (Chinese) / Re: 提前祝贺今天论坛访问人数破300
« on: June 04, 2014, 01:28:27 pm »
+5%

274
General Discussion / Re: [ACTIVE] New testnet iteration
« on: June 04, 2014, 01:12:58 pm »
XTS51N8ki7UP2KJgwCsHMpq8CNDBuqtReKRkSGKuqkPTcRXc4w6sS

Please sent me some fund for test, thanks.

send it

seems i did not receive it.

Quote
crazybit (unlocked) >>> get_info
{
  "blockchain_head_block_num": 523,
  "blockchain_head_block_time": "20140604T130900",
  "network_num_connections": 8,
  "wallet_balance": [[
      0,
      "XTS"
    ]
  ],

  "wallet_unlocked_seconds_remaining": 29926,
  "wallet_next_block_production_time": null,
  "wallet_seconds_until_next_block_production": null,
  "wallet_local_time": "20140604T131027",
  "blockchain_bips_per_share": 12.50000009532172,
  "blockchain_random_seed": "9244e1710a31b29524413c6632d4cd7ba54ad94e",
  "blockchain_shares": 79999999389941,
  "network_num_connections_max": 12,
  "network_protocol_version": 101,
  "wallet_open": true,
  "wallet_unlocked_until": "20140604T212913.937749",
  "wallet_version": 100
}


275
General Discussion / Re: [ACTIVE] New testnet iteration
« on: June 04, 2014, 12:47:36 pm »
XTS51N8ki7UP2KJgwCsHMpq8CNDBuqtReKRkSGKuqkPTcRXc4w6sS

Please sent me some fund for test, thanks.

276
其实现在的toolkit 已经做到了,可以通过json -rpc 调用接口。native invoke 现在应该也是支持的。

277
General Discussion / Re: TITAN Test Net for XTS Open for Savvy Users
« on: June 03, 2014, 01:40:27 pm »
Please sent me some fund, thanks

XTS6YmGeNjZkqimUc7AVF3RJ1iX537XNPePxLEX7NuqzJ8FBsLCWx


BTW, i was rejected while connecting to seed node: 107.170.30.182:8764 with following error. is the connection pool full? please share if you have any available seed node.

Quote
1159635ms       th_a      connect_to_task ] Sent "hello" to peer 107.170.30.182:8764         node.cpp:2042
1159636ms       th_a      connect_to_task ] The hello message I just sent contains connection information: my_ip: 192.168.0.2, my_outbound_port: 2243, my_inbound_port: 2243         node.cpp:2044
1160206ms       th_a on_connection_reject ] Received a rejection from 107.170.30.182:8764 in response to my "hello", reason: "You're on a different chain than I am.  I'm on ?h W奾秕執??˙愱蔅? and you're on 炑乊.;珣哾=
?j ?p?耻琲˙?"         node.cpp:1276
1160209ms       th_a            read_loop ] disconnected eof
End of file
    {"message":"End of file"}
    asio  asio.cpp:22 fc::asio::detail::read_write_handler

    {"len":16}
    th_a  stcp_socket.cpp:73 bts::net::stcp_socket::readsome         message_oriented_connection.cpp:130
Delete you ~/.BitSharesX folder and start over again .. chains had a reset due to TITAN

thanks, replace the genesis.dat and it works now.

278
General Discussion / Re: TITAN Test Net for XTS Open for Savvy Users
« on: June 03, 2014, 01:24:25 pm »
A tip for those getting:

Code: [Select]
Error starting rpc server

The default config.json file uses port=0 for both RPC settings, just change them to two different ports and the RPC server will start correctly.

if you start up the client with the argument "--server" but without  the argument "--rpcport" and "--httpport",0 would be the default listen port for RPC and HTTP servers,  but the port 0 is invalid based on the existing checking logic, so that the RPC and HTTP servers would  not be started up properly. you can change the the variables "rpc_endpoint" and "httpd_endpoint" to non-zero value in file config.json to start up the RPC server ,and i think it is a program bug.

279
General Discussion / Re: TITAN Test Net for XTS Open for Savvy Users
« on: June 03, 2014, 12:43:13 pm »
Please sent me some fund, thanks

XTS6YmGeNjZkqimUc7AVF3RJ1iX537XNPePxLEX7NuqzJ8FBsLCWx


BTW, i was rejected while connecting to seed node: 107.170.30.182:8764 with following error. is the connection pool full? please share if you have any available seed node.

Quote
1159635ms       th_a      connect_to_task ] Sent "hello" to peer 107.170.30.182:8764         node.cpp:2042
1159636ms       th_a      connect_to_task ] The hello message I just sent contains connection information: my_ip: 192.168.0.2, my_outbound_port: 2243, my_inbound_port: 2243         node.cpp:2044
1160206ms       th_a on_connection_reject ] Received a rejection from 107.170.30.182:8764 in response to my "hello", reason: "You're on a different chain than I am.  I'm on ?h W奾秕執??˙愱蔅? and you're on 炑乊.;珣哾=
?j ?p?耻琲˙?"         node.cpp:1276
1160209ms       th_a            read_loop ] disconnected eof
End of file
    {"message":"End of file"}
    asio  asio.cpp:22 fc::asio::detail::read_write_handler

    {"len":16}
    th_a  stcp_socket.cpp:73 bts::net::stcp_socket::readsome         message_oriented_connection.cpp:130

280
恭喜!给女娃留10bts,以后她就什么都不愁了。

281
我很好奇波神在3i和社区里扮演的是什么角色?看网站上说中国区的CEO,不过好像也没做什么事,还是其实他为社区做一些事,只是我们不知道?

282
Technical Support / Re: AGS potential security issue
« on: May 31, 2014, 07:08:18 am »
We disscused sth similar in the "Mirrorchain" thread .. you should take a look
Thx,i would take a look

283
Quote
Inspired by logxing's proposal, i come up with an idea which may completely solve this potential security issue.  if we could use the signature which sign on the specified text(e.g the donation address) with private key, to claim the corresponding shares in different DACs,then we would not worry about private key stolen,as we do NOT need to expose our private key and use different signature to claim the shares in different DAC. e.g signature to claim the XTS shares =sign(“XTS”+Pts/BTC donation address, PrivateKey), signature to claim the DNS shares =sign(“DNS”+Pts/BTC donation address, PrivateKey)

my idea, please discuss if it is feasible.

https://bitsharestalk.org/index.php?topic=4732.msg62135#msg62135

284
我对这个方法是否可行存怀疑态度,如果是针对领取地址签名,那么这个签名是唯一的。倘若用这个签名就可以Clain DAC里面的shares,那泄露签名跟泄露私钥没有什么分别, 除非在其他DAC里用来Clain shares的签名是针对不同的文本进行签名的,但是能证明这些shares的唯一文本就是你捐AGS的地址,这个地址是不变的。
不同dac会有不同的特定信息,地址只是信息之一,任何签名都应该保证签署信息的独特和完整,避免模棱两可的情形,以避免对签名信息的滥用。

来自我的 HUAWEI P6-C00 上的 Tapatalk

在你这个想法的基础上,想出来的方案。
https://bitsharestalk.org/index.php?topic=4732.0

285
Technical Support / Re: AGS potential security issue
« on: May 31, 2014, 05:04:20 am »
Inspired by logxing's proposal, i come up with an idea which may completely solve this potential security issue.  if we could use the signature which sign on the specified text(e.g the donation address) with private key, to claim the corresponding shares in different DACs,then we would not worry about private key stolen,as we do NOT need to expose our private key and use different signature to claim the shares in different DAC. e.g signature to claim the XTS shares =sign(“XTS”+Pts/BTC donation address, PrivateKey), signature to claim the DNS shares =sign(“DNS”+Pts/BTC donation address, PrivateKey)

Pages: 1 ... 12 13 14 15 16 17 18 [19] 20 21 22 23 24 25 26 ... 29