Topic: [BOUNTY] - Bugs at the Kraken.com Exchange - page 4. (Read 22291 times)

raze - you should be getting a bounty soon since your confusion about ordering showed how the order form is confusing in a sense. I take it you were looking at this



and naturally thought that you were creating an order to sell 5 million XRP. After all, you were looking at something that essentially seemed to be saying "sell 5 million XRP." There was also a little message below this saying "Amount of XRP to receive." And a big red button saying "sell BTC for XRP," but still that part of the screen in the shot is misleading. I'm pushing to get this changed, but don't know when it might be. At the very least, though, I will be adding content to the FAQ/Trading Guide to address this potential confusion.

To address monsterer's point, there is a reason why orders to sell more of a currency than you have (or buy more than you can afford) make it to the matching engine. The reason is that an account may have orders executing in the background and if so there is no way to know how much of a currency is there up until the moment the order executes. So the system lets the order through and resizes to whatever you can afford. For someone who doesn't trade actively and is just doing simple order types, it would be easier to know how much currency is available. But to allow for more active traders/advanced order types this isn't easy. Again, I should probably add something to the site content to make this aspect of ordering clear. 

Yeah, I think most of the confusion stems from the value pairs combined with the ordering page. It wasn't made clear to me that I was selling BTC, which would probably make a customer using real funds a little unhappy. This should definitely be made clearer somewhere on the order page, or at least the confirmation page.

P.S I'll happily accept a tip if you decide to change it

Thanks for the clarification dree, I get it now. I don't think it should be "market + xxx.xx" because this isn't a market order. It's a limit order and that's why it says limit. But "limit +105" might be taken as a limit order at 105, so something more clear would be an improvement.

I want to check with the devs on this, but I see your point. More tickets isn't so bad in itself, what concerns me more is the increased likelihood of ordering mistakes. If I have 10 BTC but create an order to sell 500K BTC, most likely I'm confused and creating an order that will do something I don't intend (I probably don't want to sell my 10 BTC).

On the order details page, you see this text:


This might be confusing, as the order is actually buying at 210! Instead, the text could be changed to:


This makes it clear that the 105.20508 is relative and not absolute.

This is a bad policy IMO - invalid orders shouldn't ever make it to the matching engine. Allowing this will increase the likelihood of support requests due to misunderstanding on the part of the user.

The css thing isn't really an issue - since it's a large site, not every page is going to use 100% of the defined css styles (though eventually the css style sheet rules could be trimmed down a bit).

This is just happening on the deposit & withdraw pages since they are disabled right now. It will change once they are enabled. But the error should only be on these two pages, so if you can show other pages with the error, this might be an issue.

Yes, but reloading makes this goes away. So not seeing a bug here. Reviewing the code/css points - will get back to you on these later.

This isn't a bug. The check of the username on the signup page is just checking formal validity - i.e. at least 5 characters. It doesn't check whether the username is already taken. So the username can be deemed OK initially but later rejected.

Can you explain how this is a bug? I'm not seeing it.

Thanks Dargo, bounty received.

After above bug, CAPTCHA does not show.  See http://grab.by/nmn8.

I disabled and enabled JS, but the site still says it's disabled.  See: http://grab.by/nmmU and http://grab.by/nmn0

EDIT: Only when inspect element open.

Not a bug, but you could probably improve the site by removing unused CSS rules.

See http://grab.by/nmmK

On "Withdraw" page, there is an error in your code:
"Cannot call method 'replace' of undefined"
Located at this line:
                    var a = typeof (b.showtab) == "string" ? b.showtab : xchg.util.hashnav.getParam(b.param), e = h.find("li.active a").attr("href").replace(/^#+/, ""), g = true, c = false, f;

Edit: Looks like this is on every page?

When creating an account, the username says "OK" even if it isn't:
http://grab.by/nmmk
http://grab.by/nmmm

I can get ridiculous orders by enabling the "disabled" usd field ( 4 USD = 400btc), but the order fails if tried to place.
http://img.adamncasey.co.uk/i/170/d/o

Looks worthy of a small reward for a small issue. Thanks austin.

This isn't exactly a bug. You did in fact sell BTC for XRP. What you did was submit an order to sell 5,000,000 (!) BTC for XRP. If you submit an order to sell more of a currency than you have, the system gives you a partial fill by selling what you've got. So the order sold all your Bitcoins for XRP.

If you want to sell XRP for BTC, what you want to do is buy BTC when you have the BTC/XRP pair selected. The order button should then say "Buy BTC with XRP," and when you click that, you will get the confirmation screen which will say that you are buying BTCXRP, meaning that you are buying BTC with XRP (equivalent to selling XRP for BTC). It's a bit confusing, since we don't have an XRP/BTC pair you actually have to buy BTC/XRP in order to sell XRP. Got it?

Even though this isn't exactly a bug, I am going to submit a ticket because I'm not sure why the confirmation screen has '(XRP)' in front of 'BTCXRP'. That makes things more confusing. Also, I'm wondering if perhaps we should have some kind of check in place if someone tries to sell more of a currency than they have, especially in your case where you had 110 BTC and tried to sell 5 million BTC. At the very least I think it calls for some kind of clarification in the FAQ/Trading Guide. I'll see about a bounty and let you know, but I'll need your address to send. (Edit: nevermind I see you have it posted) Thanks raze!

Edit: Actually, the above isn't quite correct. What you did was sell BTC for XRP, but you specified the volume in XRP. So, you created an order to sell 5 million XRP worth of BTC in exchange for XRP. That's how the '(XRP)' got there - it's the (non-default) volume currency. The thing to remember is that the "Amount" field specifies the volume and the currency in which the volume is measured, but it doesn't determine what you are buying or selling - the selected currency pair determines this.