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 - alt

Pages: 1 ... 11 12 13 14 15 16 17 [18] 19 20 21 22 23 24 25 ... 189
256
General Discussion / to GOLD/SILVER/BTC holders
« on: July 08, 2017, 01:24:49 am »
I saw big margin call had happen on these three market,
but the share holders seems refuse to take the 10% profit help others quit short position.

you need to know when the price continue drop, black swan will happen in these SILVER,
then these SILVER you hold will lose the value it can be.

sell your SILVER, take the 10% profit, this is what you should do, or your SILVER will not worth 1 real SILVER after the blackswan

257
区块号: 17,588,990
TXID: 15dc4c08c9e6ef6864a0876b52e5704f8fea1cb5
你充值的是CNY,不是BTS
http://cryptofresh.com/tx/15dc4c08c9e6ef6864a0876b52e5704f8fea1cb5

258
General Discussion / Re: Cryptofresh update, feedback
« on: June 28, 2017, 01:45:53 am »
I remember you have got about 4 million BTS from your last worker,
can you tell us what's the 4 M BTS pay for?

259
中文 (Chinese) / btsbots.com 代码
« on: June 15, 2017, 01:22:43 pm »
手机掉水里了,最近没办法上微信了,看到的朋友帮忙在微信群说一下

很早就答应要把 btsbots.com 代码开源,但是一直没找到时间整理
今天先把现有的代码开源供有需要的朋友参考,地址为:
https://github.com/pch957/btsbots-demo-2016

操作系统建议 ubuntu1604, 使用方法
1 安装 meteor
2 下载代码,安装 npm 包
Code: [Select]
cd btsbots-demo-2016; npm install
3 运行 meteor 服务端程序,默认端口为本机 3000 端口,运行成功之后通过浏览器访问本机 3000 端口可以看到页面,但是还没有数据。
Code: [Select]
cd btsbots-demo-2016; meteor run
4 使用 scripts 目录下的 python 脚本生成数据, 需要 python3,
1) 安装依赖 bts 包
Code: [Select]
pip3 install bts
2) 修改配置文件 config.json
一个是 mongodb 数据库,上面 meteor 启动后默认在 3001 端口开了个 mongodb 服务器。
一个是 witness_node api 地址,用来获取区块链数据
3) 初始化 balance, order 数据,只需要初始化运行一次
运行 python3 correct-balance.py config.json ,注意作为 demo 代码中我只获取了很少量的数据。
4) 实时监控历史记录、orderbook, balance 等数据
python3 monitor.py config.json
5) 处理统计数据:
python3 statistics.py config.json


这份代码中只有架构值得借鉴,其它部分都会重写。主要几个工作:
1. 优化 mongodb 数据以及索引
2. 实时监控脚本需要处理分叉,保证 balance , order book 正确无误
3. meteor UI 部分使用 reactjs 引擎重写,优化页面,减少订阅数据量

260
General Discussion / Re: Next Committee Proposal: Witness Pay
« on: May 18, 2017, 12:41:07 pm »
seems jerryliu had fixed the feed price problem,
I have vote again.

261
General Discussion / Re: bitGold-bitSilver-bitBTC
« on: May 18, 2017, 11:45:07 am »
Gold and Silver is good
but bitBTC should remove from the list.
we'll have big trouble when BTC fork to two coin just like ETC/ETH

I was wondering whether those nice friendly bts whales that we have and the rest of us can do something about bringing more liquidity in bitbtc, bitsilver and bitgold so  people can safely store their value in those as well within bitshares DEX. Do we need to adjust some parameters?

I am very happy that finally we have a lot of bitusd and bitcny into existence and this brings huge confidence to keep funds within the DEX..I know from my self that for the first time after 3 years I can park some bitusd on the DEX and not worry about lack of liquidity but on the other side I am afraid of a currency fiat crisis coming soon so some bitsilver and bitgold and maybe bitbtc would be nice to have..But I feel idiot to  overpay huge premiums to buy those assets on the DEX and I do not feel safe buying gold and keep it under my mattress..

So what can we do about this? We need to do something for sure before it is late..Thoughts?

262
General Discussion / Re: Next Committee Proposal: Witness Pay
« on: May 18, 2017, 01:28:20 am »
I have remove my vote for witness jerryliu.

