BitShares Forum
Main => General Discussion => Topic started by: bytemaster on August 20, 2014, 09:15:00 pm
-
http://bitshares.org/BitSharesXT-17.dmg
This dry run includes all of the latest fixes proposed for version 0.4.5 of BTSX including:
1) Tighter short/cover restrictions (+/- 10% of moving average)
2) Fixed a rounding bug
3) New GUI features...
Known issues:
Min/Max bid/ask displayed in various places may not be updated to what the blockchain is enforcing.
Alt has earned some significant BitUSD from the prior run, I think everyone owes him a +1.... Keep testing like your investment depends upon it.
-
@Alt: +5% :P keep up great work
-
Alt has earned some significant BitUSD from the prior run, I think everyone owes him a +1.... Keep testing like your investment depends upon it.
+5% Alt, thank you very much!
As someone said in another thread - I am very happy & grateful your are on our side :)
-
how glad to see this news when I just wake up, thank you very much. ;D
来自我的 HUAWEI P7-L00 上的 Tapatalk
-
how glad to see this news when I just wake up, thank you very much. ;D
来自我的 HUAWEI P7-L00 上的 Tapatalk
alt, great work!
-
So @alt is the first person who owns bitUSD, history will remember you! +5%
-
Alt,great work
-
Alt,
Trying to follow your testing and your creative attacks on the market have been eye opening, educational, humbling, and frankly a little disturbing all at the same time. I had no idea how much I didn't know.
+5% for all you have done.
James.
-
how glad to see this news when I just wake up, thank you very much. ;D
Well earned. Great work!
-
Cheers!
-
Ditto, Brother!
-
I just (as in an hour ago) compiled from bitshares_toolkit github. so I'm running the right version, right?
if so could I get the hookup on some of that sweet sweet XTS?
XTS5wPoUzmKHdLiw8vg73SF88ZxQzJpNNv4TrJgYPYYNXWveQBnDL edit: hold up, recompiling.
also whats a good node to add? don't seem to be connecting to the network.
-
I just (as in an hour ago) compiled from bitshares_toolkit github. so I'm running the right version, right?
if so could I get the hookup on some of that sweet sweet XTS?
XTS5wPoUzmKHdLiw8vg73SF88ZxQzJpNNv4TrJgYPYYNXWveQBnDL
also whats a good node to add? don't seem to be connecting to the network.
Check to see if the delegates are producing blocks. If you did git checkout develop you should be good.
-
I just (as in an hour ago) compiled from bitshares_toolkit github. so I'm running the right version, right?
if so could I get the hookup on some of that sweet sweet XTS?
XTS5wPoUzmKHdLiw8vg73SF88ZxQzJpNNv4TrJgYPYYNXWveQBnDL
also whats a good node to add? don't seem to be connecting to the network.
Check to see if the delegates are producing blocks. If you did git checkout develop you should be good.
crap.
recompiling <_<
-
Also check blockchain_is_synced and network_get_peer_count. You can also do bitshares_client --version. Ask me why I know so many sanity checks lol.
-
Also check blockchain_is_synced and network_get_peer_count. You can also do bitshares_client --version. Ask me why I know so many sanity checks lol.
git checkout develop was what i needed to know.
went to the github, didn't see a version number, didn't know what to use.
yea im a noob.
-
Increasing the min cover ask to .90 may be better.
I am thinking what's the problem if we increasing the min cover ask to 1.0 * average price.
for 0.9, when price fall to 10/9 * 3/4 = 5/6, the short position still under attack probably,
especially when the short amount is very huge.
this possible attack maybe keep user not dare to short much usd.
-
bitshares_client --version
{
"bitshares_toolkit_revision": "945d2e8d323ef49796d8993addd73c82d7341375",
"bitshares_toolkit_revision_age": "4 hours ago",
"fc_revision": "8468f392cebb291587e0d87cdf9bef9bf167acfc",
"fc_revision_age": "7 days ago",
"compile_date": "compiled on Aug 20 2014 at 20:51:27"
}
delegates do not seem to be producing blocks.
>> network_get_peer_info
[]
>> blockchain_is_synced
false
didn't feel right when I did git checkout develop:
merockstar@merockstar-HP-Pavilion-dv6-Notebook-PC:~/bitshares_toolkit$ git checkout develop
Branch develop set up to track remote branch develop from origin.
Switched to a new branch 'develop'
-
+5% Great work!
-
+5% Great work!
is that at me? cause i'm totally not finding any peers.
-
+5% Great work!
is that at me? cause i'm totally not finding any peers.
::) Sorry, Its for alt. Also for you~ :P :P
-
+5% Great work!
is that at me? cause i'm totally not finding any peers.
::) Sorry, Its for alt. Also for you~ :P :P
but noooooooooo i'm failing.
-
Do git pull after git checkout develop
Sent from my SCH-I535 using Tapatalk
-
Do git pull after git checkout develop
Sent from my SCH-I535 using Tapatalk
roger that. will check in again soon.
-
3I should invite alt to become a full member.
-
(http://ww2.sinaimg.cn/bmiddle/e2700da8jw1ejk0jz1slwj20hp0953ze.jpg)
I think this change is important for some one like me.
I am sensitive to icon not to letter.
Yesterday , I want to issue 4000 rose to friends ,but send 4000 btsx.
If this is a good idea .Please vote me : x.ebit.
-
Do git pull after git checkout develop
Sent from my SCH-I535 using Tapatalk
roger that. will check in again soon.
it said "Already up-to-date."
I've been following these instructions (https://bitsharestalk.org/index.php?topic=6008.msg80548#msg80548) which have been working for me just swell on the live version.
but just did a cat BUILD_UBUNTU.md and saw that it says do make buildweb and make BitSharesXT seperately. could that be my issue?
-
发到btc38的交易, 49498.5bts, 点击确认后广播成功,
但是交易结果变成 wulalalalala btc38-btsx-sobo-72722 (memo信息略) 0.00 BTSX 0.5 BTSX 41 minutes ago
时代那边什么都没收到
Transaction #07f6b6c5 Block #276206 , transaction #0 , next #0 Timestamp: 2014年8月21日 GMT+8上午9:47:30
-
发给bitrose的交易, 发送4098.5bts(个位数可能有错, 记不太清了)
点击交易确认后广播成功, 交易记录变成了这样, 发送数量只有998.49999
callmeluc bitrose
- 998.49999 BTSX
0.5 BTSX 56 minutes ago
Transaction #46533b68
Block #276137 , transaction #0 , next #0
Timestamp: 2014年8月21日 GMT+8上午9:35:20
-
Hi5 to the team ;)
(http://cdn.blackenterprise.com/wp-content/blogs.dir/1/files/2011/09/Team-Hi-Five-620x480.jpg)
PS alt please find more issues! :)
-
bitshares_client --version
{
"bitshares_toolkit_revision": "945d2e8d323ef49796d8993addd73c82d7341375",
"bitshares_toolkit_revision_age": "4 hours ago",
"fc_revision": "8468f392cebb291587e0d87cdf9bef9bf167acfc",
"fc_revision_age": "7 days ago",
"compile_date": "compiled on Aug 20 2014 at 20:51:27"
}
delegates do not seem to be producing blocks.
>> network_get_peer_info
[]
>> blockchain_is_synced
false
didn't feel right when I did git checkout develop:
merockstar@merockstar-HP-Pavilion-dv6-Notebook-PC:~/bitshares_toolkit$ git checkout develop
Branch develop set up to track remote branch develop from origin.
Switched to a new branch 'develop'
Same problem here.
{
"bitshares_toolkit_revision": "92e1fb307788c245ffe15e0b80bb2eddec49076e",
"bitshares_toolkit_revision_age": "11 hours ago",
"fc_revision": "8468f392cebb291587e0d87cdf9bef9bf167acfc",
"fc_revision_age": "7 days ago",
"compile_date": "compiled on Aug 20 2014 at 13:51:37"
}
>> network_get_peer_info
[]
Am i compiling the wrong version?
-
发到btc38的交易, 49498.5bts, 点击确认后广播成功,
但是交易结果变成 wulalalalala btc38-btsx-sobo-72722 (memo信息略) 0.00 BTSX 0.5 BTSX 41 minutes ago
时代那边什么都没收到
Transaction #07f6b6c5 Block #276206 , transaction #0 , next #0 Timestamp: 2014年8月21日 GMT+8上午9:47:30
This is V0.4.4
-
发给bitrose的交易, 发送4098.5bts(个位数可能有错, 记不太清了)
点击交易确认后广播成功, 交易记录变成了这样, 发送数量只有998.49999
callmeluc bitrose
- 998.49999 BTSX
0.5 BTSX 56 minutes ago
Transaction #46533b68
Block #276137 , transaction #0 , next #0
Timestamp: 2014年8月21日 GMT+8上午9:35:20
I received your 4097.39999btsx.
I think the system distributed the check to two parts, because I send two part yesterday .
-
@alt +5%，good work.
-
Keep up the good work alt +5%
Can someone post some seed nodes for this dry run?
-
Increasing the min cover ask to .90 may be better.
I am thinking what's the problem if we increasing the min cover ask to 1.0 * average price.
for 0.9, when price fall to 10/9 * 3/4 = 5/6, the short position still under attack probably,
especially when the short amount is very huge.
this possible attack maybe keep user not dare to short much usd.
I thought about this issue and concluded that the risk a short takes for running low on collateral. A short can avoid this by maintaining plenty of collateral. Even if they they don't use any extra collateral the probability of executing a successful attack is very low.
I am still good with a 10% window because it gives the market more flexibility.
-
can not connect too
20140821T145621.333207 th_a fetch_next_batch_of_ ] sync: sending a request for the next items after 0000000000000000000000000000000000000000 to peer 107.170.30.18
2:1919, (full request is []) node.cpp:1961
20140821T145621.335042 th_a read_loop ] disconnected 11 eof_exception: End Of File
End of file
{"message":"End of file"}
asio asio.cpp:22 read_write_handler
{"len":16}
th_a stcp_socket.cpp:72 readsome message_oriented_connection.cpp:165
20140821T145621.335163 th_a on_connection_closed ] Remote peer 107.170.30.182:1919 closed their connection to us node.cpp:2350
20140821T145621.335194 th_a display_current_conn ] Currently have 1 of [8/200] connections node.cpp:1368
-
The test network had issues when an old test chain attempted to sync to it. We are working through the issue and will restore the network shortly.
-
when i execute a short the proceeds go to the market instead of my account. is anyonelse having this issue?
-
when i execute a short the proceeds go to the market instead of my account. is anyonelse having this issue?
When you execute a short it creates a COVER order in your "open orders list".
-
The test network had issues when an old test chain attempted to sync to it. We are working through the issue and will restore the network shortly.
i think that very well may have been my bad, as documented above.
my bad guys.