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

Pages: 1 2 3 [4] 5 6 7 8 9 10 11 ... 80
46
.22941 BTS is a fixed bitshares transfer fee, 0.0003 BTC is a fixed gateway fee. There is no sense to withdraw less than the gateway fee, since it is applied to withdrawal. And keep in mind, that bitcoin transaction pool is currently clogged with unconfirmed transactions

https://blockchain.info/unconfirmed-transactions

This is not a problem of openledger, this is a problem of bitcoin, so you might want to try cashing out through some other coin. Last time I cashed out through OPEN.ETH and this worked for me smoothly, but you may consider different variants and choose which one works best for you. Try small amount first, but make it larger than fee.

47
Quote
So lets say that I need to get US Cash out of Bitshares from the BTS that I am holding. Would I convert that back to OPEN.BTC then send it back to my Coinbase account which is connected to my bank account?

Yes, this is one way you can do. I use openledger gateway for withdrawals all the time and they never failed me. You can also use blocktrades bridge or any other exchange which trades bitshares assets to get out.

If you don't need cash to spend, you may buy bitUSD and keep them in your bitshares wallet.

48
Openledger / Re: openledger Lost my eth
« on: December 26, 2017, 01:11:55 pm »
Just made a withdrawal of OPEN.ETH with no problems. It went through almost immediately.

49
BTSBOTS was overly reliant on Poloniex for price feed stats.

This is not true. Btsbots price feed deviated from poloniex by a lot, because it was heavily weighted by Chinese exchanges with high volume.

51
General Discussion / Re: DAI stablecoin in OasisDEX
« on: December 24, 2017, 10:52:42 pm »
Oh, smart coin on ethereum, I wonder what took them so long :)

52
It has too few price feeds. But yes, when price feed is established it will be a good profit opportunity for shorters. Thanks for bringing this up.

53
General Discussion / Re: review for price feeding
« on: December 24, 2017, 04:00:18 pm »
Quote
get DEX price A

What is "DEX price A"? Which pair exactly?

it refers to the price in bitCNY/BTS pair in DEX.

You should not use bitCNY/BTS price (not on DEX nor on other exchange) to calculate bitCNY price feed , because it depends on price feed. This is fundamentally wrong, because you trigger a feedback this way, which may be negative (stabilizing) or positive (destabilizing) with equal chance.

54
General Discussion / Re: review for price feeding
« on: December 24, 2017, 03:55:02 pm »
Quote
get DEX price A

What is "DEX price A"? Which pair exactly?

55
Can one of these proposals be recalled?

56
Technical Support / Re: orderbook api call is showing blank orderbook
« on: December 23, 2017, 08:16:48 pm »
There are no orders on BTS:GAME market. Do you mean BTS:OPEN.GAME?

57
Have no idea, I am not a crypto developer. Bitshares may be good enough if you understand how to build apps on top of its api.


58
Can we support this please? The expenses which they request will eventually return back to reserve with trading fees, so the community is unlikely to lose something. And open trading bot has proven to be a strong selling point. Can you name many exchanges where a regular user can set up account and start automated trading in few minutes?

59
Yes, those who built their business on bitcoin suck these days. Confirmation time is horrible, and fee is ridiculous. Not sure if bitshares would be the best solution to these problems, but they have to do something about this if they want to save their business.

60
Meta / Re: do you have modify the trade logic in this fork?
« on: December 21, 2017, 01:38:16 pm »
seems not the same issue.
This issue has been discussed on github:
* https://github.com/bitshares/bitshares-core/issues/453 and
* https://github.com/bitshares/bitshares-core/issues/338#issuecomment-318808452

There is a test case to reproduce it:
* https://github.com/bitshares/bitshares-core/pull/341/commits/aa60533269d7ca5e534bedb8a63ac4742d50164c

It's on the to-do list, will be fixed in a future release.
It is.

The issue was submitted a long ago, why wasn't the fix included in the last fork?

Pages: 1 2 3 [4] 5 6 7 8 9 10 11 ... 80