Topic: www.BITSTAMP.net Bitcoin exchange site for USD/BTC - page 67. (Read 231282 times)

BITSTAMP ADDS WITHDRAWAL E-MAIL CONFORMATION

As the popularity of crypto currencies increases, so do the chances of unauthorized account logins. Although Bitstamp is constantly pursuing the highest standards of security, we cannot guarantee for security breaches, which result from the actions of our users.

To raise the level of protection, Bitstamp provides email conformations for withdraws. The new safety feature, which offers additional protection of our users’ funds, includes the option to make E-mail Confirmations of bitcoin, ripple and bank withdrawals. This option, along with the highly recommended Two-factor Authentication, forms a solid security standard, which will surely gain wide recognition and use among our users.

To setup this feature go to Account > Security > Withdrawal e-mail conformation and choose the preferred setting. We highly recommend you also setup two factor authentication for accessing your Bitstamp account.

You need to fund your Ripple wallet with 100 XRP first in order to activate it. You can purchase XRP here: https://www.bitstamp.net/market/xrp/

We determined that using Ripple is superior to our code system in all respects.

Keep getting this ... You have to be funded before you can grant a trust

Hazek,

Is this purely a move to ripple or was there a legal implication for you in providing codes? (similar to Gox).

Thanks

And yes, its offline most of the time. How is this an improvement to anything?

Well I tried it, it works, but... First of all there is an issue  with trusted address. I cant send ripple (practicaly same as bittamp code) to other bitstamp customer, but I have to go to ripple website, open account, define trusted address, send money from bitstamp there, then from there send to other bitstamp account ... Pretty stupid if you ask me

Especially the Ripple part. How are people supposed to take this seriously.

 Damn, thats bad news....

BITSTAMP CODE TERMINATION

Dear Bitstamp customer,

as of Monday, 17th of June 2013, 0:00 GMT, Bitstamp will cease to offer its Bitstamp Code feature. All codes active at that time will be redeemed back to their issuing accounts.

The termination of the Bitstamp Code feature is the result of a successful implementation of Ripple, which replaced and improved its functionality.

Partnered services, which relied on our Bitstamp Code feature to operate, will be able to swiftly replace it through the use of our API and Ripple.

This is news to me.

+1   looks like it's bitcoinity?

Whats wrong with the API?
Why is it working here:
http://bitcoincharts.com/markets/
and not here:
http://bitcoinity.org/markets/bitstamp/USD

Or is it something with Bitcoinity?

SEPA withdraw getting a little late with processing. So far nothing alarming, just thought to report it. 

 Some banks/services have an extra fee for same day processing, just an idea, maybe the bitstamp guys could introduce something like that.

Relevant:  https://bitcointalksearch.org/topic/m.2378578

I've only used bitatamp   for  selling xrp never had a problem btc withdraws  were fast and  when they start trading ltc  I will use them more often.

2 days to initiate the wire?  Or 2 days from request until the money was in your bank account....  Where are you located?

TL;DR: I'm having troubles designing my tradebot because bitstamp API doesn't provide enough information; I'm asking for help and/or requesting this information to be provided through the API

Bitstamp allows to do JSON/HTTP-based API trading using https://www.bitstamp.net/api/function/

The tradebot that I'm about to create needs to know the current balance and the currently open orders at a synchronised(!) point in time.
The API allows to get the current balance using /api/balance/ and the currently open orders using /api/open_orders/. But this is awkward and doesn't work properly because:

- The access is not synchronized: It is possible that a trade happens just inbetween the API calls for balance/open orders, causing the returned information to be inaccurate (I've already seen losses due to this effect while testing)

- The list returned by /api/open_orders/ can be quite large; it's wasting bandwidth, which is rare at my site. (and I need to download this list quite often)

To work around these problems, I'm trying the following approach:
The bot maintains an offline list of all open orders that it has posted to the market using /api/buy/ and /api/sell/; it also keeps track of canceled orders.
The bot keeps itself up-to-date about all user transactions using /api/user_transactions/. This allows my bot to know the current balance before and after every transaction.
Now I'm trying to match the user transactions to the open orders, i.e. the bot tries to figure out what user transaction happened due to what open order.
If this matching can be done, then I'm happy because then the bot could know about open orders and balance at any point in time (i.e. before and after every transaction).

However, this matching can be quite tricky. Let me show you an example where I think it's impossible:
Now, the tricky question is: What open orders does the bot have after this transaction??

I know about at least two possibilities:
1.: After the bot canceled order X, someone else sold 1 BTC, which partially fulfilled order Y. Consequently, after the transaction, there's one remaining open order: buy 1 BTC at 120 USD each
2.: Even before the bot posted order X, there already was someone else's order to sell 1 BTC at 120 USD each, causing order X to immediately match against it. So order X was only "buy 1 BTC at 122 USD each" while it was canceled. Consequently, after the transaction, there's one remaining order: buy 2 BTC at 120 USD each

So my bot can't know what open order caused the received transaction
This makes it impossible to maintain an offline list of all open orders posted by the bot.

It would be a lot easier to code this stuff if the user transactions returned by /api/user_transactions/ would contain an additional entry about what open order's id issued this transaction.
In the example above it would clearly indicate order id X or order id Y, allowing the bot to maintain an offline list of open orders.

Consider this post as being a feature request

My withdraw took surprising 2 days instead of a week or something.

Well, that sucks. Bitstamp really need to get their act together, they are pissing off their customers.