It's clear his bid for 0.18 was a mistake and is not valid.
If Monetizer hadn't bid it's impossible WhalingWhales would have paid 0.18 instead of 0.16.

Just read your PM.
Unfortunately I can't transfer the data partially. Please confirm if you can test the service directly on https://www.privatetunnel.com and want to buy.

In my opinion his bid at 12:51 was not valid because he wrote 0.18 by mistake. His real bid for 0.16 was at 12:53. But this is really a tricky one! It's incredible a few seconds make the difference.

1. BTC5 is ridiculously high for this domain.
2. You're not very trustable now after changing the rules so many times.

Is there any native block explorer for Android?
I mean one really written in Java for Android, not just a webview for a web explorer.
That would be cool.

Still available. Price is somewhat negotiable.

FYI, especially to master-P

https://bitcointalk.org/index.php?topic=987084.0

By checking your auction it doesn't seem like you have a reserve price anymore:

I'm pretty sure the bidder doesn't know you have a BTC5 reserve price.

You can't just change the rules every 5 minutes and sell the same good on 2 different threads.

I do think we'll need more in the future.
And that's why the "gavincoin" fork is proposed.

You're already auctioning this domain and you even have a bid:
https://bitcointalk.org/index.php?topic=987015.0

You can't sell it at the same time!  

My last bid: BTC0.14

Yes, you're understanding it right. And yes it is allowed as long as the account wasn't hacked.

BIN reduced to BTC0.08 for all 3 domains.

Minimum bid is still BTC0.04.

Yes that was my first suggestion. It's a hassle as things are now. But it could work with some changes. For example:

- User has the private key stored on the mobile on an app with QR Code scanning capabilities
- The website shows a QR Code with the user's username and date, plus a base URL (https://example.com/2fa/?session=sessionID&signature=)
- The user scans that QR Code with the app.
- The app signs the message (optionally asks for the password if the private key is encrypted) and calls the provided URL (https://example.com/2fa/?session=sessionID&signature=abcSignatureHere[/b])
- The website detects username posted his signature and let's the user log in

This is just a basic idea. But this way there would be no typing required, would be very fast and the actual private key would never be sent anywhere.

I bid BTC0.1

In my opinion BTC0.3 is way too high for a one-day old domain (BTC15 is just ridiculous), I'm out.
But that's just my opinion, good luck.

Has this ever happened to you with a transaction shown as "Medium Priority" at blockchain (not "Low Priority")?

That's strange, but I'm pretty sure it will get confirmed soon.
There are services that can help in this cases by creating a new TX with the same inputs but with a higher fees but I don't think it would be worth in this case for this amount and because it's not low priority but medium.

It has Medium Priority, so it may take about one hour but it will get confirmed. You don't need to do anything except wait.
Not every transaction needs a TX fee to go through.

Can you prove ownership by signing a message with an address posted by that account a while ago?