61
General Discussion / Is there a whole detail expense AGS fund?
« on: August 07, 2015, 02:43:26 am »
Is there a whole detail expense AGS fund?
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.
62
General Discussion / I mined bitusd two days but did not receive bitusd
« on: July 28, 2015, 12:54:18 pm »
I mined bitusd two days but did not receive bitusd
63
General Discussion / which of them is develop delegate are working for bts2.0
« on: June 19, 2015, 02:15:07 am »
I notice there are 35 delegates with 100% pay! and who can let me know which of them is develop delegate are working for bts2.0. maybe many of delegate done contribution to bts ,though many thing I don`t konw.
but because now the price of bts is a little low , so I temporarily just support the delegates that are working for bts2.0
but because now the price of bts is a little low , so I temporarily just support the delegates that are working for bts2.0
64
General Discussion / Is there no initial seed nodes to connect after client run in version 0.9.2?
« on: June 07, 2015, 05:18:23 pm »
Is there no initial seed nodes to connect after client run in version 0.9.2?
65
General Discussion / if private key of one account is leak out, other account in this wallet is safe
« on: June 06, 2015, 05:55:33 am »
if private key of one account is leak out, other account in this wallet is safe
each private key of account in wallet is individual? I think if each private of account is individual, then all other account are safety if private of one account was leak out in this wallet.
but I heard somewhere , there is a private key of wallet ? all private of account in wallet has some relationship ?
each private key of account in wallet is individual? I think if each private of account is individual, then all other account are safety if private of one account was leak out in this wallet.
but I heard somewhere , there is a private key of wallet ? all private of account in wallet has some relationship ?
66
中文 (Chinese) / 用bitcny众筹，为你节约成本。
« on: May 30, 2015, 01:09:01 pm »
我一直说bitcny要被更多的使用的话，那一定是使用bitcny会更低成本，比如时代用bitcny充值，我相信时代是一种支持的态度，但我想时代使用bitcny充值肯定要比用代理充值或多或少成本低，至少代理提成这点成本可以省下来。而且比用代理充值方便多了，而在圈内众筹领域，如果实用bitcny作为支付方式，那么也可以为发起者省下不少成本。
在虚拟货币社区常常有很多众筹项也就是ipo，有些可能纯粹忽悠，有些想真正做事。他们的众筹方式无非两种，通过btc和通过支付宝。两种方式都有很大的缺点
第一种通过btc，由于btc价格是波动的，在众筹期间如果btc价格波动太大，会让部分参与者谋受损失。可能对于本身就持有btc的参与者影响不大，但对于用法币买入btc的参与者来说却是实实在在的损失。众筹后资金的保存也是一个难题，如果继续用btc保存那么就会承受btc波动的风险，如果btc价格跌了，资金损失项目不能按预算进行，我所知道的几个使用btc的众筹项目，btc严重跌价是项目失败的一个重要原因。 如果换成法币保存，很难公开花费明细，这点限制本身就会降低众筹的吸引力。
第二种通过支付宝众筹，他的缺点是从众筹开始阶段项目就变的不透明，同时还需要花费人力去统计每个参与者的资金数，因为很多项目最后都涉及到权益类资产的分配，还需要花费力气去统计每个参与者的权益账户／地址。这切无疑增加了成本。
如果是通过bitcny众筹。
1.bitcny价值稳定，众筹资金任何时候都可以保值。
2.无需要格外的人力去统计参与者，可以自动快照出参与者份额和账户，大大减少成本。
3.可以保值每笔花费都可以实时公开，使用多重签名的话，还可以保值资金不被乱花费。
在虚拟货币社区常常有很多众筹项也就是ipo，有些可能纯粹忽悠，有些想真正做事。他们的众筹方式无非两种，通过btc和通过支付宝。两种方式都有很大的缺点
第一种通过btc，由于btc价格是波动的，在众筹期间如果btc价格波动太大，会让部分参与者谋受损失。可能对于本身就持有btc的参与者影响不大，但对于用法币买入btc的参与者来说却是实实在在的损失。众筹后资金的保存也是一个难题，如果继续用btc保存那么就会承受btc波动的风险，如果btc价格跌了，资金损失项目不能按预算进行，我所知道的几个使用btc的众筹项目，btc严重跌价是项目失败的一个重要原因。 如果换成法币保存，很难公开花费明细，这点限制本身就会降低众筹的吸引力。
第二种通过支付宝众筹，他的缺点是从众筹开始阶段项目就变的不透明，同时还需要花费人力去统计每个参与者的资金数，因为很多项目最后都涉及到权益类资产的分配，还需要花费力气去统计每个参与者的权益账户／地址。这切无疑增加了成本。
如果是通过bitcny众筹。
1.bitcny价值稳定，众筹资金任何时候都可以保值。
2.无需要格外的人力去统计参与者，可以自动快照出参与者份额和账户，大大减少成本。
3.可以保值每笔花费都可以实时公开，使用多重签名的话，还可以保值资金不被乱花费。
67
中文 (Chinese) / 一句话说明BTA2.0
« on: May 30, 2015, 04:09:24 am »
一种货币稳定需要很多因素，比如人民的预期，信心，等等，但我感觉最根本的因数还是，供给和需求的平衡；当然这个需求包含了很多类型，比如，投机需求，保值需求，支付需求，在bts 内盘应该还有一个平仓需求。
如果供给大于了需求，那么这个货币肯定贬值，同理如果供给小于需求那么这个货币肯定增值，这个道理大家都知道，但怎么让供给跟踪需求呢？这应该是很大的一个难题。
BTA(后面用bitusd代替）的供给方式只有一种那就是 做空bitusd.下面来说说做空bitusd 的过程。
做空bitusd 可以分解成两个部分。
1.抵押2倍的bts，向bts系统借出1倍的bitusd，并且用这个借出来的bitusd 去买入bts。
2.如果成功买入bts，那么将买入的bts 同样抵押给系统。
可以看出short过程完成后，抵押了3倍价格的bts，向市场供给1倍价格bitusd。如果只供给不回收，由于市场的供给是非理性的，当bitusd的供给大于需求的时候必然导致bitusd贬值。所以也就来平仓的规则，short 方再某个特定的条件下必须回收自己制造出来的bitusd.
现有的规则是
1.如果bts贬值导致自己的抵押不足。
2.Short 30天后。
我们可以看出，这两条回收bitusd 流动性的规则可以回收bitusd 但他和bitusd是否供给大于需求 没有特别的关系。
这就好比得了炎症用抗生素治疗没有错，但不知道应该用多少量，类比过来也就是 应该30天平仓呢，还是60天平仓呢，还是一年平仓呢？
而在2.0中
只有当bta的需求小于供应的时候，才要求回收流动性，也是要求bts short方平仓（清算）
因为前面说需求有很多种，投机的，保值的，平仓的，甚至还有bitusd丢失了的（bitusd丢失我认为是永久持有bitusd),很难跟踪。但可以用一个指标来反应，那就是人们不想持有bitusd的时候就代表bitusd需求不足了，需求不足怎么办，当然是要求short方平仓啊（在bta2.0 是转换了一种方式，但逻辑和平仓类似，这里不详说）
所以我用一句话来说明bta2.0
当人们不想持有bta的时候，系统就开始回收流动性。
如果供给大于了需求，那么这个货币肯定贬值，同理如果供给小于需求那么这个货币肯定增值，这个道理大家都知道，但怎么让供给跟踪需求呢？这应该是很大的一个难题。
BTA(后面用bitusd代替）的供给方式只有一种那就是 做空bitusd.下面来说说做空bitusd 的过程。
做空bitusd 可以分解成两个部分。
1.抵押2倍的bts，向bts系统借出1倍的bitusd，并且用这个借出来的bitusd 去买入bts。
2.如果成功买入bts，那么将买入的bts 同样抵押给系统。
可以看出short过程完成后，抵押了3倍价格的bts，向市场供给1倍价格bitusd。如果只供给不回收，由于市场的供给是非理性的，当bitusd的供给大于需求的时候必然导致bitusd贬值。所以也就来平仓的规则，short 方再某个特定的条件下必须回收自己制造出来的bitusd.
现有的规则是
1.如果bts贬值导致自己的抵押不足。
2.Short 30天后。
我们可以看出，这两条回收bitusd 流动性的规则可以回收bitusd 但他和bitusd是否供给大于需求 没有特别的关系。
这就好比得了炎症用抗生素治疗没有错，但不知道应该用多少量，类比过来也就是 应该30天平仓呢，还是60天平仓呢，还是一年平仓呢？
而在2.0中
只有当bta的需求小于供应的时候，才要求回收流动性，也是要求bts short方平仓（清算）
因为前面说需求有很多种，投机的，保值的，平仓的，甚至还有bitusd丢失了的（bitusd丢失我认为是永久持有bitusd),很难跟踪。但可以用一个指标来反应，那就是人们不想持有bitusd的时候就代表bitusd需求不足了，需求不足怎么办，当然是要求short方平仓啊（在bta2.0 是转换了一种方式，但逻辑和平仓类似，这里不详说）
所以我用一句话来说明bta2.0
当人们不想持有bta的时候，系统就开始回收流动性。
68
General Discussion / question about private key of BTS
« on: May 27, 2015, 03:40:08 pm »
I read bts code recently ,but I am a newbee of code . so many question about it
I notice private class
just use this union to record private key ?
union {
T _align;
char _data;
}
I notice private class
just use this union to record private key ?
union {
T _align;
char _data
}
69
General Discussion / if you want to vote negative vote to all 100% delegate.
« on: May 26, 2015, 04:31:15 pm »
I am a supporter of block-chain hire , but I think there are many bts -holder that is opposed to delegates with 100% pay.
so I think we must give a way to them to oppose all 100% delegates . if they cannot express their view by vote ,they maybe sell their bts ,this would make price of BTS drop, delegate income would become less because low price of bts.
but there is no negative vote with direct methods.
but people can vote his negative vote indirectly by voting all 3% delegates
so if you want to oppose all 100% delegates you can do as follow
1.Un-appove all delegate
2.Click this link bts:negative-vote/approve approve my delegate this is a 1% pay rate delegate , vote all 3% delegate in top 101
3. then vote you delegate "As My delegates Recommanded"
so I think we must give a way to them to oppose all 100% delegates . if they cannot express their view by vote ,they maybe sell their bts ,this would make price of BTS drop, delegate income would become less because low price of bts.
but there is no negative vote with direct methods.
but people can vote his negative vote indirectly by voting all 3% delegates
so if you want to oppose all 100% delegates you can do as follow
1.Un-appove all delegate
2.Click this link bts:negative-vote/approve approve my delegate this is a 1% pay rate delegate , vote all 3% delegate in top 101
3. then vote you delegate "As My delegates Recommanded"
70
General Discussion / Peer 24.229.107.109:4584 disconnected us: You offered us a block that we reject
« on: May 24, 2015, 03:48:38 pm »
what is wrong ?
Peer 24.229.107.109:4584 disconnected us: You offered us a block that we reject as invalid
this node attack network?
Peer 24.229.107.109:4584 disconnected us: You offered us a block that we reject as invalid
this node attack network?
72
General Discussion / Let us vote out all 100% marketing delegate , we don`t know what they really do
« on: May 19, 2015, 09:00:19 am »
Let us vote out all 100% marketing delegate , we don`t know what they really do
73
General Discussion / Theoretical maximum supply 3,685,688,577 BTS
« on: May 15, 2015, 09:25:20 am »
The least theoretical maximum supply:3,685,688,577 BTS
74
General Discussion / Vote for delegate with a term.
« on: May 10, 2015, 04:38:20 pm »
I notice all 100% delegate except developer delegate ,
they would very active when vote competition, but after they was voted in 101, basically less speak on this forum , maybe they work hard on marketing ,but I the progress is very slow.
so suggest that the vote should have a a term. like 3 months or 6 months,
they would very active when vote competition, but after they was voted in 101, basically less speak on this forum , maybe they work hard on marketing ,but I the progress is very slow.
so suggest that the vote should have a a term. like 3 months or 6 months,
75
General Discussion / Let decrease block interval to 2s,but only increase 8M total block size.
« on: May 10, 2015, 09:00:40 am »
if we decrease block interval , it would decease confirm time, but it would increase block size, become each block is 188B size at least.
I `d like to introduce a block-chain model to decrease block interval but never increase block size so much.
1.there is a buffer -chain parallel with main chain. the buffer chain include all TX as normal block-chain.
2.this buffer-chain only keep 1 day , it mean buffer chain 1 days ago would been discard.
3.block interval of buffer -chain is b1 second that is less than main-chain m1 second
4.as follow picture show head of each block in main chain have to include the previous block hash in main chain , also include the recently block in buffer chain, set m1/b1=integer,
5.include all translation in blocks in buffer-chain that between block in main -chain. , so all TX have been included in main-chain ,the we can discard the buffer chain now ,
I `d like to introduce a block-chain model to decrease block interval but never increase block size so much.
1.there is a buffer -chain parallel with main chain. the buffer chain include all TX as normal block-chain.
2.this buffer-chain only keep 1 day , it mean buffer chain 1 days ago would been discard.
3.block interval of buffer -chain is b1 second that is less than main-chain m1 second
4.as follow picture show head of each block in main chain have to include the previous block hash in main chain , also include the recently block in buffer chain, set m1/b1=integer,
5.include all translation in blocks in buffer-chain that between block in main -chain. , so all TX have been included in main-chain ,the we can discard the buffer chain now ,
