Author

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

legendary
Activity: 1036
Merit: 1000
https://bmy.guide
}
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
No valid shares to submit to pool
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
{

This randomly happens ~1-3 times a day, where I get this message spammed at me in the command prompt.  As far as I can tell, I'm still getting payments and all from pool.  Anything I should be worried about?
I don't know about the other 0-2 times per day, but I restarted my v2 pool a few minutes ago applying an update.

i accidentally sent the v2 pool 500 coin three times lol
full member
Activity: 126
Merit: 100
The price is down and i think it's a good time to buy some,don't mine it,just buy it
sr. member
Activity: 280
Merit: 250
}
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
No valid shares to submit to pool
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
{

This randomly happens ~1-3 times a day, where I get this message spammed at me in the command prompt.  As far as I can tell, I'm still getting payments and all from pool.  Anything I should be worried about?
I don't know about the other 0-2 times per day, but I restarted my v2 pool a few minutes ago applying an update.
legendary
Activity: 1164
Merit: 1010
}
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
No valid shares to submit to pool
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
Error: Unable to get mining info from wallet
{

This randomly happens ~1-3 times a day, where I get this message spammed at me in the command prompt.  As far as I can tell, I'm still getting payments and all from pool.  Anything I should be worried about?
sr. member
Activity: 423
Merit: 250
Wow some of you guys, the underhanded tactics here are ridiculous.

People are telling other people to bag hold so THEY can dump at good prices. Holding off selling prices, will not increase demand for the coin, it'll make a artificial bubble, which of course will be even more dramatic when it actually pops, because more people are bag holding and instead of a gradual decrease in the value of the coin to equilibrium in which people can see and take it into account, it'll just straight off bomb.

The 'taking awhile to plot keeps big guys out' is complete BS, it just has a longer spool up time. It'll still result in people getting on the coin only later and the coin looks deceptively profitable because of it. As I said in my earlier post, there are tons of people spooling up storage right now, so even though the coin looks profitable, it is for people that got into it like a week ago or more. Big miners can just as easily partition storage and run more then one miner as it would take less time to plot (I'm not sure why people aren't doing this anyway). If the processor isn't being pegged, that means you can run more miners either through partitions or hard partitions (such as with firmware). Using a pool this really isn't a issue.

This also appears to be a 'I had to do it, so other people should' sort of thing. There are already people taking a week before they can start making profits so they want other people to take a week as well, so they can have that week to 'get ahead'. Thats also why people are poopooing on GPU assisted plotting, because it will reduce entry time and reduce the time they have to maintain more profitability, even though it'll be better for the coin in the long run as the amount of time miners have to react to the market will be less (so less people will still be jumping on the coin when it becomes less profitable).

Bag holding wont help this coin, production of coins is outstripping demand right now and trying to hold the price artificially higher then its equilibrium will just lead to the coin diving worse in the future due to panic sells. There is ALOT of coins out there and very few BTCs on CCEX to match it. This coin really needs to get on a major exchange before the BTC on CCEX dries up. Buys on CCEX literally halved in the last two days.
full member
Activity: 238
Merit: 100
every of you crying pumping whole the day, but so little will vote this coin
https://hitbtc.com/vote
everyone can vote at least 2 votes, logout and sign up both can vote, but you didn't even click it , did you, from blockexplore, at least 830 miners have solo to get a block , not including those new miners who join the pool , but several days passed, only 300 votes in it, that means only 100+ pepople vote it, i have vote 5 times, you guys crying other exchange whole the day, but didn't willing to take a little time to vote it,, that's funny
if you guys want the coin be popular, vote it, no matter what the exchange, more people know this coin, more popular of it
legendary
Activity: 3248
Merit: 1070
is the last dcct released for windows?
hero member
Activity: 646
Merit: 500
hero member
Activity: 588
Merit: 500
What, price is going up again!?
Some good news might be coming  Wink

Not sure what to think yet, anyway I'm just holding on, hoping for better adoption, and more devs(more devs like burstcoin, he/she's just amazing!!!).
hero member
Activity: 672
Merit: 500
What, price is going up again!?
Some good news might be coming  Wink
hero member
Activity: 672
Merit: 500
sr. member
Activity: 504
Merit: 250
why are people dumping this coin?
hero member
Activity: 588
Merit: 500
What, price is going up again!?
hero member
Activity: 955
Merit: 1004
My 4 3 TB drivs are going to take 10 days or more to plot, and as much as I'd like to have them done NOW, I must agree.  The length of time to plot will help keep big farms out.
member
Activity: 112
Merit: 10
Burstcoin, could you please post your GPU plotter?  I know it's incomplete, but I would love to take a look at it.

