BTC machines Trade (advanced trading tool for crypto currencies)

[lenin_ra]

Our service is now live and it's called BTC machines Trade:

https://btcmachin.es

A new trading tool BTC machines Trade based on BTC-e exchange platform has been released. BTC machines Trade provides advanced trading tools and a user interface designed to enhance trading experience. BTC machines Trade features include

- automatic trading
- trading sessions
- trading simulator
- profits tracking
- rich graphing features

...and much more!

BTC machines Trade is initially free and it's available at https://btcmachin.es

NEW! MOVING AVERAGE ALGORITHM IS NOW SUPPORTED IN AUTOMATED TRADING!

Best regards,
lenin_ra

[1714726822]

1714726822

[1714726822]

1714726822

[1714726822]

1714726822

[Pangia]

Hi,

Is is possible to trade with this within the BTC-E exchange between the Alt-coins. 

What I'm interested in is a tool that could determine if there is an arbitrage-like opportunity between the alt-coins on BTC-E. Is this possible?

Thanks.

[Pangia]

Okay,

So I'm not computer savvy, so where is the FAQ for this product.  There's clear information on how to FUND the account but very little on how to use this product.

[ninjaboon]

Hi OP

In what way have you secured your service?
Inputs.io was just hacked.

[lenin_ra]

Hi,

Is is possible to trade with this within the BTC-E exchange between the Alt-coins. 

What I'm interested in is a tool that could determine if there is an arbitrage-like opportunity between the alt-coins on BTC-E. Is this possible?

Thanks.

Multi currency arbitrage profitability analysis would be an intriguing feature! I might start working on it tomorrow... if not too tired

Currently we support only LTC, BTC and USD. If you run simultaneous sessions on all pairs, you will profit on these intercurrency rate dissassociations (rates on different pairs don't always correlate), even though it's not proper arbitrage.

I'll think seriously about adding those features!

[lenin_ra]

Okay,

So I'm not computer savvy, so where is the FAQ for this product.  There's clear information on how to FUND the account but very little on how to use this product.

You are absolutely right. I will add some more usage instrctions ASAP! Any specific kind of guidance you would have special interest in?

lenin_ra

[lenin_ra]

Hi OP

In what way have you secured your service?
Inputs.io was just hacked.

Db server uses authentication and is firewalled, passwords are hashed, api keys and secrets are scrambled, authentication happens per request and is verified against session token and IP combination.

Plus I don't keep any users money. All I have are service fee deposits (when I'll start charging them at some point).

lenin_ra

[moderate]

Hi OP

In what way have you secured your service?
Inputs.io was just hacked.

By now you should know that the answer for this is completely and totally irrelevant.

[MPOE-PR]

Hi OP

In what way have you secured your service?
Inputs.io was just hacked.

By now you should know that the answer for this is completely and totally irrelevant.

The failure of many to do something right does not mean the right thing cannot be done. The question of security always was important, it's just taken a lot of bullshit to get at least a few people to start insisting.

[moderate]

Hi OP

In what way have you secured your service?
Inputs.io was just hacked.

By now you should know that the answer for this is completely and totally irrelevant.

The failure of many to do something right does not mean the right thing cannot be done. The question of security always was important, it's just taken a lot of bullshit to get at least a few people to start insisting.

I feel like you missed the point, entirely. I hope and expect any service to do the best to protect itself and their users, by all means try to achieve that when making your new super-service-x.

Then the trust issue kicks in, you can't even know for sure whether a supposedly cold storage is actually cold storage. The moment a service starts using cloudflare providing ssl is close to pointless. You have no clue whatsoever about the code quality in the server, as well how well administered it is. If you ask the question "how safe is(are) your server(s)?" it is very likely that the least knowledgeable person will anwswer "it is the most secure thing ever!" and then sites like coindesk will happily reproduce such answer.

[lenin_ra]

Hi OP

In what way have you secured your service?
Inputs.io was just hacked.

By now you should know that the answer for this is completely and totally irrelevant.

The failure of many to do something right does not mean the right thing cannot be done. The question of security always was important, it's just taken a lot of bullshit to get at least a few people to start insisting.

I feel like you missed the point, entirely. I hope and expect any service to do the best to protect itself and their users, by all means try to achieve that when making your new super-service-x.

Then the trust issue kicks in, you can't even know for sure whether a supposedly cold storage is actually cold storage. The moment a service starts using cloudflare providing ssl is close to pointless. You have no clue whatsoever about the code quality in the server, as well how well administered it is. If you ask the question "how safe is(are) your server(s)?" it is very likely that the least knowledgeable person will anwswer "it is the most secure thing ever!" and then sites like coindesk will happily reproduce such answer.

