Son of a bitch.. it's stuck again!  Block 236921 Almost the same time as yesterday. |
|
|
|
How do you create new sharechain for a coin? Change IDENTIFIER & PREFIX and delete the data directory. Although not necessary consider changing the P2P_PORT as well. Change persist to false(?). |
|
|
|
Neat...thanks for the input. Get's the gears working on new ideas  |
|
|
|
As an example of another coin that has not implemented the "supposed" fix to KGW yet you can see a similar situation...it is currently stuck at block 440127 and I expect it will be stuck there for a few hours. Hopefully miners wont notice and ditch the coin before the next block is found or it may get stuck. Notice the blocks going back in time right before getting stuck. This coin normally has about 100 Mh/s and a diff in the 0.7 range:  One thing that should be noted is that there is not really 77.3 Gh/s on this coin. That estimated hashrate and diff are an effect of the exploit. (I think) |
|
|
|
we did patch the KGW remember -
we patched right after aurora got attacked, we where one on the first coins to patch and we did it very quick....
WE MAY PUSH THE HALVING FORWARD TO REVIEW THESE ATTACKS TO FIND A WE CAN FIND A FIX>>>> i will talk to the team. we are working on the wallets now so this is good timing.
Good to hear....I hear the "patch" for the KGW flaw was more of a bandaid as it still left the vulnerability in place but only made it harder to exploit. Just passing along what I recall. I have not followed it closely. Wish you and your team the best of luck! |
|
|
|
|
Thanks for confirming it was the timewarp vulnerability. I obviously don't follow this coin closely but noticed the situation right before I was about to start mining. Went elsewhere as I knew it would be stuck for a few hours.
Have seen the same thing happen to other coins that have not yet fixed this....the "reported" diff and hashrate shoot way up until the next block is found. Without enough hash power a coin can get stuck in this situation.
I suggest the devs make fixing this vulnerability a priority over anything else.
|
|
|
|
Look around block 234897. Does POT use KGW? Looks like a timewarp attack. Notice block 234894 go back in time then two hours between block 234897 and 234898.  |
|
|
|
|
What's up with the diff and network hashrate right now?
Hashrate 1.56TH/s
Difficulty 14500
Timewarp?
|
|
|
|
Error on make: make all-recursive
make[1]: Entering directory `/home/sandor_kicks_ass/cpuminer-gc3355'
Making all in compat
make[2]: Entering directory `/home/sandor_kicks_ass/cpuminer-gc3355/compat'
make[3]: Entering directory `/home/sandor_kicks_ass/cpuminer-gc3355/compat'
make[3]: Nothing to be done for `all-am'.
make[3]: Leaving directory `/home/sandor_kicks_ass/cpuminer-gc3355/compat'
make[2]: Leaving directory `/home/sandor_kicks_ass/cpuminer-gc3355/compat'
make[2]: Entering directory `/home/sandor_kicks_ass/cpuminer-gc3355'
gcc -std=gnu99 -DHAVE_CONFIG_H -I. -pthread -fno-strict-aliasing -O2 -MT minerd-cpu-miner.o -MD -MP -MF .deps/minerd-cpu-miner.Tpo -c -o minerd-cpu-miner.o `test -f 'cpu-miner.c' || echo './'`cpu-miner.c
cpu-miner.c: In function ‘api_parse_get’:
cpu-miner.c:1468:124: error: expected ‘)’ before ‘;’ token
cpu-miner.c:1470:4: error: expected ‘;’ before ‘}’ token
cpu-miner.c: In function ‘api_request_handler’:
cpu-miner.c:1621:7: warning: ignoring return value of ‘write’, declared with attribute warn_unused_result [-Wunused-result]
make[2]: *** [minerd-cpu-miner.o] Error 1
make[2]: Leaving directory `/home/sandor_kicks_ass/cpuminer-gc3355'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/sandor_kicks_ass/cpuminer-gc3355'
make: *** [all] Error 2
Think it's here...missing a closing ')': https://github.com/siklon/cpuminer-gc3355/commit/020c54c4cc425a61bd017186520a06b91f128c13 |
|
|
|
|
I see that you added support for any freq....do you still recommend only using increments of 25 even though we can do anything now?
|
|
|
|
Can I mining skrypt-n coin at same speed like scrypt coins
Or not???!
Scrypt ASICs will only mine Scrypt. Nothing else. There are a few new ones that also do Srypt-N....but you'll have to find them on your own  |
|
|
|
Just for comparison here are the freq's on my stock (non-moded) 5 chippers are pulling with close to 0 HW errors:  Is it okay to run with --debug on or is that only recommended when dialing in your settings? I'm running on a core i7 so CPU is not an issue. Also, I really like how dtbartle cgminer does per_chip_stats=1. I realize that's hard with the blades but would be nice to see at least for the 5 chip miners. |
|
|
|
Can you try the latest commit, I think I just fixed that. Yes, works now. Major props! |
|
|
|
Yes it's real...but I would skip it. They want too much for it ($10k) and for that cost you will soon have 300Mh+ |
|
|
|
Built v0.9g on Ubuntu and --gc3355-detect no longer works. Also the serial numbers are gone? Works using gc3355=/dev/ttyACM0,/dev/ttyACM1,etc *** glibc detected *** ./minerd: double free or corruption (out): 0x0000000001a42640 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x7eb96)[0x7fef1a88bb96]
/lib/x86_64-linux-gnu/libtinfo.so.5(_nc_last_db+0x16)[0x7fef1abdb316]
/lib/x86_64-linux-gnu/libtinfo.so.5(_nc_read_entry+0x12f)[0x7fef1abe1fbf]
/lib/x86_64-linux-gnu/libtinfo.so.5(_nc_setup_tinfo+0x29)[0x7fef1abdd559]
/lib/x86_64-linux-gnu/libtinfo.so.5(_nc_setupterm+0x98)[0x7fef1abdd8d8]
/lib/x86_64-linux-gnu/libncurses.so.5(newterm+0x6b)[0x7fef1ae038eb]
/lib/x86_64-linux-gnu/libncurses.so.5(initscr+0x62)[0x7fef1ae00732]
./minerd[0x404333]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7fef1a82e76d]
./minerd[0x4045f5]
======= Memory map: ========
00400000-0044b000 r-xp 00000000 08:01 3147781 /home/sandor_is_king/cpuminer-gc3355/minerd
0064a000-0064b000 r--p 0004a000 08:01 3147781 /home/sandor_is_king/cpuminer-gc3355/minerd
0064b000-0064d000 rw-p 0004b000 08:01 3147781 /home/sandor_is_king/cpuminer-gc3355/minerd
01a42000-01a84000 rw-p 00000000 00:00 0 [heap]
7fef10000000-7fef1002a000 rw-p 00000000 00:00 0
7fef1002a000-7fef14000000 ---p 00000000 00:00 0
7fef14b01000-7fef14b16000 r-xp 00000000 08:01 655404 /lib/x86_64-linux-gnu/libgcc_s.so.1
7fef14b16000-7fef14d15000 ---p 00015000 08:01 655404 /lib/x86_64-linux-gnu/libgcc_s.so.1
7fef14d15000-7fef14d16000 r--p 00014000 08:01 655404 /lib/x86_64-linux-gnu/libgcc_s.so.1
7fef14d16000-7fef14d17000 rw-p 00015000 08:01 655404 /lib/x86_64-linux-gnu/libgcc_s.so.1
7fef14d17000-7fef14d18000 ---p 00000000 00:00 0
7fef14d18000-7fef15518000 rw-p 00000000 00:00 0 [stack:1382]
7fef15518000-7fef15519000 ---p 00000000 00:00 0
7fef15519000-7fef15d19000 rw-p 00000000 00:00 0 [stack:1381]
7fef15d19000-7fef15d22000 r-xp 00000000 08:01 655378 /lib/x86_64-linux-gnu/libcrypt-2.15.so
7fef15d22000-7fef15f22000 ---p 00009000 08:01 655378 /lib/x86_64-linux-gnu/libcrypt-2.15.so
7fef15f22000-7fef15f23000 r--p 00009000 08:01 655378 /lib/x86_64-linux-gnu/libcrypt-2.15.so
7fef15f23000-7fef15f24000 rw-p 0000a000 08:01 655378 /lib/x86_64-linux-gnu/libcrypt-2.15.so
7fef15f24000-7fef15f52000 rw-p 00000000 00:00 0
7fef15f52000-7fef15ff0000 r-xp 00000000 08:01 791549 /usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6
7fef15ff0000-7fef161f0000 ---p 0009e000 08:01 791549 /usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6
7fef161f0000-7fef161f2000 r--p 0009e000 08:01 791549 /usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6
7fef161f2000-7fef161f4000 rw-p 000a0000 08:01 791549 /usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6
7fef161f4000-7fef161f5000 rw-p 00000000 00:00 0
7fef161f5000-7fef1623a000 r-xp 00000000 08:01 795843 /usr/lib/x86_64-linux-gnu/libhx509.so.5.0.0
7fef1623a000-7fef1643a000 ---p 00045000 08:01 795843 /usr/lib/x86_64-linux-gnu/libhx509.so.5.0.0
7fef1643a000-7fef1643c000 r--p 00045000 08:01 795843 /usr/lib/x86_64-linux-gnu/libhx509.so.5.0.0
7fef1643c000-7fef1643e000 rw-p 00047000 08:01 795843 /usr/lib/x86_64-linux-gnu/libhx509.so.5.0.0
7fef1643e000-7fef1643f000 rw-p 00000000 00:00 0
7fef1643f000-7fef1644d000 r-xp 00000000 08:01 795837 /usr/lib/x86_64-linux-gnu/libheimbase.so.1.0.0
7fef1644d000-7fef1664c000 ---p 0000e000 08:01 795837 /usr/lib/x86_64-linux-gnu/libheimbase.so.1.0.0
7fef1664c000-7fef1664d000 r--p 0000d000 08:01 795837 /usr/lib/x86_64-linux-gnu/libheimbase.so.1.0.0
7fef1664d000-7fef1664e000 rw-p 0000e000 08:01 795837 /usr/lib/x86_64-linux-gnu/libheimbase.so.1.0.0
7fef1664e000-7fef16676000 r-xp 00000000 08:01 795840 /usr/lib/x86_64-linux-gnu/libwind.so.0.0.0
7fef16676000-7fef16875000 ---p 00028000 08:01 795840 /usr/lib/x86_64-linux-gnu/libwind.so.0.0.0
7fef16875000-7fef16876000 r--p 00027000 08:01 795840 /usr/lib/x86_64-linux-gnu/libwind.so.0.0.0
7fef16876000-7fef16877000 rw-p 00028000 08:01 795840 /usr/lib/x86_64-linux-gnu/libwind.so.0.0.0
7fef16877000-7fef1687a000 r-xp 00000000 08:01 655687 /lib/x86_64-linux-gnu/libkeyutils.so.1.4
7fef1687a000-7fef16a79000 ---p 00003000 08:01 655687 /lib/x86_64-linux-gnu/libkeyutils.so.1.4
7fef16a79000-7fef16a7a000 r--p 00002000 08:01 655687 /lib/x86_64-linux-gnu/libkeyutils.so.1.4
7fef16a7a000-7fef16a7b000 rw-p 00003000 08:01 655687 /lib/x86_64-linux-gnu/libkeyutils.so.1.4
7fef16a7b000-7fef16a7e000 r-xp 00000000 08:01 655683 /lib/x86_64-linux-gnu/libgpg-error.so.0.8.0
7fef16a7e000-7fef16c7d000 ---p 00003000 08:01 655683 /lib/x86_64-linux-gnu/libgpg-error.so.0.8.0
7fef16c7d000-7fef16c7e000 r--p 00002000 08:01 655683 /lib/x86_64-linux-gnu/libgpg-error.so.0.8.0
7fef16c7e000-7fef16c7f000 rw-p 00003000 08:01 655683 /lib/x86_64-linux-gnu/libgpg-error.so.0.8.0
7fef16c7f000-7fef16c90000 r-xp 00000000 08:01 795815 /usr/lib/x86_64-linux-gnu/libp11-kit.so.0.0.0
7fef16c90000-7fef16e8f000 ---p 00011000 08:01 795815 /usr/lib/x86_64-linux-gnu/libp11-kit.so.0.0.0
7fef16e8f000-7fef16e90000 r--p 00010000 08:01 795815 /usr/lib/x86_64-linux-gnu/libp11-kit.so.0.0.0
7fef16e90000-7fef16e91000 rw-p 00011000 08:01 795815 /usr/lib/x86_64-linux-gnu/libp11-kit.so.0.0.0
7fef16e91000-7fef16ea1000 r-xp 00000000 08:01 795817 /usr/lib/x86_64-linux-gnu/libtasn1.so.3.1.12
7fef16ea1000-7fef170a0000 ---p 00010000 08:01 795817 /usr/lib/x86_64-linux-gnu/libtasn1.so.3.1.12
7fef170a0000-7fef170a1000 r--p 0000f000 08:01 795817 /usr/lib/x86_64-linux-gnu/libtasn1.so.3.1.12
7fef170a1000-7fef170a2000 rw-p 00010000 08:01 795817 /usr/lib/x86_64-linux-gnu/libtasn1.so.3.1.12
7fef170a2000-7fef170b6000 r-xp 00000000 08:01 795809 /usr/lib/x86_64-linux-gnu/libroken.so.18.1.0
7fef170b6000-7fef172b5000 ---p 00014000 08:01 795809 /usr/lib/x86_64-linux-gnu/libroken.so.18.1.0
7fef172b5000-7fef172b6000 r--p 00013000 08:01 795809 /usr/lib/x86_64-linux-gnu/libroken.so.18.1.0
7fef172b6000-7fef172b7000 rw-p 00014000 08:01 795809 /usr/lib/x86_64-linux-gnu/libroken.so.18.1.0
7fef172b7000-7fef172e8000 r-xp 00000000 08:01 795834 /usr/lib/x86_64-linux-gnu/libhcrypto Command line: sudo ./minerd --gc3355-detect --freq=850 --gc3355-autotune --gc3355-timeout=1800 -o stratum+tcp://xpool.net:9555 -u KitKat -p x |
|
|
|
My Dogecoin Station  I saw that, and that's why got me to put my little one up... very nice. Can I ask where you got the USB hub that has ATX in and a switch? About the power supply, I'm switching over to an ATX power supply once I get the adaptors... Hello, That orange USB Hub is one of the best ones out there! A block-erupter hub is not coming close to the quality of this one. I got this one from eyeboot.com Deeplink here. I only use this hub`s for my projects, For example the block-erupter hubs use give me a lot of problems whit stability, or just died within weeks due to bad components  Check this picture "loaded whit miners of 1.2 Amp each", no other (still affordable) usb-hub stays stable whit that kind of load. https://dl.dropboxusercontent.com/u/304909/Photo%2028-3-14%2011%2025%2035%20pm.jpgHope your question get answered here. Out of the box Video: http://dai.ly/x1tlwz9I like the version of this hub that takes 6-pin PCIe for power vs ATX. Anyone have a source for that? A barrel plug version would be good too but haven't seen a version that has that. |
|
|
|
So, what's the plan regarding the github repo? If transcoder has disappeared, maybe it's time we bite the bullet and fork the repo. What are your thoughts?
I say we give it another week, making It 1 full month without having the main developer here. We can fork but will take some time to get everyone on board including cryptsy, my gambling sites, explorers, miners, etc etc Id like to get other thoughts as well, thanks gold Cartman what do you think? Vert hby? Set a deadline that everyone can agree on as fair and then nominate a new dev or dev team. Also give plenty of time/notification for people to be informed of the fork. New dev/team can bring some excitement and attention back into the coin if done right. Thoughts? Edit: this new dev team does not have to exclude transcoder if he finds the time to get involved again. As we have seen it is hard to rely on one person to carry the work so a group of people with the skills and time would be preferred. |
|
|
|
Thanks poopypants! I'm glad you enjoyed it. It was a fun project and I hope it helped people. I certainly learned quite a bit in the process. It looks like it will probably be one of my last as newer miners seem to be coming out in rack mountable versions. Ultimately that is a good thing as it will quickly allow you to deploy and operate over figuring out how to house and wire but it does take away a little of the fun/hobbyist perspective. Have my eye on the KNC Titan or the Flower Tech Lilac |
|
|
|
Finally put it in the rack. Not the greatest wiring job since I was in a rush. Started to wire it up:  All wired up (missing one miner).  Back side:  Observations: Could have made the case longer and still fit in the rack. A longer case would be about enough room for 10 miners with fans on each row. 40 miners total. Each power supply is more than enough to power 10 miners dual mining and one 10 port USB hub. Case has enough room to fit 5 power supplies and about 5 USB hubs. I will not be building this up further as newer (much) more powerful rack mountable scrypt miners are soon to be released. These 5 chip gridseed miners are too much of a pain to wire up and rack.
|
|
|
|
|
Show Posts