First implementation:
http://pastebin.com/UccPBr4B

Slower than dcct's plotter.
Takes an array as a parameter of workgroupsize * 262160 bytes. Expects the address/nonce as last 16 bytes of each 262160 byte chunk, and the 262144 before that are written to as output for that plot.
Seems to work ok.

Second attempt:
http://pastebin.com/pQAhvbc2

Don't know if it works or not since it's too slow.
Parameters: array of 16 bytes * workgroupsize, with address/nonce filled in each 16 bytes. array 262144 * workgroupsize for output. local buffer of size 32768 bytes
I can't figure out why it's slower. Some restructuring was done to avoid conditionals, and a rotating buffer was used to read from faster local memory instead of hammering global. The problem seems to be writing the results to global memory, since commenting that out makes it run fast, but obviously won't give correct results.

Any input would be appreciated, since I'm about ready to give up on making a gpu plotter.

If you want this thing to not become another Doge then I think the best thing to do is abandon the idea of a GPU plotter - as soon as that happens every asshole and his dog will be down to Bestbuy for 10x 4TB harddrives on the old Mastercard and rape this thing to death.

The current slowness for plotting at least provides a barrier to entry to the massive storage farms.
hero member
Activity: 955
Merit: 1004
Hurry rape the fuck of out this coin as many others do to any new coin. That's why I am sure crypto won't last, be sure to milk every last cent and then sell those half burnt out hard drives to other suckers you computer repair guys always do.

No.  Believe it or not, I am one of the best and most ethical PC repair people you will ever meet.  I am far better than anyone at Geek Squad.  I take the time to make sure my work is done right.  I zero wipe hard drives before formatting and reloading Windows even though it's probably not necessary.  I refuse jobs on computers that are too old to bother spending money on.  I test all hard drives with several testing programs and anything that fails my high standards gets replaced.  As a businessman, it is better to have a happy customer and make less profit, than to squeeze someone for extra cash and their PC has inadequate parts.
sr. member
Activity: 336
Merit: 250
What a bunch of douche bags, are the same guys with a thread on here?
sr. member
Activity: 462
Merit: 250
Thanks, burstcoin.
legendary
Activity: 1164
Merit: 1010
Burstcoin, could you please post your GPU plotter?  I know it's incomplete, but I would love to take a look at it.

First implementation:
http://pastebin.com/UccPBr4B

Slower than dcct's plotter.
Takes an array as a parameter of workgroupsize * 262160 bytes. Expects the address/nonce as last 16 bytes of each 262160 byte chunk, and the 262144 before that are written to as output for that plot.
Seems to work ok.

Second attempt:
http://pastebin.com/pQAhvbc2

Don't know if it works or not since it's too slow.
Parameters: array of 16 bytes * workgroupsize, with address/nonce filled in each 16 bytes. array 262144 * workgroupsize for output. local buffer of size 32768 bytes
I can't figure out why it's slower. Some restructuring was done to avoid conditionals, and a rotating buffer was used to read from faster local memory instead of hammering global. The problem seems to be writing the results to global memory, since commenting that out makes it run fast, but obviously won't give correct results.

Any input would be appreciated, since I'm about ready to give up on making a gpu plotter.

So...I could use gpu plotter for one plotting on one drive, and cpu plotter for another drive?  See any probs with that as long as I get the ranges right?
Jump to: