Pool seems to be handling fork very well. I will start Super Block earlier this month around when the balance is 14k.
Thank you for mining at my pool and good luck with converting! I never had a lot of TB so I just replot.
Did you change the the reward recipient through the wallet or through the web page for changing recipient?
It would appear that you are still pointing to the burstnation burst4all pool, and there appears to be no reward recipient assignment changes on the block explorer looking at your address (although this could be a dymaxion thing)
Mine shows the following for when I changed the reward recipient -
Reward Recipient Assignment 12340918958792358241 0 Burst MBCG-4ERH-FVH5-2GTXB 2018-06-08 19:08:32
If you have not already tried the webpage for changing, you could give it a go at https://wallet.burst.cryptoguru.org:8125/rewardassignment.html
Other than that, does your miner work if you point it back to the burst4all pool?
Last post was deleted as I was trying to do it on my phone whilst out and about and it looked a mess
Just tried out the web-link and it records the change of recipient and updates the blockchain accordingly after a couple of blocks, so it looks like your change request has not been processed through for some reason
If you're using the modified Blago miner, test out different values for the cache/cache2 values - they can make a huge performance difference.
I tested with different values from 8K upto 512K. Then tested performance to 50% of plot read and 100% read. This is around 1PB of mixed PoC1 PoC2 plots - around 50/50. Some example readings:
256K/64K - 50% @ 2,950MB/s, Total: 120 Seconds
512K/64K - 50% @ 3,120MB/s, Total: 117 Seconds
512K/8K - 50% @ 3,600MB/s, Total: 189 Seconds (!)
512K/128K - 50% @ 2,800MB/s, Total: 99 Seconds.
As the ratio of PoC1 to PoC2 changes, I'd expect the optimal settings to change. As a general rule of thumb it seems to be: Use a larger C1/smaller C2 for a lot of Poc2 files, Large C2/Smaller C1 for a lot of PoC1 files.
@Zippymine No problem. The bright green means the deadline has been accepted as valid, but does not mean you have won the block. You should be able to check on your wallet for any blocks you have won under the "Forged (Mined) Balance" option
I had the same issue with my Synology NAS but I think i found a way to make it work.
Go to Computer > This PC > connect with network drive.
Then create One.
Go to Disk Management and create a Virtual Harddrive.
Paste the path where you want your Virtual HDD to be stored on your NAS.
After you Created a Virtual HDD you have to initialise the VHDD and create a new Volume.
Then it behaves like a local drive.
I am currently plotting my virtual drive...
Confirmed - use version 1.7.17 from here: https://github.com/Creepsky/creepMiner/releases
It can use PoC2 plots right now, and should be able to use PoC1 plots in the future while you get on with your conversion!
keep in mind that when you stop mining in a pool if the pool keeps finding blocks you keep winning, what you do not win now you get it later.
Changing pool costs only 1 burst so my advice for all is to try each pool for a week at least and see which one is best suited to you
@meni-menindorf said in 50-50-pool.burst.cryptoguru.org not recognizing my shares?:
That's like 30 hours? Geeze~
Can I ask, is crypto-guru the pool you use? I've switched pools a few times trying to find one that is the best fit~ I solo mined for a while with pretty good effect, but I just don't like the inconsistency~
The whole focus of mining is to accomplish three things:
Provide bookkeeping services to the coin network. Mining is essentially 24/7 computer accounting called 'verifying transactions'.
Get paid a small reward for your accounting services by receiving fractions of coins every couple of days.
Keep your personal costs down, including electricity and hardware.
That wallet isn't really a good idea you should upgrade to the latest qbundle because its compatible with network changes such as dymaxion which will be very soon and that's when your wallets version will no longer function I believe also it has he higher risk of being compromised being obsolete. We all pretty much have anti malware running one way or another. I use Microsoft. I turn off live cloud based protection that stops the wallet getting its throat cut as some terds just manually submit wallet code to make it look bad when it isn't. Latest wallet has new Blago miner that will still work after the fork. So to put it simply: uninstall your wallet install the latest one.
Nice setup @haitch!
@Eq I currently only have a few usb 3.0 drives running off of a 7 port hub (only 3 used at the moment). 1 8TB Seagate and 2 Western Digital 8TB. I thought it important to make sure the drives are running off of an external power source and not the ODROID just to make sure they're fully powered and you have more expansion options. I'm sure it would work fine plugging just two drives into the front USB 3 ports though if that's all you had.
I'm still experimenting on getting the total round time (read & verify) down in creepMiner, but it's a bit tricky. Ideally I'm trying to keep the round under 60s if possible, which I'm setting as my "drive limit". You're probably fine if you're under 4 min though. The beauty of such a cheap system is that you can just clone it and run multiples with a proxy for relatively low cost.
Don't use the latest 1.8.0 creepMiner. It has an extra database function that really slows down the ODROID. 1.7.16 works fine.
I've posted a little testing data here: https://www.minesomeburst.com/valid-deadlines-last-360-blocks/
I'm also looking into porting Blago's miner to Linux along with some possible optimizations for the NEON instruction set. We'll see how that goes after I've got some benchmarking in.
I don't know if you really NEED the eMMC module, but it's working pretty well for me thus far. It gives a little extra speed for messing around with compiling with different options, etc. Micro SD is cheaper by far though..
@ciscler Yep, same for me ... but as long as you do not run into memory issue, it will at least work. Now it is on you, how fast you get your plots converted. Best case would be to maybe convert up to 50% until the fork happens, and than convert the other 50% after it to reach normal scantimes again. Thats at least my strategy so far.