Author

Topic: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000 - page 1132. (Read 2170889 times)

full member
Activity: 138
Merit: 100
what is the difference between -Xmx2048M and -Xmx8192M? is there any impact to finding a block?
full member
Activity: 238
Merit: 100
Nothing was changed in regards to getting wallet info, so there shouldn't be any difference. Did you change something in your config on 1.0.2 and not copy it over?

With 1.0.2 the results were:
{"result":"deadline: 18684"}

Now its:
{"result":"success","deadline":18684}

Just noticed, caused no problems  Wink

yeah first time seeing that message i though i've found a block LOL
i have not found a block within nearly 30 hours Cry can feel the deeply calling by the pool v2
hero member
Activity: 781
Merit: 501
Nothing was changed in regards to getting wallet info, so there shouldn't be any difference. Did you change something in your config on 1.0.2 and not copy it over?

With 1.0.2 the results were:
{"result":"deadline: 18684"}

Now its:
{"result":"success","deadline":18684}

Just noticed, caused no problems  Wink

yeah first time seeing that message i though i've found a block LOL
full member
Activity: 238
Merit: 100
just before you announced the update my miner started with cant get info from wallet even though I have wallet opened in IE and running.  I then updated and it still says the same thing???

Yeah, same problem here. You mining on the pool as well, I assume?
Pool is down at the moment. I took it down to update the wallet, and it's not loading the current state correctly. If I can't figure it out in a few more minutes I'm just going to load it back up as-is and we'll have one screwed up payout on its next block and it should be fine after that.

EDIT: brought the pool back up, not worth the downtime. for some reason it didn't pick up on what its last block was, and loaded all shares submitted instead of just the current ones, so payout will be wrong once, then should be normal.
the same problem, with wallet 1.0.3 always report can't get wallet info, is the wallet's bug? or we should use 1.0.2 back and wait the next 1.0.3 or the wallet is fine?
Nothing was changed in regards to getting wallet info, so there shouldn't be any difference. Did you change something in your config on 1.0.2 and not copy it over?
Ok, find the reason, my memory is nearly full, when it reached some level, miner will disconnect with wallet, while wait a will when memory usage falls, then connect the wallet back  :)again
sr. member
Activity: 280
Merit: 250
Nothing was changed in regards to getting wallet info, so there shouldn't be any difference. Did you change something in your config on 1.0.2 and not copy it over?

With 1.0.2 the results were:
{"result":"deadline: 18684"}

Now its:
{"result":"success","deadline":18684}

Just noticed, caused no problems  Wink
sr. member
Activity: 302
Merit: 250
If you don't copy the blockchain by hand like explained, the new wallet has to download it -> This may result the loss of wallet info 'till it's downloaded again.
sr. member
Activity: 280
Merit: 250
just before you announced the update my miner started with cant get info from wallet even though I have wallet opened in IE and running.  I then updated and it still says the same thing???

Yeah, same problem here. You mining on the pool as well, I assume?
Pool is down at the moment. I took it down to update the wallet, and it's not loading the current state correctly. If I can't figure it out in a few more minutes I'm just going to load it back up as-is and we'll have one screwed up payout on its next block and it should be fine after that.

EDIT: brought the pool back up, not worth the downtime. for some reason it didn't pick up on what its last block was, and loaded all shares submitted instead of just the current ones, so payout will be wrong once, then should be normal.
the same problem, with wallet 1.0.3 always report can't get wallet info, is the wallet's bug? or we should use 1.0.2 back and wait the next 1.0.3 or the wallet is fine?
Nothing was changed in regards to getting wallet info, so there shouldn't be any difference. Did you change something in your config on 1.0.2 and not copy it over?
full member
Activity: 238
Merit: 100
just before you announced the update my miner started with cant get info from wallet even though I have wallet opened in IE and running.  I then updated and it still says the same thing???

Yeah, same problem here. You mining on the pool as well, I assume?
Pool is down at the moment. I took it down to update the wallet, and it's not loading the current state correctly. If I can't figure it out in a few more minutes I'm just going to load it back up as-is and we'll have one screwed up payout on its next block and it should be fine after that.

EDIT: brought the pool back up, not worth the downtime. for some reason it didn't pick up on what its last block was, and loaded all shares submitted instead of just the current ones, so payout will be wrong once, then should be normal.
the same problem, with wallet 1.0.3 always report can't get wallet info, is the wallet's bug? or we should use 1.0.2 back and wait the next 1.0.3 or the wallet is fine?
full member
Activity: 194
Merit: 100
hero member
Activity: 781
Merit: 501
It can, but AWS is expensive.

how much for the 1 tera?
[/quote]

24$/Month
[/quote]

can it rent by day or hour?
sr. member
Activity: 280
Merit: 250
can be done with AWS on amazon
free for some gb and some hd space ?

It can, but AWS is expensive.

