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

Pages: 1 ... 10 11 12 13 14 15 16 [17] 18 19 20 21
241
中文 (Chinese) / Re: BTS矿池设想
« on: May 01, 2014, 12:04:22 am »
分红计算规则可能比较麻烦，最公平的是按每block计算，矿池的主要门槛应该就在计算分红规则及相关的计算了。当然一个比较稳定的服务器资源也是应该保证的，这个算是矿池运行的成本。
关于比例：
1 挖矿所占资源较少
2 矿池生存基础是投票，所以分红比例较高应该是应该的。我估计以后会高到90%左右。只是初期矿池投入较大，所以比例会比较小。

242
中文 (Chinese) / BTS矿池设想
« on: April 30, 2014, 11:47:40 pm »
要做BTS矿池应该比较容易，就是叫参与者投票到我的矿池就可以。
那么参与者为什么要投票呢？借用矿池的概念就好了，每个给我投票的人可以分红。比如挖矿的收入50%分红，每周分红。这样的矿池可以做到分布非常广，哪怕你只有一个BTS也可以参与挖矿。当然，如果发送分红手续费太高，可以设置进入的门槛，比如10BTS以上。

243
General Discussion / Re: Interested in a node-webkit implementation of GUI.
« on: April 29, 2014, 07:16:08 pm »
Quote from: bytemaster on April 29, 2014, 12:44:34 pm
We have changed the API of sendtoaddress to make it compatible with Bitcoin RPC....   We are attempting to be as compatible with Bitcoin as possible and to have extended APIs for handling our special features (like support for multiple asset types on one chain).

I agree that the RPC API should be compatible with bitcoin's. As I understand sendtoaddress will be without asset type where asset type defaults to BTS and an extended API like sendtoaddress_asset will be added. I can also see get_transaction_history and will play with that. Good progress, thanks.

Edit: Seems like there's some uncommited changes in fc at the time of writing and I've manually fixed that by adding needed changes (in time.hpp) on my local machine.

244
General Discussion / Re: BitShares X Status Update
« on: April 27, 2014, 01:24:09 am »
Quote from: bytemaster on April 26, 2014, 10:08:52 pm
1) Yes the inactivity fee applies to all balances.   The BitUSD collected by this fee is sold for BTS and the BTS is destroyed to pay dividends to shareholders.
2) A long time a go when I was implementing dividends via direct accounting this applied.  Once I switched to implicit dividends (via fee destruction) it was no longer viable to pay this way. 

Instead what the dividends on collateral does is increase the backing on the BitUSD over time.
To have something which price linked with fiat is so important that it's very important to make bitUSD and bitCNY work.
 
I think it was a good idea to support bitUSD value with interest of collateral. Actually the burning of bitUSD transaction fee has the similar effect but you've decided to buy and burn BTS instead.

Now with implicit dividends I think we can still get the similar approach by returning same amount of BIP instead of BTS when shorters cover the short. The dividends (new collateral BIP - old collateral BIP) can still go to all the holders of bitUSD. It's more complex in implementation but I think it's really important to have some thing supporting the bitAsset to prevent price going to 0 instead of just a name link between bitUSD and USD. I hope we can find an easier way to dispatch dividends.

245
General Discussion / Re: BitShares X Status Update
« on: April 26, 2014, 09:41:06 pm »
1. Does 5% inactivity fee apply to bitAssets like bitUSD?
2. I remember that the interest of collateral (XTS) will go to holders of bitAsset. I believe this can support the price of bitAsset and prevent its price goes to 0. As the interest is got from transaction fees, will this calculation be based on block by block? If yes, I wonder what is the simplest way to implement it in wallet code as for each block you need to calculate that and adjust the balance of bitAsset holder.

246
General Discussion / Re: Interested in a node-webkit implementation of GUI.
« on: April 26, 2014, 09:11:06 pm »
Quote from: bytemaster on April 26, 2014, 01:19:54 pm

Quote from: HackFisher on April 26, 2014, 01:06:20 pm
For mobile device, or those env not suitable to run a local light client node, solutions like blockchain.info would be nice.
One js API to abstract both use cases.


Sent from my iPhone using Tapatalk

I guess the new API with username in openwallet is for this purpose. As this doesn't add too much complexicity to C code, I think it's fine.
But from security point of view, the unlocking of private key still happens on server. The fact that unlocking happens in browser makes me believe that I'm safe with blockchain.info wallet. I may choose another solution If I'm going to setup some online wallet services like blockchain.info. As I understand, the online wallet like blockchain.info only need to provide 2 things:
1. Storage of encrypted private keys.
2. Publishing signed transactions. This can be public interface and doesn't have to be done from one's wallet (means no login).

247
General Discussion / Re: Interested in a node-webkit implementation of GUI.
« on: April 24, 2014, 04:15:58 am »
Well, I misunderstood you and am very glad that if I can help.
Added receiving address list page.
There seems to be some bugs in sending transactions as it will clear the balance to 0 in some cases. But for testing ui, it's ok.
Plan to merge received transactions and send transactions to single transactions list with different colors for sent and received transactions.

248
中文 (Chinese) / DAC化的淘宝（私路3.0?）
« on: April 24, 2014, 02:16:04 am »
从私路的收入看，被淘宝排斥物品（比如比特币相关）的交易也是个很大的生意。所以DAC化股东的分红应该能保证。具体可以从每笔交易中收取手续费。
技术上，商品数据的分布式数据存储及搜索方案用类似twister的方案也可以很好解决。第三方担保方案有几个选择：
1.可以用bitshares insurance保险类似的仲裁人
2.每笔交易生成多签名地址做担保，双方都打入资金进这个地址担保。
3.1+2，如果出现争执由仲裁人仲裁。比较复杂。初期可以先用一个固定的私钥做仲裁。多签名地址2/3，三个人（买方卖方仲裁）中的两个同意就可以转账。

249
General Discussion / Re: Interested in a node-webkit implementation of GUI.
« on: April 23, 2014, 10:42:52 pm »
Quote from: bytemaster on April 23, 2014, 09:20:16 pm
I am working on this. 


Sent from my iPhone using Tapatalk

That's great. I'll stop here and please don't hesitate if anything I can help.
btw, I think an integrated window could be more user friendly. I mean let the user feel like a real desktop app than populating it in a browser. Maybe cef(https://code.google.com/p/chromiumembedded/) can help here.

250
General Discussion / Re: Interested in a node-webkit implementation of GUI.
« on: April 23, 2014, 09:15:15 pm »
First JSON/RPC call on getbalance done.
You can see it working from http://114.215.104.153:9091/index.html#/transactions where user/password should be "user" and "pwd".

Notice the balance is "1000" at the moment which is got from calling json/rpc getbalance.

251
General Discussion / Re: Interested in a node-webkit implementation of GUI.
« on: April 23, 2014, 08:17:13 pm »
Pulled lastest bitshares code finally build it on my debian box.
Excited to see that the latest bts_xt_client supports --server and uses ./htdocs as http root. This makes it easier to put my code just at ./htdocs. Will play with that if I find some time.
RPC tricks:
You need to go through the below steps to send xts:
1. openwallet()
2. walletpassphrase('<<send password>>')
3. sendtoaddress('address', {"amount":<number>,"unit":0},'comment')

From RPC commands, I don't find how to retrieve latest transactions but I can try to simulate it by directly using getblock and get_transaction.
My config.json:
{"rpc":{"rpc_user":"user","rpc_password":"pwd","rpc_endpoint":"0.0.0.0:0","httpd_endpoint":"0.0.0.0:9091","htdocs":"./htdocs"},"ignore_console":false}

252
中文 (Chinese) / Re: BTX界面开发[4.23更新]
« on: April 23, 2014, 12:55:31 pm »
Quote from: 蜗牛 on April 23, 2014, 11:21:12 am
我觉得传统GUI和网页版都是必不可少的

不同意，JS完全可以做成像传统的桌面应用，你都感觉不出来是网页应用。参考https://github.com/rogerwang/node-webkit

253
General Discussion / Re: Interested in a node-webkit implementation of GUI.
« on: April 22, 2014, 10:03:19 pm »
Quote from: betax on April 22, 2014, 10:21:55 am
That is what I thought, you could have a desktop and a server version (own home / network server), so mobile / tablets can connect.
Yes, exactly. I don't know if they provide RPC on HTTP. If they don't, things will be a bit difficult as I have to use node/phonegap to setup tcp connections. I'm still trying to find some documents on their RPC interfaces.

254
General Discussion / Re: Interested in a node-webkit implementation of GUI.
« on: April 21, 2014, 08:47:37 am »
Quote from: betax on April 21, 2014, 07:56:54 am
Great idea, what is your plan? Create a desktop application using node webkit that interacts with a local / own network rpc server? Or a centralize solution ?

node webkit that interacts with a local / own network rpc server. For an online wallet, I think we may have legal issues with running such a service.

255
DAC PLAY / Re: Blockchain RNG with DPOS
« on: April 20, 2014, 10:09:33 am »
Can there be known numbers where S1,S2 have the same HASH(S)? If yes, delegates can use this to cheat. Say the number is SH. Say I always publish SH and choose S1 or S2 to reveal if I'm the last one in the round. How can I reduce this risk?

Pages: 1 ... 10 11 12 13 14 15 16 [17] 18 19 20 21

Page created in 0.178 seconds with 20 queries.