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

Apologies for the delay.

Your ticket was now addressed.

i did ... TICKET #8689 (4 HOURS, 13 MINUTES)

answer was

  (3 HOURS, 40 MINUTES)


 

darkfriend77, please contact support and we will look into your issue.

it's done it took about 2 hours ... fine :-)

one thing that i haven't understood till now are the fees ....

I sent 1000 USD from my USD bank account to Bitstamp ... no SEPA ...
I get this accounted ... on Bitstamp ...


And on the account i get 967.98$

I don't undestand ... wtf I got exchange Rate? I sent USD!

According to


i should get ... 985$ accounted

my bank fees where added to the 1000$ it was cleared on my side with 1004.27$ ....

can somebody bring some light into the dark?

Which address/tx?

... grmpf ... i got a withdrawl ... BTC ...
and it's marked as finished ...
and the BTC aren't accounted on the adresse ...
2 tickets nothing ...
waiting since 2 hours.

amount: 11 BTC

normal? How long should that take usually?

Got my SEPA credited to Bitinstant in under 2h yesterday.
I guess because my new bank is UniCredit Group, too.

Earlier this year, I started getting site down messages on Bitstamp, and noticed that I was always the only one having that issue. Every time, the site started working again after I waited an hour or so without trying to connect. That started happening right after Bitstamp had some maintenance downtime. Finally I thought I fixed it for good by increasing the timeout value of established TCP connections on my router. The default was very low compared to usual settings, 300-600 seconds I think, and I increased it to 7200.

Today I got that problem again for the first time in many months. Just like the first time, I can still access all other websites normally, but Bitstamp is down for me. After remembering how I 'fixed' that last time, I doubled the timeout value again on my router. I expect that Bitstamp will start working for me again after a few hours, just like the problem always temporarily resolved itself earlier.

What I'm wondering is if this could be an issue on Bitstamp's or CloudFront's end, since I've never had any problems like this with other websites. I even tried using multiple computers behind my router, both Windows & Linux, but Bitstamp appears to be down for all of them. I realize that the router (Asus RT-N56U) is rather cheap, and even the increased timeout value of 7200 is quite low compared to the default value of 432000 on Linux. Many consumer routers use low values to save memory.

It could've actually been pure coincidence that increasing the timeout value helped the first time, it's hard to see how that could've been the cause. This time I tried to check what's happening with Wireshark, and the error I see is "TCP PREVIOUS SEGMENT LOST", which seems to point to a MTU problem, or some other very odd type of packet loss. I'll have to try another router if this persists now.

On Monday I sent funds to my Bitstamp accound using a SEPA transfer and they got credited the next day!

Well done Bitstamp, from a pleased customer

The SEPA transfers that I did with Bitstamp were processed and deposited in my account within 48 hours.

Hi, I would like to ask, how long it takes to get funds from Bitstamp into my SEPA bank account?

Or Yubikey, if you can. Thanks!

Please add Google Authenticator for withdrawal 2FA. I do not want to use email.

Germany the frontrunner in European legislation made profits from Bitcoins tax free for one.
And anyway you look at it, Europe is much more liberal than the NSA...ehhmm...USA.

Security improvement proposal: destroy user session on ip change. Current implementation allows to stay logged in even on ip change.

This may allow to steal user cookie and use it to login to bitstamp.

haha I was wondering... like hm? all good now I suppose.

Why should they have to comply with US regulations?
They are in the EU, their bank is in the EU and the EU has no problems with BTC.

@Nejc Kodric Please announce well in advance when you will be forced to comply with the US regulations, and require all kinds of verification even to withdraw BTC, the way gox was. I want to be able to leave Bitstamp before that hassle starts. Thanks.

API access for https://www.bitstamp.net/api/transactions/ has changed again. POST doesn't work anymore, but GET does, like proposed in the documentation.

Also, contrary to what many people seem to believe, Google Authenticator requires no communication with Google. The device that carries your codes could even be offline, if you can keep it's clock synchronized accurately enough.

If you don't trust Google Authenticator (which by design has no reason to communicate with Google), the algorithm it uses is completely open and you can implement it yourself. But I think someone would have already noticed if the application was secretly doing network communications, when it has no reason to do so.

It's true that some sites offering 2FA use the QR code drawing service of Google, and that really doesn't help in making people understand how the system works. Since in that case the code IS coming from Google, it's only natural that people assume Google is somehow unavoidably involved in the 2FA process, no matter how it's implemented. Obviously the proper way is that sites draw the QR codes themselves, instead of using an external service and leaking codes in the process.