BitShares X Status Update

[alt]

match_order for claim_long

Code: [Select]

                     if( ask_amount_usd < bid_amount_usd )
                     { // then we have filled the ask
                         pay_asker         += ask_amount_usd;
                         loan_amount       += ask_amount_usd;
I think here should change to

Code: [Select]

 
              if( ask_amount_bts < bid_amount_bts )


[bytemaster]

do this:
buy 100,000,000 usd with 1bts
short 100,000,000 usd with 1bts

then I get 100,000,000 usd, 2bts will be margin call

That looks right to me... 2 bts is the collateral.   Margin call would be at .66667 bts price point.

[alt]

do this:
buy 100,000,000 usd with 1bts
short 100,000,000 usd with 1bts

then I get 100,000,000 usd, 2bts will be margin call

[bytemaster]

I think something is not correct, but i can't write with english.

拿 bts /usd 市场看，假如现有很多买单了

10000 usd 0.01 bts/usd
800 usd 0.009 bts/usd
800 usd 0.008 bts/usd
.....

我先挂一个买单
100,000,000 usd 0.00000001 bts/usd
排在最末尾

然后我挂一个 short 操作
按 0.000000001 bts/usd 价格发行 1000,000,000 usd

是不是所有买单都能成交？大家都拿到了 bitusd，我自己也拿到了 100,000,000 bitusd。
然后下一次，我的 short 会被强制平仓，损失所有抵押的 1bts。

最终结果是 我会有1bts 抵押损失，留下大量 bitusd 空头，及 100,000,000 bitusd

应该改撮合算法。
对short 撮合算法应该按 bts 数量判断是否完成。
比如我 1bts 发行 100000 usd，只要我收到 1bts 就结束，最终结果不一定能发行 100000 usd，可能 100 usd 就结束了。
结果是2 bts 抵押 100 usd。

在系统刚运行，市场上没任何买单时，还是会有漏洞。
比如我自己做了唯一的买单是 1bts  1亿美金，唯一的 short 也是这个价。那我就是牺牲2个bts，拿到1亿美金。
程序可以限制 short 撮合算法必须在足够买单之后才能启动。

Will someone translate this for me.  Thanks. 


Sent from my iPhone using Tapatalk

[alt]

I think something is not correct, but i can't write with english.

拿 bts /usd 市场看，假如现有很多买单了

10000 usd 0.01 bts/usd
800 usd 0.009 bts/usd
800 usd 0.008 bts/usd
.....

我先挂一个买单
100,000,000 usd 0.00000001 bts/usd
排在最末尾

然后我挂一个 short 操作
按 0.000000001 bts/usd 价格发行 1000,000,000 usd

是不是所有买单都能成交？大家都拿到了 bitusd，我自己也拿到了 100,000,000 bitusd。
然后下一次，我的 short 会被强制平仓，损失所有抵押的 1bts。

最终结果是 我会有1bts 抵押损失，留下大量 bitusd 空头，及 100,000,000 bitusd

应该改撮合算法。
对short 撮合算法应该按 bts 数量判断是否完成。
比如我 1bts 发行 100000 usd，只要我收到 1bts 就结束，最终结果不一定能发行 100000 usd，可能 100 usd 就结束了。
结果是2 bts 抵押 100 usd。

在系统刚运行，市场上没任何买单时，还是会有漏洞。
比如我自己做了唯一的买单是 1bts  1亿美金，唯一的 short 也是这个价。那我就是牺牲2个bts，拿到1亿美金。
程序可以限制 short 撮合算法必须在足够买单之后才能启动。

[bytemaster]

Today I spent some time refining the wallet security and robustness.  This work is incomplete but I can summarize some of the changes:

1) Address Book for send and recv addresses can now take a label
2) the wallet.bts file can be entirely encrypted (including all of your addressbook info) separately from your private keys.
3) private keys are now always stored encrypted.
4) added ability to enter passwords without echo to console
5) Improved tracking of transactions so that I can produce a meaningful transaction history.

The current code in github compiles but does not function, I will complete this task tomorrow. 

[bytemaster]

Today I fixed some minor bugs, added support for reading a configuration file for bts_wallet and focused on updating the documentation which generated a whole host of new TODO items for me. 

You can view the latest BitShares X wallet and JSON-RPC documentation here:

http://invictus.io/bitsharesx_wallet_docs.html

This documentation is a work in progress and I am missing many calls.

According to this documentation, the feature to display transaction history seems missing.

You are correct, it currently prints your unspent outputs with the balance output.   I will have some significant wallet enhancements tomorrow that will address this.

[coolspeed]

Today I fixed some minor bugs, added support for reading a configuration file for bts_wallet and focused on updating the documentation which generated a whole host of new TODO items for me. 

You can view the latest BitShares X wallet and JSON-RPC documentation here:

http://invictus.io/bitsharesx_wallet_docs.html

This documentation is a work in progress and I am missing many calls.

According to this documentation, the feature to display transaction history seems missing.

[toast]

I just identified an missing feature that people will probably want / complain about if I don't fix.    Right now you cannot use your collateral to buy BitUSD to cover your position.  You must use additional funds to buy the BitUSD then use the BitUSD to recover your collateral.   While I am sure market participants could work around and manage the requirement to have extra BTS around so they can cover their position, we may want to resolve this issue.   

From where I sit this may require a new output type (bid with collateral) and thus this change is non-trivial to implement.   This is probably a 2-3 day task in its own right.

Put it off IMO, same class of feature as being able to pay tx fees in assets rather than bts

[bytemaster]

I just identified an missing feature that people will probably want / complain about if I don't fix.    Right now you cannot use your collateral to buy BitUSD to cover your position.  You must use additional funds to buy the BitUSD then use the BitUSD to recover your collateral.   While I am sure market participants could work around and manage the requirement to have extra BTS around so they can cover their position, we may want to resolve this issue.   

From where I sit this may require a new output type (bid with collateral) and thus this change is non-trivial to implement.   This is probably a 2-3 day task in its own right.

[bytemaster]

Today I fixed some minor bugs, added support for reading a configuration file for bts_wallet and focused on updating the documentation which generated a whole host of new TODO items for me. 

You can view the latest BitShares X wallet and JSON-RPC documentation here:

http://invictus.io/bitsharesx_wallet_docs.html

This documentation is a work in progress and I am missing many calls. 

[bytemaster]

Perhaps verbiage makes all the difference... we are decommissioning the shares.....  holding them forever in a 'share heaven' where they will live happily ever after as God rewards them for sharing with others during their life on the chain.   

[clout]

When you cover your position those BitUSD are destroyed... but if you lack enough collateral to cover it all then some BitUSD will be left in circulation despite your position being closed.

Can you use some sort of a queue for short positions so that bitassets do not need to be destroyed?

What is wrong with destroying coins?  The value has to go somewhere... either the miner or everyone. 

Nothing is wrong with destroying coins, its obviously better than paying all transaction fees to miners, particularly when they do not add to the security of the network. I just don't like the general idea of destroying things, but since you're destroying coin days all over the place, might as well destroy some coins also haha

[bytemaster]

What is wrong with destroying coins?  The value has to go somewhere... either the miner or everyone. 

[bytemaster]

When you cover your position those BitUSD are destroyed... but if you lack enough collateral to cover it all then some BitUSD will be left in circulation despite your position being closed.