Does anybody know how to make AwesomeMiner work with Claymore when -mpsw is set? After I set the -mpsw option, AwesomeMiner can no longer detect the miners and keep saying "Interface offline". Thanks in advance.

MN reward is 6 Crave coins roughly every 8 hours or so. Sometimes you get reward more often, sometimes less.

My Jan 20 to 31 order was shipped on 01/04/18 and delivered on 01/09/18. I was quite surprised I got them that early.

I'm sorry if this question has been asked before. How do I set spool-specific options with sgminer? I need to specify "-p c=BTC,d=864" for zpool and I can easily do it with ccminer 2.2.2 by going to Options, Online services and add "p -c=BTC,d=864" in the Command line parameters of the zpool I want to change; however, sgminer ignores this command line parameters because it parses awesome.conf file for the password value. Is there a way to manually edit the awesome.conf file and make it permanent? Thanks in advance.

You're right. I just checked the hashboard connections of the 4 D3 that I have. One of them have hashboards connected to port 0,1,2 and the other 3 have hashboards connected to port 1,2,3. Thanks for pointing that out to me.

Hi Blissz,

I think there is a bug in your latest firmware 08/12 v1.11. On the Miner Status page, the chains are numbered 2, 3, 4, but on the Miner Advanced Configuration page, they are numbered 1, 2, 3. Any changes made to chain 2 on the Miner Configuration page will be applied to chain 3 on the Miner Status page, and any changes to chain 3 will be applied to chain 3 and 4. Changes to chain 1 on the Miner Configuration page doesn't seem to affect anything.

As an experiment, I set the global frequency at 450M, chain 1 at 444M, chain 2 at 438M and chain 3 at 425M. Below is an excerpt from kernel log:

Jan  1 00:35:47 (none) local0.notice cgminer[12817]: set_frequency: frequency = 444
Jan  1 00:35:47 (none) local0.notice cgminer[12817]: set_frequency: frequency = 438
Jan  1 00:35:47 (none) local0.notice cgminer[12817]: set_frequency: frequency = 425
Jan  1 00:35:47 (none) local0.notice cgminer[12817]: set_frequency: frequency = 425
Jan  1 00:35:47 (none) local0.notice cgminer[12817]: software_set_address: chain 0 has 0 ASIC, and addrInterval is 1
Jan  1 00:35:47 (none) local0.notice cgminer[12817]: software_set_address: chain 1 has 60 ASIC, and addrInterval is 1
Jan  1 00:35:47 (none) local0.notice cgminer[12817]: Now Set [1] Chain Address
Jan  1 00:35:48 (none) local0.notice cgminer[12817]: software_set_address: chain 2 has 60 ASIC, and addrInterval is 1
Jan  1 00:35:48 (none) local0.notice cgminer[12817]: Now Set [2] Chain Address
Jan  1 00:35:48 (none) local0.notice cgminer[12817]: software_set_address: chain 3 has 60 ASIC, and addrInterval is 1
Jan  1 00:35:48 (none) local0.notice cgminer[12817]: Now Set [3] Chain Address

On the Miner Status page, it shows that the frequency of chain 2, 3, and 4 are 438M, 425M, and 425M respectively.

Hey Supnurd,

Thank you for your clarification. Got me worried there that you had left the project. Just out of curiosity. How would one get in contact with you if you're no longer on Discord?

Hi all. I just set up a Crave masternode, and it seems to be running fine. I just wonder if I need to specify the "Reward Address" and "Reward %" when I entere information on the My Masternodes tab. Thanks.

Starting to accumulate Bata for a masternode. Is there a guide on how to set one up soon?

Thanks!

FYI, I tried to join discord but couldn't. Discord invite is invalid/has expired.

Just out of curiosity. Who's controlling this wallet address http://202.5.19.121/address/DR42dVZ6oPCcWJEGCYhKwgP82UhqD1spDv, that has 77.71% of total coins on the top 100 rich list http://202.5.19.121/richlist?

I'm happy to report that I just got a credit of 3.6 CHC for one of my masternodes. It's not much but it's a good start. I'll keep my 2 masternodes running.

It's 0 right now for both nodes because I just reinstalled my Chaincoin Core Wallet. Post #2866 links a post in DASH forum, in which someone suggested that deleting the whole blockchain and then syncing from bootstrap seemed to fix the issue with  "MasternodePOS::mnse - MasternodeB ranking is too low" error. I'll let the nodes run for a few days and report back here.