Well, even CIA and Sony get hacked. I think I did pretty good job with security. All the standard measures are in place:

- DB auth
- DB server firewall
- Password hashing
- Sensitive data scrambling
- Per request auth
- Request auth by token + IP
- SSL secured connection

What comes to code quality, it's a good point. I think I might make the code repository public. Even more transparency this way.

-lenin_ra

[Atruk]

Hi OP

In what way have you secured your service?
Inputs.io was just hacked.

By now you should know that the answer for this is completely and totally irrelevant.

The failure of many to do something right does not mean the right thing cannot be done. The question of security always was important, it's just taken a lot of bullshit to get at least a few people to start insisting.

I feel like you missed the point, entirely. I hope and expect any service to do the best to protect itself and their users, by all means try to achieve that when making your new super-service-x.

Then the trust issue kicks in, you can't even know for sure whether a supposedly cold storage is actually cold storage. The moment a service starts using cloudflare providing ssl is close to pointless. You have no clue whatsoever about the code quality in the server, as well how well administered it is. If you ask the question "how safe is(are) your server(s)?" it is very likely that the least knowledgeable person will anwswer "it is the most secure thing ever!" and then sites like coindesk will happily reproduce such answer.

Maybe the answer is to stop using web services in general?

[moderate]

Hi OP

In what way have you secured your service?
Inputs.io was just hacked.

By now you should know that the answer for this is completely and totally irrelevant.

The failure of many to do something right does not mean the right thing cannot be done. The question of security always was important, it's just taken a lot of bullshit to get at least a few people to start insisting.

I feel like you missed the point, entirely. I hope and expect any service to do the best to protect itself and their users, by all means try to achieve that when making your new super-service-x.

Then the trust issue kicks in, you can't even know for sure whether a supposedly cold storage is actually cold storage. The moment a service starts using cloudflare providing ssl is close to pointless. You have no clue whatsoever about the code quality in the server, as well how well administered it is. If you ask the question "how safe is(are) your server(s)?" it is very likely that the least knowledgeable person will anwswer "it is the most secure thing ever!" and then sites like coindesk will happily reproduce such answer.

Maybe the answer is to stop using web services in general?

Not using those that think claiming SSL secured connection is something of importance to mention as security, it is the most basic thing and I don't know whether the guy knows if he using TLS or not. Authentication, firewall, and password hashing are such basic things that if you are not doing that you shouldn't be touching servers. Data scrambling provides zero protection. ....

[lenin_ra]

Hi OP

In what way have you secured your service?
Inputs.io was just hacked.

By now you should know that the answer for this is completely and totally irrelevant.

The failure of many to do something right does not mean the right thing cannot be done. The question of security always was important, it's just taken a lot of bullshit to get at least a few people to start insisting.

I feel like you missed the point, entirely. I hope and expect any service to do the best to protect itself and their users, by all means try to achieve that when making your new super-service-x.

Then the trust issue kicks in, you can't even know for sure whether a supposedly cold storage is actually cold storage. The moment a service starts using cloudflare providing ssl is close to pointless. You have no clue whatsoever about the code quality in the server, as well how well administered it is. If you ask the question "how safe is(are) your server(s)?" it is very likely that the least knowledgeable person will anwswer "it is the most secure thing ever!" and then sites like coindesk will happily reproduce such answer.

Maybe the answer is to stop using web services in general?

Not using those that think claiming SSL secured connection is something of importance to mention as security, it is the most basic thing and I don't know whether the guy knows if he using TLS or not. Authentication, firewall, and password hashing are such basic things that if you are not doing that you shouldn't be touching servers. Data scrambling provides zero protection. ....

Well, we don't even store users' money in our system. But anyway I just wonder, what kind of criteria or assurances would satisfy such a concerned user like you?

BTW, I do use TLS.

-lenin_ra

[MPOE-PR]

I feel like you missed the point, entirely. I hope and expect any service to do the best to protect itself and their users, by all means try to achieve that when making your new super-service-x.

Then the trust issue kicks in, you can't even know for sure whether a supposedly cold storage is actually cold storage. The moment a service starts using cloudflare providing ssl is close to pointless. You have no clue whatsoever about the code quality in the server, as well how well administered it is. If you ask the question "how safe is(are) your server(s)?" it is very likely that the least knowledgeable person will anwswer "it is the most secure thing ever!" and then sites like coindesk will happily reproduce such answer.

Sure, but this doesn't affect the importance and sanity of asking about security (or identity, or proof of competence, etc). Those who are actually qualified to be running a service will answer such questions just fine, and those who aren't, including coindesk and its ilk, will continue to be irrelevant.