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

Amount+Fee 9990+10 Nr. TX 1, what does this mean on my transaction list?

Is the source code available on GitHub, or just included in the wallet download?

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!  

More size of HDD = more found block. Like in every coin invest more get more.

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?

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

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

Okay so SSD Read speed id around 500 mb/s -> 120 gb?

it should be within 240 seconds to be exact, based on OP post of blocktime is 4 minutes

Any benchmarks yet about plot size limits aka what can you pc scan within 2000 seconds?

I did a few skims over the source today, a diff against NXT and a quick glance over all of the classes in the crypto library.  No hidden surprises in the wallet, no obviously blatent bugs/oversights, no shenanigans with hidden pre-mines etc.  This means the only argument someone could make to yell "SCAM" with would be the dev pre-generating some huge plot.  I think this is not so unfair at all, and would be hard to call scammy.

Overall an excellent launch.  Kudos to the dev(s)!

To be sure, I deleted all of jars, downloaded dependencies manually, and built from source on both linux and windows under cygwin.  Building on windows took some fiddling with classpath, but otherwise went fine.

I've generated a few GB of plot and am mining, but no blocks yet.  I'm assuming by now that some people already have huuuuge plots.

I think the mining process could be optimized a lot, but I personally don't have much time to put toward it and don't want to have to either trudge through java land or do a new implementation...  Maybe later.

I think this is a great concept and has a lot of promise to move blockchain technologies forward, but I worry about the economics of the coin.  It is hard to value "empty storage space over time" in a meaningful way.  It is pretty easy to quantify your availability of electric capacity under traditional PoW, as energy costs are fairly fixed.  Storage space is not very scarce, and it's costs (at large scales, anyway) are somewhat variable.

Hi. I have a problem here.
The plot generator got stuck in the middle of work (nonce 40000).
Now I have in the plots dir the file adr_0_81920, but it is only 10gb rather than 20gb.

How should I act now?
continue from 81921 or 40000?