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 2 3 4 5 6 [7] 8 9 10 11 12 13 14 ... 21
91
空单基本都只能在price feed筑墙了,而且利率还不能太低。反正我每次看short wall都是几百万BTS。我的理解是这个故意设计成这样好让空单给利息。

92
中文 (Chinese) / Re: JustDice风格的骰子DAC提议(JDS)
« on: November 13, 2014, 01:49:48 pm »
win下客户端编译好了,就是运行报错,出错模块在qtcore.dll上,可能跟版本有关吧,我再想想办法.
多谢,我也没有编译过windows版,所以还请多费心。

另外我查了下fork的时间大概是Sep 17,你可以把所有的submodule都调到对应日期的版本试试。

93
中文 (Chinese) / Re: JustDice风格的骰子DAC提议(JDS)
« on: November 08, 2014, 02:08:53 pm »
最近比较忙,另外身体也不太好,需要找合作者处理测试网络及发布准备。

合作者主要处理以下事务:
1、负责测试网络准备及windows exe编译。处理windows相关bug的修复。
2、准备/发布测试信息及处理dry run dice competition组织,测试JDS分发及奖金统计
3、提供1-2个正式版本的seed node
4、发布正式版本及合规处理(类似dac sun之于bts)
5、可分享一定的JDS开发基金

有意者请PM我或微博联系。

94
中文 (Chinese) / Re: JustDice风格的骰子DAC提议(JDS)
« on: November 07, 2014, 07:02:43 pm »
想看看1s的dpos的稳定性
1s不敢试,5s对我都已经是极限了。 :o

95
中文 (Chinese) / Re: JustDice风格的骰子DAC提议(JDS)
« on: November 02, 2014, 01:55:02 am »
你可能最近没有关注Play,Play的重心已经不是博彩平台,而是一个游戏币商城和二手交易所,不过第三方开发者扔可以在其上开发JDS这样的游戏.
嗯,我主要是指支持第三方构建可以看做平台。

96
旗帜鲜明的反对膨胀
这是赤裸裸的掠夺BTS用户
无论用什么口径
且只能给BTC社区一个巨大的笑柄!
3I 可以独断专行
大众只能用脚投票
看看价格吧
就知道!

POS的弊端啊。我的期望是通胀不超过BTC,而且需要承诺不只是代码固定。说实在的这个期望已经被调整了,原来说是通缩吧,现在倒好,不通缩也就罢了,来个通胀还不封顶。

97
中文 (Chinese) / Re: JustDice风格的骰子DAC提议(JDS)
« on: November 01, 2014, 01:34:06 pm »
是否有计划,开发一个博彩平台,可以有双色球,福彩等
双色球的结果,可以让代表参考真正双色球的结果发布,51%代表为有效
我的想法还是做个简单的JDS,所以目前没有这个计划。
Play是做博彩平台的。
双色球的问题,首先没有必要参考外部的结果,直接用分布式产生随机数的方式就可以了。
其次,如果是需要类似代表投票或feed外部事件的结果,据我所知有人提议叫bts vegas可以做这类事。

98
If we can with the new BitShares on Nov 5th have a some kind of constitution with an unchangeable maximum dilution rate (competitive with Bitcoin), enshrined as the first rule/principle, I personally believe that would be superior to a maximum flexibility DAC.
+5%

99
中文 (Chinese) / Re: JustDice风格的骰子DAC提议(JDS)
« on: October 31, 2014, 02:47:46 pm »
因为3i最新的调整和本人的健康原因,JDS开发有点放缓了。不过代码基本已经准备好,接下来主要是发布前的准备工作了,所以需要大家多帮忙测试。准备等DAC合并完成后做几轮Dry run同时做计划中的Dice competition,然后就找合适的合作伙伴(主要是市场和法律方面的,开发方面当然也欢迎)进行发布的准备。
关于初始股份分配,不知道参照原来的DNS方案是否还合适,大家有没有什么建议?

是否考虑过,运行在bts的块链上
运行在bts块链上可能比较小,主要有两个原因:
1 BTS现在的出块不能满足JDS要求。首先10秒时间太长,其次为了防止作弊,JDS会在每次出块后做一次shuffle以保证代表不能预先知道自己会在哪一块出块从而预先下注。
2 JDS有自己的operation和jackpot规则,就我现在的了解,是没有办法加入JDS的。

