Since they are used to control an existing position, you don't have to care about the period you choose, it doesn't matter since they don't open new loans (they just allow you to take profit or limit loss, thus to reimburse your existing loan).
But if you set a stop/limit order bigger than your open position then you will have to check the period and interests rates, because a new position will be created or increased.
I have a question for you and others users: do you find margin trading complicated to use, and if so, does the current explanation you find on the site or I give you here enough? Thanks for your feedback.
Raphael
Topic: [BETA]Bitfinex.com first Bitcoin P2P lending platform for leverage trading - page 60. (Read 137528 times)
January 11, 2013, 07:32:34 AM
January 11, 2013, 07:23:39 AM
Alright thanks.
What about setting up Stop/Limit to our orders ?
What about setting up Stop/Limit to our orders ?
January 11, 2013, 07:12:15 AM
Hi Starensell,
You can stop your positions any time you want of course.
Currently lending offers are not renewed automatically for opened positions. That means if the 1 day loan of your position expire, the position will be reduce or close for the amount expired, even if the lender has the "auto-renew" feature on. And even if we did autorenew your loans, there's no garantee that the lender won't turn off the autorenew settings at one point, forcing you to close the position. But if you choose a 60 days loans, you are sure that it won't expire before 60 days.
Let me know if you have any more question, and good luck making profits!
Raphael
You can stop your positions any time you want of course.
Currently lending offers are not renewed automatically for opened positions. That means if the 1 day loan of your position expire, the position will be reduce or close for the amount expired, even if the lender has the "auto-renew" feature on. And even if we did autorenew your loans, there's no garantee that the lender won't turn off the autorenew settings at one point, forcing you to close the position. But if you choose a 60 days loans, you are sure that it won't expire before 60 days.
Let me know if you have any more question, and good luck making profits!
Raphael
January 11, 2013, 06:52:34 AM
Hello I have a question.
I did a couple of trades inside the same day so I choosed 1 day lend to have the better %rate.
But if I'd like to do a long term trade I don't understand the necessary to choose 60 days long lend if:
1) I cant stop the order when I want
2) The 1 day lend renew automaticaly (and has a better %rate).
May be the renewal of the lend is fee costly?
Edit:
Add. Question
How can i set Limit/Stop?
I did a couple of trades inside the same day so I choosed 1 day lend to have the better %rate.
But if I'd like to do a long term trade I don't understand the necessary to choose 60 days long lend if:
1) I cant stop the order when I want
2) The 1 day lend renew automaticaly (and has a better %rate).
May be the renewal of the lend is fee costly?
Edit:
Add. Question
How can i set Limit/Stop?
January 10, 2013, 01:50:40 PM
Remember the BFX fee is 0.1% using routing option can save you some money 
January 10, 2013, 04:43:34 AM
@ninjaboon you have a deposit account is that correct ?
a work around this is go to account settings > account type and select trader instead of depositor it seams the bug happen only for depositor accounts
a work around this is go to account settings > account type and select trader instead of depositor it seams the bug happen only for depositor accounts
you are right. the bug only occurs on deposit acconts. thank you.
Hi Ninjaboon,
This javascript bug should be solved for depositor account.
Thanks for reporting it
Raphael
January 10, 2013, 03:52:27 AM
@ninjaboon you have a deposit account is that correct ?
a work around this is go to account settings > account type and select trader instead of depositor it seams the bug happen only for depositor accounts
a work around this is go to account settings > account type and select trader instead of depositor it seams the bug happen only for depositor accounts
you are right. the bug only occurs on deposit acconts. thank you.
January 10, 2013, 03:16:39 AM
Aren't you a sassy one.
Data can still seriously be messed up with, and in subtle ways that won't make it look like something is wrong when you manually approve outgoing transfers.
January 10, 2013, 02:22:06 AM
@ninjaboon you have a deposit account is that correct ?
a work around this is go to account settings > account type and select trader instead of depositor it seams the bug happen only for depositor accounts
a work around this is go to account settings > account type and select trader instead of depositor it seams the bug happen only for depositor accounts
January 10, 2013, 01:07:08 AM
Not sure if others found this as a bug?
I've clicked on Lending page. Then BTC tab.
I don't see a box to specify the Rate (% per 365 days)
until I moved the Limit option to Market and then back to the Limit option.
I've clicked on Lending page. Then BTC tab.
I don't see a box to specify the Rate (% per 365 days)
until I moved the Limit option to Market and then back to the Limit option.
January 09, 2013, 08:51:24 PM
I did lol at the part where "nothing bad can happen here because we do one thing like MPEx".
I fail to see how terrible PR increases security in any way. January 09, 2013, 06:55:42 PM
I did lol at the part where "nothing bad can happen here because we do one thing like MPEx".
January 09, 2013, 05:46:43 PM
January 09, 2013, 05:44:30 PM
Our users know that no coins or usd can be stolen here, even in case of a hack. https://www.bitfinex.com/pages/security
And the source code we use is unique, unless you can point me to a bitcoin platform that ever worked like bitfinex does. But thanks for the warning
Data can still seriously be messed up with, and in subtle ways that won't make it look like something is wrong when you manually approve outgoing transfers.And the source code we use is unique, unless you can point me to a bitcoin platform that ever worked like bitfinex does. But thanks for the warning
The source code your platform is based upon is stolen as everybody knows, the data model is pretty much public, and even if it has been altered since, SQL injections would let an attacker reverse-engineer it easily.
So come up with a better answer, one that includes a pinch of humility and an answer as to whether the fix has been applied would do just fine <3
Done dear Davout
January 09, 2013, 05:41:30 PM
OK I'll answer a bit more seriously against this attacks because I don't want to scare anyone.
The source code has been rewriten from scratch. Those that don't believe it can test bitfinex features, they'll see that in no way the engine can be the same than bitcoinica. Anyway... about security:
We update our linux servers (all software) every week. We do use Ruby on rails. It is currently on Rails 3.2.11 (latest good version) so this SQL injection problem is irrelevant here.
I'll never repeat this enough but we take security very seriously. And we don't hide nothing (well I won't make the data schema public but you get the point), because you can be transparent and still very secure.
Thanks for eveyone that trust us
Raphael
The source code has been rewriten from scratch. Those that don't believe it can test bitfinex features, they'll see that in no way the engine can be the same than bitcoinica. Anyway... about security:
We update our linux servers (all software) every week. We do use Ruby on rails. It is currently on Rails 3.2.11 (latest good version) so this SQL injection problem is irrelevant here.
I'll never repeat this enough but we take security very seriously. And we don't hide nothing (well I won't make the data schema public but you get the point), because you can be transparent and still very secure.
Thanks for eveyone that trust us
Raphael
January 09, 2013, 05:25:12 PM
Our users know that no coins or usd can be stolen here, even in case of a hack. https://www.bitfinex.com/pages/security
And the source code we use is unique, unless you can point me to a bitcoin platform that ever worked like bitfinex does. But thanks for the warning
Data can still seriously be messed up with, and in subtle ways that won't make it look like something is wrong when you manually approve outgoing transfers.And the source code we use is unique, unless you can point me to a bitcoin platform that ever worked like bitfinex does. But thanks for the warning
The source code your platform is based upon is stolen as everybody knows, the data model is pretty much public, and even if it has been altered since, SQL injections would let an attacker reverse-engineer it easily.
So come up with a better answer, one that includes a pinch of humility and an answer as to whether the fix has been applied would do just fine <3
January 09, 2013, 04:51:08 PM
Our users know that no coins or usd can be stolen here, even in case of a hack. https://www.bitfinex.com/pages/security
And the source code we use is unique, unless you can point me to a bitcoin platform that ever worked like bitfinex does. But thanks for the warning
And the source code we use is unique, unless you can point me to a bitcoin platform that ever worked like bitfinex does. But thanks for the warning
January 09, 2013, 04:33:25 PM
http://it.slashdot.org/story/13/01/09/1557235/ruby-on-rails-sql-injection-flaw-has-serious-real-life-consequences
The codebase you've stolen and are running is, of course, built on RoR.
Act now to either shut down or fix it. And if you don't shut down, you'd better be damn sure you have in fact fixed it, because there's no backsies in BTC.
The codebase you've stolen and are running is, of course, built on RoR.
Act now to either shut down or fix it. And if you don't shut down, you'd better be damn sure you have in fact fixed it, because there's no backsies in BTC.
January 08, 2013, 04:55:45 AM
check ur emails, update on the way
January 02, 2013, 08:44:23 AM
Hi Lucif,
Yes the trading engine did stalled yesterday.
To avoid this in the future, I added a system monitor that restart stalled workers if necessary.
Thanks for your feedback
Raphael
Yes the trading engine did stalled yesterday.
To avoid this in the future, I added a system monitor that restart stalled workers if necessary.
Thanks for your feedback
Raphael
Jump to: