Topic: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000 - page 1290. (Read 2170895 times)
August 11, 2014, 11:25:14 AM
Just to clarify, can I make a bunch of different plots, say from 1-100000, 100001-200000, 200001-300000 etc?
August 11, 2014, 11:24:48 AM
how the hell are people getting so many blocks when some cant get any.i have been mining since near start and nothing yet some have hit several blocks 
ive been here since block 2, still nothing either.
August 11, 2014, 11:23:52 AM
how the hell are people getting so many blocks when some cant get any.i have been mining since near start and nothing yet some have hit several blocks
Same here buddy 
August 11, 2014, 11:23:02 AM
how the hell are people getting so many blocks when some cant get any.i have been mining since near start and nothing yet some have hit several blocks
August 11, 2014, 11:17:37 AM
selling 59,900 Burst for 1 btc or 10k at .2 btc we can use escrow prefer just a quick honest sale.
August 11, 2014, 11:16:16 AM
Amount+Fee 9990+10 Nr. TX 1, what does this mean on my transaction list?
there are 1 transaction on that block
that transaction amount is 9990 + fee 10
anyway, is this ur address : BURST-YGB2-S53R-7MLK-4YB7A ?
August 11, 2014, 11:15:29 AM
Amount+Fee 9990+10 Nr. TX 1, what does this mean on my transaction list?
August 11, 2014, 11:04:30 AM
Is the source code available on GitHub, or just included in the wallet download?
its java, source included in wallet and miner
August 11, 2014, 11:03:19 AM
Is the source code available on GitHub, or just included in the wallet download?
August 11, 2014, 10:03:47 AM
hey any one tel me why it happen ,
my nonce went to 23k then its shows error and again start from nonce 1
already two times happen , anything wrong in my pc or else error
my nonce went to 23k then its shows error and again start from nonce 1
already two times happen , anything wrong in my pc or else error
August 11, 2014, 10:02:49 AM
I think that it's rather hard to understand the technical lingo due to this being a new algorithm and all, so here's an analogy:
Generating plots are like making treasure maps. It is:
1) Okay to transfer your treasure maps around because they will still contain the same information about the treasure(i.e. you can copy and paste a generated plot onto another HDD and mine from there)
2) Not useful to copy and paste the same treasure map and try to mine from both locations, because they'll all be telling you the same treasure locations (i.e. you cannot duplicate your generated plots onto different HDDs and run miners on both, both miners will be calculating the same nonces)
3) Okay to stop generating treasure maps for awhile, and continue generating from the last treasure map you've generated. (you can stop generating nonces to do other work, but when you continue, be sure to configure your run_generate.bat to start generating from the last nonce that you've generated).
I'm not sure if that is helpful to you, but it was to me in trying to understand this whole PoC thing. Best of luck in mining! Only got 2 blocks here, and I've got a 256 Gb plot!
Generating plots are like making treasure maps. It is:
1) Okay to transfer your treasure maps around because they will still contain the same information about the treasure(i.e. you can copy and paste a generated plot onto another HDD and mine from there)
2) Not useful to copy and paste the same treasure map and try to mine from both locations, because they'll all be telling you the same treasure locations (i.e. you cannot duplicate your generated plots onto different HDDs and run miners on both, both miners will be calculating the same nonces)
3) Okay to stop generating treasure maps for awhile, and continue generating from the last treasure map you've generated. (you can stop generating nonces to do other work, but when you continue, be sure to configure your run_generate.bat to start generating from the last nonce that you've generated).
I'm not sure if that is helpful to you, but it was to me in trying to understand this whole PoC thing. Best of luck in mining! Only got 2 blocks here, and I've got a 256 Gb plot!
Very nice analogy and easy to understand, thats how i got it too.
August 11, 2014, 10:01:05 AM
Any benchmarks yet about plot size limits aka what can you pc scan within 2000 seconds? 
it should be within 240 seconds to be exact, based on OP post of blocktime is 4 minutes
Okay so SSD Read speed id around 500 mb/s -> 120 gb?
i am updated my post, you dont need to read whole plot data each block, its only on relevant scoop, based on previous block hash
So basicly more machines don't really help in mining, just speed up plot generation because block chance depends on plot size?
Unless of course you reach your machines plot read limit but if it only reads 0.024% of your plot this would be around a few TB, hundreds?
More size of HDD = more found block. Like in every coin invest more get more.
Roger that, creation just takes time, 1tb plot needs about 24 gb of reading which is roughly the limit of a regular hdd, times 5 for ssd - have fun generating ^^
August 11, 2014, 10:00:34 AM
I think that it's rather hard to understand the technical lingo due to this being a new algorithm and all, so here's an analogy:
Generating plots are like making treasure maps. It is:
1) Okay to transfer your treasure maps around because they will still contain the same information about the treasure(i.e. you can copy and paste a generated plot onto another HDD and mine from there)
2) Not useful to copy and paste the same treasure map and try to mine from both locations, because they'll all be telling you the same treasure locations (i.e. you cannot duplicate your generated plots onto different HDDs and run miners on both, both miners will be calculating the same nonces)
3) Okay to stop generating treasure maps for awhile, and continue generating from the last treasure map you've generated. (you can stop generating nonces to do other work, but when you continue, be sure to configure your run_generate.bat to start generating from the last nonce that you've generated).
I'm not sure if that is helpful to you, but it was to me in trying to understand this whole PoC thing. Best of luck in mining! Only got 2 blocks here, and I've got a 256 Gb plot!
Generating plots are like making treasure maps. It is:
1) Okay to transfer your treasure maps around because they will still contain the same information about the treasure(i.e. you can copy and paste a generated plot onto another HDD and mine from there)
2) Not useful to copy and paste the same treasure map and try to mine from both locations, because they'll all be telling you the same treasure locations (i.e. you cannot duplicate your generated plots onto different HDDs and run miners on both, both miners will be calculating the same nonces)
3) Okay to stop generating treasure maps for awhile, and continue generating from the last treasure map you've generated. (you can stop generating nonces to do other work, but when you continue, be sure to configure your run_generate.bat to start generating from the last nonce that you've generated).
I'm not sure if that is helpful to you, but it was to me in trying to understand this whole PoC thing. Best of luck in mining! Only got 2 blocks here, and I've got a 256 Gb plot!
August 11, 2014, 09:56:45 AM
Any benchmarks yet about plot size limits aka what can you pc scan within 2000 seconds?
it should be within 240 seconds to be exact, based on OP post of blocktime is 4 minutes
Okay so SSD Read speed id around 500 mb/s -> 120 gb?
i am updated my post, you dont need to read whole plot data each block, its only on relevant scoop, based on previous block hash
So basicly more machines don't really help in mining, just speed up plot generation because block chance depends on plot size?
Unless of course you reach your machines plot read limit but if it only reads 0.024% of your plot this would be around a few TB, hundreds?
More size of HDD = more found block. Like in every coin invest more get more.
August 11, 2014, 09:56:30 AM
it could be improved by instead of storing un-relevant data, its store useful data.
for example to store a filesharing on blockchain, the larger u store people (network) file, the larger chance that ur nonce will be valid to announce block
for example to store a filesharing on blockchain, the larger u store people (network) file, the larger chance that ur nonce will be valid to announce block
So I look at this as proof of capacity
Www.storj.io is proof of storage. Storj is being developed to store data to build a decentralized cloud network.
The way I'm looking at these you could have free space devoted to storj. As that fills up and you need more delete a burst plot. But you can at least utilize your drive fully
August 11, 2014, 09:49:58 AM
Any benchmarks yet about plot size limits aka what can you pc scan within 2000 seconds?
it should be within 240 seconds to be exact, based on OP post of blocktime is 4 minutes
Okay so SSD Read speed id around 500 mb/s -> 120 gb?
i am updated my post, you dont need to read whole plot data each block, its only on relevant scoop, based on previous block hash
So basicly more machines don't really help in mining, just speed up plot generation because block chance depends on plot size?
Unless of course you reach your machines plot read limit but if it only reads 0.024% of your plot this would be around a few TB, hundreds?
August 11, 2014, 09:48:47 AM
Is it possible transfer the same data on a smaller hdd to larger and still mine with no issues? If mining with multiple hdd's on the same PC, how would it be possible to use one wallet to mine with or does it have to be separate ones in a multi-hdd setup?
August 11, 2014, 09:44:12 AM
Any benchmarks yet about plot size limits aka what can you pc scan within 2000 seconds?
it should be within 240 seconds to be exact, based on OP post of blocktime is 4 minutes
Okay so SSD Read speed id around 500 mb/s -> 120 gb?
i am updated my post, you dont need to read whole plot data each block, its only on relevant scoop, based on previous block hash
August 11, 2014, 09:43:54 AM
Dev any road map??? We need some exchange for it. 
August 11, 2014, 09:40:06 AM
Any benchmarks yet about plot size limits aka what can you pc scan within 2000 seconds?
it should be within 240 seconds to be exact, based on OP post of blocktime is 4 minutes
Okay so SSD Read speed id around 500 mb/s -> 120 gb?
Jump to: