There are 4 hours with the problem from above and all RIGS remained locked with zero income and 4 hours are lost.
WHY ?

@Mr.Spider703 dear one even Excavator dev admit speed is not top one & they need to tune better & main problem of excavator is stability ... but what ever use what ever you like & believe is best for you ... there are discussion there github dev place already about this with feedback & all what a well informed person need

we are starting to compare apples to oranges here, but anyway I never was able to get higher hashrate on neoscrypt with Excavator. I gave it try again today, default settings benchmark from NiceHash miner 2.0.1.10 for single MSI GTX Gaming X 1070 pl90%/+100core/+400mem - result is 1241 kh/s. If I manually run Excavator from cuda91 folder - it gives more, about 1276 kh/s. But it is still way behind Nsrminer_neoscrypt_fork (even normal priority version) - 1322 kh/s.

You can see full hashrate compare of ccminer klaust, excavator and hsrminer_neoscrypt_fork at the 1st msg in my topic under Hashrate compare tag.

It is hard to understand what you want to say, but PHI algo was already included in January, 2 versions ago:

Version 4.4 (2018-01-25)
- Phi algorithm included

Check my fork, guys. New version is just out, API improved, palgin's bug with -d option fixed and more.

I disabled hashrefinery, it is very unreliable, they are reporting 100 times more profit to attract miners and by misleading the statistics they get overwhelmed with 10k connections form AM simultaneously and the server crashes so the result is that you do not get not even 50% of the money you will get from other pools, so be aware.

I don't think some of you understand how mining works. Mining is a pie, rewards are distributed among all participants. That means the more miners hope on a coin, the less you earn. When people start earning less then lets say about average earnings they switch coins. When they switch coins, they, of course hope on other coins. This means when you're talking about mainstream coins they're a order of magnitude larger then small coins.

Lets talk context here. Zcash, just Zcash, none of the other large and mainstream cryptos has 400Mh on it. At 460s per 1070 that's 869,565 1070s. Lets assume on average each user has 3 GPU rigs, that's 18 cards, that's ~48,000 miners. The closer we get to power costs, the more desperate those users get to find new coins that they can mine at profit. That means they will load balance themselves across multiple coins, that's what they do, that's what YOU do. That's just one coin. I don't think you guys realize how close we are to oblivion when we approach energy costs on mainstream coins. Those miners wont switch off their rigs, they'll mine negative and a lot of them will find something, anything they can mine that will earn them more. That makes it much, much, much, much harder to find niche coins that earn you your profit.

When profit is up on mainstream coins that means it's much easier to reap profits on niche coins as people get lazy and complacent, like Nicehash miners. When profit goes down, everything dries up, especially now days when we have many more miners then we had say a year ago. That's a lot more eyeballs and a lot more people search for those niche coins. Where you could mine a niche coin for months before, you get days. I mined one for about 9 months last year before it was eventually whored out and now it no longer produces as most people know about it. Coins are generally non-renewable, once enough people find out about it to equalize it with mainstream coins it's dead.

It's pretty hilarious that some of you think that mainstream coins have absolutely no impact on your lives, they do, the entire crypto scene rotates around them.

THANKS MAN

3b560c363cac51dc22ed445630cf52df15ca3e2e32f13d9b072aa3fe6609669a

Thanks in advance!

98352da3d1e07f7fa8e537e3fcccba4d843ea179635f825958d39f80ac5dd1eb

Please help me confirm this transaction: https://blockchain.info/tx/f30267d2e31a055a059da36e3ec45a68dd4ffedff81442098575e9674c4181e8
After confirmation, I will donate some BTC’s to you, thanks!

Hello,

I need help in confirming my transaction:


Please help and thanks in advance

hello bro
c207b8a4bfe9c8b4a8fbb48ed06618840f90b2cfcd1721844e2662edf3e5f70e
f021383c64d6d4c5452281d936ffb9783c79b53680aced6b479ba4680878cab9

help pls.
thanx

hello bro
c207b8a4bfe9c8b4a8fbb48ed06618840f90b2cfcd1721844e2662edf3e5f70e
f021383c64d6d4c5452281d936ffb9783c79b53680aced6b479ba4680878cab9

help pls.
thanx

I can get it to close, by setting the API port on command line (-p 4028), when it is set to old Excavator compatibility mode. But it does not report any stats (hash rate/accepted etc).

That's the problem. We can create multiple files for each algo for one pool, but there is no feasible way to provide multiple files for multiple pools.

So if we wanted to only stay in Ahashpool and switch between algos only in Ahashpool, then that is possible.

Sadly, while some excavator support was added as 'External Miner", its pretty pointless for using with Profit switching.

If anyone is using these algos with built-in miner, then they are literally throwing money down the toilet. I simply can't use AM with this situation.

[
  {
    "time": 0,
    "commands": [
      {
        "id": 1,
        "method": "algorithm.add",
        "params": [
          "neoscrypt",
          "204.27.59.90:4233",
          "1J6ERS9LjhRhXkifkVfdpbP56aY7TLqEoe:home_video_card,c=BTC"
        ]
      }
    ]
  },
  {
    "time": 3,
    "commands": [
      {
        "id": 1,
        "method": "worker.add",
        "params": [
          "0",
          "0"
        ]
      }
    ]
  },
  {
    "time": 3,
    "commands": [
      {
        "id": 1,
        "method": "worker.add",
        "params": [
          "0",
          "1"
        ]
      }
    ]
  },
  {
    "time": 3,
    "commands": [
      {
        "id": 1,
        "method": "worker.add",
        "params": [
          "0",
          "2"
        ]
      }
    ]
  },
  {
    "time": 3,
    "commands": [
      {
        "id": 1,
        "method": "worker.add",
        "params": [
          "0",
          "3"
        ]
      }
    ]
  },
  {
    "time": 3,
    "commands": [
      {
        "id": 1,
        "method": "worker.add",
        "params": [
          "0",
          "4"
        ]
      }
    ]
  },
  {
    "time": 3,
    "commands": [
      {
        "id": 1,
        "method": "worker.add",
        "params": [
          "0",
          "5"
        ]
      }
    ]
  },
  {
    "time": 10,
    "loop": 10,
    "commands": [
      {
        "id": 1,
        "method": "algorithm.print.speeds",
        "params": [
          "0"
        ]
      }
    ]
  }
]

Pomoc potrzebna!
b55206b00ed735cb244385710babdeb6dba3e3e7eac470e3a86427ea7e89b9a8

Dzięki z góry!