Search results

One potential solution I think might be interesting would be use zerocoin-style zero knowledge proofs for passing outputs to a masternode. A sender could give his input transaction and another piece of data to the masternode, then after the inputs are collected, the masternode can calculate an...

I think you need to step back and consider what the average person using it really wants to know when they open it. The 2 most important things are balance, and recent transactions. Most users don't care about difficulty. They don't care about net hashrate. They don't care about the block...

Of course. It would be a fairly safe one though, as it would be a trivial change.

I was just thinking about the current situation with pools not updating, and was wondering, why not cap the amount a miner can earn on a block to 80% of the total reward ( the amount they would get if they paid a masternode ), regardless of whether they actually do pay a masternode. This would...

There is no way to know the amount of hashing done by each entity in the network, so this is impossible.

I like this. Random enable and disable totaling 8 hours of enforcement per day would cause the bad pools to earn less, as 30% of their blocks would be rejected, more than offsetting the gain they get on the ones that do.

Sorry I wasn't clear. I meant your card must support cuda 3 to use ccminer 1.2, or cuda 2 to use ccminer 1.0. Basically I don't think you can use ccminer with that card.

geforce 210 only supports cuda 1.2. I think you need cuda 3 for 1.2, or cuda 2 for 1.0.

I'm taking a shot in the dark here, but success in mintpal is a string, and success in cryptsy is an int, and QJsonObject operator[] returns a QJsonValue, so a direct comparison or using of QJsonValue against/with an int might not work how you expect it without extracting it from the QJsonValue...

Although I don't know why it won't start for you, I've always found temperature monitoring to be broken when using rdp, so vnc ends up being a better choice.

Your main barrier is going to be that you'll need javascript implementations of the following hash functions: blake512 bmw512 groestl512 skein512 jh512 keccak512 luffa512 cubehash512 shavite512 simd512 echo512 This project https://github.com/drostie/sha3-js will help you quickly get halfway...

1. You can try to use it for other tasks, but it likely won't be pleasant. Frame rates can be significantly reduced, often resulting in things skipping instead of being smooth. Doing actions which place high load on the machine can sometimes be enough to crash it when combined with mining also...

The chart you linked is for mining scrypt. Drk uses x11. On most algorithms the radeons are much faster than nvidia cards, however I'm not sure what the current situation for x11 is. If you plan on mining non-x11 coins also, the radeons will likely be more useful.

In the updated guide, it says to make sure masternode=0 on local client, but then it shows masternode=1 in the sample file at the end. Which is correct, or when do you change it? Also, what exactly is masternodeprivkey? Putting anything called privatekey on the remote server seems like a bad...

Paying all masternodes every block is certainly doable without too much bloat, however it would be difficult to integrate into the bitcoin-based source. If changes in masternode list state were included in blocks( ex: block 1 -> mn 1 and 2 up; block 2 -> nothing; block 3 -> mn 3 up, 2 down)...

I could be misunderstanding something, but it seems to me that it's very different than hashpower. Hashpower can be verified by walking through the blockchain from the beginning, regardless of what point in time the verification is done. For checking on whether a masternode is accessible and...

The main intention of using fail2ban is to prevent brute-force attacks by temp-banning ips that repeatedly fail to login. Using it just like that provides a major benefit and won't lock you out(at least for more than a time limit you set.) Restricting it to 1 ip only is just an extra if you are...

The darkcoin code directly uses sphlib ( http://www.saphir2.com/sphlib/ (page isn't loading at the time of writing this, but it was working for me not too long ago, so probably just temp downtime)) for its hashes, so the documentation can likely clear up those issues. There actually is a warning...

I'm still not quite following how this is tamper-proof. If the client is allowed to decide whether it agrees or not and how to vote, then why wouldn't miners use modified clients that never vote when they mine a block? It may not directly affect their earnings for that block they mined, but...

I worked off the the darkcoin block verification code rather than that miner, as I figured a straightforward implementation would be easier to look at than a highly optimized one. The data being hashed is the block header(80 bytes total). It is in the following format: (4 bytes little endian)...