Supercomputing,
It appears so, thank you for updating your miner to submit more than 4 ch, this will help this optimization be as fair as possible for those that do not understand how to modify it.
edit: we might want to run a check though before submitting share [GetPrimeDifficulty] to ensure it will be accepted by Coinshield Network. This will help reduce confusion concerning rejected shares. More debug output == less confusion
Viz.
Topic: Nexus - Pure SHA3 + CPU/GPU + nPoS + 15 Active Innovations + More to Come - page 331. (Read 785514 times)
September 30, 2014, 05:53:25 PM
September 30, 2014, 05:44:15 PM
Actual block submission log:
[METERS] 22 Block(s) ACC=22 REJ=0| Height = 6616 | Diff = 5.583707 | 16:44:10
Total Number of 4-Chains Found = 4339
[METERS] 22 Block(s) ACC=22 REJ=0| Height = 6616 | Diff = 5.583707 | 16:44:21
Total Number of 4-Chains Found = 4340
Total Number of 4-Chains Found = 4341
******* BLOCK FOUND *******
Preparing for Block Submission...
Submitting Block...
[MASTER] Prime Cluster of Difficulty 5.864469 Found on Thread 52
ed48c405cf83b4b38ad5a733ccb2250ab952cfbd6b8f6148f3b3c49885153e929d2180c25210614 adda8de6255c63060e9b191834e35d0ba5414099428e8aa07a1e437b90c333da18959522223275e 79bd2bc67826b021110a336e50935a299b4e18ff74718bee38a3e22770ccdadda7fb5882eb39af2 e3a6374358614a1873d
[MASTER] Block Accepted By Coinshield Network.
[MASTER] Coinshield Network: New Block 6617
[METERS] 23 Block(s) ACC=23 REJ=0| Height = 6617 | Diff = 5.586752 | 16:44:34
[METERS] 23 Block(s) ACC=23 REJ=0| Height = 6617 | Diff = 5.586752 | 16:44:45
[METERS] 23 Block(s) ACC=23 REJ=0| Height = 6617 | Diff = 5.586752 | 16:44:57
Total Number of 4-Chains Found = 4342
[METERS] 22 Block(s) ACC=22 REJ=0| Height = 6616 | Diff = 5.583707 | 16:44:10
Total Number of 4-Chains Found = 4339
[METERS] 22 Block(s) ACC=22 REJ=0| Height = 6616 | Diff = 5.583707 | 16:44:21
Total Number of 4-Chains Found = 4340
Total Number of 4-Chains Found = 4341
******* BLOCK FOUND *******
Preparing for Block Submission...
Submitting Block...
[MASTER] Prime Cluster of Difficulty 5.864469 Found on Thread 52
ed48c405cf83b4b38ad5a733ccb2250ab952cfbd6b8f6148f3b3c49885153e929d2180c25210614 adda8de6255c63060e9b191834e35d0ba5414099428e8aa07a1e437b90c333da18959522223275e 79bd2bc67826b021110a336e50935a299b4e18ff74718bee38a3e22770ccdadda7fb5882eb39af2 e3a6374358614a1873d
[MASTER] Block Accepted By Coinshield Network.
[MASTER] Coinshield Network: New Block 6617
[METERS] 23 Block(s) ACC=23 REJ=0| Height = 6617 | Diff = 5.586752 | 16:44:34
[METERS] 23 Block(s) ACC=23 REJ=0| Height = 6617 | Diff = 5.586752 | 16:44:45
[METERS] 23 Block(s) ACC=23 REJ=0| Height = 6617 | Diff = 5.586752 | 16:44:57
Total Number of 4-Chains Found = 4342
September 30, 2014, 05:26:35 PM
C] Total Number of 4-Chains Found = 214: When difficulty is 5.x 4 CH won't be accepted. The only logical reason I can see that chains are getting accepted above 5.x is somebody expanded supercomputing's code for 5.x and kept it private, or that the 4 ch that are found by his miner at random times are 5x too, which would account for so many rejects.
Correction, the wheel factorization procedure implemented in the code can efficiently sieve for prime twins, triplets, quadruplets, quintuplets, and sextuplets without any modifications to the code. But only prime constellations which meet the minimum difficulty requirements are submitted. The sieve is only for admissible k-tuples.
Please see:
http://math.mit.edu/~primegaps/
http://ocw.mit.edu/courses/mathematics/18-785-analytic-number-theory-spring-2007/lecture-notes/k_tuples.pdf
September 30, 2014, 03:50:50 PM
Everyone,
A] When wallet is encrypted, you need to unlock it to be able to mine. This is done with using RPC command walletpassphrase password.
This is why you cannot update height or mine with encrypted wallet.
B] Source code is closed to prevent clones from raping my hard work, so this puts more work upon my shoulders until it is released open source. It will be released in 1 -2 months with the opening of the first exchange channel; and trust me I'm just as excited as everyone to release it: this means more eyes, more minds, and a better code base.
C] Total Number of 4-Chains Found = 214: When difficulty is 5.x 4 CH won't be accepted. The only logical reason I can see that chains are getting accepted above 5.x is somebody expanded supercomputing's code for 5.x and kept it private, or that the 4 ch that are found by his miner at random times are 5x too, which would account for so many rejects.
D] Mining LLP can handle way more than 100 Requests per Second, I tested it up to 80k on a local IP and 10k remote using 128 byte packets.
E] Every mining connection has its own reserve key: Wallet::CReserveKey* pMiningKey. Keep in mind that Coinshield is running secp571r1 private keys, so building the keypool takes longer than with other alternative coins. A keypool size of 100 is fine to work with, for if another key is ever needed, it is created and added to the pool by the Mining LLP. I just started a wallet file with keypool size of 1000, and it started up just fine ~3 minutes. Keep in mind if your hard drive speed is slower this process can take longer.
Regards,
Viz.
A] When wallet is encrypted, you need to unlock it to be able to mine. This is done with using RPC command walletpassphrase password.
This is why you cannot update height or mine with encrypted wallet.
B] Source code is closed to prevent clones from raping my hard work, so this puts more work upon my shoulders until it is released open source. It will be released in 1 -2 months with the opening of the first exchange channel; and trust me I'm just as excited as everyone to release it: this means more eyes, more minds, and a better code base.
C] Total Number of 4-Chains Found = 214: When difficulty is 5.x 4 CH won't be accepted. The only logical reason I can see that chains are getting accepted above 5.x is somebody expanded supercomputing's code for 5.x and kept it private, or that the 4 ch that are found by his miner at random times are 5x too, which would account for so many rejects.
D] Mining LLP can handle way more than 100 Requests per Second, I tested it up to 80k on a local IP and 10k remote using 128 byte packets.
E] Every mining connection has its own reserve key: Wallet::CReserveKey* pMiningKey. Keep in mind that Coinshield is running secp571r1 private keys, so building the keypool takes longer than with other alternative coins. A keypool size of 100 is fine to work with, for if another key is ever needed, it is created and added to the pool by the Mining LLP. I just started a wallet file with keypool size of 1000, and it started up just fine ~3 minutes. Keep in mind if your hard drive speed is slower this process can take longer.
Regards,
Viz.
September 30, 2014, 01:11:35 PM
There might be issues on the wallet side but without the source code, our hands are tied.
And this is yet another reason why CoinShield wallet needs source code available.I was extremely interested in this project until the dev decided to keep it closed source without any good reason.
September 30, 2014, 12:29:43 PM
September 30, 2014, 11:50:17 AM
...or exchange?!
September 30, 2014, 08:40:27 AM
any news about pool?
September 30, 2014, 02:12:06 AM
Starting to make some progress on my issues. I've not been able to increase my keypool size (one of the reasons I didnt deploy a wallet with a shared wallet.dat to my VM's). When I run the daemon or QT with --keypool=xxx it just hangs indefinitely. I know it can take a little while to generate, but I gave up after 30 mins. I then checked my current size and found I had a keypool of just under 9000!! So I created a fresh wallet.dat in order to transfer my funds to it and found that I cannot send them all in one go, or indeed in any large amounts, as I get Transaction Creation Failed errors. So I'm guessing there is something wrong with my wallet. So I'm now transferring my funds piecemeal into a new wallet. I'll try mining again after that.
The woes continue. With an encrypted wallet, my miner gives "Failed to Update Height" whenever my wallet is locked. This has to be a bug.
September 30, 2014, 02:10:51 AM
We need a lot more voting on coinshieldtalk.org if you haven't signed up already please do! If you have signed up be sure to add your opinion to the existing petitions or create your own!
September 30, 2014, 01:26:57 AM
Just a reminder: Any questions or issues for Viz please post them here http://coinshieldtalk.org/forum/coin/technical-support
September 30, 2014, 01:00:44 AM
Starting to make some progress on my issues. I've not been able to increase my keypool size (one of the reasons I didnt deploy a wallet with a shared wallet.dat to my VM's). When I run the daemon or QT with --keypool=xxx it just hangs indefinitely. I know it can take a little while to generate, but I gave up after 30 mins. I then checked my current size and found I had a keypool of just under 9000!! So I created a fresh wallet.dat in order to transfer my funds to it and found that I cannot send them all in one go, or indeed in any large amounts, as I get Transaction Creation Failed errors. So I'm guessing there is something wrong with my wallet. So I'm now transferring my funds piecemeal into a new wallet. I'll try mining again after that.
September 30, 2014, 12:11:00 AM
https://www.dropbox.com/s/qszqn79q48828f4/CoinShieldV1.1.zip?dl=0
Added stats for accepted and rejected blocks.
Removed mutexes for a more reliable bock submission process.
I have some optimization ideas to improve the mining performance approximately 4x; they will be added to this miner after the GPU channel launch.
In 15 minutes, 1 cpu, 3 blocks, 3 rejects. So still having all rejects... had like 20 with previous miner.
Please verify that you are using the latest wallet software. This miner will not work correctly with the older wallet. I have mined 9 blocks with no rejects on a single machine in about 2 hours and 45 minutes.
That is correct, it seems as if the version numbers are the same. Also for now, the best way to deploy on virtual machines would be to also include a wallet with a large enough keypool in your master image. Then you can mine directly to the local wallet which will tremendously reduce latency.
September 29, 2014, 11:38:25 PM
https://www.dropbox.com/s/qszqn79q48828f4/CoinShieldV1.1.zip?dl=0
Added stats for accepted and rejected blocks.
Removed mutexes for a more reliable bock submission process.
I have some optimization ideas to improve the mining performance approximately 4x; they will be added to this miner after the GPU channel launch.
In 15 minutes, 1 cpu, 3 blocks, 3 rejects. So still having all rejects... had like 20 with previous miner.
Please verify that you are using the latest wallet software. This miner will not work correctly with the older wallet. I have mined 9 blocks with no rejects on a single machine in about 2 hours and 45 minutes.
September 29, 2014, 11:27:59 PM
https://www.dropbox.com/s/qszqn79q48828f4/CoinShieldV1.1.zip?dl=0
Added stats for accepted and rejected blocks.
Removed mutexes for a more reliable bock submission process.
I have some optimization ideas to improve the mining performance approximately 4x; they will be added to this miner after the GPU channel launch.
In 15 minutes, 1 cpu, 3 blocks, 3 rejects. So still having all rejects... had like 20 with previous miner.
Please verify that you are using the latest wallet software. This miner will not work correctly with the older wallet. I have mined 9 blocks with no rejects on a single machine in about 2 hours and 45 minutes.
September 29, 2014, 11:22:50 PM
https://www.dropbox.com/s/qszqn79q48828f4/CoinShieldV1.1.zip?dl=0
Added stats for accepted and rejected blocks.
Removed mutexes for a more reliable bock submission process.
I have some optimization ideas to improve the mining performance approximately 4x; they will be added to this miner after the GPU channel launch.
In 15 minutes, 1 cpu, 3 blocks, 3 rejects. So still having all rejects... had like 20 with previous miner.
There is something weird going on here. you had 3 blocks in 15 mins?
I've done another 1000 cores for an hour with the new miner, and I didn't find a single block. no errors, no rejects. I am using gmp 6.0.0
How many wallets are you using? If mining to a single wallet, it will generate hundreds of request a second. We do not yet have the ability to generate a new block hash without a roundtrip to the wallet. Would you please run a couple of cores on testnet. There might be issues on the wallet side but without the source code, our hands are tied.
Just one wallet. Agreed it would generate hundreds of requests a second. On day 1-2 this was no problem with ~500 cores/threads so unless your miner is generating significantly more requests it should be ok shouldn't it?. I've had to close my VM's down now. I think I might just have to stop mining until I can sell some coins to cover my costs as I have been racking up the costs without mining anything
September 29, 2014, 11:04:14 PM
i havent had any problems with ver 1.0 but the wallet doesnt show unconfirmed though im running windows with amd cpus phenom ii opterons and fx
September 29, 2014, 10:59:56 PM
https://www.dropbox.com/s/qszqn79q48828f4/CoinShieldV1.1.zip?dl=0
Added stats for accepted and rejected blocks.
Removed mutexes for a more reliable bock submission process.
I have some optimization ideas to improve the mining performance approximately 4x; they will be added to this miner after the GPU channel launch.
In 15 minutes, 1 cpu, 3 blocks, 3 rejects. So still having all rejects... had like 20 with previous miner.
There is something weird going on here. you had 3 blocks in 15 mins?
I've done another 1000 cores for an hour with the new miner, and I didn't find a single block. no errors, no rejects. I am using gmp 6.0.0
How many wallets are you using? If mining to a single wallet, it will generate hundreds of request a second. We do not yet have the ability to generate a new block hash without a roundtrip to the wallet. Would you please run a couple of cores on testnet. There might be issues on the wallet side but without the source code, our hands are tied.
September 29, 2014, 10:53:15 PM
https://www.dropbox.com/s/qszqn79q48828f4/CoinShieldV1.1.zip?dl=0
Added stats for accepted and rejected blocks.
Removed mutexes for a more reliable bock submission process.
I have some optimization ideas to improve the mining performance approximately 4x; they will be added to this miner after the GPU channel launch.
In 15 minutes, 1 cpu, 3 blocks, 3 rejects. So still having all rejects... had like 20 with previous miner.
There is something weird going on here. you had 3 blocks in 15 mins?
I've done another 1000 cores for an hour with the new miner, and I didn't find a single block. no errors, no rejects. I am using gmp 6.0.0
I'm finding blocks with new miner, I think GMP6.0.0 is faster on newer arch (eg haswell)
September 29, 2014, 10:42:04 PM
https://www.dropbox.com/s/qszqn79q48828f4/CoinShieldV1.1.zip?dl=0
Added stats for accepted and rejected blocks.
Removed mutexes for a more reliable bock submission process.
I have some optimization ideas to improve the mining performance approximately 4x; they will be added to this miner after the GPU channel launch.
In 15 minutes, 1 cpu, 3 blocks, 3 rejects. So still having all rejects... had like 20 with previous miner.
There is something weird going on here. you had 3 blocks in 15 mins?
I've done another 1000 cores for an hour with the new miner, and I didn't find a single block. no errors, no rejects. I am using gmp 6.0.0
Jump to: