Only the banks exchange fees:
http://www.unicreditbank.si/tecajna_lista/?t=1&id_menu=&language=ENG
What i was wondering for qquite some time:
Bitstamp is a majotr player in Europe, why not offer a EUR exchange???
There are already plans for other Exchanges to focus more on EU customers.
Why is this not implemented, which doesnt take a genius to copy and you guys are loosing money daily.
Topic: www.BITSTAMP.net Bitcoin exchange site for USD/BTC - page 64. (Read 231282 times)
Sorry if this is mentioned elsewhere, but I couldn't find it on the site: Are there any fees for converting USD to EUR during withdrawal or deposit?
While it's not new, if at all possible please also make sure to use the two factor authentication security feature with the email confirmation security feature for the most possible security for your account. You can download a guide how to set it up here: https://www.bitstamp.net/s/documents/bitstamp_2_factor_authentication_guide.pdf
Okay Thanks for the info on that, hazek.
I just wanted to get that cleared up to make sure myself and others know its in our best interest.
I actually think this is very important just in case. Good work on this feature.
And keep up the good work in the value you offer here to the community!
Unless I'm mistaken, confirmation emails are only sent when you withdraw USD or BTC. That should deter most attackers, since they can't directly steal anything if they have access to the account.
Correct, if the featured is activate on an account (it is on by default) then all USD or BTC withdrawals and API key activation require email confirmation.
I just wanted to get that cleared up to make sure myself and others know its in our best interest.
I actually think this is very important just in case. Good work on this feature.
And keep up the good work in the value you offer here to the community!
5th transaction with BITSTAMP and still happy.
I love the security feature which requires (EMAIL CONFIRMATION) during transaction. This is a great security feature/mechanism just in case...
Question for Bitstamp:
How often does this email confirmation occur? or is it when I am not doing too many transactions
when email confirmations kick in? or is it random? what is the going rate for email confirms.
I love the security feature which requires (EMAIL CONFIRMATION) during transaction. This is a great security feature/mechanism just in case...
Question for Bitstamp:
How often does this email confirmation occur? or is it when I am not doing too many transactions
when email confirmations kick in? or is it random? what is the going rate for email confirms.
Unless I'm mistaken, confirmation emails are only sent when you withdraw USD or BTC. That should deter most attackers, since they can't directly steal anything if they have access to the account.
Correct, if the featured is activate on an account (it is on by default) then all USD or BTC withdrawals and API key activation require email confirmation.
Yes, during withdraws. Okay perfect! Thanks for your response.
Unless I'm mistaken, confirmation emails are only sent when you withdraw USD or BTC. That should deter most attackers, since they can't directly steal anything if they have access to the account.
5th transaction with BITSTAMP and still happy.
I love the security feature which requires (EMAIL CONFIRMATION) during transaction. This is a great security feature/mechanism just in case...
Question for Bitstamp:
How often does this email confirmation occur? or is it when I am not doing too many transactions
when email confirmations kick in? or is it random? what is the going rate for email confirms.
I love the security feature which requires (EMAIL CONFIRMATION) during transaction. This is a great security feature/mechanism just in case...
Question for Bitstamp:
How often does this email confirmation occur? or is it when I am not doing too many transactions
when email confirmations kick in? or is it random? what is the going rate for email confirms.
Unless I'm mistaken, confirmation emails are only sent when you withdraw USD or BTC. That should deter most attackers, since they can't directly steal anything if they have access to the account.
5th transaction with BITSTAMP and still happy.
I love the security feature which requires (EMAIL CONFIRMATION) during transaction. This is a great security feature/mechanism just in case...
Question for Bitstamp:
How often does this email confirmation occur? or is it when I am not doing too many transactions
when email confirmations kick in? or is it random? what is the going rate for email confirms.
I love the security feature which requires (EMAIL CONFIRMATION) during transaction. This is a great security feature/mechanism just in case...
Question for Bitstamp:
How often does this email confirmation occur? or is it when I am not doing too many transactions
when email confirmations kick in? or is it random? what is the going rate for email confirms.
Unless I'm mistaken, confirmation emails are only sent when you withdraw USD or BTC. That should deter most attackers, since they can't directly steal anything if they have access to the account.
Correct, if the featured is activate on an account (it is on by default) then all USD or BTC withdrawals and API key activation require email confirmation.
5th transaction with BITSTAMP and still happy.
I love the security feature which requires (EMAIL CONFIRMATION) during transaction. This is a great security feature/mechanism just in case...
Question for Bitstamp:
How often does this email confirmation occur? or is it when I am not doing too many transactions
when email confirmations kick in? or is it random? what is the going rate for email confirms.
I love the security feature which requires (EMAIL CONFIRMATION) during transaction. This is a great security feature/mechanism just in case...
Question for Bitstamp:
How often does this email confirmation occur? or is it when I am not doing too many transactions
when email confirmations kick in? or is it random? what is the going rate for email confirms.
Unless I'm mistaken, confirmation emails are only sent when you withdraw USD or BTC. That should deter most attackers, since they can't directly steal anything if they have access to the account.
5th transaction with BITSTAMP and still happy.
I love the security feature which requires (EMAIL CONFIRMATION) during transaction. This is a great security feature/mechanism just in case...
Question for Bitstamp:
How often does this email confirmation occur? or is it when I am not doing too many transactions
when email confirmations kick in? or is it random? what is the going rate for email confirms.
I love the security feature which requires (EMAIL CONFIRMATION) during transaction. This is a great security feature/mechanism just in case...
Question for Bitstamp:
How often does this email confirmation occur? or is it when I am not doing too many transactions
when email confirmations kick in? or is it random? what is the going rate for email confirms.
what's the point to use google authenticator if using the trading API anyone that steals my username and password can empty my account?
If I remember that correctly, I had to enable API access in my account settings before I could start using the API.So it's disabled by default, i.e. only API traders will have it enabled, and those should know what they are doing.
what's the point to use google authenticator if using the trading API anyone that steals my username and password can empty my account?
Fuck yeah, money math precision is an ass pain of all financial amateurs running bitcoin services. Looks like only gox using int64 for internal money calculations. All others use some shitty rounding or floating point math.
Of course, this is pennies and I don't care. But small or daily traders should.
Bitstamp uses fixed-point arithmetics, just like they ought to do. The orders are executed with the precise BTC amount that they were posted for. The transaction's USD amount is calculated as BTC amount times price, rounded like the following:Of course, this is pennies and I don't care. But small or daily traders should.
- x.499999.... rounds down to x
- x.50000....1 rounds up to x+1
- exactly x.5 triggers a randomness, rounding to x or x+1 with a 50/50 chance.
The fee is calculated as USD amount times your personal fee rate, the result is rounded up, minimum 0.01 USD. I think this is what kakobrekla is complaining about.
Fuck yeah, money math precision is an ass pain of all financial amateurs running bitcoin services. Looks like only gox using int64 for internal money calculations. All others use some shitty rounding or floating point math.
Of course, this is pennies and I don't care. But small or daily traders should.
Bitstamp uses fixed-point arithmetics, just like they ought to do. The orders are executed with the precise BTC amount that they were posted for. The transaction's USD amount is calculated as BTC amount times price, rounded like the following:Of course, this is pennies and I don't care. But small or daily traders should.
- x.499999.... rounds down to x
- x.50000....1 rounds up to x+1
- exactly x.5 triggers a randomness, rounding to x or x+1 with a 50/50 chance.
The fee is calculated as USD amount times your personal fee rate, the result is rounded up, minimum 0.01 USD. I think this is what kakobrekla is complaining about.
Fuck yeah, money math precision is an ass pain of all financial amateurs running bitcoin services. Looks like only gox using int64 for internal money calculations. All others use some shitty rounding or floating point math.
Of course, this is pennies and I don't care. But small or daily traders should.
Bitstamp uses fixed-point arithmetics, just like they ought to do. The orders are executed with the precise BTC amount that they were posted for. The transaction's USD amount is calculated as BTC amount times price, rounded like the following:Of course, this is pennies and I don't care. But small or daily traders should.
- x.499999.... rounds down to x
- x.50000....1 rounds up to x+1
- exactly x.5 triggers a randomness, rounding to x or x+1 with a 50/50 chance.
The fee is calculated as USD amount times your personal fee rate, the result is rounded up, minimum 0.01 USD. I think this is what kakobrekla is complaining about.
Fuck yeah, money math precision is an ass pain of all financial amateurs running bitcoin services. Looks like only gox using int64 for internal money calculations. All others use some shitty rounding or floating point math.
Of course, this is pennies and I don't care. But small or daily traders should.
Of course, this is pennies and I don't care. But small or daily traders should.
Huh, didn't know about it.
If I were to write a trading engine I'd certainly use fixed-point arithmetic and at least five decimal places to make it as precise and transparent as possible.
If I were to write a trading engine I'd certainly use fixed-point arithmetic and at least five decimal places to make it as precise and transparent as possible.
LOL, u guys must have some serious beef. 
The recent hacks were database-oriented, so I assume the attackers have an extensive knowledge of MySQL and similar...
But I am here to warn you, Bitstamp, to repair this horrible security faux pass -- you use for API access the same name and password as for the main login on the site. This is unacceptable, because if anyone gains an API login, he/she can then raid the account. The point of API access is to allow automated and/or remote trading, not doing account transfers! Look at btc-e for a better implementation.
Simply, API access needs to be a separate access name/password than that of the main account.
You could also allow the users to make separate API entry accounts and assign funds to these sub-accounts from your main account, so that you could, for example have 1000 USD in the main account and diverge 400$ into API_1 and 400$ into API_2. This way, each of the separate accesses can be managed individually. But even if you don't apply this improvement, changing the API access conditions and maybe including and external RSA key hardware for trade confirmations, and for main account access would be of great help! (For confirmation of bank and bitcoin transfers out of an account a simple "Trezor" external key dongle could be used, this is to cost 1BTC only, and an alternative is in development by another 'lab'.
Anyway, even if you used printed gridcards, like many banks do (postage is cheap these days, still), you would enhance account security by 1000x, because a physical piece of plastic with numbers on it, is way more secure than any data you transfer over the internet via third parties.
But I am here to warn you, Bitstamp, to repair this horrible security faux pass -- you use for API access the same name and password as for the main login on the site. This is unacceptable, because if anyone gains an API login, he/she can then raid the account. The point of API access is to allow automated and/or remote trading, not doing account transfers! Look at btc-e for a better implementation.
Simply, API access needs to be a separate access name/password than that of the main account.
You could also allow the users to make separate API entry accounts and assign funds to these sub-accounts from your main account, so that you could, for example have 1000 USD in the main account and diverge 400$ into API_1 and 400$ into API_2. This way, each of the separate accesses can be managed individually. But even if you don't apply this improvement, changing the API access conditions and maybe including and external RSA key hardware for trade confirmations, and for main account access would be of great help! (For confirmation of bank and bitcoin transfers out of an account a simple "Trezor" external key dongle could be used, this is to cost 1BTC only, and an alternative is in development by another 'lab'.
Anyway, even if you used printed gridcards, like many banks do (postage is cheap these days, still), you would enhance account security by 1000x, because a physical piece of plastic with numbers on it, is way more secure than any data you transfer over the internet via third parties.
Don't bother. CSS is way more important than any of the serious issues, like scamming trading engine.
The recent hacks were database-oriented, so I assume the attackers have an extensive knowledge of MySQL and similar...
But I am here to warn you, Bitstamp, to repair this horrible security faux pass -- you use for API access the same name and password as for the main login on the site. This is unacceptable, because if anyone gains an API login, he/she can then raid the account. The point of API access is to allow automated and/or remote trading, not doing account transfers! Look at btc-e for a better implementation.
Simply, API access needs to be a separate access name/password than that of the main account.
You could also allow the users to make separate API entry accounts and assign funds to these sub-accounts from your main account, so that you could, for example have 1000 USD in the main account and diverge 400$ into API_1 and 400$ into API_2. This way, each of the separate accesses can be managed individually. But even if you don't apply this improvement, changing the API access conditions and maybe including and external RSA key hardware for trade confirmations, and for main account access would be of great help! (For confirmation of bank and bitcoin transfers out of an account a simple "Trezor" external key dongle could be used, this is to cost 1BTC only, and an alternative is in development by another 'lab'.
Anyway, even if you used printed gridcards, like many banks do (postage is cheap these days, still), you would enhance account security by 1000x, because a physical piece of plastic with numbers on it, is way more secure than any data you transfer over the internet via third parties.
But I am here to warn you, Bitstamp, to repair this horrible security faux pass -- you use for API access the same name and password as for the main login on the site. This is unacceptable, because if anyone gains an API login, he/she can then raid the account. The point of API access is to allow automated and/or remote trading, not doing account transfers! Look at btc-e for a better implementation.
Simply, API access needs to be a separate access name/password than that of the main account.
You could also allow the users to make separate API entry accounts and assign funds to these sub-accounts from your main account, so that you could, for example have 1000 USD in the main account and diverge 400$ into API_1 and 400$ into API_2. This way, each of the separate accesses can be managed individually. But even if you don't apply this improvement, changing the API access conditions and maybe including and external RSA key hardware for trade confirmations, and for main account access would be of great help! (For confirmation of bank and bitcoin transfers out of an account a simple "Trezor" external key dongle could be used, this is to cost 1BTC only, and an alternative is in development by another 'lab'.
Anyway, even if you used printed gridcards, like many banks do (postage is cheap these days, still), you would enhance account security by 1000x, because a physical piece of plastic with numbers on it, is way more secure than any data you transfer over the internet via third parties.
Don't bother. CSS is way more important than any of the serious issues, like scamming trading engine.
The recent hacks were database-oriented, so I assume the attackers have an extensive knowledge of MySQL and similar...
But I am here to warn you, Bitstamp, to repair this horrible security faux pass -- you use for API access the same name and password as for the main login on the site. This is unacceptable, because if anyone gains an API login, he/she can then raid the account. The point of API access is to allow automated and/or remote trading, not doing account transfers! Look at btc-e for a better implementation.
Simply, API access needs to be a separate access name/password than that of the main account.
You could also allow the users to make separate API entry accounts and assign funds to these sub-accounts from your main account, so that you could, for example have 1000 USD in the main account and diverge 400$ into API_1 and 400$ into API_2. This way, each of the separate accesses can be managed individually. But even if you don't apply this improvement, changing the API access conditions and maybe including and external RSA key hardware for trade confirmations, and for main account access would be of great help! (For confirmation of bank and bitcoin transfers out of an account a simple "Trezor" external key dongle could be used, this is to cost 1BTC only, and an alternative is in development by another 'lab'.
Anyway, even if you used printed gridcards, like many banks do (postage is cheap these days, still), you would enhance account security by 1000x, because a physical piece of plastic with numbers on it, is way more secure than any data you transfer over the internet via third parties.
But I am here to warn you, Bitstamp, to repair this horrible security faux pass -- you use for API access the same name and password as for the main login on the site. This is unacceptable, because if anyone gains an API login, he/she can then raid the account. The point of API access is to allow automated and/or remote trading, not doing account transfers! Look at btc-e for a better implementation.
Simply, API access needs to be a separate access name/password than that of the main account.
You could also allow the users to make separate API entry accounts and assign funds to these sub-accounts from your main account, so that you could, for example have 1000 USD in the main account and diverge 400$ into API_1 and 400$ into API_2. This way, each of the separate accesses can be managed individually. But even if you don't apply this improvement, changing the API access conditions and maybe including and external RSA key hardware for trade confirmations, and for main account access would be of great help! (For confirmation of bank and bitcoin transfers out of an account a simple "Trezor" external key dongle could be used, this is to cost 1BTC only, and an alternative is in development by another 'lab'.
Anyway, even if you used printed gridcards, like many banks do (postage is cheap these days, still), you would enhance account security by 1000x, because a physical piece of plastic with numbers on it, is way more secure than any data you transfer over the internet via third parties.
Jump to: