I moved all my ITNS from stocks.exchange to local wallet.

This exchange either hacked or broken. Look at two attached images. It has weird top rates, and there was abnormal trade flow when buy prices were lower than sell prices (usually green buy is higher than red sell).

I also placed few tickets about broken API calls, misconfigured DDoS protection (CloudFlare), browser DDoS protection for JSON API (weird). I first got closed tickets with suggestion to email admin (and I did that). Later I made new ticket (previous were closed, as I said) and asked for resolution. They asked do not open more tickets (with no responses) and promised to give answer by email. 2 weeks later still nothing fixed, nothing answered.

I decided to leave it to be safe. Just a heads up warning. But make your own decisions.

https://i.imgur.com/9Z3wD9r.png
https://i.imgur.com/s2Nn6Qc.png

@Claymore,

I am trying to solo mine ETH fork using Parity node . It works well with GetWork protocol, but since 1.6 Parity offers Stratum protocol support. I was unable to configure your miner to work using Parity stratum. All ESM modes (0,1,2) did not authenticate properly and returned protocol errors.

Does this miner support Parity stratum solo mining or not? If it does, how to configure it?

I don't know if those are separate issues. But it looks very similar in the end result: double payment.

In my case I built 1.2.2 wallet from the source before you published "official" 1.2.2 binary for Mac. In that 1.2.2 self-built wallet my attempt to send 1000 ITNS to the exchange created exactly TWO IDENTICAL transactions with different TxIDs. Both were succeeded. In his case I don't know if the pool issued two payments by error, or its underlying ITNS daemon generated two identical TXs exactly as with my wallet.

I did not say it's not occurring in 1.2.2.

I said that with self-built Mac wallet 1.2.2 I had issue, but with "officially" distributed Mac wallet 1.2.2 (same version) there was no one. In any other regard they were identical. I can't comment what was wrong, I removed self-built wallet and did not report problems.

Actually, if that specific pool was built from the source and had exactly the same behaviour with doubled TXs as my wallet, then it is the same issue with common code that is not reproducible on every system.

I can confirm the issue with the following comment: when there was no official Mac wallet 1.2.2 published yet, I built it myself from the source. All seemed to be fine, and I received mined txes from a pool. When I tried to send some amount to an exchange, all my txes were duplicated. Actually, after clicking the send button, they were generated twice in the list of txes, both were successful, and the exchange received double amounts (did not try to send more than I had, though).

After updating to the official Mac 1.2.2 wallet the issue had disappeared. I decided that it was some build issue and did not report it. But after your report it seems there is some issue that needs to be fixed.

Yes, thanks, I sent some ITNS to sell and now see that. Also sent some ITNS to/from the exchange to ensure both ways work.

And yes, +1 for new Mac version, donwloaded 2 hours ago, it still is 1.2.0.

Weird exchange. Anybody knows their withdrawal fees?
I wanted to know their BTC fee but since there is no BTC on the wallet, there is no info. And I will not put any coins unless I know how I can withdraw them later. Don't they ask for 0.1BTC for transaction? :-)  Anybody knows/tried?

Higher clocks => higher power, yes.

To undervolt there are few ways:
- change powerplay table voltages (in BIOS or at runtime)
- change DPM states (use lower states = lover volts with high clocks)
- change VDDC voltage offsets (either fix BIOS tables, or patch VDDC offsets into BIOS tables, or use I2C at runtime)

The issue is that different drivers and platforms behave differently. Say, some ignore BIOS voltage tables, some use driver defaults, etc, etc. So there is no single "right" way to downvolt any card.

On Windows the best way could be to use WattTool to change VDDC offset, it uses i2c to update hardware voltage offset. But every voltage regulator requires own commands. WattTool was great and worked with many cards but its author disappeared. Still, even with latest drivers WattTool does not work with powerplay tables but can change VDDC offset. I2C method is better than -cvddc since it allows to set VDDC lesser than MVDDC. Changing VDDC sets it to max(MVDDC, VDDC).

Linux used by big farms, and no one wants to share the technology with public for free. They usually want 1-5-10 BTC for that (and actually different cards, different patches).

On Windows I use any tool (AB, Trixx, -mclock) to set memory clocks, and use WattTool to downvolt via VDDC offset. It gives best results but requires settings VDDC offset at runtime once after boot (not an issue). Linux tools similar to WattTool are not available freely, AFAIK.

On Linux the simplest way is to set higher clocks for lower DPM states (4, 5, 6, 7) and force lower state (4-6) to use lower voltages. All can be done at boot. Runtime voltage changes usually show successful changes, but actually do not change real wattage (from the wall). And BIOS changes ofter are ignored by Linux drivers.

@Claymore: BUG REPORT.

TL;DR: please run reboot.bat by -minspeed if r>=1 (not only with r=1).


Win10, miner 10.0, latest blockchain drivers (23 Aug). It does not reboot if -minspeed not reached and -r X set (X>1), just restarts miner.
This, formally speaking, is not a bug (since README says it reboots if r=1). But by logic, if one sets r>1 (that is, wants reboot on either error or by timer), seems reasonable to reboot also by -minspeed.

The real use case: unstable rig instance after miner restart (first boot ok but any miner restart may fail).
1) pool drops connection every 24h (some pools)
2) miner reconnects, but system hangs and reboots
3) AMD driver resets clocks to default
4) miner starts with default clocks and has low hashrate (AMD driver changes it only after miner restarted)
5) miner restarts by -minspeed, rates set to ok, but unstable system hangs and reboots again...
6) loop to 3 (default clocks again)

If miner reboots on -minspeed instead of restart, all would be ok (since new clocks are already set, and reboot is by command, not by driver error).

Using AB/Trixx to preset clocks will resolve the issue, but I prefer to set rates in the miner.


ANOTHER ISSUE: does anybody have reboots on Linux with NVIDIA on OpenCL error? I set -r1 but even if some card has 0 H/s, and/or -minspeed is set, miner does not react and does not reboot neither restart. Anybody to confirm?

Could you answer my question above:

The hashrate is the same as Monero (there is a lot of resources to get different hardware rates).
Then there is a calculator on the official pool to estimate ITNS/day with known hashrate.

If so, then another question: what's the difference between this project and Tor except that Tor nodes are free for everyone and still are decentralised?

Understand. But no matter what, if major exchanges ask so much just for listing, we can do nothing except either pay or use something else until the coin will be more popular. It is impossible unless the coin has at least some value. So better some exchange to start with rather than no exchange at all.

The answer to your question is: yes, they can list, but they need 9-14 BTC to do that right now. And that is what I meant suggesting to read news. It was answered right there.

Same for me.

You should probably read something about the coin. At least, news on the site. It is said in clear that listing it on most exchanges either impossible or cost 10-15 BTC for that. Nova asks 1 BTC and devs are willing to pay it from their pockets. But if you're willing to donate 9-14 BTC more to list on a big exchange, I think, they say thanks to you :-)

https://intensemining.pro/

33 workers at the moment.

What about power consumption? Did you downvolt them?

Din't you forget to add 'amdgpu.vm_fragment_size=9'? Without that module option the hashrate will be the same.

As for me, rocm kernel works as expected. Except it does not downvolt cards. I tried SMOS with original kernel and rocm. With original it can decrease power consumption, but has low hashrate. With rocm kernel the hashrate is higher, but DPM state changes do nothing, consumption is always high.

Is a real reason to build new kernel such as performance or stability issues?

Since I wasn't sure what patches to apply, I used a mix of both ways:
1. Installed not whole rocm package but only kernel image and headers 4.11 from rocm repository.
2. Installed compute-only 17.30 amd driver as recommended above (without dkms).
3. Added amdgpu module option.

Still there are issues with very slow boot (known issue if VBIOS was patched). But it runs.
Is 4.12 kernel somehow better?

On Windows I had 1162W. After switch to this kernel on Linux I tried to downvolt my rx470 by changing voltage table offsets in the DPM stages (that is, set offset of stage 4 or 6, or directly 1000-1050mV, to stage 7, so power consumption is lesser). At the same time I overclock memory and downclock GPU (mostly the same as on Windows). Used ohgodatool for that in realtime.

At the moment I was unable to get the same power consumption, it went from 1162 to 1300 now.

I know that it is not the best way to downvolt. I tried to change VDDC offset in the BIOS (since realtime VDDC change tools are not publicly available, and I have too few cards to hack it myself). This way works with my Sapphire cards, but it requires many reflashes when tuning every card for a stable operation. So I hoped to use only software ways to overclock and downvolt without changing BIOS (except timings).

Probably I have to use the BIOS way anyway if I want a comparable consumption to Windows rig.

As for the hashrate: even if displayed rates are bit lower (Claymore's miner) than on Windows, actual pool rates are the same. So the consumption is only my headache yet.

Much better way, does not pull whole rocm.
But which patches to apply from the link above? All?

Success!

HowTo:
1) Install ubuntu 16.04.3.
2) Install rocm as described above.
3) Add amdgpu parameter as described above. It is the key to success, don't miss that step.
4) Install amdgpu-17.30 as told by AMD.
Kernel module build fails, but correct driver is in the rocm installation. AMD driver is necessary for libOpenCL, etc.
5) Overclock using any tool (if desired).
6) Enjoy!

ETH hashrate under linux seems to be 0.3MH/s lesser than on Windows, it is a known issue and probably just measurement difference (see Claymore's FAQ).

But I should be able to run more than 8 cards per MB, will try ASAP.