961
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.
962
General Discussion / Re: All users, please upgrade your client version to 0.4.4
« on: August 20, 2014, 11:42:45 pm »
http://bitsharesblocks.com/#/blocks and http://x.bitmeat.com/ seem to be on minority forks
963
General Discussion / Re: How to adjust my delegate burn ratio after I have already registered?
« on: August 20, 2014, 11:02:53 pm »After selecting your account in the GUI, go to "Edit" check the "delegate" box and change rate. You don't have to pay the delegate fee again, just a normal transaction fee.
Remember you can go down in pay rate, but you can't increase it.
Hi, sorry I forgot to mention I'm running on ubuntu commandline (since I'm told it's not recommended to run in gui). How to do from command line?
Use wallet_account_update_registration command
964
General Discussion / Re: All users, please upgrade your client version to 0.4.4
« on: August 20, 2014, 02:52:25 am »
Again, new market engine will be enabled on block 274000. A specific market will not start matching orders until 51 delegates have published a price feed for it.
I recommend upgraded delegates do not publish any price feeds until the community has confirmed that remaining delegates, exchanges, and seed nodes have upgraded for the hardfork.
I recommend upgraded delegates do not publish any price feeds until the community has confirmed that remaining delegates, exchanges, and seed nodes have upgraded for the hardfork.
965
General Discussion / Re: Dry Run 16 - Armageddon ($5000 Bounty inside)
« on: August 19, 2014, 11:11:08 pm »Here is what I am seeing:Code: [Select]default (unlocked) >>> blockchain_market_order_book USD XTS
BIDS (* Short Order) | ASKS
TOTAL QUANTITY PRICE | PRICE QUANTITY TOTAL COLLATERAL
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
27.6359 USD MARKET PRICE | 0.011363636364 USD 88,000.00000 XTS 999.9999 USD
9,798.9999 USD 881,910.00000 XTS 0.011111111111 USD*| 0.100000000000 USD 100,000.00000 XTS 10,000.0000 USD
9,999.9999 USD 1,200,000.00000 XTS 0.008333333333 USD*|
10,000.0000 USD 2,000,000.00000 XTS 0.005000000000 USD*|
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| MARGIN
| CALL PRICE QUANTITY TOTAL COLLATERAL
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
| 0.008571428476 USD 1,050,000.00000 XTS 8,999.9999 USD 1,400,000.00000 XTS
| 0.008571428476 USD 1,050,000.00000 XTS 8,999.9999 USD 1,400,000.00000 XTS
| 0.008426966292 USD 1,335,000.00000 XTS 9,999.9999 USD 1,780,000.00000 XTS
| 0.008426966292 USD 13,349.99998 XTS 99.9999 USD 17,799.99998 XTS
| 0.008426966292 USD 13,350.00000 XTS 99.9999 USD 17,800.00000 XTS
| 0.008389261745 USD 134,100.00000 XTS 999.9999 USD 178,800.00000 XTS
| 0.008333333333 USD 135.00000 XTS 0.9999 USD 180.00000 XTS
| 0.008333333333 USD 27,135.00000 XTS 200.9997 USD 36,180.00000 XTS
| 0.008241758242 USD 13,650.00000 XTS 99.9999 USD 18,200.00000 XTS
| 0.003787863636 USD 13,200.00000 XTS 49.9998 USD 17,600.00000 XTS
Average Price in Recent Trades: 0.01109056481093343 USD / XTS Maximum Short Price: 0.01478741974791124 USD / XTS Minimum Cover Price: 0.00739370987395562 USD / XTS
Bid Depth: 4,081,910.00000 XTS Ask Depth: 5,054,559.99999 XTS Min Depth: 2,000,000.00000 XTS
Here are my questions:
- What is the 27.6359 USD in the top left?
This is no longer relevant for market-issued assets and has been removed just now. For user-issued assets, this represents the accumulated fees of that asset which will be traded for XTS once at least 10,000 shares have been accumulated to avoid dust.
966
General Discussion / Re: Delegates and seed nodes, upgrade your client version to 0.4.2
« on: August 19, 2014, 09:13:09 pm »967
General Discussion / Re: Ethereum & BitShares Partnership?
« on: August 19, 2014, 09:09:07 pm »I've complained many times about provocative thread titles that mislead people, specifically coming from Bytemaster, since forever.I agree with Adam here... Dan should know better.
For somebody that posts 75-100 post a day, I refused to post in this thread up to now. Above is more or less the reason I did so.
http://www.reddit.com/r/ethereum/comments/2e0q0a/bitshares_guy_here_sorry_we_caused_such_a_stir_we/
968
General Discussion / Re: Delegates and seed nodes, upgrade your client version to 0.4.2
« on: August 19, 2014, 02:59:25 pm »
Delegates do NOT publish price feeds until confident all delegates and users are upgraded. Publish price feed operation will officially hardfork the chain and freeze old clients. We recommended all delegates wait until latest XTS testnet is thoroughly tested to *your* satisfaction before publishing price feed.
969
General Discussion / Re: Delegates and seed nodes, upgrade your client version to 0.4.2
« on: August 19, 2014, 02:46:23 pm »For those of us without the tools/skills to compile?This is a version only for delegates, exchanges, and seed nodes. GUI version will be provided later.
You are saying only people who have these skills/tools are allowed to be delegates? I know there are more than just myself who are current delegates that probably need the GUI.
If this is a requirement, please vote me out. I would prefer that route rather than to start missing blocks because I am late to the game. Plus I could kill my VPS sooner.
Thanks!
We do not recommend running delegates with the GUI. You are free to do so of course, but we do not test or provide support for this.
970
General Discussion / Re: Dry Run 15: Fifteen ( Market GUI ! )
« on: August 19, 2014, 01:14:29 am »I think the average price is still not hard to manipulate
current_bid->get_price() maybe very highCode: [Select]// TODO: rename avg_price_24h to average_price_1h
market_stat->avg_price_24h.ratio *= (BTS_BLOCKCHAIN_BLOCKS_PER_HOUR-1);
// limit the maximum movement rate of the price.
if( _current_bid->get_price() > min_cover_ask )
market_stat->avg_price_24h.ratio += _current_bid->get_price().ratio;
else
market_stat->avg_price_24h.ratio += min_cover_ask.ratio;
if( _current_ask->get_price() < max_short_bid )
market_stat->avg_price_24h.ratio += _current_ask->get_price().ratio;
else
market_stat->avg_price_24h.ratio += max_short_bid.ratio;
market_stat->avg_price_24h.ratio /= (BTS_BLOCKCHAIN_BLOCKS_PER_HOUR+1);
When this section of code is called, all matching orders should have been filled. So any high bids would have been filled, leaving current_bid at this point to be the highest bid which no longer matches any asks.
In other words, the average only counts the average of the spread on each block after filling all orders.
Actually, this does make me aware of a potential bug. It may be the case that this line: https://github.com/BitShares/bitshares_toolkit/blob/03dbac9fd674aae29d50cdab2685318c47c89667/libraries/blockchain/market_engine.cpp#L324 should come AFTER this line: https://github.com/BitShares/bitshares_toolkit/blob/03dbac9fd674aae29d50cdab2685318c47c89667/libraries/blockchain/market_engine.cpp#L390
I will verify with bytemaster.
971
General Discussion / Re: Dry Run 15: Fifteen ( Market GUI ! )
« on: August 19, 2014, 12:57:50 am »I think the average price is still not hard to manipulate
current_bid->get_price() maybe very highCode: [Select]// TODO: rename avg_price_24h to average_price_1h
market_stat->avg_price_24h.ratio *= (BTS_BLOCKCHAIN_BLOCKS_PER_HOUR-1);
// limit the maximum movement rate of the price.
if( _current_bid->get_price() > min_cover_ask )
market_stat->avg_price_24h.ratio += _current_bid->get_price().ratio;
else
market_stat->avg_price_24h.ratio += min_cover_ask.ratio;
if( _current_ask->get_price() < max_short_bid )
market_stat->avg_price_24h.ratio += _current_ask->get_price().ratio;
else
market_stat->avg_price_24h.ratio += max_short_bid.ratio;
market_stat->avg_price_24h.ratio /= (BTS_BLOCKCHAIN_BLOCKS_PER_HOUR+1);
When this section of code is called, all matching orders should have been filled. So any high bids would have been filled, leaving current_bid at this point to be the highest bid which no longer matches any asks.
In other words, the average only counts the average of the spread on each block after filling all orders.
972
General Discussion / Re: Delegates and seed nodes, upgrade your client version to 0.4.1
« on: August 18, 2014, 10:52:57 pm »
A round consists of 101 blocks (not timeslots). Assuming you have only 1 active delegate, once you produce your first block 1 <= k <= 101 in the round, you will either produce after the next shuffle or produce again in the same round if many others are missing blocks. In both cases, the exact time of your next production is unknown until at least (101 - k) time slots have passed.
The get_info output tries to reflect this uncertainty in a somewhat user-friendly way by printing "at least ..." when appropriate. This is purely a display enhancement and does not affect the actual scheduling of block production.
I did find a bug in the display calculation which I've fixed: https://github.com/BitShares/bitshares_toolkit/commit/4d67f6fcf34ea7e382a929696adb970509ee7614
The get_info output tries to reflect this uncertainty in a somewhat user-friendly way by printing "at least ..." when appropriate. This is purely a display enhancement and does not affect the actual scheduling of block production.
I did find a bug in the display calculation which I've fixed: https://github.com/BitShares/bitshares_toolkit/commit/4d67f6fcf34ea7e382a929696adb970509ee7614
973
General Discussion / Re: Dry Run 15: Fifteen ( Market GUI ! )
« on: August 17, 2014, 12:54:50 am »https://www.youtube.com/watch?v=Pb-K2tXWK4w
1) You can now increase the call price of a cover order
(5% fee still applies)
2) Switched to 1 hour moving price average rather than feeds
3) You now need 51 delegates to publish a feed (up from 3)
4) The client now warns you if you are making a bid or ask that is 5% worse than best price
GUI's hosted by our UI dev Valentine:
http://valzav.com/BitSharesXT.dmg
https://www.dropbox.com/s/0adsrsaw28v9zbd/BitSharesXT-0.0.15.exe
md5's:
Windows: a1fd771b49d22ff4ebc15c9a80a6ac28
OSX (.dmg): 0d66cbbfb05f37c8d457b00daa37dab1
yesterday i created 20 usd with 84 xts , is it a bug ?Code: [Select]{"type":"ask_op_type","data":{"amount":4200000,"ask_index":{"order_price":{"ratio":"0.047619047619047616","quote_asset_id":22,"base_asset_id":0},"owner":"XTS7wvWjSuuFszcVHis3PcAtPjMJTjuWWeYb"}}}
{"type":"short_op_type","data":{"amount":4200000,"short_index":{"order_price":{"ratio":"0.047619047619047616","quote_asset_id":22,"base_asset_id":0},"owner":"XTS4ukE6dmDYkp3fxEKmtHRm3f3M4VN6579c"}}}
Transaction #dffe91ef
This seems like it should have created 2 USD not 20. Can you post your transaction history?
974
General Discussion / Re: Dry Run 15: Fifteen ( Market GUI ! )
« on: August 16, 2014, 07:57:40 pm »@alt: so all is fine now? market is still safe?no, control the average price to higher is still very quickly, only need 1 block.
control to low price is more difficult.
In fact, this is not a big problem, we can get the medium price just like feed price, sort and use the middle price.
and use a time more than 1 hour.
what I am worried about is the rule:
1. margin call can create bts, this can be use to attack the whole system. I still prefer just clear the short position can't be cover.
2. the short price is limit, if the limit is too lower for some reason, like a sudden price grow of bts, nobody ask with a lower price, and no asset can be create.
I have post for my thought here.I have no doubt that market consensus will make bitusd track the price of USD.
but the rules with leak will break the market consensus.
the rules with too many limit will stop the market consensus.
I think we should make a rule with less limit, and without leak.
here is my solution.
the main different is the short bitusd is separate from bid XTS.
for example:
If I want to short 100 bitUSD with price 1bitUSD/xts, I need to freeze 200 XTS, and I can get 100 bitUSD immediately.
then I can usd these bitUSD to buy XTS with a different price, for bit order. maybe 0.5 bitUSD/XTS or whatever, there is no limit for the price of bid order.
the same, there is no limit for the price of ask order. there is no limit for the market depth check.
the key is to limit the short price.
the maximum short price is coming from the minimum matched bid price of latest blocks(maybe latest 24*60*6 blocks).
at the beginning there is no matched bid price, we can set a safety initial limit price, come from the central trade market, like 0.01USD/XTS.
What are your thoughts on bytemaster's latest revision?
975
General Discussion / Re: Dry Run 15: Fifteen ( Market GUI ! )
« on: August 16, 2014, 03:49:42 am »
Try any of:
Code: [Select]
network_add_node "69.164.192.144:33863"
network_add_node "180.153.142.120:8764"
network_add_node "207.12.89.119:1776"
network_add_node "114.215.104.153:1776"
network_add_node "188.138.107.159:45883"
network_add_node "188.138.107.159:58090"
