We have updated DigiByte scrypt pool with latest wallet. Will put some hashes in order to test and lower also the difficulty. |
|
|
|
That block still doesn't show up in the statistics as an orphan. Did you mean that any future orphans will show up, but not this one?
Yes, if the previous orphan block was not accepted by Nomp stratum, this block was not recorded into database. Thrassos has fixed this problem, all next blocks submitted should be displayed. Yes that is correct. Thank you very much MinersPoolEU. |
|
|
|
Thrassos, in your Skein DGB pool, I think the hashrate reported in the pool statistics is wrong. My cgminer says I have about 203Mh/s, your pool has been showing my hashrate between 1100Mh/s and 1600Mh/s. (edit: this looks like it's fixed now) Thank you bogglor. I think now hashrate is shown correctly in pool's statistics. Can you please confirm? Yes, it looks right now. I noticed something else with the Skein pool. This isn't a big deal, but we found an orphan block which isn't being reported in the pool statistics. I know we don't get any credit, but shouldn't that be listed in the pool? Thank you bogglor. This should be fixed now, as there was an issue with nomp stratum; it could not verify the submitted block because the blockhash using to do the verification was not correct. Moreover, the specific block is not shown as orphan in the transactions of our wallet (I will have to check this). [digibyte-skein] (Thread 1) We thought a block was found but it was rejected by the daemon, share data: {"job":"14f","ip":"xxx.xxx.xxx.xxx","port":5019,"worker":"xxxxxxxxxx","height":173577,"blockReward":757083663854,"difficulty":0.62335653,"shareDiff":"1802.29621833","blockDiff":1312.094260319,"blockDiffActual":1312.094260319,"blockHash":"0000000000245ca8930225c59debd1a267bcdbde27f2a77a2b810c68350bcfb9"} |
|
|
|
Thrassos, in your Skein DGB pool, I think the hashrate reported in the pool statistics is wrong. My cgminer says I have about 203Mh/s, your pool has been showing my hashrate between 1100Mh/s and 1600Mh/s. (edit: this looks like it's fixed now) Thank you bogglor. I think now hashrate is shown correctly in pool's statistics. Can you please confirm? |
|
|
|
Thanks, i have a strange feeling... With your miner, i get 12Mh/s with all pool on groestl. I have 2 270x.
But with the grs-sgminer i get 7-8 with all other pool than cryptohunger and 30Mh/s with cryptohunger ... same configuration. There is something inside the code of the grs-sgminer make by cryptohunger that can give some strange hashrate ? ...
I don't know but now i'm switching on qubit, earning is the same i think.
I don't know if this helps: http://myriad.theblockexplorer.com/help.php |
|
|
|
Someone could explain me something. I use grs-miner1_4_0 to mine grostl DGB... i get 30Mh/s in cryptohunger pool but if i go to other pool (p2p pools or love2hash) i get only 7-8Mh/s ... with the same kernel.
I don't understand, payout seems good with cryptohunger even seems there are less than we could have.
There is other grostl miner i can test ?
There is also SPH-SGMINER: https://bitcointalk.org/index.php?topic=475795.0Example usage: GPU_MAX_ALLOC_PERCENT=100 ./sgminer -k myriadcoin-groestl -o <host>:<port> -u <user> -p <password> -I 19 -g 4 -w 64 |
|
|
|
Moreover for pool owners. We can add at insight block explorer, in each found block the name and link of the pool that found the block. nomp stratum pools: You can change the scriptSigPart2 in node_modules/stratum-pool/lib/transactions.jsvar scriptSigPart2 = util.serializeString('/YourPoolsName/');python stratum pool: You can change the COINBASE_EXTRAS in your config.py file COINBASE_EXTRAS = '/YourPoolsName/' |
|
|
|
Anyone used this? http://digiaddress.org/I am considering transferring the majority of my DGB holding to a paper wallet... but not sure the best way to do it. I don't care what it looks like.... plain old piece of paper with the address/key pair is fine with me. Tested this with a 1 DGB send.... which sends without issue, can see it in the blockchain. Haven't been able to successfully re-import the private key though. Get " Error: Error parsing JSON:importprivkey". This happens both within Windows and Ubuntu. Any ideas? I have tested the key.html from nomp and it works. Can you check: http://love2hash.com/key.html? |
|
|
|
Pretty cool mining DGB in SCRYPT and SHA on your pool at the same time! Looks solid...
This is pretty cool.... but one request I'd like to make is the ability to auto-payout to different addresses for each algo. To accomplish this I created a second account for mining SHA... but that got old real quick logging into each account separately to view stats. So, back to my original account, mining Scrypt + SHA... but payouts going to single address. No biggie... just a nice to have. This can be done, however after that a different payment address will be needed for each DGB pool for all users. I will look into this later on today and let you know. |
|
|
|
Is there a way to see what the network hash rate for each algo is? Relatively speaking, how much hash is pointed at sha256 for instance compared to qubit?
I am just really curious to see if there is an algo that is favored by the miners compared to another.
Not sure how accurate it is, but you can see the net hash for all the NEW algos (not scrypt) at http://birdonwheels5.no-ip.org/dgb-hub/Also, tomorrow I'll be updating the rest of my website to reflect the Digibyte P2pool nodes + source code, and changing to Myriad logo on the node hub to the Digibyte logo (Didn't have time to change it a mist the chaos lol). However, I don't know if I'll ever get around to setting up an insight block explorer (Since someone else already made it... Unless that person is kind enough to share the networks file), but I might be able to get a richlist up... Eventually. Thing is, college is starting in 2 days, so I'm going to be tight on time. And since there isn't a bounty or anything... There's not too much incentive other than the curiosity of seeing how big your whales are :p Anyways, I'm going to leave my miners mining on qubit for the night and see how much I earn. Have fun mining, guys! birdonwheels5, I will sent you tomorrow (or later on today, as it's already 04:30 now) the networks file for insight  |
|
|
|
I think there is ... Thrassos are you sorting it ;-) It seems to be a problem with payments after the fork. Will try to sort out all payments manually for now. The same issue is happening also with scrypt pool. |
|
|
|
Thanks 24! Not sure how I missed that but, I appreciate it! Interesting ... I am using port 5015 and seems to be working. Thrassos ... do both ports work? The direct mining port for dgb-sha256d is 5015. The other one is a profit switching port for sha256 coins |
|
|
|
Groestl optimized pool is now working on http://cryptohunger.com:81/3 blocks found already. Please join. The pool is using optimized groestlmyriad kernel and achieves 34.0 MH/s on AMD R9 290. Diff on cryptohunger and love2hash seems different... i think there is a problem That is the pool difficulty. Depending on which port you connect to for each algo you can set different difficulties. Network is this right now:
13:24:42

getmininginfo
13:24:42

{
"blocks" : 145332,
"currentblocksize" : 0,
"currentblocktx" : 0,
"pow_algo_id" : 0,
"pow_algo" : "sha256d",
"difficulty" : 1606912.97427173,
"difficulty_sha256d" : 1606912.97427173,
"difficulty_scrypt" : 90.04959529,
"difficulty_groestl" : 2.15371644,
"difficulty_skein" : 159.32535613,
"difficulty_qubit" : 2.11252134,
"errors" : "",
"genproclimit" : -1,
"pooledtx" : 0,
"testnet" : false,
"generate" : false,
"hashespersec" : 0
}
You can see the difficulties also at: http://insight.dgb.cryptopoolmining.com/status |
|
|
|
You guys can see all my node stats (all of them) at http://birdonwheels5.no-ip.org/dgb-hubI was the one who instamined on Skein.... Not sure why but the network keeps rejecting my transactions when I try to send I do have the same issue with sha256: ERROR --> E0078: RPC method did not return 200 OK: Address: DKCxg5Hp5VdHzF5bcdU9DK18hPoGiD5ekM ERROR: RPC call did not return 200: HTTP error: 500 - JSON Response: [-4] Error: The transaction was rejected! This might happen if some of the coins in your wallet were already spent, such as if you used a copy of wallet.dat and coins were spent in the copy but not marked as spent here. |
|
|
|
|
Show Posts
