You are outbidding yourself, i call you out of this auction.

Price goes back to the last valid offer not done from him and relative counter offers.

I'm worried that you are bringing the price up without any will to purchase it later (you are a newly registered member). I'm i wrong?

I changed that point at the end of the first page:

I call that void, it was a mistake, and it's way too much

+1
[/quote]

this was the last post before timer ran out
[/quote]
No, auction extends for five minutes for each new bid (read at the end of the first page).

Please use PRICE @ qnt

+1

This however doesn't mind that the correct bitcoin price is 100USD+

To make it simpler, i will pay the escrow fee.
The shipping fee is already included.

(there is no need to specify in every offer x, but with fees paid)

Since that the auction is for 2 units, it would be important that you specific into how much you are interested into. This also because maybe one unit will be sold for a lower price than the other.

Its the Avalon itself and yes, its in cms. Rudrigo wrote the packaging dimension. It was listed as 20kg each on my dhl invoice, but I suspect them to be lighter.

39.5*45*16.5

It was due to the April firmware somehow preloaded

Your offer is lower than the ones already posted, also, this is a public auction; why don't you post it here?

Countdown:

I think i should update it, since that i finally got them

Ok, thanks for your interest.

Yes, 150/piece. They all have 3 modules in it. (should be around 71GH/s)

They are located in Italy and yes, sure, i will ship internationally.

Thanks!

I have to update the offer:
#1 - the "order" for the other unit got cancelled, so i can now sell 2. This auction is now for 2 units.
#2 - after the end of the auction, the auction continues if more offers are made: the end of the auction is extended by 5 minutes recursively. Minimum price increase is 2 BTC.

I got the units.

I got my units today. Before starting, thank you Avalon, 2 months late is always better than never.

I would like to share my view.

#1

First of all, that is one third of a failover. It means that the 2 before them must be down. Just a rough calculation: let's suppose that the uptime of the first 2 providers is 90% (that's a low uptime). That means that the RLW address accounts for (10/100)^2 = 0.01 of the time. If 0.01 is 700BTC, 1 is 70'000 BTC. I'm not claiming that this is correct, i'm just doing some math.
I'm not sure that the failover works like that, i didn't check the code: it could be doing a round robin; in that case, the math above is completely wrong.

#2

Of the 3 units i connected, 2 had a firmware that was release in April. April was the initial release date of these units, before all of the delays happend. The units where also full of dust.

If these units have been produced a week ago, like we are being told (new magic smt line, 50 units per day), how is it that they have an April firmware on it?

You are right about this. However, on the other side, I think that 2 weeks is a too long timeframe.
I guess that the optimal should be 1 week, or 5 days.

Anyway, 2 weeks is not that bad, since that the basic idea is good.