Simple plotting process description
-
@k06a if plotter makes gaps, miner read it as zeroed bytes (or garbage), calculate deadline, send #nonce to the pool, pool calculate it again, got deadline and compare. Then pool send to miner "Your deadline wrong"
p.s. my English too bad for describing whole process.
@luxe help :)
-
@Blago thanks for your message, looks like 1 nonce gap will shrink your mining size.
-
@k06a На русском будет проще рассказать, Антон
-
So for [n0s0], this is a 64 byte word or 512 bits. I think that this value is some algorithm output with inputs nonce, scoop and acct id hashed together?
What is the algorithm?E.G., For scoop 4000 and nonce 120001 and account id 7979631613202555765:
Is the algorithm "4000+120001+7979631613202555765" (string) ==>>sha 512==>>digest ===>>>[n120001,S4000]?
or "12001+4000+7979631613202555765" (string) ==>>sha 512==>>digest ===>>>[n120001,S4000].
or is it "4000+120001+7979631613202555765" (hex addition) ==>>sha 512==>>digest ===>>>[n120001,S4000]?
Or something else?
I think that's what @k06a needs to know how to develop his own optimized plotter.
-
@rds
https://github.com/Blagodarenko/XPlotter/blob/master/Nonce.cpp#L244[n0s0] this is a 64 bytes
do_something("120001+7979631613202555765") ==>>sha 256==>>digest ===>>>[n120001]
then we split each nonce by parts and write them to the file in different places[n120001s0][n120001s1][n120001s2][n120001s3]...[n120001s4095]
https://github.com/Blagodarenko/XPlotter/blob/master/Nonce.cpp#L275
-
@Blago said in Simple plotting process description:
@rds
https://github.com/Blagodarenko/XPlotter/blob/master/Nonce.cpp#L244[n0s0] this is a 64 bytes
do_something("120001+7979631613202555765") ==>>sha 256==>>digest ===>>>[n120001]
then we split each nonce by parts and write them to the file in different places[n120001s0][n120001s1][n120001s2][n120001s3]...[n120001s4095]
https://github.com/Blagodarenko/XPlotter/blob/master/Nonce.cpp#L275
So the digest of sha256 is 256 bits or 32 bytes. So where do the other 32 bytes come from?
Are you saying you split nonce 120001 apart? how?
-
@rds
better to see, than describe
https://ip.bitcointalk.org/?u=http%3A%2F%2Fi.imgur.com%2FalnEGIj.jpg&t=577&c=NWqgoPs7-7AVPAright side
-
@Blago said in Simple plotting process description:
@rds
better to see, than describe
https://ip.bitcointalk.org/?u=http%3A%2F%2Fi.imgur.com%2FalnEGIj.jpg&t=577&c=NWqgoPs7-7AVPAright side
Very nice, thanks
-
@Blago Given the variety of topics covered in this thread, I'll throw mine in - if using the same nonce Algorithm calculation, how is it that clients and pools so drastically disagree on some DL's? Why does a 50 second DL on my miner get rejected as a 50,000Year DL from the pool ? In flight TCP corruption ?
-
@haitch when miner found DL, it send to the pool only #nonce and own ID.
Pool calculate DL based at #nonce, ID and generationSignature.
If generationSignature which was used when miner tried find DL not the same as pool's generationSignature (new block at pool), then pool get wrong DL
(or user's plot corrupted :) )
-
@Blago Seeing as the client and pool are still mining the same Block when I get this error, I think I have some replotting to do ....
-
if it helps, last November i used a tcp packet inspector on a few pools it reported many malformed packets from the pool at random intervals. Those kinds of errors occurred with all flavors of miners and pools I intend to look for signs of it again in future to determine when it is at risk of occurring. For example: does it occur when the pool is busy or not, if its the difference between a pool ran on the pool owners computer or his/hers remote managed vps. What prompted me to do such was miner errors on both rx and tx.
-
Good thread. Very informative. @Blago, spacibo! Ochen xoroscho.
-
@haitch, I seem to recall you saying you were plotting some SMR drives recently. Hope those plots are "good". I think I'd rather have some of your hot sauce poured in my eyes before replotting an SMR a second time! Plotting 4rth of 5 8TB SMRs now. I'm learning the true meaning of patience.
-
@Evo The SMR's finally finished plotting, and no bad plot errors so far. I've got another 6 * 8TB non-SMR drives on order - I'll plot all of them in way less time than the two SMR drives took.
And no one should ever have my sauces poured in their eyes!!!!
