What is MaxTarget in the block reward calculation?
MaxTarget is the maximum possible target. It's 0x00000ffff0000000000000000000000000000000000000000000000000000000 for proof-of-work. P.S. If you want to get current block reward or current target, you can use getblocktemplate RPC call for this. coinbasevalue?
|
|
|
out of curiosity how would being on the multipool that picks the currency help unless you're selling your coins when you mine them? This would also be difficulty with it being PPNS right? What am I missing?
Coin profitability fluctuations are mostly due to difficulty changes. Price fluctuation plays a small part. Unless a coin crashes in value you should be able to sell it for close to what it was when we were mining it. Most of our coins pay out after 20 confirms or less. I'm planning to implement an "actual profitability" for last 24h but there are some challenges involved.
|
|
|
I should mention that the logo artwork was donated by user esquinato. I'm not sure if he's active on these boards or not.
|
|
|
What is MaxTarget in the block reward calculation?
|
|
|
Need info on the following before I can implement NVC: https://github.com/CryptoManiac/novacoin/wiki/FAQProof-of-Work block reward can be calculated using formula nBlockReward = 100 / (nMaxTarget / nCurrentTarget) ^ (1/6). It means, that reward cut a half every 64x multiply of difficulty. So, the question is, what is MaxTarget? Anyone know?
|
|
|
Hey guys...here´s my next question coming up my mind: Why is speed jumping around that showed way? My miner is mining at a very constant speed and says 1.800MH/s which is about where I marked the red line. So have I something missconfigured (as said above I´m using a mining proxy) or is that just normal? It's probably normal. The reason it's jumping around is because I've set the pools to use 2 minute averages rather than 10 minute averages.. The pool doesn't count invalid shares in your hashrate so it will show up a bit less than your miner reports.
|
|
|
Is there a way to see the daily average profitability of TRC on the site? I'm just curious because I expect some ASIC goodness in the near future, and trying to look at what SHA-256 coins to mine.
Good question.. I will try to whip something up. I'm also waiting for something in the mail Here are the potential logos:
|
|
|
Looks great, playing around with an android app to display the data. Do you have a logo? I have three, actually. I need to pick one soon and put it on the site. Didn't get as much done as I wanted to this weekend. Also another user requested some API changes which should hopefully make a little more sense.. Check out api2.php.
|
|
|
I wasn't comparing them; Aquaman is talking about these like they're just silver coins with the Litecoin logo stamped on them, he doesn't appear to understand that they're preloaded with LTC.
It wasnt said they were going to be, if they are, then yes, itll be worth more, otherwise yes its just a silver coin with a logo stamped on it. In that case they wouldn't be Physical LTC at all. They'd just be silver coins.
|
|
|
Just to add on my own experience in case it helps with debugging, I'm not experiencing this problem. I'm at 31818 Accepts and 962 Rejects right now total, and ever since it jumped to LTC my Accepts have been going up while Rejects have stayed pretty low (most of my Rejects were from the fast-block coins).
This was on FTC... just now... The Diff changed mid-stream due to the number of workers online now. diff 32 hurts when it drop due to new block found, and rejects up to 6x shares that were "waiting" for delivery, just before the block was found. Not so bad on slow coins like FTC, but on fast coins, it cuts you short by almost 50% of shares. Alleviated by reducing my work-load size to 64 also... thus, it finishes up to 4x faster and then submits... instead of waiting for workload 256 to finish, before submitting on every card. Problem resolved... Use CGminer 3.2.1 (I was only using 3.2.0 for issues related before all the wallets updated when I was solo-mining on this machine.) Is it recommended to use WL of 64 for all coins (er, the multipool) then? that's more of a card setting than a coin setting, afaik. Well, I mean for LTC there are almost no stales. When it comes to the quick-block coins, though, after each block is found I have anywhere from 3 to 10 stales, which sometimes adds up quick. I'm wondering if the work load will decrease this (I don't quite get what the work load does). I think it just controls the size of the packets that get sent to the GPU.
|
|
|
Litecoin is MySpace to Bitcoin Facebook. Litecoin is Yahoo Auctions to Bitcoin EBay Litecoin is Betamax to Bitcoin VHS
Myspace was first, facebook improved on the idea. so this would support LTC being the best. betamax lost cuz the pron industry picked vhs. honestly if the pron industry picks LTC then BTC will be pretty fucked. People still pay for porn? Nevermind, I forgot about the bible belt.
|
|
|
Kicking you 1% donation now. Any idea when you will turn back on API? I am pretty handy with android appbuilder and could make a lil android app pretty quick like for mobile stats.
Hoping to have it enabled either tonight or tomorrow.
|
|
|
Last connection was at 19:00 (7PM)... Lost three hours... Arg... Should have had a fallback pool setup.
Still down I see... Trying again using the load-balance option, so I can see when you go online.
Sorry for the downtime.. Always have a backup! Even I have give-me-ltc.com configured as a backup lol...
|
|
|
Just to add on my own experience in case it helps with debugging, I'm not experiencing this problem. I'm at 31818 Accepts and 962 Rejects right now total, and ever since it jumped to LTC my Accepts have been going up while Rejects have stayed pretty low (most of my Rejects were from the fast-block coins).
This was on FTC... just now... The Diff changed mid-stream due to the number of workers online now. diff 32 hurts when it drop due to new block found, and rejects up to 6x shares that were "waiting" for delivery, just before the block was found. Not so bad on slow coins like FTC, but on fast coins, it cuts you short by almost 50% of shares. Alleviated by reducing my work-load size to 64 also... thus, it finishes up to 4x faster and then submits... instead of waiting for workload 256 to finish, before submitting on every card. Problem resolved... Use CGminer 3.2.1 (I was only using 3.2.0 for issues related before all the wallets updated when I was solo-mining on this machine.) Is it recommended to use WL of 64 for all coins (er, the multipool) then? that's more of a card setting than a coin setting, afaik.
|
|
|
Yeah, I can't connect to port 7777 either.
Not sure what was going on there, mincoin pool software was hung for some reason.. Things should be better now.
|
|
|
Yeah, I am mining FTC directly.
It is possible, that his shares are worth more because of higher difficulty. His hash rate is jumping from 6 to 18mhash. He didnt find any blocks... Hopefully that is just due bad luck.
Correct, Terracoin is the only coin that has its share count adjusted for difficulty at the moment. I will fix this soon.
|
|
|
I've had to institute a minimum of 1 coin to cash out (all currencies).
We are getting killed by LTC transaction fees (down 30 LTC as of this post).
I really think you need to add a mining fee to at least cover your expenses (server, transactions, other?). It's more long-term stable, and would allow you to add many more coins without it being about server costs. I'm sure not everyone would be happy about it getting added, but I think adding 10 new coins (even if enabled for multi-port only) would more than make up for them. I have some thoughts regarding this. Will be releasing some info shortly.
|
|
|
I've had to institute a minimum of 1 coin to cash out (all currencies).
We are getting killed by LTC transaction fees (down 30 LTC as of this post).
I switched my auto cashout to manual (I just like to see them pile up on my account anyway). Where do you get your FTC numbers, though? I know you have to take into account stales and several exchange rates, but I don't know where the 1.51 comes from. It looks like FTC difficulty just went up, the pool may be switching soon. Edit: actually, not sure this is the case, my client is still reporting 94. Coinchoose says 133, but coinwarz and dustcoin agree with me. It's possible that 133 is the difficulty for current block in which case the multipool should switch to mnc after the next FTC block.
|
|
|
|