how much for the 1 tera?

24$/Month
legendary
Activity: 3248
Merit: 1070
can be done with AWS on amazon
free for some gb and some hd space ?

It can, but AWS is expensive.

how much for the 1 tera?
sr. member
Activity: 280
Merit: 250
A scaling factor is used and adjusted based on recent block times to attempt to get 4min/block. The difficulty used internally is (2^64)/scaling_factor. What is displayed in nrs info is cumulative difficulty(block 1 dif + block 2 dif + ... + block n dif).

A general difficulty -> TB amount could likely be found but I don't know it.

Just as a suggestion: Now we have to calculate the results as quick as possible as some deadlines are just a few seconds.

Why don't we just add some seconds to the deadline, just to give everyone enough time to finish processing?

And some blocks take too long. We can just add some math to reduce them!

Code:
Say: Actual deadline = (calculated_deadline ^ 0.8) + 120

10s => 126s
100s => 160s
240s => 200s
300s => 215s
1000s => 371s
3600s => 820s

This way we average at around 240s again, have some extra time for slow HDD/CPU's and avoid extra long block solving times.

If you like it I can do the math to get exactly back to 240s average.

I thought of this also, however I never got around to examining it in depth for potential repercussions. It might be possible that a function like that could open it up to sub 51% attacks. One potential attack vector that comes to mind is if an attacker mined their own chain with timestamps intentionally boosting the difficulty, then they would be avoiding the +120 seconds more, and would have the *0.8 reduction apply to more of their total deadline each time. This might allow them to build up the cumulative difficulty faster than they should be able to with that amount of TB.
newbie
Activity: 35
Merit: 0
I like to announce:

The Plot-generator rewritten in C!

It has several advantages over the one written in Java:
- About twice as fast
- Support for larger stagger sizes, only limited by system memory
- More efficient memory handling. With just 3GB you can use Stagger size 8191, with 8GB 24000 is possible. Plots with larger stagger sizes are better, as they require less disk seeks to be read.

You need a 64bit Linux environment to run this. Maybe someone can port it to Windows?

How to run it:
Download, unpack (tar -xzf plotgenerator.tgz), compile (make)

Then use the same command line options as with the Java-generator:

Code:
./plot     

You can download it here:
https://bchain.info/plotgenerator.tgz


Anyone have any luck compiling this for Windows? It runs fine in Linux after compiling.

I used the this in terminal in Linux after I compiled it: "x86_64-w64-mingw32-gcc plot -o plot.exe"

Then I try to run it on Windows and can not run. I think I am suppose to use "x86_64-w64-mingw32-g++ plot -o plot.exe"

My skills are novice in compiling, so any help is greatly appreciated. Once I can get this running, I'll share a link to download it for Windows users.


where is a link ? _)

I'm still trying to work on it, but remember my coding skills is novice at best. I can not make any promises if I even get it to run.


using 2047 MB memory

i have 32 GB RAM
how i can make more memory for plotting?
sr. member
Activity: 280
Merit: 250
can be done with AWS on amazon
free for some gb and some hd space ?

It can, but AWS is expensive.
hero member
Activity: 518
Merit: 500
just before you announced the update my miner started with cant get info from wallet even though I have wallet opened in IE and running.  I then updated and it still says the same thing???

Yeah, same problem here. You mining on the pool as well, I assume?
Pool is down at the moment. I took it down to update the wallet, and it's not loading the current state correctly. If I can't figure it out in a few more minutes I'm just going to load it back up as-is and we'll have one screwed up payout on its next block and it should be fine after that.

EDIT: brought the pool back up, not worth the downtime. for some reason it didn't pick up on what its last block was, and loaded all shares submitted instead of just the current ones, so payout will be wrong once, then should be normal.

You should take it down if you need to prepare it. Think the community wouldn't mind.
legendary
Activity: 1188
Merit: 1001
can be done with AWS on amazon
free for some gb and some hd space ?
sr. member
Activity: 280
Merit: 250
just before you announced the update my miner started with cant get info from wallet even though I have wallet opened in IE and running.  I then updated and it still says the same thing???

Yeah, same problem here. You mining on the pool as well, I assume?
Pool is down at the moment. I took it down to update the wallet, and it's not loading the current state correctly. If I can't figure it out in a few more minutes I'm just going to load it back up as-is and we'll have one screwed up payout on its next block and it should be fine after that.

EDIT: brought the pool back up, not worth the downtime. for some reason it didn't pick up on what its last block was, and loaded all shares submitted instead of just the current ones, so payout will be wrong once, then should be normal.
sr. member
Activity: 336
Merit: 250
Yeah on the pool, glad its not just me!
hero member
Activity: 672
Merit: 500
I can't seem to pool mine, is that intentional for now?
I have updated to 1.0.3 but it says can't get mining info from wallet.
Jump to: