These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more
1 | <?php |
||
0 ignored issues
–
show
|
|||
2 | $defflip = (!cfip()) ? exit(header('HTTP/1.1 401 Unauthorized')) : 1; |
||
3 | |||
4 | |||
5 | /** |
||
6 | * Our coin base class that we extend our other coins from |
||
7 | * |
||
8 | * We are implementing all basic coin methods into this class but it |
||
9 | * must be extended for customized coins. |
||
10 | **/ |
||
11 | class CoinBase extends Base { |
||
0 ignored issues
–
show
PSR1 recommends that each class must be in a namespace of at least one level to avoid collisions.
You can fix this by adding a namespace to your class: namespace YourVendor;
class YourClass { }
When choosing a vendor namespace, try to pick something that is not too generic to avoid conflicts with other libraries.
Loading history...
|
|||
12 | // Our coins target bits |
||
13 | protected $target_bits = NULL; |
||
14 | |||
15 | // Our coins share difficulty precision |
||
16 | protected $share_difficulty_precision = 0; |
||
17 | |||
18 | // Our coin value precision, mostly used on frontend |
||
19 | protected $coin_value_precision = 8; |
||
20 | |||
21 | /** |
||
22 | * Read our target bits |
||
23 | **/ |
||
24 | public function getTargetBits() { |
||
25 | return $this->target_bits; |
||
26 | } |
||
27 | |||
28 | /** |
||
29 | * Read our coin value precision |
||
30 | **/ |
||
31 | public function getCoinValuePrevision() { |
||
32 | return $this->coin_value_precision; |
||
33 | } |
||
34 | |||
35 | /** |
||
36 | * Read our share difficulty precision |
||
37 | **/ |
||
38 | public function getShareDifficultyPrecision() { |
||
39 | return $this->share_difficulty_precision; |
||
40 | } |
||
41 | |||
42 | /** |
||
43 | * Calculate the PPS value for this coin |
||
44 | * WARNING: Get this wrong and you will over- or underpay your miners! |
||
45 | **/ |
||
46 | public function calcPPSValue($pps_reward, $dDifficulty) { |
||
47 | return ($pps_reward / (pow(2, $this->target_bits) * $dDifficulty)); |
||
48 | } |
||
49 | |||
50 | /** |
||
51 | * Calculate our hashrate based on shares inserted to DB |
||
52 | * We use diff1 share values, not a baseline one |
||
53 | **/ |
||
54 | public function calcHashrate($shares, $interval) { |
||
55 | return $shares * pow(2, $this->target_bits) / $interval / 1000; |
||
56 | } |
||
57 | |||
58 | /** |
||
59 | * Calculate estimated shares of this coin, this is using baseline |
||
60 | * according to our configuration difficulty |
||
61 | **/ |
||
62 | public function calcEstaimtedShares($dDifficulty) { |
||
63 | return (float)round(pow(2, (32 - $this->target_bits)) * $dDifficulty, $this->share_difficulty_precision); |
||
64 | } |
||
65 | |||
66 | /** |
||
67 | * Calculate our networks expected time per block |
||
68 | **/ |
||
69 | public function calcNetworkExpectedTimePerBlock($dDifficulty, $dNetworkHashrate) { |
||
70 | if ($dNetworkHashrate > 0) { |
||
71 | return pow(2, 32) * $dDifficulty / $dNetworkHashrate; |
||
72 | } else { |
||
73 | return 0; |
||
74 | } |
||
75 | } |
||
76 | /** |
||
77 | * Calculate next expected difficulty based on current difficulty |
||
78 | **/ |
||
79 | public function calcExpectedNextDifficulty($dDifficulty, $dNetworkHashrate) { |
||
80 | $iExpectedTimePerBlock = $this->calcNetworkExpectedTimePerBlock($dDifficulty, $dNetworkHashrate); |
||
81 | if (!empty($iExpectedTimePerBlock) && $iExpectedTimePerBlock > 0) { |
||
82 | return round($dDifficulty * $this->config['cointarget'] / $iExpectedTimePerBlock, 8); |
||
0 ignored issues
–
show
The property
config does not exist. Did you maybe forget to declare it?
In PHP it is possible to write to properties without declaring them. For example, the following is perfectly valid PHP code: class MyClass { }
$x = new MyClass();
$x->foo = true;
Generally, it is a good practice to explictly declare properties to avoid accidental typos and provide IDE auto-completion: class MyClass {
public $foo;
}
$x = new MyClass();
$x->foo = true;
Loading history...
|
|||
83 | } else { |
||
84 | return 0; |
||
85 | } |
||
86 | } |
||
87 | } |
||
88 |
The PSR-1: Basic Coding Standard recommends that a file should either introduce new symbols, that is classes, functions, constants or similar, or have side effects. Side effects are anything that executes logic, like for example printing output, changing ini settings or writing to a file.
The idea behind this recommendation is that merely auto-loading a class should not change the state of an application. It also promotes a cleaner style of programming and makes your code less prone to errors, because the logic is not spread out all over the place.
To learn more about the PSR-1, please see the PHP-FIG site on the PSR-1.