miner leeches KST

[Tyrasuki]

so, i recently noticed i never mined any coins anymore, so i fired up wireshark to see what was happening with the hashes being generated (my krist address is k5n6r931i1), thinking that they might not be sending, but when i check the HTP, i see this:

The blocks i mine are being sent to k57znvlpvk, even tho i specified my own address to mine can anyone explain to me why my mined krist is being sent to another adress??

[dmarcuse]

This is more likely to be an issue with the miner you're using than with Krist itself. Which miner are you using? The best public Krist miner is turbokrist (shameless plug) which is the only hardware accelerated Krist miner right now.

[Tyrasuki]

im using TurboKrist-cli (which is yours)

[dmarcuse]

What arguments are you passing it?

[Tyrasuki]

java -jar turbokrist-cli.jar -h k5n6r931i1 -w 1:1248445321

[Tyrasuki]

there is some activity on the network right now, someone is mining (guessing thats you?)

[dmarcuse]

I just tested it myself and it's working properly.

Also, you're using the -w option incorrectly - it should be signature:size where signature is the signature found using the -l option, and size is the number of concurrent threads to run. I use -w -1195358334:$((2**24)) (-1195358334 is the signature of my dGPU)

[Tyrasuki]

i just got a block!, but i dont get why the hashes where being redirected to that address.

[Lustyn]

Most likely, you are viewing the wrong http request and someone is just beating you to blocks. The miner isn't stealing your coins ;P

[Tyrasuki]

@apemanzilla how do i get the signature? i am using a GTX 750

[dmarcuse]

Run turbokrist with the -l argument - java -jar turbokrist-cli.jar -l.

Then, copy the signature and try increasing work sizes with powers of two. Since you're on Linux, you can do something like java -jar turbokrist-cli.jar -h k5n6r931i1 -w signature:$((2**20)) and if that works at an acceptable temperature, increment the 20 and continue.

[Tyrasuki]

@justync7 i dont think so, it was from source: 192.168.0.156 ; destination: 192.99.175.37

[Tyrasuki]

@apemanzilla there is no signature showing

lolmaker2002@DesktopPC ~/Desktop $ java -jar turbokrist-cli.jar -1
Exception in thread "main" org.apache.commons.cli.UnrecognizedOptionException: Unrecognized option: -1
    at org.apache.commons.cli.DefaultParser.handleUnknownToken(DefaultParser.java:347)
    at org.apache.commons.cli.DefaultParser.handleShortAndLongOption(DefaultParser.java:484)
    at org.apache.commons.cli.DefaultParser.handleToken(DefaultParser.java:243)
    at org.apache.commons.cli.DefaultParser.parse(DefaultParser.java:120)
    at org.apache.commons.cli.DefaultParser.parse(DefaultParser.java:76)
    at org.apache.commons.cli.DefaultParser.parse(DefaultParser.java:60)
    at me.apemanzilla.krist.turbokrist.cli.Launcher.main(Launcher.java:74)

[Lustyn]

You sure? It's requesting /blocks/last/ and the data you see there is the last address that mined a block. It's not a request submitting a block.

[dmarcuse]

@lolmaker2002 that's a lowercase L, not a 1.

[Tyrasuki]

@justync7 i overlooked that, sorry!

[Tyrasuki]

i think i should go see a eye specialist, i overlook a request for the latest block and i cant spot the difference between an l and a 1

[dmarcuse]

Also, in the screenshot the packet you have highlighted is actually from 192.99.175.37 to 192.168.0.156 (i.e. from Krist to your PC). If I had to guess I'd say that you're not getting any blocks because of the incorrect usage of -w, and you're instead looking at the work data that turbokrist periodically pulls from the Krist server.

Closing this for now, if it happens again let me know.

[Tyrasuki]

well that increase of blocks is amazing

[Tyrasuki]

thanks for the help everyone !

[dmarcuse]

No problem. If you don't mind me asking, what's your hashrate? I haven't done any tests with a GTX 750, only a GTX 760 which hit about 230 MH/s.