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 ... 18 19 20 21 22 23 24 [25] 26 27 28 29
361
it is fine to let the developer make the final decision for the third party DACs, but for the DAC which will be developed by 3I, most of the resource come from the AGSer. isn't it reasonable to allocate more shares for AGSer?

Should we allocate more shares for the AGSer in the coming DACs, let us say not 50/50 for PTS/AGS, but 60/40, 70/30...., coz i think the AGSer shows more support and confidence for the project ,without the AGSer, the crowdfunding would not such successful as we are seeing now, the AGSer contributes more for 3I, even for the DAC industry. there is a Chinese proverb:get more pay for more work done.

This decision must be made by the developers of each new DAC based upon their marketing and business plans.

As long as they treat both PTS and AGS equally with the first 10% each, they have honored the Social Consensus.

Now, they need to tune the remaining 80% to make their DAC successful.  If they need to attract donations, then emphasize a pool of proven patron donors - like AGS.  If they want to attract people who buy and hold liquid shares in the whole industry, or a specialized industry sector, then emphasize a deal tuned for PTS or one of its proto-children.

Whatever they choose, they must remember to ask what opportunity they are leaving open for their competitors to fork some other, "better" mix.

In the end, smart developers will do whatever gives them the best competitive edge for their new DAC. 

Market forces rule.

 :)

362
Should we allocate more shares for the AGSer in the coming DACs, let us say not 50/50 for AGS/PTS, but 60/40, 70/30...., coz i think the AGSer shows more support and confidence for the project ,without the AGSer, the crowdfunding would not such successful as we are seeing now, the AGSer contributes more for 3I, even for the DAC industry. there is a Chinese proverb:get more pay for more work done.

363
中文 (Chinese) / Re: 动态加密
« on: March 30, 2014, 03:33:38 am »
犯了密码学的大忌:自定义非公开加密算法。

364
Technical Support / Re: AGS from electrum
« on: March 21, 2014, 02:26:32 pm »
Just to make sure. There is no problem with donating to AGS from an electrum wallet?

You can set the electrum wallet to create new addresses everytime you receive or send. So this doesnt let me look up my balance. But that souldnt matter for the ability to claim BTS with the private keys provided by the electrum wallet?

I think it is ok to claim the xts with electrum wallet,seems the qt,electrum ,MultiBit and Armory wallet are supported currently . it does not matter even if the electrum is not supported, you could export your private key and import to other wallet.

365
好文章,受益匪浅。

366
Technical Support / Re: Compiling Bitshares in Ubuntu
« on: March 14, 2014, 03:22:32 am »
i tried to compile in ubuntu,but got the enclosed error below, any idea?

Quote
Linking CXX executable bts_server
`.text._ZN5boost16exception_detail10bad_alloc_D2Ev' referenced in section `.text._ZN5boost16exception_detail10bad_alloc_D1Ev[_ZN5boost16exception_detail10bad_alloc_D1Ev]' of /usr/local/lib/libboost_thread.a(thread.o): defined in discarded section `.text._ZN5boost16exception_detail10bad_alloc_D2Ev[_ZN5boost16exception_detail10bad_alloc_D5Ev]' of /usr/local/lib/libboost_thread.a(thread.o)
`.text._ZN5boost16exception_detail14bad_exception_D2Ev' referenced in section `.text._ZN5boost16exception_detail14bad_exception_D1Ev[_ZN5boost16exception_detail14bad_exception_D1Ev]' of /usr/local/lib/libboost_thread.a(thread.o): defined in discarded section `.text._ZN5boost16exception_detail14bad_exception_D2Ev[_ZN5boost16exception_detail14bad_exception_D5Ev]' of /usr/local/lib/libboost_thread.a(thread.o)
`.text._ZN5boost16exception_detail19error_info_injectorINS_21thread_resource_errorEED2Ev' referenced in section `.text._ZN5boost16exception_detail19error_info_injectorINS_21thread_resource_errorEED1Ev[_ZN5boost16exception_detail19error_info_injectorINS_21thread_resource_errorEED1Ev]' of /usr/local/lib/libboost_thread.a(thread.o): defined in discarded section `.text._ZN5boost16exception_detail19error_info_injectorINS_21thread_resource_errorEED2Ev[_ZN5boost16exception_detail19error_info_injectorINS_21thread_resource_errorEED5Ev]' of /usr/local/lib/libboost_thread.a(thread.o)
`.text._ZN5boost16exception_detail19error_info_injectorINS_10lock_errorEED2Ev' referenced in section `.text._ZN5boost16exception_detail19error_info_injectorINS_10lock_errorEED1Ev[_ZN5boost16exception_detail19error_info_injectorINS_10lock_errorEED1Ev]' of /usr/local/lib/libboost_thread.a(thread.o): defined in discarded section `.text._ZN5boost16exception_detail19error_info_injectorINS_10lock_errorEED2Ev[_ZN5boost16exception_detail19error_info_injectorINS_10lock_errorEED5Ev]' of /usr/local/lib/libboost_thread.a(thread.o)
`.text._ZN5boost16exception_detail19error_info_injectorINS_15condition_errorEED2Ev' referenced in section `.text._ZN5boost16exception_detail19error_info_injectorINS_15condition_errorEED1Ev[_ZN5boost16exception_detail19error_info_injectorINS_15condition_errorEED1Ev]' of /usr/local/lib/libboost_thread.a(thread.o): defined in discarded section `.text._ZN5boost16exception_detail19error_info_injectorINS_15condition_errorEED2Ev[_ZN5boost16exception_detail19error_info_injectorINS_15condition_errorEED5Ev]' of /usr/local/lib/libboost_thread.a(thread.o)
`.text._ZN5boost16exception_detail19error_info_injectorINS_6system12system_errorEED2Ev' referenced in section `.text._ZN5boost16exception_detail19error_info_injectorINS_6system12system_errorEED1Ev[_ZN5boost16exception_detail19error_info_injectorINS_6system12system_errorEED1Ev]' of /usr/local/lib/libboost_chrono.a(chrono.o): defined in discarded section `.text._ZN5boost16exception_detail19error_info_injectorINS_6system12system_errorEED2Ev[_ZN5boost16exception_detail19error_info_injectorINS_6system12system_errorEED5Ev]' of /usr/local/lib/libboost_chrono.a(chrono.o)
collect2: error: ld returned 1 exit status
make[2]: *** [bts_wallet/bts_server] Error 1
make[1]: *** [bts_wallet/CMakeFiles/bts_server.dir/all] Error 2
make: *** [all] Error 2

367
as we know,the genisis.json is generated from third party tool, how can we verify if the bts allocation in genesis.json which used to initial the bts genesis block is correct and not manually modified.

368
General Discussion / Re: BitShares X Status Update
« on: March 01, 2014, 07:12:30 am »
Daniel ,what does your signature mean?
Quote
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

369
General Discussion / Re: GET YOUR BTS XT Wallet Here!
« on: March 01, 2014, 12:58:23 am »
has the snapshot completed?

370
General Discussion / Re: Script to calculate BitAsset prices
« on: February 25, 2014, 08:19:18 am »
it would be nice

371
中文 (Chinese) / Re: 成立BTS基金会的提议
« on: February 25, 2014, 08:09:51 am »
提议很好,不过3i不会同意的。理由你懂的。

372
中文 (Chinese) / Re: 修改强制平仓算法
« on: February 17, 2014, 02:35:21 pm »
Quote
拿抵押的BTS买

Quote
现在的平仓算法是直接拿抵押的BTS按卖单的价购买

好绕,这两个有什么不一样吗?

373
中文 (Chinese) / Re: 修改强制平仓算法
« on: February 17, 2014, 02:10:32 pm »
Quote
网络强制挂出一个买单:按  1000usd/1.5bts 的价格,买 1000 usd。
如何强制,强制谁买?
BTC网络强制挂单,挂一个买单,拿 1.5bts买 1000bitusd。
可以和bitusd的卖单撮合

拿谁的bts来买?哪里来的私钥用来签名买单?

374
中文 (Chinese) / Re: 修改强制平仓算法
« on: February 17, 2014, 01:18:59 pm »
Quote
网络强制挂出一个买单:按  1000usd/1.5bts 的价格,买 1000 usd。
如何强制,强制谁买?

375
General Discussion / Re: BitShares X Status Update
« on: February 17, 2014, 12:28:39 pm »
2 issues seems are identified in margin call algorithm, please find the detail in highlighted below, not sure if i misunderstood the logic,please correct me if so.

issue 1:
Quote
                  if( payoff > bid_usd )
                         { // consume the full bid, leaving a balance on the call
                            loan_amount         += bid_usd;
                            collateral_amount   += bid_usd * call_price;// line 474 of blockchain_db.cpp,why not double collateral in this short position?half from long bid, half from cover, should be bid_usd * call_price+bid_usd * call_price?

                            working_call.amount -= bid_usd * call_price;
                            cover_claim.payoff  -= bid_usd;

                            // add bid as input, and give the bidder their new cover position
                            market_trx.inputs.push_back( bid_itr->location );
                            market_trx.outputs.push_back(
                                       trx_output( claim_by_cover_output(loan_amount, bid_payout_address), collateral_amount) );
                            collateral_amount = asset();
                            loan_amount = asset( 0.0, quote );

                            // goto next bid
                            ++bid_itr;
                            if( bid_itr != bids.rend() ) working_bid = get_output( bid_itr->location );
                         }

issue 2:
Quote
else // payoff == bidusd
                         { // consume full call and bid..
                            auto cover_amount    = bid_usd * call_price;
                            loan_amount         += bid_usd;
                            collateral_amount   += cover_amount + cover_amount; // collat from bid+cover
                            working_call.amount -= cover_amount;

                            market_trx.outputs.push_back(
                                       trx_output( claim_by_cover_output( loan_amount, bid_payout_address ), collateral_amount) );
                     //line 521 of blockchain_db.cpp ,why needn't reset the variables collateral_amount and loan_amount after pushing short position output,won't it cause the incorrect output in next round  matching, is following code required?
                            collateral_amount = asset();
                            loan_amount = asset( 0.0, quote );

                           
                            if( working_call.amount.get_rounded_amount() > 0 )
                            {
                               // TODO.. charge a 5% fee
                               market_trx.outputs.push_back(
                                       trx_output( claim_by_signature_output( cover_claim.owner ), working_call.amount ) );
                            }

                            market_trx.inputs.push_back( call_itr->location );
                            market_trx.inputs.push_back( bid_itr->location );

                            ++bid_itr;
                            if( bid_itr != bids.rend() ) working_bid = get_output( bid_itr->location );

                            ++call_itr;
                            if( call_itr != margin_positions.end() )
                            {
                               working_call = get_output( call_itr->location );
                               cover_claim  = working_call.as<claim_by_cover_output>();
                            }
                         }

Pages: 1 ... 18 19 20 21 22 23 24 [25] 26 27 28 29