https://mega.nz/#!fIVxGAxJ!9ANfWcxbRsUHzM6p1KH3uzqFmTZBXGW5X6Lq1fhGps8 Requisite is GMP, this is the algo (Quark Based Alternation + Magi M72 Diff + X17 Dependancies) Can you please make a CPUMiner, apperently implementing the inclient miner causes SIGABRT do you really want this? for(int i=0; i < NM7M; i++)
{
...
for(int i=0; i <= iterations; i++)
{
 Elbandi |
|
|
|
Just a note. This will crash: int bytes = mpz_sizeinbase(product, 512); 512 is too high, docs say: base can vary from 2 to 62. but other algo (m7m) is using 256, so i think thats works too. Elbandi |
|
|
|
Can you add funcaptcha as a captcha provider? It is for bot usage issue. Or at leas, a tutorial how to add it manually. Thanks!
FunCaptcha support added by latest commit. Configure at config.php: - set $recaptchaVersion to "funcaptcha"
- set the site keys to $recaptchaPub and $recaptchaPrv
Elbandi |
|
|
|
walletnotify=cmd-A && cmd-B
I'm guessing the second is better, if the first is even possible. While I am asking, how about alertnotify and blocknotify? walletnotify=/usr/local/bin/notifyscript.sh and you can call any commands in the script. |
|
|
|
We are aware of that and solution is possible once all miners use xnsub compatible software. But as long as there are reconnects involved, we cannot never know what will be the speed of incoming miner (considering that miners may change IP or there may be multiple miners using same IP).
You can identify "old" miner by the sessionid |
|
|
|
@NICEHASH please allow lower minimum hash rental from 0.1gig hash to 0.05gig hash... FROM this >" Limit hashing speed (0 for no limit, min. 0.1) " to this Limit hashing speed (0 for no limit, min. 0.05) < plz thx  We may only increase limit in future, not decrease. Reason are fast ASICs, that are well beyond this limit. When fast ASIC is assigned to your order, your speed jumps significantly. And customers usually do not like speed fluctuations. That's bad  There is old coin with low (<= 100M) global hashrate, coin fans cannot use you service, because a +100M hashrate will raise the difficulty more, the miner will be own enemy... I looked the miner stats, and i can see low hashrate addresses, there is some gridseeds miners |
|
|
|
whether a somebody this script working with DOGE coin?
On faucetbox i have ltc, btc and doge faucet.. and minifaucet script set to doge faucet always get btc balance
where did I go wrong?
Open this file: FaucetBOXWalletProvider.php search this: global $faucetBoxKey;
$this->faucetbox = new FaucetBOX($faucetBoxKey);
Change to global $faucetBoxKey, $coinType;
$this->faucetbox = new FaucetBOX($faucetBoxKey, $coinType);
Elbandi |
|
|
|
If pools do not follow specifications, then make them follow. Usually after some time, they adopt.
Eh? From Stratum Mining Protocol official documentation (bold is marked by me): Server Can Occasionally Ask Miner to Change Share Difficulty
Default share difficulty is 1 (big-endian target for difficulty 1 is 0x00000000ffff0000000000000000000000000000000000000000000000000000), but server can ask you anytime during the session to change it:
{ "id": null, "method": "mining.set_difficulty", "params": [2]}
This Means That Difficulty 2 Will Be Applied to Every Next Job Received From the Server. Let's say a telnet to your pool: [L0] {"id": 1, "method": "mining.subscribe", "params": []}
[L1] {"result": [[["mining.notify", "00097c41"]], "20a6a503", 8], "id": 1, "error": null}
[L2] {"params": ["55c69c0300006fdc", "a3b32fc515975727a8fe91857c6f4f71a4359df1117c96430000000000000000", ".....", "1814dd04", "55d20bf8", true], "method": "mining.notify", "id": null}
[L3] {"params": [1042], "method": "mining.set_difficulty", "id": null}
...
[L4] {"method": "mining.notify", "params": ["55c69c0300006ff6", "295d51c341c96d1d7690ec202fddef62841374930cb892270000000000000000", "....", "1814dd04", "55d20e33", true], "id": null}
L0: this is the client subscribe L1: pool response for clien subscribe L2: first mining.notify -> share difficulty calculates to 1 (default share difficulty based on stratum mining doc) L3: change the difficulty to 1042 for next job L4: next mining.notify -> share difficulty sould calculate to 1042! The cgminer has the "bug": apply the difficulty for current job: so L2 job has 1042 sharediff. this conflict with mining doc. Solutions: - fix the doc: "Applied to Every Next Job" -> "Applied to Every Current Job"
- fix cgminer (with the patch) and fix your pool: send the set_difficulty first and mining.notify next
|
|
|
|
Can't seem to compile (Ubuntu 14.02...all dependencies are installed). Anyone else have any hints:
apt-get install libssl-dev libcurl4-openssl-dev |
|
|
|
Please create a worker on one of the pools and allow us to see for ourselves?
And prove to what ? he can made a high speed worker with proxy+lots of cpu...  |
|
|
|
I have no idea how to compile from source...but would be interested to learn.  Than scroll down on github url, find the build section, and use it. If you get stuck, just use google, the internet has full of tutorials/howtos, you can find anything. Elbandi |
|
|
|
A good bounty for working cpuminer? |
|
|
|
Perhaps using something similar to this: function sql_query($sql)
{
global $mysqli;
$sql = $mysqli->real_escape_string($sql);
return $mysqli->query($sql);
}
Will solve the problem, as it escapes the string before continuing with the query. It's half true: real_escape_string is not a silver bullet to protect against sql inject. google://sql+injection+with+mysql+real+escape+string. If you always belive in realescapestring, you have in false safety. My goal is to check/verify the input before the sql code, and do not execute sql if it is not good (eg verifyaddress). I have only two eyes, so if you find place where i dont check something, feel free to msg me The hacked faucets used a modified versions from minifaucet, so we dont know the bug/sqlinject/whatever is in the original code or in the modified code. So we are just groping in the dark Did someone checked that modified code? At all, do someone have the modified code? Elbandi |
|
|
|
Thank you. I have an image of the drive here but not uploaded any where yet. Do you think that is safe to do so?
I understand it is encrypted but even so?
Ah, i see, you have btc on it. (i thought just you have important mail/data/etc on usb). Basectly, it's encrypted, so you can share the encrypted data (same situation, if someone stole your usb)... |
|
|
|
|
Show Posts