---

I just set up 2 Masternodes and run them from my desktop wallet. They have been running for 5 days straight without receiving any rewards. I am running the latest 90302 version and "chaincoin-cli masternodelist pose IPADDRESS" returns a result of 0. The debug log does show a lot of "MasternodePOS::mnse - MasternodeB ranking is too low" errors. Is there any guide to troubleshoot problems with masternodes? I had faith in Chaincoin when I decided to start running Masternodes, but I am fairly disappointed with the loss in initial investment (bought in at $0.20), and lack of rewards.

Not everybody in batch 3 will get their tokens in 2 weeks. Batch 3 has a capacity equivalent to 4.5 MW. According to the email, only 1.2 MW worth of tokens will be issued, which means only ~26.7% people in batch 3 can expect to receive their tokens when these pods go into production. I suspect these tokens will be issued on a FIFO basis.

Yes, you can rent all the tokens you need to power your miners. If you placed the order through Giga Watt, they will have to find replacement PSU for you. If you placed the order directly with Bitmain, you need to contact Giga Watt support to resolve the PSU issue because you have to purchase the PSU yourself and ship them to GW.

Giga Watt sent out the email below on 09/01/17.

-------------------------------------------------------------------------------------

Hello one and all.

First I want to thank everyone for the positivity we've been experiencing both via online channels as well as at the open house events! I've also received a TON of really supportive energy from the community and I can't thank you enough... it really keeps us all going when there's huge amounts of hard work to do.

Unfortunately, I have to announce a delay in construction which will block us from issuing Batch 3 tokens on time. We've been working tirelessly to bring pods out of the ground, but several conditions related to the construction and planning process have introduced additional delays that are now clearly keeping us from turning up as many pods as planned for Sept and October. The process of building the pods and deploying equipment is going as expected. The real time-impact has to do with permitting, planning and inspections. Our GigaPods were virtually the first purpose-built blockchain processing facilities these people had ever seen, and it has caused small delays at every turn.

The good news is that we are through most of that. We have educated the stakeholders in two counties about our GigaPod construction processes and how the finished product looks and works. I expect these types of delays to become less and less now that it has become familiar to them.

Our construction crews and electricians are getting pod construction down to a science. We will continue to run day and night crews to bring up as much power capacity as possible, as soon as possible.

On the topic of hardware arriving in September: there's significantly less equipment arriving in September than the amount of power we are building, so it becomes a little easier to see through to getting it all running. I expect to have much of the September hardware running soon after it comes in. Because the construction process is not a perfect science, its hard to know exactly when backed up gear will be put into service. To mitigate the situation, GW is seeking any and all alternative solutions to get gear running as soon as possible so that it won't just sit on the warehouse shelves. As a miner myself, I know just how important that is to our customers.

I'm sure that questions and concerns will still linger, so I am planning to make myself personally available on chat channels in order to answer questions whether to the group or to me personally. I do appreciate your continued patience and support. I want you to know that the whole GW team is directly focused on getting tokens issued and miners running as fast as humanly possible.

It’s always hard to maintain communications and transparency during the chaotic startup phase, but we are committed to improving on this front. We are improving our support to clients slower than we and everyone wanted but are progressing on that. Within the next 3 to 4 business days I will begin releasing weekly updates to help everyone track progress along the new timelines. I aim to improve confidence in Giga Watt and significantly reduce concerns you may have going forward.

Best Regards
Dave Carlson, CEO
Giga Watt, Inc.

-------------------------------------------------------------------------------------

Batch 3 is delay 4-6 weeks. Batch 4 is unknown, probably 6-10 weeks. I think the 4 pods under construction on Giga Watt timeline are for batch 1 & 2.

How did you transfer WTT tokens to your Giga Watt account? Did you withdraw them from "EtherDelta" column to "Wallet" column first, then transfer from Wallet to you GigaWatt account? It's a 2-step process. It also takes some time for the tokens to be transferred.

As long as you have a few WTT tokens in your Giga Watt account, you should be able to rent the rest to cover your miners' usage.

Hope it helps.

Not me. I have Ethman running on 4 rigs (RX470, Win10 Pro, blockchain drivers) for days with no issue.