Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - lordfirefox

#1
BitShares PTS / Re: PTS GPU miner x64 - Ypool
January 10, 2014, 09:07:52 AM
I'm not even going to bother until there is one for AMD GPU's. :(
#2
Pimu7pvvbCJF9LKsCUw2ZUb2pdHRzLLjBa

Thank you!
#3
Quote from: luckybit on December 28, 2013, 04:40:54 PM
Quote from: mikezweighaft on December 28, 2013, 02:23:32 PM
Anyone have insight on this? Thanks.

People on the Litecoin forum were threatening to boycott unless they removed certain stuff.

Source links please.
#4
I just realized my final draft somehow removed the line:


sudo apt-get install build-essential libssl-dev libboost-all-dev yasm unzip mc


It appears in the earlier drafts of the document however. Not sure why or how it vanished from my Google Doc's version. (And no it's not set editable by the public)

Anyways I corrected it.
#5
Is there a way to get a more recent version of the miner on to the instance?
#6
Someone with a AMD FX-9590 needs to post their scores. I'm curious what the CPM would be.
#7
Quote from: HCarvalho on December 03, 2013, 09:50:09 AM
Is it true that AWS is cracking down on all those that are using EC2 instances to mine? Making them paying full price instead of spot isntance prices? Or this rumour is just an hoax to make spot instances prices go down?

That's the first I've heard of it. Why would amazon deny themselves revenu by clamping down on PTS miners? That doesn't make any sense.
#8
BitShares PTS / Re: Confirmation time, is this normal?
December 03, 2013, 10:47:13 PM
Status: 0/unconfirmed
Date: 12/3/2013 01:37
To: Transfer to Bter.com PmCv9LBtBsaVnmzRSwGEcYmh76kShQEy1v
Debit: -1.68 PTS
Transaction fee: -0.0002 PTS
Net amount: -1.6802 PTS
Transaction ID: 3404b3e59db9e5ab22db7d0523a7168579fb013c0b2015da28c47c0836a2c558


About 16 hours and counting. Still no confirmations.
#9
BitShares PTS / Re: Rebuild block
December 03, 2013, 10:37:12 PM
I don't see a protoshares.conf anywhere in the %appdata% Protoshares folder. Maybe I'm looking inthe wrong place.
#10
Quote from: pankkake on November 16, 2013, 09:39:42 PM
Just switch to sha256 merged mining. You'll have dedicated miners and the most secure network (after Bitcoin).

By the way, I don't really understand how "cloud mining" being replaced by "15 year old gamers in their mom's basements" are a good thing.

Because Crypto should belong to the people, not just the big investor types wearing suit and ties. That's what BTC was all about when it was still underground. Hard to see that now.
#11
Quote from: reorder on November 24, 2013, 06:11:51 PM
Quote from: crendore on November 24, 2013, 06:08:53 PM
Python is significantly slower than C.  Buyer beware.  Personally i would wait for a C implementation than buy a python one.
Sorry, but so what? You do not need ultra performance to send 10-20 packets of data/sec over network :) Most pools are running python, for that matter.

Anyway, sold.

EDIT: sold exclusively.

Conveinently "sold exclusively" immediately when people started asking to buy it from you. I smell a rat.

Unless you can produce, I'm inclined to NOT believe you.
#12
If the prices are getting crazy then go with some smaller Spot instances. You can set up multiple instances to mine. Just check prices before you commit.
#13
BitShares PTS / Re: Dying out
November 30, 2013, 03:24:12 AM
With blocks coming in so slowly even with a crap-ton of cores pointed at a pool it's becoming really boring to mine PTS. I'm not sure what can be done about it.
#15
Quote from: jabbaah on November 29, 2013, 10:17:55 AM
Well, unfortunately even with RC2 it is not yet fixed. Anyway your work-around is working. (Command line parameter)

If someone is using my ptstools (description here: http://www.dmsp.de/Protoshares)... meanwhile I included a watchdog resulting in a fallback to SSE4 after having tried (and failed) with AVX. Nevertheless all parameters are passed transparently to the ptsminer itself. If you did not enter any additional parameters it used the default set with AVX -> SSE4 fallback.

Actually you have to use the SSE4 because some of the EC2 Instance options do not let you use AVX even though it's incorrectly listed as being able to.