100
General Discussion / Re: 10% dilution = 650,000 BTS a day
« on: October 22, 2014, 08:54:23 pm »
It is 2/0.8=2,5

I'm wrong. It should be 2.5 billion.

101
General Discussion / Re: 10% dilution = 650,000 BTS a day
« on: October 22, 2014, 08:37:52 pm »
That is the limit.. no one will be voted in anywhere near that.

To be honest, I don't like voting and politics behind it. But anyway, how can I check the current average pay rate of top 101 delegates?

102
General Discussion / 10% dilution = 650,000 BTS a day
« on: October 22, 2014, 08:31:25 pm »
2 billion bts * (1+20%) = 2.4 billion. 2.4 billion * 10% / 365 = 657,534 bts

That makes about 650,000 bts a day. To me, this has much much bigger impact than PTS, AGS, DNS merge.

Well, btc currently has about 10% dilution but it's also decreasing along the time.

If we have to pay high to delegates at the moment, at least we should decrease the rate along the time.

103
AGSer+PTSer+BTSXer,选项4
我最担心的是可以经过shareholders投票增发。一是币量无上限,操守无下限;二是所谓的shareholders,我怎么听觉得就是3i呢。
10%我的理解是为了维护原来的DAC承诺,这样新加的东西到bts上,pts和ags也算是分到10%了,这个我勉强可以接受(屁股决定脑袋)。

104
General Discussion / Re: JDS Dry Run #2
« on: October 14, 2014, 01:29:19 am »
There's a bug in the code and it should be:

Code: [Select]
      void chain_database_impl::update_active_delegate_list( const full_block& block_data,
                                                             const pending_chain_state_ptr& pending_state )
      {
          std::vector<account_id_type> active_del;
          if( block_data.block_num % BTS_BLOCKCHAIN_NUM_DELEGATES == 0 )
          {
             // perform a random shuffle of the sorted delegate list.

             active_del = self->next_round_active_delegates();
          } else {
              active_del = self->get_active_delegates();
          }
             auto rand_seed = fc::sha256::hash(self->get_current_random_seed());
             uint32_t block_index = block_data.block_num % BTS_BLOCKCHAIN_NUM_DELEGATES;
             size_t num_del = active_del.size();
uint32_t signee_delegate_index = -1;
if (block_index!=0) {
    //from 0 to where the block signee, we need to swap them to tail to ensure they can only particapant once in a round.
    public_key_type block_signee;
    block_signee = block_data.signee();
    //get delegate's active key
    for (uint32_t i=0;i<num_del;++i) {
        auto delegate_record = pending_state->get_account_record( active_del[i] );
        FC_ASSERT( delegate_record.valid() && delegate_record->is_delegate() );
       
        if (delegate_record->active_key()==block_signee) {
            signee_delegate_index = i;
            break;
        }
    }
}
             for( uint32_t i = signee_delegate_index+1; i < num_del; ++i )
             {
                for( uint32_t x = 0; x < 4 && i < num_del; ++x, ++i )
                   std::swap( active_del[i], active_del[[b]i+(rand_seed._hash[x]%(num_del-i))[/b]] );
                rand_seed = fc::sha256::hash(rand_seed);
             }

             pending_state->set_property( chain_property_enum::active_delegate_list_id, fc::variant(active_del) );
      }

105
General Discussion / Re: JDS Dry Run #2
« on: October 14, 2014, 12:35:36 am »
You are making sure that a delegate can only participate in a round once on average. 

This means that a delegate does not know in advance when he will go...but when he does get to go he can mine his secrets to make sure he gets to go next....

So you have to wait until at least N delegates have gone before you can be secure.   You gain nothing by shuffling every time. 

If you want to gain something then you need delegates to commit in advance to 101 secrets to be revealed in time and then shuffle every turn.  A delegate would not be able to mine their secret on their turn because they have pre-committed to the next 101 secrets.
It's not 1 delegate in one round but still 50 delegates a round and shuffle the rest delegates after each block.

Pages: 1 2 3 4 5 6 [7] 8 9 10 11 12 13 14 ... 21