Blago,
do not see the new files in the zip?
do not see the new files in the zip?
me too, only old dll files included, please update your zip, Blago
Topic: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000 - page 627. (Read 2171073 times)
October 20, 2014, 07:27:48 AM
me too, only old dll files included, please update your zip, Blago
October 20, 2014, 07:27:29 AM
@ Blago:
Can you at some point also include Runaurufu changes to the miner (no more memory caching).
https://burstforum.com/index.php?threads/windows-mining-guide.14/page-4
Can you at some point also include Runaurufu changes to the miner (no more memory caching).
https://burstforum.com/index.php?threads/windows-mining-guide.14/page-4
October 20, 2014, 07:22:14 AM
[miner]
Changed the way to work with the server now uses asynchronous transmission-reception.
Immediately after finding the best deadline, miner sends it to the pool (blue). Poole sets deadline in the queue for processing and after processing sends a confirmation (green).
Added the ability to use a local wallet for network scan the changed block (recommended).
you can enter any IP address.
Added parameter "Debug" - for paranoic mode
Tested for Uray's pool.
Dev's pools did not support yet.
new libs in zip-file: msvcr120d.dll msvcp120d.dll
src: https://github.com/Blagodarenko/miner-burst
update miner-burst-1.141020
https://www.dropbox.com/s/3fsmhysbxpp4hq4/miner-burst-1.141020.zip?dl=0
https://www.dropbox.com/s/3fsmhysbxpp4hq4/miner-burst-1.141020.zip?dl=0
Changed the way to work with the server now uses asynchronous transmission-reception.
Immediately after finding the best deadline, miner sends it to the pool (blue). Poole sets deadline in the queue for processing and after processing sends a confirmation (green).
Added the ability to use a local wallet for network scan the changed block (recommended).
Code:
"UpdaterAddr" : "localhost",
"UpdaterPort": 8125,
Added parameter "Debug" - for paranoic mode
Tested for Uray's pool.
Dev's pools did not support yet.
new libs in zip-file: msvcr120d.dll msvcp120d.dll
src: https://github.com/Blagodarenko/miner-burst
Blago,
do not see the new files in the zip?
October 20, 2014, 07:05:40 AM
[miner]
Changed the way to work with the server now uses asynchronous transmission-reception.
Immediately after finding the best deadline, miner sends it to the pool (blue). Poole sets deadline in the queue for processing and after processing sends a confirmation (green).
Added the ability to use a local wallet for network scan the changed block (recommended).
you can enter any IP address.
Added parameter "Debug" - for paranoic mode
Tested for Uray's pool.
Dev's pools did not support yet.
new libs in zip-file: msvcr120d.dll msvcp120d.dll
src: https://github.com/Blagodarenko/miner-burst
update miner-burst-1.141020
https://www.dropbox.com/s/3fsmhysbxpp4hq4/miner-burst-1.141020.zip?dl=0
https://www.dropbox.com/s/3fsmhysbxpp4hq4/miner-burst-1.141020.zip?dl=0
Changed the way to work with the server now uses asynchronous transmission-reception.
Immediately after finding the best deadline, miner sends it to the pool (blue). Poole sets deadline in the queue for processing and after processing sends a confirmation (green).
Added the ability to use a local wallet for network scan the changed block (recommended).
Code:
"UpdaterAddr" : "localhost",
"UpdaterPort": 8125,
Added parameter "Debug" - for paranoic mode
Tested for Uray's pool.
Dev's pools did not support yet.
new libs in zip-file: msvcr120d.dll msvcp120d.dll
src: https://github.com/Blagodarenko/miner-burst
October 20, 2014, 05:34:49 AM
...
blago,
in which version of miner is implemented this features highlighted in red?
thanks!
blago,
in which version of miner is implemented this features highlighted in red?
thanks!
Now this version is being tested, will soon be available on the public
so miner stops reading the file at that point? or it keeps trying until it's able to finish reading that file?
miner stops to read the file, since the end of file 
October 20, 2014, 05:19:46 AM
Obviously they do.
They start to panic, selling @ 90satoshi, that´s just how a stupid crowd reacts to a drop, silly humans
They start to panic, selling @ 90satoshi, that´s just how a stupid crowd reacts to a drop, silly humans
October 20, 2014, 05:14:47 AM
No, it's a bottom. Just look at the volume, yesterday was the lowest this month. No one wants to sell this cheap.
There is completely no reason to go above dogecoin price, which has 94 billion coins. Burst is much undervalued.
There is completely no reason to go above dogecoin price, which has 94 billion coins. Burst is much undervalued.
October 20, 2014, 05:11:31 AM
The owners of 1000Burst asset at Nxt Asset Exchange - please withdraw your BURST coins from Burst gateway with 5% interest (5% more BURST coins).
Just transfer your 1000BURST assets (not less than 1 asset) to the issuing account (NXT-VVTV-U25N-U2FY-2V35H) and in the attached message place your BURST address (in alpha-numeric format, like BURST-MCHC-LBKK-ZLZY-C3XL5).
Just transfer your 1000BURST assets (not less than 1 asset) to the issuing account (NXT-VVTV-U25N-U2FY-2V35H) and in the attached message place your BURST address (in alpha-numeric format, like BURST-MCHC-LBKK-ZLZY-C3XL5).
Those, who has 1000Burst assets at Nxt Asset Gateway and did not sellback at 50 NXT, please withdraw your BURST coins from Burst gateway with 5% interest.
October 20, 2014, 04:50:13 AM
I think the fail is way to much CPB, value will decrease more.
I liked this coin, nevermind.
I liked this coin, nevermind.
October 20, 2014, 04:44:02 AM
I cry for Burstcoin, 93 satoshi?
That´s sad, if it gets worse, i don´t have to sell, because it´s complety worthless.
That´s sad, if it gets worse, i don´t have to sell, because it´s complety worthless.
dev should do some marketing, or this coin will die.....
As long there is development and a community the coin can't die. The price will rise when people think the coin is cheap enough.
I wonder which translations for Burst do we have. I know about an german and a italian guide. Would be nice to get more and write them into the OP.
Especially translations for countries with a huge population like China, India, Southamerica - which have not so much money but a some HDD space left.
Nobody there can afford mining Bitcoin or some other Altcoin, but Burst!
I'll write some guide in spanish if we don't have one.
October 20, 2014, 04:36:02 AM
From the "shoddily made flow chart", this algorithm looks like essentially a more complex and simpler (in different ways) version of scrypt, just with very high memory requirements.
It is probably just as weak to ASICs, though I can't say for sure without more information.
Do actual specifications exist for the algorithm?
Also, is anyone interested in doing a BFGMiner port I can merge?
It is probably just as weak to ASICs, though I can't say for sure without more information.
Do actual specifications exist for the algorithm?
Also, is anyone interested in doing a BFGMiner port I can merge?
This algo mines via hdd capacity. Only way an asic would be useful is during the plotting process, but that's not a mining process.
This is essentially the same way scrypt works, except scrypt altcoins aren't using as much capacity.
The flowchart is missing the caching and retrieving from disk parts. Since the account id and nonces are run through the repeat hashing step before any network state is used, the results of the repeat hashing can be saved and reused every block, with the miner only having to do the repeat hashing once ever per nonce. This makes it so the computational expense of that initial repeat hashing can be increased any amount without causing miners to do any extra work after the initial caching process. The more expensive that repeat hashing step becomes, the more efficient using pre-cached work is over computing everything on the fly.
I'd be curious to follow up on this and see if Luke-Jr still thinks this coin is weak to ASICs.
October 20, 2014, 04:31:44 AM
I cry for Burstcoin, 93 satoshi?
That´s sad, if it gets worse, i don´t have to sell, because it´s complety worthless.
That´s sad, if it gets worse, i don´t have to sell, because it´s complety worthless.
dev should do some marketing, or this coin will die.....
October 20, 2014, 04:02:46 AM
I use Blago's miner across all of my 5 rigs (8 TB each) total 40 TB.
Since when Uray has changed his servers, I get lots of block which ends up even before my miner can complete reading the entire plots (~25 sec)
And I get really lot many blocks with this kind of message ! almost like once every 4-5 blocks (i.e. ~20-25%)
So who is the culprit here,
Uray's Pool which can't response in time after hardware change ?
Blago's miner which takes more time to sending the data ?
Something else which makes very short blocks & get those 20-25% blocks by solo ?
If it's something else, may be it's the reason why people reported above don't find enough blocks by solo !
Since when Uray has changed his servers, I get lots of block which ends up even before my miner can complete reading the entire plots (~25 sec)
Quote
-------------- New block 24862, basetarget 3581481 --------------
[2988616918834149562] confirmed deadline: 2954071 34d 4h 34m 31s
Thread "D:\plots\" done! [~25 sec] (18 files)
Thread "E:\plots\" done! [~25 sec] (18 files)
recieving data...
-------------- New block 24864, basetarget 3583972 --------------
shares lost due to new block
[2988616918834149562] confirmed deadline: 2954071 34d 4h 34m 31s
Thread "D:\plots\" done! [~25 sec] (18 files)
Thread "E:\plots\" done! [~25 sec] (18 files)
recieving data...
-------------- New block 24864, basetarget 3583972 --------------
shares lost due to new block
And I get really lot many blocks with this kind of message ! almost like once every 4-5 blocks (i.e. ~20-25%)
So who is the culprit here,
Uray's Pool which can't response in time after hardware change ?
Blago's miner which takes more time to sending the data ?
Something else which makes very short blocks & get those 20-25% blocks by solo ?
If it's something else, may be it's the reason why people reported above don't find enough blocks by solo !
miner sends data and waits for an acknowledgment from the server. In the first 2 minutes it takes a lot of time on overloaded servers.
Now I do asynchronous work with the server - first send all the data, and then we'll wait for them to confirm.
blago,
in which version of miner is implemented this features highlighted in red?
thanks!
what do you mean by highlighted? you put it super size, but why?
October 20, 2014, 04:00:41 AM
I cry for Burstcoin, 93 satoshi?
That´s sad, if it gets worse, i don´t have to sell, because it´s complety worthless.
That´s sad, if it gets worse, i don´t have to sell, because it´s complety worthless.
October 20, 2014, 03:15:20 AM
I use Blago's miner across all of my 5 rigs (8 TB each) total 40 TB.
Since when Uray has changed his servers, I get lots of block which ends up even before my miner can complete reading the entire plots (~25 sec)
And I get really lot many blocks with this kind of message ! almost like once every 4-5 blocks (i.e. ~20-25%)
So who is the culprit here,
Uray's Pool which can't response in time after hardware change ?
Blago's miner which takes more time to sending the data ?
Something else which makes very short blocks & get those 20-25% blocks by solo ?
If it's something else, may be it's the reason why people reported above don't find enough blocks by solo !
Since when Uray has changed his servers, I get lots of block which ends up even before my miner can complete reading the entire plots (~25 sec)
Quote
-------------- New block 24862, basetarget 3581481 --------------
[2988616918834149562] confirmed deadline: 2954071 34d 4h 34m 31s
Thread "D:\plots\" done! [~25 sec] (18 files)
Thread "E:\plots\" done! [~25 sec] (18 files)
recieving data...
-------------- New block 24864, basetarget 3583972 --------------
shares lost due to new block
[2988616918834149562] confirmed deadline: 2954071 34d 4h 34m 31s
Thread "D:\plots\" done! [~25 sec] (18 files)
Thread "E:\plots\" done! [~25 sec] (18 files)
recieving data...
-------------- New block 24864, basetarget 3583972 --------------
shares lost due to new block
And I get really lot many blocks with this kind of message ! almost like once every 4-5 blocks (i.e. ~20-25%)
So who is the culprit here,
Uray's Pool which can't response in time after hardware change ?
Blago's miner which takes more time to sending the data ?
Something else which makes very short blocks & get those 20-25% blocks by solo ?
If it's something else, may be it's the reason why people reported above don't find enough blocks by solo !
miner sends data and waits for an acknowledgment from the server. In the first 2 minutes it takes a lot of time on overloaded servers.
Now I do asynchronous work with the server - first send all the data, and then we'll wait for them to confirm.
blago,
in which version of miner is implemented this features highlighted in red?
thanks!
October 20, 2014, 02:11:07 AM
Difficulty increase too fast... can't catch up..
October 20, 2014, 01:58:50 AM
node update
URL US: burst-us.cryptomining.farm port 80
URL EU: burst-eu.cryptomining.farm port 80
URL SG: burst-sg.cryptomining.farm port 80
please restart your miner
thanks
URL US: burst-us.cryptomining.farm port 80
URL EU: burst-eu.cryptomining.farm port 80
URL SG: burst-sg.cryptomining.farm port 80
please restart your miner
thanks
October 19, 2014, 11:53:16 PM
I get quiet a few red lines about some plots being "locked?". But nothing uses the files beside the miner so I'm not sure what's going on.
This error occurs when the unexpected end of file.
Recalculate size/file name, reduce the "CacheSize".
Miner reads the file in chunks of CacheSize nonces, but suddenly the end of file (possibly in the middle).
October 19, 2014, 11:47:00 PM
The chart don't look interesting, might drop to 70-80 sats. Too much coins
October 19, 2014, 11:39:29 PM
350 burst a day last week, but it seems that burst price is too low, lots of miners leave away, now should be more, last week , has 6000TB, now seems only 5000TB
how do you calculate the total network hash?
Jump to: