Got IT! I copied the host line from the pool and he had the port at the end of the line so I left it as is.
I entered it as port [xxxx] and it works.
The rest is a pool issue with getting work.
Yeah, I missed that it was malformed there. Hopefully now it will work! |
|
|
|
I think this thread is a waste of time and efforts. Litecoin will fail anyway.... no need for an attack.
I doubt it given the ever increasing $10 million USD market cap. |
|
|
|
|
It looks like you swapped the contents of reaper.conf and litecoin.conf, if I had to guess.
Be sure to move the litecoin-reaper.cl file over if you want to mine litecoin, too.
|
|
|
|
What would the open source documentation consist of exactly?
Perhaps we also need to draw up a To Do List of things that missing or need to be done.
Go through Sunny King's C++ code and figure out what the christ is going on in it. It's poorly commented and difficult to read through. |
|
|
|
root@xxxx:/home/xxxx/Desktop/reaper/build# ./reaper
\|||||||||||||||||||||/
- Reaper v13 64-bit -
- BETA 4 -
- coded by mtrlt -
/|||||||||||||||||||||\
/----------------------------------------------\
| Please donate to support Reaper development! |
|----------------------------------------------|
| SLC: sdJMdNAEaJMVaxPFxaWibty9bec6Y4ubJK |
| BTC: 1DjMcD5oQUap7kXrwa9J8S5esMryUs777o |
| LTC: LZ5xurMLgdEzeuXuJvYB4DwyprCC1asfmp |
\----------------------------------------------/
2013-03-17 16:37:00 Error: Config file reaper.conf not found.
root@xxxx:/home/xxxx/Desktop/reaper/build#
This is with litecoin.conf and reaper.conf in the same directory? (you can see both when you run 'ls'?) |
|
|
|
Do you have a BTC address you use for small donations?
This one is fine 17bmYcP6Vio6c1gnyPsaDSv4B11SLe81Ab C: |
|
|
|
Nothing should change except the attribute on the file. now, Should do something, because the FS recognizes it as an executable. |
|
|
|
|
Q: Can you fork the chain by turning your client off for a long time, then spamming PoS blocks when it comes back online?
I think the easiest implementation to test this is to just start up the coin with 10,000 coins or whatever in a bunch of public addresses on a test net with PoW disabled. Then, see if anyone can spam the chain quickly enough with PoS blocks to fork it and do things they shouldn't be able to do, like invalidate transactions.
|
|
|
|
Sorry if this is off topic,
I finally got reaper to compile, I think. It said it was linking the CXX executable to reaper or something similar.
Now I cannot get reaper to run. The readme.md seems to suggest I go to the build folder and run reaper. I click on reaper, or try and run reaper from the root terminal and get a command not found error.
If you cannot tell I know zilch about Linux. I'm using Debian squeeze 64 if that makes any difference.
Thanks.
did you ? |
|
|
|
|
With a market cap in the millions and thousands of dedicated miners, I doubt that. Additionally, the scrypt implementation and then the GPU miner for scrypt took way, way longer than 10 minutes to code (you're forgetting Tenebrix/Fairbrix, advancements in the mining algorithm that allowed it to be GPU mined, etc etc).
The point of Litecoin was being a dedicated memory hard chain based on scrypt -- something that was achieved in spades. Even the other coins with active development like PPCoin haven't updated to 0.7 backend yet, because 0.6.3 is a solid, stable release.
|
|
|
|
It is easy, just not everyone knows what exactly to do :trlf:
There are a lot of ways to get around WriteProcessMemory or OpenProcess call monitoring if that's what you're talking about. It's really easy to write straight binary code to memory from a C program from overflow or other simple calls that will never be detected that way. |
|
|
|
Just check if any system files have injected any different byte arrays into the systems memory. Checking if anything has been written to the VirtualMemory or any space has been allocated in the memory.
If it were that easy, anti-virus software companies would be out of a job pretty quickly.  |
|
|
|
You buy a "botkiller". It kills all the other peoples infected file besides yours so the zombie is all yours.
That I would trust even less than the botnet computers themselves. That would need to be something you yourself programmed, and even then it'd be difficult to tell what other backends were and weren't installed on the compromised computer. |
|
|
|
The only problem I hate about checkpoints is once we restore and the coins are gone, the coin is over.
There is another massive problem with the litecoin botnet scheme too -- when people realize that they can make lots of money using a botnet to mine litecoin, the price of renting a botnet will increase tremendously based upon demand and there will be intense competition now for "zombie" computers. The other thing is that computers you get from a botnet are usually shared as far as I can tell, so you're competing with other people also using the CPUs. My personal guess is that if you purchase a large botnet you'll probably hit less than a KH/s per computer because they're already busy chugging out all kinds of shitty code for other people. If this is the case, you're looking at $100k USD+ to attack the network. |
|
|
|
Try settings GPU threads to 2 instead of 1 for the 7970s. That's the only thing I can think of. If that fixes it, I'll update it in the next GUIminer release.
There are a lot of complaints about cgminer 2.11.3 right now, I need to verify it functions correctly before I will add it to GUIminer
2 threads = 421Kh/s This may help 1 card, 16 gb system ram. Cgminer allocates only about 40MB, video memory usage is 1133MB.
Here are some hashrate numbers at different frequencies:
Gpu/Mem Hashrate~
800/790 555kH/s
800/870 555kH/s
850/930 585kH/s
850/1065 585kH/s
900/1000 620kH/s
900/1155 625kH/s
900/1310 620kH/s
925/1000 635kH/s
925/1001 400kH/s
950/1205 655kH/s
950/1370 650kH/s
963/1375 665kH/s
963/1220 670kH/s
1000/1250 660kH/s
1000/1251 450kH/s
1000/1455 690kH/s
1024/1475 710kH/s
1044/1500 720kH/s
1044/1501 495kH/s
Klear, if you can verify any of these work let me know |
|
|
|
 nope |
|
|
|
Yeah, anyone using 2.11.3 please chime, mostly people are saying that either the program doesn't run or the kernel throws lots of invalids so I'm a little skeptical. Quick test of scrypt mining on my Windows 7 machine. Same everything.
2.11.2 - No HW errors.
2.11.3 - Lot of HW errors, very low accepted rate.
Don't have time to play with it so I sticking with 2.11.2 for now. I've been playing a bit with cgminer (2.11.2 and 2.11.3) and scrypt during the last few hours. So far the best performance I could achieve on my GV-R797OC-3GD on windows 7 x64 with catalyst 13.2b7 was around 720kH/s with the following settings: cgminer.exe --scrypt -o http://xxx -u x -p x --intensity 13 -g 2 --thread-concurrency 8192 --lookup-gap 2 --gpu-engine 1044 --gpu-memclock 1500 a more conservative 620kH/s with cgminer.exe --scrypt -o http://xxx -u x -p x --intensity 13 -g 2 --thread-concurrency 8192 --lookup-gap 2 --gpu-engine 900 --gpu-memclock 1155 and an even more conservative 550kH/s with cgminer.exe --scrypt -o http://xxx -u x -p x --intensity 13 -g 2 --thread-concurrency 8192 --lookup-gap 2 --gpu-engine 800 --gpu-memclock 870 Increasing thread concurrency above 8192 with --lookup-gap 2 always returns an error like Maximum buffer memory device 0 supports says 536870912
Your scrypt settings come to 1467482112
Error -61: clCreateBuffer (padbuffer8), decrease CT or increase LG Lowering thread concurrency below 8192 always produces hardware errors. With -g > 1 using any intensity higher or lower than 13 will result in lower hashrates. With -g 1 higher than 13 intensities will more or less match -g 2 -I 13 hashrate at the expenses of system responsiveness. Increasing lookup gap allows for higher thread concurrencies, but it won't improve performance. Setting the correct core/memory ratio for your card is the most important tweak, even a small 10MHz difference can make you lose/gain 100-200kH/s. |
|
|
|
|
Probably someone testing new ASICs, like BFL.
|
|
|
|
|
Try settings GPU threads to 2 instead of 1 for the 7970s. That's the only thing I can think of. If that fixes it, I'll update it in the next GUIminer release.
There are a lot of complaints about cgminer 2.11.3 right now, I need to verify it functions correctly before I will add it to GUIminer
|
|
|
|
|
Show Posts
