 Show Posts
|
|
Pages: « 1 [2]
|
|
Hi Pablo,
I think it would be very useful to put a warning that says "WARNING: THE BOT WILL BUY AT THE CURRENT PRICE, WHATEVER THE MARKET CONDITION IS AS SOON AS YOU ENABLE TRADING. (I UNDERSTAND/STOP THE BOT)".
In the future you should add an additional per-market setting like "Initial buy price: XXX".
Then when you click on the "enable trading" link or button the BOT should show an alert that says: "Do you want to wait until a price of XXX has been reached before allowing the BOT to buy? (YES/NO/CHANGE THRESHOLD)"
Of course the BOT should use the threshold only when trading goes from disabled to enabled and not during its normal operation.
This could help with users that start to try the BOT in a day that shows a lot of fluctuation and avoid a situation where the BOT buys at 700 and sells 30 seconds later at 500.
|
|
|
|
I know two weeks isn't a good indication for trades based on ema indicators, but using one of the weeks I used the bot for back testing, the bot says I should have made 46% using the same settings I did during live trading.
And in this market by just holding on the coins you would have made more, still not the bot's fault. |
|
|
|
There are a few things that MBHD won't provide because they create LOTS of support calls and it's just not sustainable going forward if and when there are more users.
For instance, choosing where to put your wallet sounds an innocent feature but causes lots of support calls when people create a wallet and then cannot find it. For MBHD I am only going to put wallets in the user data directory to simplify things. Edit: the wallet file name will be derived from the master public key so users won't even choose the filename (there will still be a description field).
For the love of God, give me the ability to put all the files together with the executable.  Better: instead of having to create a .properties file (like with multibit "classic") within the same directory where the Multibit HD executable is/will be, create one there by default. Then give an advanced used the possibility to make portability happen just by changing a simple flag. Something like this: # Set this to true if you want to carry Multibit around on a USB stick
# Default: false
portable = true
And pick the location for the rest of the files accordingly. |
|
|
|
|
Scusate, ma se si vogliono fare prendere per il culo, voi prendeteli per il culo.
Non accettano PDF? Benissimo.
- Stampate il PDF
- Mettete la stampa sul tavolo
- La fotografate un po' storta con una macchina fotografica digitale, non col cellulare che viene una porcheria
- A scelta, gli mandate la JPG, o ristampate la JPG in un PDF a 300DPI e glielo mandate
|
|
|
|
I have similar experience..
IMHO profit should be calculated in BTC, not USD, or you should be able to chose do you want for profit to be displayed in USD or BTC.
In a market where the price only goes up when you sell high and buy later a little bit lower, you expose yourself to erosion. E.g. Buy at 100, sell at 112. Buy at 109, sell at 121, buy at 118, sell at 125 and so on > BTC erosion. Buy at 100, sell at 112. Buy at 98, sell at 121, buy at 95, sell at 125, buy at 93 > BTC profit. The latter is not happening, so calculating profits in BTC does not make sense, because you will only see losses. One thing that we should considers however is that 1 mont ago 1BTC on bitstamp.net was 126$, now it's 499. - The BOT tweaked to trade at 15 minutes intervals would have given 158% in 13 trades - Buy and Hold would have given a profit of 194% So IMHO with this trend it's difficult to choose between buy and hold, manual day-trading or the BOT. |
|
|
|
We are looking at security to the best of our ability and as far as is reasonable for us to do so (I.E. if they NSA or CIA decide they really want to hack us well... ), but hosting will include very clear disclaimers regarding this issue. Nothing anyone can build is fool proof and although we are confident that hosting is not a decent target for an organized attack (because you can't steal any coins) and we are confident we can build an infrastructure to withstand most other situations, we really can't make any absolute guarantees, in computer security, no one can. So to answer your question: We are taking every reasonable precaution but in the end it is a personal choice to use or not the service, we can't make absolute guarantees. Please let me know if you need anything at all . Pablo. If you are implementing the bot as a web application, the best authentication you can put in front of it is Apache's. In this way you don't have to worry too much about sanitising input at least when you login. 2FA after Apache would be nice as well. As I have said I am not worried about people stealing BTC/money: the permissions granted to teh BOT by the API Key are already preventing this. I am worried about DOS scenarios, where accounts can be wiped out because of intentional misconfiguration (typically things like: buy high, sell low, reverse EMA, absurd TSL and so on). If you are rewriting the BOT, consider the possibility of creating a console application that can be daemonised, configurable through a JSON configuration file and an added GUI on top of it for remote interaction. In this way you could sell 3 versions of the BOT: 1-Classic (browser extension) 2-Standalone hosted 3-Standalone self-hosted 3 being the same of 2, just run using customer's resources will come without added efforts and may potentially save you some money in the long run (people pay for the subscription, you don't pay for the resources to run the BOT). |
|
|
|
Remote connection to a virtual desktop will most likely be overkill. I'm sure he's looking into hosting the bot as a web application.
They will have to rewrite it, since for now you need a browser. Someone asked for a console application and Pablo said that it was not possible at the moment. I seem to have read that this has been taking some time to figure out. I have mine currently running on my home server iMac, no trades yet - possibly the uptrend?
Take a look and set the interval to 1h, 30m, 15m. http://bitcoinwisdom.com/markets/bitstamp/btcusdhttp://bitcoinwisdom.com/markets/mtgox/btcusdWith this trend - and depending on the exchange - with trading set to 30/60minutes the bot should be doing buy&hold mostly. |
|
|
|
Hi there - running the bot off my laptop entails that I keep it on and Chrome open as far as I understand. I am reading comments about a planned hosted solution - will this mean you'll provide a web interface to manage our bot settings on your server?
Hi BigB , Yes, that's exactly what that means, when hosting is live, you will be able to run Butter from our servers through a web interface. I hope that answers your questions, please do not hesitate to let me know if you need anything at all . Pablo. Hi Pablo, I hope that you are considering all possible scenarios because from a security point of view this can be easily become a nightmare. Nobody will be able to steal money/BTC, however the potential for wiping out accounts because of intentional misconfiguration of the BOT parameters is huge. What would be the details on how to interact with the BOT in a hosted environment? RDC? Teamviewer? A web application? |
|
|
|
Hey, sorry about that, we actually checked it and concluded that there wasn't anything to fix on our end, apologies for forgetting to answer. It seems to be a font aliasing issue on your side, I found a Vista system to test it on and couldn't reproduce the issue, wasn't reported by anyone else either. Look into your aliasing settings and tell me if it helps. If other people experience this issue they're welcome to comment. I have noticed that every site using the Roboto fonts looked like shit using IE 10, Chrome 29 and Firefox 25, with or without ClearType, so this looked like a "system" wide problem. Then it came to my mind to check what fonts were installed in the system and I have found I had installed what was probably an old version of Roboto. I have deleted it and now all the sites that were rendering in a problematic way look like they should. So this was entirely my fault, sorry for the inconvenience. I hope this could help people with the same issue (and to the hell installing fonts). |
|
|
|
|
I am not writing this to bash the service or whatever (BTW I am still waiting for verification to happen for many days as well), however I have opened a ticket suggesting not to use Google fonts that are unreadable on a desktop web browser and the ticket has been sitting there forever unacknowledged and unanswered.
Even a "we will think about it" or "f*ck you we like the way numbers are garbled on the screen" would have made a difference.
This lack of communication in my opinion is detrimental to the users' trust as it feels like nobody is monitoring the platform.
My 2 cents.
|
|
|
|
I think we are going to add a separate address book or 'Contacts' in MBHD as it will need more flexibility going forward.
I agree the Bitcoin-QT address book and multisend works pretty well.
Transaction display I agree with your comments - not sure if we are going to have a full grid of transactions displayed yet.
We use the XChange code for our tickers so will use what they have coded up. We would not want to add in "insert your ticker code here". It's too error prone. We want MBHD to be as close as we can manage to being bulletproof.
Currently MultiBit is being used by something like 80,000 or 100,000 users. They will be 9,000 downloads just today.
MBHD we want to be usable in 'the next push' of Bitcoin's expansion so we are thinking about what we need to do for 1,000,000 users. Inevitably this will entail a bit of simplification and hand holding.
The separate address book seems a nice idea. It would be nice to separate transactions from the addresses as well: at the moment the process is kinda cumbersome because you can send money and edit the addresses at the same time (and by the way with 0.5.14, if you select an address from the address book on the bottom panel, delete the address from the textfield in the top panel and then click "new", the address gets wiped in the address book). It would be very nice to be able to send BTC by either typing/pasting an address or by typing a label in the address field. In this case autocompletion with a drop down menu (think about how google works) could be a way to select quickly the address we need, after all it is a lot easier to remember labels. About the tickers, I see that XChange allows access to Bitcoincharts: maybe you could fetch data for different exchanges, since the list of supported ones seems limited. I know this is not the right thread to ask, however... any news on the next release of multibit "classic" ? |
|
|
|
|
Hi,
I would like to see the following features implemented in Multibit HD:
Transactions
- More columns:
Split the description in Operation (sent/received) and Destination
- Add a drop down menu so that I can filter which transaction to show (Sent/Received/All)
Address book
- The possibility to discern my own remote destination addresses (think about exchanges or online wallets) from other destination addresses
- The possibility to hide receiving addresses I am not using anymore.
Overall the way Bitcoin QT managed transactions and the address book was nice.
Tickers
- More exchanges or the ability to add custom tickers, by specifying custom queries (interpreting REST/JSON/whatever comes back)
This could be achieved using external config files where youo could specify your query and how to map the results to specific variables "plotted" in the GUI
|
|
|
|
|
Timeconsuming.
Like if it were a single word. :/
|
|
|
|
Hug is ok, but pleeease no sexytime. |
|
|
|
Isn't the rule promoting posting silly messages like *cough*cough* this one? |
|
|
|
|
