Latest posts of: cchazz

Show Posts
Pages: [1]

Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][CRC]🚀CrowdCoin POW| MASTERNODES | ZERO TX FEE | NO ASIC | VC

on: December 28, 2017, 05:18:40 PM

Quote from: carbonc on December 28, 2017, 04:37:43 PM No, your wallet is not jacked. You just need to add some "addnode=blahblahblah" to your crowdcoin.conf file in your AppData folder. Check the previous pages in this post for how to do that. Okay, thank you. That did get my wallet syncing again. Not sure why it crapped out to begin with, but oh well. I now can't get my masternode to start back up for the life of me though. It began last night with NEW_START_REQUIRED, so I did that. Next thing I know it's WATCHDOG_EXPIRED. It had been running perfectly fine for 6 days now, prior to this. I saw back a page what you did to fix yours, and I've tried that as well. Even restarted my VPS. My wallet continues to tell me that my WATCHDOG_EXPIRED, and now my VPS shows "Node just started, not yet activated". Any thoughts on how to remedy this? Thank you. EDIT: I believe I've fixed the VPS portion. It appears there was something corrupt with my mn*.dat files and or the blockchain needed reindexed. I followed the directions on under the 2.b heading here to fix this: https://github.com/crowdcoinChain/sentinelLinux Thanks! 2nd EDIT: Okay, so I guess it's just the current blockchain issues that are preventing my node from showing as ENABLED in the list. From the VPS, masternode is successfully started. mnsync shows everything up to date and active. My local wallet still shows WATCHDOG_EXPIRED, even though sentinel is running and passing all tests. I guess I'll just wait it out, unless someone can help me with a fix in the short term.

Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][CRC]🚀CrowdCoin POW| MASTERNODES | ZERO TX FEE | NO ASIC | VC

on: December 28, 2017, 04:22:33 PM

So my wallet is jacked... "7 hours behind... No block source available", but it has 8 active connections to the CRC network. Wat do?

Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][SKELR] SkeletonRevive - Masternodes Swap

on: December 22, 2017, 11:05:23 PM

Having trouble figuring out how to compile this on Ubuntu 16.04. No configure nor autogen.sh... I'm noob and I don't know where to go from here. Can anyone help please? Thanks!

Alternate cryptocurrencies / Mining (Altcoins) / Re: [OS] nvOC easy-to-use Linux Nvidia Mining v0019-1.4

on: November 23, 2017, 12:01:46 AM

