Up for auction is a 7 Day lease of
2,000Khash+ of scrypt mining power.
Starting Bid:0.025
BTCBid Incriment:0.01
BTCBuy It Now: 0.25BTCReserve Price: Undisclosed
Invalid Bids will be rounded up
Lease Time: 7 Days/168 Hours
Miner: LC01 & LC02
Auction ends 5PM GMT 2/5/2014
Payment and pool information due within 24 hours.Lease Begins when payment and pool info are confirmed and ends 7 days after.
Timer is for reference only. The forum time-stamp will count as the official timer.
Lease Features:
Proven compensation with extra hashing power and/or refunds for downtime
105%-110% rated performance provided
Ability to solo mine or setup scheduled pool changes
Agreement to lease scrypt mining power:
Buyer: Highest bidder by public post at the close of the auction.
Seller: cyclops
Lease Term: Listed in auction
Hash Rate: Listed in auction
Business Day: 5PM to 10PM GMT+1
Miner: Listed in auction
Buyer agrees to pay the amount of the winning bid in BTC up front to Seller in exchange for a lease of scrypt mining power at the above defined hash rate +/-5% variance.
1. seller will host a dedicated miner for the buyer for the duration of the lease term.
2. seller will provide hash power using (c/s)gminer on Windows 7 64bit.
3. seller will cover any and all hosting/electric/cooling/network/hardware/maintenance costs.
4. Seller will reimburse buyer for downtime on an hourly basis (in one hour blocks) based on: contract price / lease term / 24 hours * hours of downtime = x BTC per hour
5. Buyer may choose what pool(s) to mine with failover, load-balance, quota, and other multi-pool options available in (c/s)gminer.
6. Buyer may further choose to solo mine coins based on client availability for Windows 7 64bit.
7. Buyer may request changes to the dedicated miner either by a predefined schedule or criteria or once per business day. Changes may take up to 8 business hours for implementation if not scheduled.
8. Sellers maximum liability is limited to the initial purchase price decreasing per hour the purchased hash power is available.
9. Any increase in hashing power will not be considered a breach by either party.
10. Hash per second numbers are as reported by (c/s)gminer after HW errors are taken into account. Pool rejects/stales/availability are not considered a decrease in the provided hashing power.
