> Block maturity was changed to 100 confirmations up from 8.
Hi!
Sorry, could you elaborate on this?
Are you saying that the problem does not exist? Or that I need to update the wallet?
Thanks
I found this code in rpcwallet.cpp: if (params[0].get_str() == "*") {
// Calculate total balance a different way from GetBalance()
// (GetBalance() sums up all unspent TxOuts)
// getbalance and getbalance '*' 0 should return the same number
int64_t nBalance = 0;
for (map<uint256, CWalletTx>::iterator it = pwalletMain->mapWallet.begin(); it != pwalletMain->mapWallet.end(); ++it)
{
const CWalletTx& wtx = (*it).second;
Notice the comment "getbalance and getbalance '*' 0 should return the same number". It does not return the same number. Proof:  Thanks for posting this! |
|
|
|
|
Time-stamp: 1:05 PM Mt Time, Block: 145,284
Time-stamp: 3:21 PM Mt Time, Block: 145,566
282 blocks in 136 minutes. 30 second target = 272 blocks.
Out of 282 blocks:
algo=0 | 64 blocks
algo=1 | 57 blocks
algo=2 | 73 blocks
algo=3 | 44 blocks
algo=4 | 51 blocks
Will up date this post every hour with block count to get a rolling average for first few hours.
You can check which algo is generating which blocks by looking in the debug.log in your appdata folder.
|
|
|
|
|
We are going to pause Love2hash and push out manual payments. We have a couple things we need to update to get payouts auto like they should be. In the mean time try some of the other pools or solo mining.
|
|
|
|
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. Hi developers, I think that there is a bug in wallet code. The mined transactions appear to be "matured" and show up as "available" in wallet. But when you try to send these DGB, you're getting "CheckInputs() : Maturity v2" error. 2014-09-01 20:52:10 CommitTransaction:
CTransaction(hash=d792e8ef2a, ver=1, vin.size=2, vout.size=2, nLockTime=0)
CTxIn(COutPoint(a05c1c505e, 1), scriptSig=30440220091b378e17be16b5)
CTxIn(COutPoint(c152b2cdb8, 1), scriptSig=3045022100c09cf538ca2c88)
CTxOut(nValue=74.21773944, scriptPubKey=OP_DUP OP_HASH160 f2fe1a86beb0)
CTxOut(nValue=3000.00000000, scriptPubKey=OP_DUP OP_HASH160 e49622db98a1)
2014-09-01 20:52:10 keypool keep 31
2014-09-01 20:52:10 AddToWallet d792e8ef2aa012deec8f2108c4ba9aa05d70053b2deb0cce8bc0b47385f12b3e new
2014-09-01 20:52:10 ERROR: CheckInputs() : Maturity v2: tried to spend coinbase at depth 68 145498 145430 100
2014-09-01 20:52:10 ERROR: AcceptToMemoryPool: : ConnectInputs failed d792e8ef2aa012deec8f2108c4ba9aa05d70053b2deb0cce8bc0b47385f12b3e
So these coin actually haven't matured yet. Because of this the automatic payouts don't work correctly. PS: The automatic payouts on cryptohunger don't work properly because of this.Once this problem is resolved, you'll get your payment. Or I will manually send it through. If this is a problem for you - try other pool or try solo mining. Thanks srcxxx Block maturity was changed to 100 confirmations up from 8. |
|
|
|
I have a question please : I was out of mining for months. I just tried to switch my 7950 from scrypt to groestl. It worked immediately... but the thing I don't understand is why I haven't received yet any coins, when the pool has already found more than 20 blocks? Is it delayed? I'm at http://cryptohunger.com, my worker is showing properly the hashrate, no HW, everything fine. I just want to know if there is a delay to receive coins? I thought this was like a p2p pool, when seeing how cryptohunger looks. Is your miner submitting shares? |
|
|
|
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 Looking good! thank you. After looking at the logs with thrassos it appears people are trying to send mined coins from a 3.0.1 mining wallet to a 2.9.1 personal wallet. The 2.9.1 wallet will reject this. Everyone needs to update to 3.0.1! That means Mintpal didn't update? They said they did. We can try a get peerinfo |
|
|
|
love2hash 0 blocks found?
Stats are off. We are working on updating this as well as lowering payment thresh holds. |
|
|
|
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 Looking good! thank you. After looking at the logs with thrassos it appears people are trying to send mined coins from a 3.0.1 mining wallet to a 2.9.1 personal wallet. The 2.9.1 wallet will reject this. Everyone needs to update to 3.0.1! |
|
|
|
Hmm... I don't know how long I can keep these pools up. My daemons still seem to be getting stuck every ~10 blocks. Restarting the daemon fixes it, but I can't keep doing that 24/7 D:
For now I'll do it so we can get some easy DGB, but there has to be something I'm missing...
Right now it seems to mostly be Skein and Qubit that refuse to stay synced
Memory shortage? |
|
|
|
qubit pool is finding block  This is good to hear!  Thanks for adding the pools! |
|
|
|
|
Join #digibytecoin on IRC if you have any bugs or questions. We will be happy to answer them there more easily!
|
|
|
|
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. This will change when the full confirmations occur. It now requires 100 confirmations for coins to mature. So this jumped from 8 to 100. This will be normal after a 100 confirmations for each algo block is made. We did this to discourage multi-pools from insta dumping coins as well as making the chain more secure. |
|
|
|
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
}
|
|
|
|
|
Time-stamp: 1:05 PM Mt Time, Block: 145,284
Will up date this post every hour with block count to get a rolling average for first few hours.
You can check which algo is generating which blocks by looking in the debug.log in your appdata folder.
|
|
|
|
Early feedback shows after 280 blocks diffs have adjusted nicely, debug log shows all 5 algos generating blocks. Now if we can get a block explorer to add the algo code we can see how many per algo. Looking good folks! 
{
"version" : 3000100,
"protocolversion" : 70002,
"walletversion" : 60000,
"balance" : 40206.13266188,
"blocks" : 145281,
"timeoffset" : 0,
"connections" : 8,
"proxy" : "",
"pow_algo_id" : 0,
"pow_algo" : "sha256d",
"difficulty" : 958989.46769076,
"difficulty_sha256d" : 958989.46769076,
"difficulty_scrypt" : 233.46404865,
"difficulty_groestl" : 1.17555787,
"difficulty_skein" : 52.20677380,
"difficulty_qubit" : 3.58759093,
"testnet" : false,
"keypoololdest" : 1408412547,
"keypoolsize" : 97,
"unlocked_until" : 0,
"paytxfee" : 0.00000000,
"relayfee" : 0.00001000,
"errors" : ""
}
|
|
|
|
either I didn't set it up right, or my skein and groestl cpu miners aren't connecting on the love2hash pool
we are restarting the wallets... forgot the pool had to reeboot Is there an ETA on love2hash working ? Love2hash online & mining! DOnt use DigiHash... we took it offline  Why? I thought I can support you with the 2% fee Had some errors with that setup. Will get it fixed once things stabilize. |
|
|
|
either I didn't set it up right, or my skein and groestl cpu miners aren't connecting on the love2hash pool
we are restarting the wallets... forgot the pool had to reeboot Is there an ETA on love2hash working ? Love2hash online & mining! DOnt use DigiHash... we took it offline |
|
|
|
either I didn't set it up right, or my skein and groestl cpu miners aren't connecting on the love2hash pool
we are restarting the wallets... forgot the pool had to reeboot |
|
|
|
|
Show Posts