Quote from: papampi on November 22, 2017, 03:22:27 PM Quote from: terex on November 22, 2017, 03:05:08 PM Hi papampi, This issue was with a mix of cards like the P106 and 1070 in a frame setting the OC speeds requires that the nvidia command to set the GPU or memory OC needs to be the [2] for some and [3] for others. The loop looks like it was designed to try both [2] [3] if NORMAL=YES above, for each gpu but the gpu variable was incremented in the inner loop so you would get [2] on gpu[0] then [3] on gpu[1], [2] on gpu [2] and so on. By moving the gpu increment out of the for loop it and into the outer while loop I believe it works as intended. I added the two echo's in here to show the behavior. Original loop: TI is 2 3, J is 2 and GPU is 0 nvidia-settings -a [gpu:0]/GPUGraphicsClockOffset[2]=-200 nvidia-settings -a [gpu:0]/GPUMemoryTransferRateOffset[2]=1500 Attribute 'GPUGraphicsClockOffset' (19_1_4:0[gpu:0]) assigned value -200. Attribute 'GPUMemoryTransferRateOffset' (19_1_4:0[gpu:0]) assigned value 1500. TI is 2 3, J is 3 and GPU is 1 nvidia-settings -a [gpu:1]/GPUGraphicsClockOffset[3]=-200 nvidia-settings -a [gpu:1]/GPUMemoryTransferRateOffset[3]=1300 TI is 2 3, J is 2 and GPU is 2 nvidia-settings -a [gpu:2]/GPUGraphicsClockOffset[2]=-200 nvidia-settings -a [gpu:2]/GPUMemoryTransferRateOffset[2]=1500 Attribute 'GPUGraphicsClockOffset' (19_1_4:0[gpu:2]) assigned value -200. Attribute 'GPUMemoryTransferRateOffset' (19_1_4:0[gpu:2]) assigned value 1500. TI is 2 3, J is 3 and GPU is 3 nvidia-settings -a [gpu:3]/GPUGraphicsClockOffset[3]=-200 nvidia-settings -a [gpu:3]/GPUMemoryTransferRateOffset[3]=1500 Attribute 'GPUGraphicsClockOffset' (19_1_4:0[gpu:3]) assigned value -200. Attribute 'GPUMemoryTransferRateOffset' (19_1_4:0[gpu:3]) assigned value 1500. TI is 2 3, J is 2 and GPU is 4 nvidia-settings -a [gpu:4]/GPUGraphicsClockOffset[2]=-200 nvidia-settings -a [gpu:4]/GPUMemoryTransferRateOffset[2]=1300 Attribute 'GPUGraphicsClockOffset' (19_1_4:0[gpu:4]) assigned value -200. Attribute 'GPUMemoryTransferRateOffset' (19_1_4:0[gpu:4]) assigned value 1300. TI is 2 3, J is 3 and GPU is 5 nvidia-settings -a [gpu:5]/GPUGraphicsClockOffset[3]=-200 nvidia-settings -a [gpu:5]/GPUMemoryTransferRateOffset[3]=1300 =============================================================== By moving the gpu increment to the while loop the execution looks like: TI is 2 3, J is 2 and GPU is 0 nvidia-settings -a [gpu:0]/GPUGraphicsClockOffset[2]=-200 nvidia-settings -a [gpu:0]/GPUMemoryTransferRateOffset[2]=1500 Attribute 'GPUGraphicsClockOffset' (19_1_4:0[gpu:0]) assigned value -200. Attribute 'GPUMemoryTransferRateOffset' (19_1_4:0[gpu:0]) assigned value 1500. TI is 2 3, J is 3 and GPU is 0 nvidia-settings -a [gpu:0]/GPUGraphicsClockOffset[3]=-200 nvidia-settings -a [gpu:0]/GPUMemoryTransferRateOffset[3]=1500 Attribute 'GPUGraphicsClockOffset' (19_1_4:0[gpu:0]) assigned value -200. Attribute 'GPUMemoryTransferRateOffset' (19_1_4:0[gpu:0]) assigned value 1500. TI is 2 3, J is 2 and GPU is 1 nvidia-settings -a [gpu:1]/GPUGraphicsClockOffset[2]=-200 nvidia-settings -a [gpu:1]/GPUMemoryTransferRateOffset[2]=1300 Attribute 'GPUGraphicsClockOffset' (19_1_4:0[gpu:1]) assigned value -200. Attribute 'GPUMemoryTransferRateOffset' (19_1_4:0[gpu:1]) assigned value 1300. TI is 2 3, J is 3 and GPU is 1 nvidia-settings -a [gpu:1]/GPUGraphicsClockOffset[3]=-200 nvidia-settings -a [gpu:1]/GPUMemoryTransferRateOffset[3]=1300 TI is 2 3, J is 2 and GPU is 2 nvidia-settings -a [gpu:2]/GPUGraphicsClockOffset[2]=-200 nvidia-settings -a [gpu:2]/GPUMemoryTransferRateOffset[2]=1500 Attribute 'GPUGraphicsClockOffset' (19_1_4:0[gpu:2]) assigned value -200. Attribute 'GPUMemoryTransferRateOffset' (19_1_4:0[gpu:2]) assigned value 1500. TI is 2 3, J is 3 and GPU is 2 nvidia-settings -a [gpu:2]/GPUGraphicsClockOffset[3]=-200 nvidia-settings -a [gpu:2]/GPUMemoryTransferRateOffset[3]=1500 Attribute 'GPUGraphicsClockOffset' (19_1_4:0[gpu:2]) assigned value -200. Attribute 'GPUMemoryTransferRateOffset' (19_1_4:0[gpu:2]) assigned value 1500. if [ $P106_100_FULL_HEADLESS_MODE == "NO" ] then gpu=0 while [ $gpu -lt $GPUS ] do for j in $TI do CORE=${__CORE_OVERCLOCK[${gpu}]} MEM=${MEMORY_OVERCLOCK[${gpu}]} echo "TI is $TI, J is $j and GPU is $gpu" echo "${NVD} -a [gpu:$gpu]/GPUGraphicsClockOffset[${j}]=$CORE" echo "${NVD} -a [gpu:$gpu]/GPUMemoryTransferRateOffset[${j}]=$MEM" ${NVD} -a [gpu:$gpu]/GPUGraphicsClockOffset[${j}]=$CORE ${NVD} -a [gpu:$gpu]/GPUMemoryTransferRateOffset[${j}]=$MEM done gpu=$(($gpu+1)) done Thanks a lot for the detailed explanation Added your fix for next release. If you found any more fixes please let us know to add for next releases. Would this be why my 2 1050 Ti's show as ERR! in the power chart when it first loads and ewbf reports them as 0 Hash/watt? They're running alongside 6 1060 6GB cards and they all seem to be working correctly (appropriate hash rates per card). Just the error bothered me was all. Thanks!

Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN] Bitcoin Gold : Make Bitcoin Decentralized Again

on: November 13, 2017, 03:04:29 AM

Miningspeed seems to be working okay, though I wish I could be certain before I go to bed...

Alternate cryptocurrencies / Pools (Altcoins) / [ANN][HASHING.FUN] hashing.fun Electroneum pool

on: November 08, 2017, 10:02:35 PM

HASHING.FUN ! Brand new community member Electroneum pool. Need help testing and more hashpower. Small pool at the moment so rewards will be great if blocks are found! Low fee pool (1%). No registration required. Payouts every 10 minutes, minimum payout of only 2 ETN! Discord server for support. Help the network and spread the hash power around! http://hashing.fun ! Thanks!

Alternate cryptocurrencies / Announcements (Altcoins) / Re: [LAUNCHED][POW]⚡ELECTRONEUM⚡Offical Moderated Thread

on: November 08, 2017, 09:22:25 PM

HASHING.FUN! Brand new community member Electroneum pool. Need help testing and more hashpower. Small pool at the moment so rewards will be great if blocks are found! Low fee pool (1%). No registration required. Payouts every 10 minutes, minimum payout of only 2 ETN! Discord server for support. Help the network and spread the hash power around! Come mine with us at http://hashing.fun! Thank you and good luck!

Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][ICO] ⚡ Electroneum ⚡ Token Sale Sept 14th Mobile Mining Crypto Coin

on: November 08, 2017, 09:14:54 PM

HASHING.FUN! Brand new community member Electroneum pool. Need help testing and more hashpower. Small pool at the moment so rewards will be great if blocks are found! Low fee pool (1%). No registration required. Payouts every 10 minutes, minimum payout of only 2 ETN! Discord server for support. Help the network and spread the hash power around! Come mine with us at http://hashing.fun! Thank you and good luck!

Alternate cryptocurrencies / Announcements (Altcoins) / Re: [LAUNCHED][POW]⚡ELECTRONEUM⚡Official Moderated Thread

on: November 03, 2017, 03:24:01 PM

Thanks for the new thread. The old one was getting out of hand. Quick question: any update on the official US pool not finding blocks for over 2 days now? I've got some pending balance stuck there. There are still a ton of miners mining there, so I'm hoping we'll get credited for our hash power even though the UI shows no blocks found.... hoping it's a frontend error or something. Anyway, thanks for the updates. For anyone that is unaware, the devs are most active on their Facebook page it would seem: https://www.facebook.com/electroneum/

Alternate cryptocurrencies / Announcements (Altcoins) / Re: [ANN][ICO] ⚡ Electroneum ⚡ Token Sale Sept 14th Mobile Mining Crypto Coin

on: November 03, 2017, 01:29:32 PM

It amazes me how quick people are to turn on a project they "believed in" after something goes wrong. Nothing is lost. In fact, these "investors" that are crying they can't access their coins should honestly be THANKING the devs that they didn't let all their coins get stolen. It wasn't the devs responsibility to ensure the safety of those coins, only to deliver them. It's no different than a bank requiring proper identification before they'll let you withdraw your own money. Otherwise, anyone off the street could walk in, claim to be you, and pull out all your money. Except in this case, the onus is on the user to use strong passwords, not reuse passwords between sites, and maintain good account security practices. Devs did you a favor. People need to chill. And for the record, I'm not an investor, though I wish I had been. I missed this opportunity but I am mining so we'll see what happens.

Pages: [1]