Search content
Sort by
Showing 20 of 21 results by Fadayko
Our MiningPool is ready for Mining !
Hardware ( Xeon1230v6, 32gb DDR4 Ram, 480GB SSD in RAID and GIGABIT Upload!! )
http://bitcoin-pool.de/
We are online 24/7
http://up.picr.de/31560445xk.jpg
Config Sample:
Algo: Scrypt
stratum+tcp://85.214.211.186:12501 -u YOUR_WALLET_ADDRESS -p c=DARX or d=8192 (your diff)
Hardware ( Xeon1230v6, 32gb DDR4 Ram, 480GB SSD in RAID and GIGABIT Upload!! )
http://bitcoin-pool.de/
We are online 24/7
http://up.picr.de/31560445xk.jpg
Config Sample:
Algo: Scrypt
stratum+tcp://85.214.211.186:12501 -u YOUR_WALLET_ADDRESS -p c=DARX or d=8192 (your diff)
Please send paid transactions with no txid for wallet address... RRKfggAiZwJU6UGf2f5V7gtS4BdinecvZ9
Thank you
What is happening? mining power.net payment without the hash of the transaction, the purse is empty.
Im not sure why the transaction ID's aren't processing on miningpower...I have payouts waiting to happen over there as well...on the home screen for mining power it mentions that the payments can take up to 12 hours to process
Our MiningPool is ready for Mining !
Hardware ( Xeon1230v6, 32gb DDR4 Ram, 480GB SSD in RAID and GIGABIT Upload!! )
http://bitcoin-pool.de/
We are online 24/7
http://up.picr.de/31560445xk.jpg
Config Sample:
Algo: Scrypt
stratum+tcp://85.214.211.186:12501 -u YOUR_WALLET_ADDRESS -p c=DARX or d=8192 (your diff)
Hardware ( Xeon1230v6, 32gb DDR4 Ram, 480GB SSD in RAID and GIGABIT Upload!! )
http://bitcoin-pool.de/
We are online 24/7
http://up.picr.de/31560445xk.jpg
Config Sample:
Algo: Scrypt
stratum+tcp://85.214.211.186:12501 -u YOUR_WALLET_ADDRESS -p c=DARX or d=8192 (your diff)
If you are going to use this pool please use a higher difficulty...the low difficulty is creating a substantial amount of orphans at the moment
Re: [ANN][BRIA] BRIACOIN | PoS/PoW Scrypt | Bounty / ICO | Win, Mac, iOS, Android
Anyone else having a problem with the wallet syncing. I just noticed my wallet hasn't got past a block from 11/24/2017???
Checked. It is ok. Maybe another program blocks it?Anyone on here mining with and ASIC?
Yes, here pool.mfcoin.netNethash of adcoin is low but the difficulty is at 7,454 and previous block was 1,863. Why is this so high? This is why it takes shareholders days to receive and transfer their adcoin. You have effectively killed mining with the premine.
Quote
According to the blockexplorer and the daemon behind coincave the current height is 132382. I have no idea where those blocks beyond that height are coming from. All I know is that an experimental code has been online for a few days which might be screwing up things if people downloaded it and are using it. I find multiple entries in the debug.log where the blockchain is altered.
I agree. In my transaction log I have already discovered block 132382 and now I am reworking the block. And with coincave requiring 120 confirmations there is no guarantee that even the current block wont be deemed and orphan for the second time.
So in theory all the orphaned blocks are altered to a confirmed status and I receive the shares for the completed block?
https://github.com/MPOS/php-mpos/issues/2248
I think the dev should really get cracking and solve these issues that currently only happen with score, most other coins are running without too many issues.
Interesting... I wish they would of closed the subject with a resolution...regardless whether its a coin source issue or an anomaly with the pool configuration the issue is a detriment to mining on coincave.nl...which I prefer over our other pools. From my experience with mining dutch they do not have this as an issue. It seems like coincave has an issue when the difficulty levels are +/- 300
The configuration is no different than any of the other coins, check TRADE or BAT, they run fine, so for now there is not much I can do from here. I have the impression that there is an alternative blockchain running that crosses the correct one frequently based on those rewrites in the debug.log.
Well...I appreciate your time and talking through the issue. We will see what the Dev has to say at a later time and hopefully reach a resolution.
Quote
According to the blockexplorer and the daemon behind coincave the current height is 132382. I have no idea where those blocks beyond that height are coming from. All I know is that an experimental code has been online for a few days which might be screwing up things if people downloaded it and are using it. I find multiple entries in the debug.log where the blockchain is altered.
I agree. In my transaction log I have already discovered block 132382 and now I am reworking the block. And with coincave requiring 120 confirmations there is no guarantee that even the current block wont be deemed and orphan for the second time.
So in theory all the orphaned blocks are altered to a confirmed status and I receive the shares for the completed block?
https://github.com/MPOS/php-mpos/issues/2248
I think the dev should really get cracking and solve these issues that currently only happen with score, most other coins are running without too many issues.
Interesting... I wish they would of closed the subject with a resolution...regardless whether its a coin source issue or an anomaly with the pool configuration the issue is a detriment to mining on coincave.nl...which I prefer over our other pools. From my experience with mining dutch they do not have this as an issue. It seems like coincave has an issue when the difficulty levels are +/- 300
Quote
According to the blockexplorer and the daemon behind coincave the current height is 132382. I have no idea where those blocks beyond that height are coming from. All I know is that an experimental code has been online for a few days which might be screwing up things if people downloaded it and are using it. I find multiple entries in the debug.log where the blockchain is altered.
I agree. In my transaction log I have already discovered block 132382 and now I am reworking the block. And with coincave requiring 120 confirmations there is no guarantee that even the current block wont be deemed and orphan for the second time.
So in theory all the orphaned blocks are altered to a confirmed status and I receive the shares for the completed block?
Quote
According to the blockexplorer and the daemon behind coincave the current height is 132382. I have no idea where those blocks beyond that height are coming from. All I know is that an experimental code has been online for a few days which might be screwing up things if people downloaded it and are using it. I find multiple entries in the debug.log where the blockchain is altered.
I agree. In my transaction log I have already discovered block 132382 and now I am reworking the block. And with coincave requiring 120 confirmations there is no guarantee that even the current block wont be deemed and orphan for the second time.
We have an issue on the coincave.nl mining pool where we are discovering blocks that have already been found. This is then forcing the unconfirmed shares of the original block to be orphaned. Please fix this as we have spent time and energy to discover these blocks and now we are working back through the blockchain for the second time. This occured in a series of 54 blocks.
Thank you,
Thank you,
Hey guys I am having trouble getting my wallet to sync with the network. I just did a manual transfer trying to initiate the sync and have had no success. Please any help would be appreciated
Thank you,
Thank you,