I will add a expstats.json for you later with avg networkhash, difficulty, avg block time, current block if thats all you need?
Wont be for a couple of hours i have a couple of things to do.
Thank you, most appreciated. Actually I only need "blockcount" and "difficulty". "Total coins" would also be useful, but I can get that from coinmarketcap if problematic. Ok done has current block and difficulty http://www.gitbox.link/expstats.jsonTotal coins you can get from http://www.expanse.tech/explorer/api/totalsupplyThanks  Wasnt aware that this calc is yours. I have seen the json exposed there, but didnt want to steal data from another calc  |
|
|
|
I will add a expstats.json for you later with avg networkhash, difficulty, avg block time, current block if thats all you need?
Wont be for a couple of hours i have a couple of things to do.
Thank you, most appreciated. Actually I only need "blockcount" and "difficulty". "Total coins" would also be useful, but I can get that from coinmarketcap if problematic. |
|
|
|
Hey,
Would like to add Expanse to my site, looking for an API with difficulty and blockcount.
Anything available?
Run a gexp node and use web3 and add a little javascript and your done. you could run a node and just pull that info
Well thats not what I asked for. I am in no position to run a node for each coin I add. Basically I was following this tweet: https://twitter.com/expanseofficial/status/701404350715994113Our block explorer has recently been updated over the last few days, the public API will be launching today. +1 Dan! I understand that this is still not done a month later? |
|
|
|
|
Hey,
Would like to add Expanse to my site, looking for an API with difficulty and blockcount.
Anything available?
|
|
|
|
Is there a way to stake with a locked wallet?
I did the `walletpassphrase xxx seconds true` command, but it says the wallet is unlocked.
It should say "Unlocked for staking" right?
There's no way to stake with a locked wallet because a locked wallet cannot process transactions. 'Unlocked for staking' is for QT GUI only to prevent someone having physical access to the wallet being able to send coins without knowing the password. You'd be asked again for password before sending out coins, even though it's unlocked for minting. Ah its locked for sending, thanks for the info. I was confused by the message that "Wallet is encrypted and currently unlocked" |
|
|
|
|
Is there a way to stake with a locked wallet?
I did the `walletpassphrase xxx seconds true` command, but it says the wallet is unlocked.
It should say "Unlocked for staking" right?
|
|
|
|
Yes I get your point, just saying that in my opinion it would be good to be consistent within Quark algo. Just like Cryptonight coins are all consistent without 2^32 multiplier. I understand there are no strong arguments one way or another. If the devs here decide to stick to 2^32, instead of 2^24, then I will adapt my code |
|
|
|
Interesting. I prefer block frequency and this is what I use:
block frequency in seconds = 2^32 * coin_difficulty / (hashrate_in_Mhs * 1e6)
And it appears you were right about the number 256 instead of 200, I'm not sure why I came up with 200 when I did my calculation long ago.
Let's see Quarkcoin with its current difficulty (228):
2^32 * 228 / (100 * 1e6) = 9792 seconds per block with 100 Mh/s which is obviously wrong.
2^32 * 228 / 256 / (100 * 1e6) = 38.2 seconds per blocks which is the correct number.
Now let's see DNET:
2^32 * 113.43 / (100 * 1e6) = 4871 seconds or 81 minutes which is correct so there's no need for a correction. (with a correction 100 Mh/s would get you a block every 19 seconds.)
If we would update the code with my suggestion, then the difficulty would already be multiplied by 256, internally by the wallet and the equation would be true again: 2^24 * 113.43 * 256 / (100 * 1e6) = 4871 seconds I only want this to be done by the wallet internally, so externally every quark coin uses the same formula. In other words, I think it would be best to return difficulty (in comparison to current) multiplied by 256, so any equation used by 3rd party includes only the 2^24 multiplier, as already used by other Quark coins. |
|
|
|
|
Yeah the problem now is that standard formula for calculating is like:
br * 86400 / 2**32 * hr / diff
But Quark coins for some time were using this: (not sure why you got 200, instead of 256)
br * 86400 / 2**24 * hr / diff
Its not something only quark does, cause Cryptonight/Ethereum uses it like:
br * 86400 * hr / diff
I am fine with having different formulas per algo, but I would still go for consistency within the same algo.
|
|
|
|
Heya, Currently the difficulty is incorrectly reported, reduced by a factor of 256. I have proposed a PR with changes that should fix it, based on the same bugfix for MUE coin: https://github.com/Darknet-Crypto/Darknet/pull/1I am not sure, if those changes are all thats required, but in the PR I have linked to the original commit. Please look into it |
|
|
|
Ah... My bad. I misunderstood it.
What miner and catalyst version did you use to get 12Mhash from 280x? I'm quite surprised that my 280x can perform upto 12Mh.
Yeah its pretty selective. As far as I know, it can only be done with 5.1.0 optimized sgminer. You can get both miner and bin from latest nicehash miner package. This miner does not seem to work with some cards (For example 380, maybe all gcn 1.2?). I am using 15.7.1 catalyst, the exact version should not matter much, as we are using a precompiled bin. Here is my short post from sgminer about it: https://bitcointalk.org/index.php?topic=632503.msg14323184#msg14323184 |
|
|
|
@miningpoolhub 1.Those results are with genoil miner. Currently there is no way to get better results on 750ti and windows. (Some users report 5Mhash on linux) 2. I cant see a reason for x15 - no worthwhile coins that I know of (almost the same for x13) Skein coins are added on the site, just not exposed on the main list. Can always be compared separately. 3. Sounds like you had a different (not default) value stored in a cookie for X11. Also possible you tried this when I have updated the multipliers Value for X11 is not supposed to change - the buttons are only for adapating the rates and powers from X11 values. 4. 12Mhash is a real value for a single 280x, so is 250W power that goes with it. For 750ti, as written in latest post, those values are: 3,25Mhash / 75W |
|
|
|
|
I have finally managed to run my 280x at 12Mhash with the 5.1.0 optimized from nicehash. (1100/1600)
5.1.1 optimized only at 7,3Mhash and 5.3.0 at 6,2Mhash. Funny how the performance drops...
My problem was that I had Tongas on the same rig and they are not compatible with 5.1.0 miner.
Used --remove-disabled switch, so they dont get initialized.
|
|
|
|
|
Updated all adapt multipliers for 280x.
Default values now start with 12Mhash and 250W of X11.
For 750ti adapt, you can input those X11 values:
3,25Mhash
75W
|
|
|
|
The data was too hardcoded imo, causing confusion as well. There is no such logic at the moment, but nothing stops you from doing 2 more json calls to both DGB and MYR skein. I think its better, cause you can input your real hashrate for that algo this way. However I can see that there is no btc_revenue key returned for index, let me add that, so you can calculate profitability yourself for Skein. (Done) Unfortunately the data is not quite the same either. On the main page, there's "profitability" and "profitability24". This has been replaced by "profit" on the pages for individual coins, which equates to the 24 hour average. Since it's switching based on current difficulty that I'm looking to do, a 24 hour average is of no use to me. Profitability is just `coin_revenue / dash_revenue`, same for profitability24: `coin_revenue24 / dash_revenue24`. So all you have to do is call for example: http://www.whattomine.com/coins/114.json and save value of `difficulty`. Then calculate revenue with that difficulty: http://www.whattomine.com/coins/114.json?d=difficulty&hr=hash_rate and save `btc_revenue` as `dgb_skein_revenue`. (remember to push hash_rate in correct units, Mhash in this case) Now either repeat it for dashcoin: http://www.whattomine.com/coins/34.json, or get it directly from gpu json http://www.whattomine.com/coins.json under dash and `btc_revenue` saving as `dash_revenue`. To receive final profitability to compare with other coins: `dgb_skein_profitability = (dgb_skein_revenue / dash_revenue) * 100%` |
|
|
|
|
Dropped Scrypt coins from GPU section, which now compares all coins to Dashcoin.
Added Ethereum to main list with nicehash.
750ti values for ethereum are really small on windows7 - around 0,5 Mhash.
There are reports of people running 5Mhash per 750ti on linux, but I havent confirmed that.
|
|
|
|
The data was too hardcoded imo, causing confusion as well. There is no such logic at the moment, but nothing stops you from doing 2 more json calls to both DGB and MYR skein. I think its better, cause you can input your real hashrate for that algo this way. However I can see that there is no btc_revenue key returned for index, let me add that, so you can calculate profitability yourself for Skein. (Done) |
|
|
|
Why? With 2mhash in windows you will earn less than $0.5 per 750ti. Decred with sp-mod private does $1.33 and use only 38 watt..
Because on my site I need to add multipliers for 750ti as well If people want to mine with 2Mhash, then I see no point telling them that this cant be done and force a `0` multiplier. Ok will research past miners myself. |
|
|
|
|
Show Posts