But I know bitcrab is very busy for help bitshares these days,
he had contact many new partner(include exchange, ico, bitCNY gateway) to join bitshares.
and attend some meetup in Beijing, Shanghai, Chengdu for Bitshares
he is the best  wealth for Bitshares,
I need our witness with a high quality
So I will vote for jerryliu again when he resovle the feed price problem.

263
General Discussion / Re: The Hero from BitShares Island
« on: May 13, 2017, 12:36:57 am »
what's the plan?
how many will you spent,
how many time will you use,
how many people will you hire,
or just another great idea will bring us to the moon?

I have shared access to the golden goose with everyone.
But I'll hold off on sharing what I plan to do with my eggs.

 :)
thanks, I'll ignore it, good luck.

264
General Discussion / Re: The Hero from BitShares Island
« on: May 12, 2017, 02:18:34 pm »
what's the plan?
how many will you spent,
how many time will you use,
how many people will you hire,
or just another great idea will bring us to the moon?

265
Really it is completely up to @bitcrab @alt who will be witnesses now because of the proxy power they have combined.
this is the spirit of POS,
you want more power, buy more shares.
bitcrab have bought 200M shares, so he deserve this power, right?
and I believe  he will  contribute more to Bitshares  than you or me or anybody anonymous.
the power belong to the share holders, not bitcrab nor me.

you are not satisfied for the fact that we don't vote for you,
I have post many times for the reason.
don't I have the right to choose who I trust? you are out so we are not decentralized?

266
General Discussion / Re: btsbots wallet release v0.0.1
« on: May 10, 2017, 10:34:04 pm »
sorry, bot crash yesterday.
and something very strange happened
I have run several witness_node, and some python scripts update transaction from these nodes with websocket connect.
but I saw all scripts exist at  19:07:07(TZ+0)  because of lost websocket connection with no reason.
I don't know what the reason, only found there are so many filled order at that time.
I guess I need to handler these type of error. automatic restart the script.

Code: [Select]
Task exception was never retrieved
future: <Task finished coro=<BaseProtocol.handler_message() done, defined at /home/alt/python-venv/lib/python3.5/site-packages/bts/ws/base_protocol.py:76> exception=ConnectionClosed('WebSocket connection is closed: code = 1009, no reason.',)>
Traceback (most recent call last):
  File "/usr/lib/python3.5/asyncio/tasks.py", line 239, in _step
    result = coro.send(None)
  File "/home/alt/python-venv/lib/python3.5/site-packages/bts/ws/base_protocol.py", line 78, in handler_message
    payload = await self.websocket.recv()
  File "/home/alt/python-venv/lib/python3.5/site-packages/websockets/protocol.py", line 299, in recv
    raise ConnectionClosed(self.close_code, self.close_reason)
websockets.exceptions.ConnectionClosed: WebSocket connection is closed: code = 1009, no reason.

267
General Discussion / Re: btsbots wallet release v0.0.1
« on: May 10, 2017, 11:48:57 am »
seems the price change much after you halt your computer.
but bots can't update your order when your browser is not acitve, because all code is running in the client side.
so when you open btsbots.com again, the bots update the old orders.

Also the bot seems to refer to the price of the last session under some circumstances:

Code: [Select]
run bots
new order OPEN.DASH BTS  amount: 7.500000000000001 price: 2628.9024795702967
new order OPEN.DASH USD  amount: 7.499999999999999 price: 124.16536069244391
run bots
cancel order --- OPEN.DASH BTS
because of price: 2628.9024786666664 change to 1985.2493480088676 ----
new order OPEN.DASH BTS  amount: 7.5 price: 1985.2493480088676
cancel order ---- OPEN.DASH USD
because of price: 124.1653601655538 change to 93.76506100000002 -----
new order OPEN.DASH USD  amount: 7.5 price: 93.76506100000002

See the price drop from 2629 to 1985 and 124 to 94 just after starting the bot. Bad thing is, orders were given before correction occurs. Nothing happend this time but this could result in huge losses.

Debug info:
Computer was turned off after last session, restarted and reconnected after about 12h, ip should also be a new one.

Hi Alt,

no, I know,  so I normally cancel all orders from my wallet after stopping all bots and closing the connection (I reckon closing the tab also closes the active websocket connection). So there were no old orders.
The log I was providing is the log of a just freshly started bot (after complete shutdown of the computer and 12h). The bot gave these orders just after start up and canceled them just after that, when he got a new price. But presumable the old price was saved from the former session and used until new price feeds went in and corrected the situation. Just guessing.

But I can assure you that there were no open orders from the last session when I started the bot. I know from my own experience that users sometimes are confident that a setup was like this or that and rule out any user error. But I'm 100% confident there were no old orders simply because there were no 15 DASH on that account in the last session.

Thanks for looking into this.
thanks for the detail.
I never thought about this condition.
I will add  some logic to make sure all data is fresh before run the bot.

268
General Discussion / Re: btsbots wallet release v0.0.1
« on: May 10, 2017, 11:46:21 am »

these is the logic, if the client can't get the newest block  in time, it will pause the bot,

Hi alt,

thank you for your work, I think one can't overestimate the value the rise in liquidity brought to bitshares by your software.
I see that it's pretty work-in-progress. And want to make a few wishes, if I may:

* An oversight of all available markets with informations about the used price feed.
I was trading DASH the other day, low liquidity there still, and was a bit worried about the price feed quality. Sometimes the prices changed but my bots didn't react. Other bots seemed not to follow the same feed, and some actions observed with others bots didn't seem to make sense. Maybe everything is alright, but I'm lacking these informations about the price feed to throw real money at such a market.

PS: I saw you writing, that Dash price feed is the poloniex data.

* Safeguard against bad or broken connections:
The main reason I halted trading for now is that I assume my connection to be poor. I don't know if I get all feeds on time and sometimes the websocket connection is lost which leaves open orders unattended. It would be nice if the client would be able to recognize delayed data (maybe a timestamp in the feed data) and missed data (if that can be the possible in websocket, maybe a index number in the feed data). Any of these events, plus the worst case a broken websocket connection, could set the client in emergency mode, making him desperately try to reconnect and cancel all orders immediately.

Does "pause the bot" mean that he will cancel all open orders? That would be awesome.
no, 'pause the bot' means the bot will stop running and do nothing.
usually client can't cancel the orders too when it lost connect to the server.

269
General Discussion / Re: btsbots wallet release v0.0.1
« on: May 10, 2017, 11:44:02 am »
got it, I will provide all these native data, and give the choice to users.

yes, for OPEN.DASH, simple  use last ticker data from poloniex.
I  have no idea, why it change such more.
PS: The price feed is simple last trade ticker data, right? I'm asking, because I see 8% changes up and down:

Code: [Select]
cancel order --- OPEN.DASH USD
because of price: 99.10707803964283 change to 107.90515943227852 ----
new order OPEN.DASH USD  amount: 7.142857142857142 price: 107.90515943227852
cancel order --- OPEN.DASH OPEN.BTC
because of price: 0.06632999839798 change to 0.07240041489940716 ----

The price goes down a few seconds again.

Maybe it would be better than to exclude mini trades from the feed, so that only trades >$100 are taken into account.

A guess you mean the ticker feed on top of the poloniex api page (https://poloniex.com/support/api/). And you take the "last" trade value, right? What about
Code: [Select]
("lowestAsk" + "highestBid")/2 . This could get a little better prices.

270
General Discussion / Re: btsbots wallet release v0.0.1
« on: May 09, 2017, 10:07:51 am »
yes, for OPEN.DASH, simple  use last ticker data from poloniex.
I  have no idea, why it change such more.
PS: The price feed is simple last trade ticker data, right? I'm asking, because I see 8% changes up and down:

Code: [Select]
cancel order --- OPEN.DASH USD
because of price: 99.10707803964283 change to 107.90515943227852 ----
new order OPEN.DASH USD  amount: 7.142857142857142 price: 107.90515943227852
cancel order --- OPEN.DASH OPEN.BTC
because of price: 0.06632999839798 change to 0.07240041489940716 ----

The price goes down a few seconds again.

Maybe it would be better than to exclude mini trades from the feed, so that only trades >$100 are taken into account.

Pages: 1 ... 11 12 13 14 15 16 17 [18] 19 20 21 22 23 24 25 ... 189