People get paid for doing this sort of thing?
Considering getting rid of the last of my miners, so some sort of
BTC income would be nice. You (anyone) can use any of my existing images for free. A mention and/or tip where they would be used would be appreciated, of course.
P.S: Someone noticed something odd with the new (hours old) Paycoin Wallet already.
https://paycointalk.org/topic/580/multiple-superfluous-addresses-in-wallet-whyNot sure what this means. Crestington? Any idea what is going on with this multiple address issue? Did someone accidentally include part of the shuffle mixing script that auto generates new addresses into the coin code? LOL.
Edit to add: The "XPY Testnet Overlord" is not even remotely concerned.
Some fucking "testnet overlord". If I were "XPY Testnet Overlord",and there was something unusual in a newly implemented code that I could not explain, I would be concerned about this being a bug or similar. Maybe this is an issue, maybe not, but the offhand flippant manner in which this idiot brushes this aside (while claiming to be "XPY Testnet Overlord" no less
) is emblematic of the whole drunken clown circus that is Team Paycoin or whatever the fuck these con men are calling themselves today.
Well seeing as they haven't changed addresses to return change into the same address, you would have many extra addresses from dust.
What is more concerning is their maxclockdrift still set at 2 hours when the minimum time to Stake is 1 hour.
static const int64 nMaxClockDrift = 2 * 60 * 60;
static const int STAKE_MIN_AGE = 60 * 60;
I suppose you could modify the client in order to use what is termed as litestake which uses std::map that tracks the block height and the last time the wallet hashed on this height. The big issue here is that you could modify it to hash into the future by a couple hours and would give you a clear advantage, drop difficulty and produce more Blocks per day.
http://bitcoinist.net/interview-presstab-pos-vulnerabilities/ This means that before the code tweak, we would create 60 hashes at a time, but after my code tweak we could all create 900 hashes at a time. This radically increased our chances of staking by 1400%. If we were to use my code on Peercoin, we would enhance our chance of staking by 11900%.
Or a Peercoin clone....
I mentioned this vulnerability some months back but couldn't be assed creating the client to do it.
Here is the LiteStake code addition to try if anyone is game enough to create the modified client and has some XPY.
https://github.com/Crestington/PayCon/commit/6d6f887b4b249d0ca972a6d402c75df8772f2e5e