[ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000

[enta2k]

does i really need to set recipient to me after mining on pool, if i want to switch to solo? because it work even without it(at least it seems so)

Yes but i think you wont receive the payments when you find something.

[1713583100]

1713583100

[1713583100]

1713583100

[dcct]

+1

We don't need to be negative.

[fivebells]

dcct, in the merge tool startnonce needs to be an unsigned long long int.

[dcct]

We need someone to re-do the flowchart in the OP:



We need something really fancy!

I'll give 5k BURST bounty for this. If there are any questions about it -> #burstcoin or send a message here.

[dcct]

dcct, in the merge tool startnonce needs to be an unsigned long long int.

Hold on for a few hours, new version is almost ready. Just needs some final testing.

[ltcnim]

@dcct: do you have any idea how to port your miner to ARM? I'm currently pulling my hair out. I was able to port the merge tool with just setting

#define _FILE_OFFSET_BITS 64

and removing O_LARGEFILE from the open() function (which shouldn't be used at least according to man pages anyway). the merge tool ran without problems after that and was able to handle my 102GB files just fine.
But the miner really gives me a hard time (mostly because of my lacking C skills ^^). It always produces way to long deadlines, while it works on my x64 linux just fine. Of course I'm using the correct shabal files.

Is there anything in the calculation which might fail or give wrong results on an ARM plattform?

[enta2k]

can someone give me an example of a "too long deadline"?
I really dont know if mine are long or not

[fivebells]

Hold on for a few hours, new version is almost ready. Just needs some final testing.

It's OK, I just changed the code.

[pinballdude]

can someone give me an example of a "too long deadline"?
I really dont know if mine are long or not

This is of course when doing solo
The system is set up to to average 4 minute blocks, so 240 seconds should be average. That means that half the time a 240 second deadline will win a block, and half the time it is too large. at 120 seconds it might be 1/4 risk you don't get a block, and at 60 it might be 1/8 risk someone is faster, etc. etc. conversely at 480 you will only win a block 1/4 of the time, at 960 only 1/8 of the time... i think.. not sure these calculations work out, but it ought to be something like that. i had one at 180 that did not win a block, and one at 114 that did win a block. Patience is pretty vital, I had to wait almost a week before i got a block, and i was cpu plotting like crazy on 3 pcs, 14 cores,  24/7 towards 4TB, so on average i must have had somewhat over 1TB plottable

[dcct]

There has been a version of my miner for uray's pool. Anyone has a link at hand? Cant find it.

[daWallet]

@dcct

https://bitcointalk.org/index.php?topic=731923.msg8738422;topicseen#msg8738422

you're welcome

[dcct]

@dcct

https://bitcointalk.org/index.php?topic=731923.msg8738422;topicseen#msg8738422

Thank you 

[Dzus1k]

Any dice casino already ?

[enta2k]

can someone give me an example of a "too long deadline"?
I really dont know if mine are long or not

This is of course when doing solo
The system is set up to to average 4 minute blocks, so 240 seconds should be average. That means that half the time a 240 second deadline will win a block, and half the time it is too large. at 120 seconds it might be 1/4 risk you don't get a block, and at 60 it might be 1/8 risk someone is faster, etc. etc. conversely at 480 you will only win a block 1/4 of the time, at 960 only 1/8 of the time... i think.. not sure these calculations work out, but it ought to be something like that. i had one at 180 that did not win a block, and one at 114 that did win a block. Patience is pretty vital, I had to wait almost a week before i got a block, and i was cpu plotting like crazy on 3 pcs, 14 cores,  24/7 towards 4TB, so on average i must have had somewhat over 1TB plottable

Okay i have to say i don´t get it, you mean your system is giving you a result every 4 Minutes average?
Isn´t the average time set by the amount of space you are using?
I mined solo some time too and sometimes theres a result after 3 seconds and sometimes it takes ages.
Can you post a screenshot of what you mean, because i think i missunderstand it.

The thing is i plottet 6GB gpu and everyone says it´s worse than cpu plots,
i really would like to see if my average whatever time is good or bad.

[SpeedDemon13]

can someone give me an example of a "too long deadline"?
I really dont know if mine are long or not

This is of course when doing solo
The system is set up to to average 4 minute blocks, so 240 seconds should be average. That means that half the time a 240 second deadline will win a block, and half the time it is too large. at 120 seconds it might be 1/4 risk you don't get a block, and at 60 it might be 1/8 risk someone is faster, etc. etc. conversely at 480 you will only win a block 1/4 of the time, at 960 only 1/8 of the time... i think.. not sure these calculations work out, but it ought to be something like that. i had one at 180 that did not win a block, and one at 114 that did win a block. Patience is pretty vital, I had to wait almost a week before i got a block, and i was cpu plotting like crazy on 3 pcs, 14 cores,  24/7 towards 4TB, so on average i must have had somewhat over 1TB plottable

Okay i have to say i don´t get it, you mean your system is giving you a result every 4 Minutes average?
Isn´t the average time set by the amount of space you are using?
I mined solo some time too and sometimes theres a result after 3 seconds and sometimes it takes ages.
Can you post a screenshot of what you mean, because i think i missunderstand it.

The thing is i plottet 6GB gpu and everyone says it´s worse than cpu plots,
i really would like to see if my average whatever time is good or bad.

Double digit millions or larger is a really bad deadline.

[sickfancy]

how to solo on 3 computer?
can run wallet on computer A and run pocminer on computer B ,C ?

thanks

Sure you can. Probably you want a miner on Computer A, too.

Just add computer B and C to nxt.allowedBotHosts= in your config.

I'd like to try this when but not sure I understand.  I have 2 computers A and B each running wallet and mining.  I want to run wallet only on computer A.  To do this, I only need to add B to nxt.allowedBotHost= in computer A config?  I don't have to do anything to computer B?

[enta2k]

lol, for example my last dadline is 707506293144
Does this tell me, that my plot file is fucked?

[burstcoin]

lol, for example my last dadline is 707506293144
Does this tell me, that my plot file is fucked?

I'd say so. I don't know how much space your using, but on 2TB you'll almost always stay under 2mill at the current difficulty. Billions or higher is bad unless you have like a 10MB plot file.

[enta2k]

My plot file is 5,4TB and i plotted everything with gpu.
If this is causing a like 10mb performance, i really hope there will be a fix for the gpu plotter soon,
because, it takes almost a week to plot with cpu

You are the dude, if you say thats a very bad performance, i really should plot again with cpu,
as hard as it is, better plott forever than having like zero performance.

[pinballdude]

lol, for example my last dadline is 707506293144
Does this tell me, that my plot file is fucked?

either that, or that the plot file has very very few nounces in it, and is super small. I've had very small plot files under generation generate crazy deadlines, but deadlines improve a lot as the file grow in size, something like perhaps the best seen deadline over some period gets half as big, with double the filesize (or something like that)

my pc with 3TB plots right now has a minimum deadline of 4721 over the last 6 hours of mining, so it's not super easy to hit the small ones.

btw. it would be overly super cool if the java wallet server could be set up to add to a file the best deadline seen for every block one is mining. Such a log would be fun to have. The current log has to be set to log *A LOT* of stuff before the wallet starts logging deadline numbers.