|
THERE IS ALREADY A QBT THAT HAS BEEN IN EXISTENCE FOR QUITE A WHILE AND DOESN'T COMPLETELY SUCK.
RENAME YOUR SHITCOIN.
|
|
|
|
The_Catman is working on it  The_Catman has no idea wtf he's doing. Way to "fix" the coin... Time to find a real dev to take this coin over!!You are a jackass. You have probably never done software development, and have no idea what is involved in a fix like this. He said he's working on it and know what the problem is. Give him time to fix it and STFU.  Yea, we'll see how that turns out... Funny how everything was working perfectly fine before he jacked it all up...now we have multiple forks, wallets that wont sync, etc, etc, etc. You trolls are fun, you get so fucking butthurt about everything. |
|
|
|
We need a new dev to take over CENT. What say you??The_Catman has royally jacked up the coin and does not know how to proceed. There are already multiple forks, wallets not syncing, etc. Are these the responses of a confident developer? I'm not sure why people are getting stuck at 50623, my chain's currently at 242690 and reports that there are currently 243036 blocks in the chain.
I will look into this further.
Alright, I need sleep, I'll continue trying to fix the problem tomorrow.
In the meantime, if anyone happens to be an expert on the proof of stake system, please take a look and see if you have any ideas. There's got to be a stake validation check somewhere I'm missing somewhere. The problem is that the new stake value is being used to check the old stake transactions and it obviously failing. On re-examination the method we used to change it was pretty obviously not going to work, but the other methods I've tried (using block nTime and nHeight, in various ways) don't seem to be working either.
To everyone having Pennies issues after Jan. 8th: Debug instructions
1. Open "Command Line Banking" and type 'getinfo'
- Make sure protocolversion is 7000 (version 0.10.0.0-beta)
- If not, go update to v0.10.0.0
2. Open "Command Line Banking" and type 'checkwallet'
- Make sure it responds {"wallet check passed" : true}
- If not, run 'repairwallet' and wait.
3. If your blockchain is stuck/not syncing
- Check your pennies.conf and wipe any nodes you aren't sure about
- Add 'node.cryptsy.com' Woops, seems cryptsy may have missed the update, hold off on that*
- Save and restart wallet
4. If it's still stuck
- Shut down wallet
- Go into your pennies appdata (%APPDATA%\Pennies)
- Delete all files other than 'pennies.conf' and 'wallet.dat'
- Relaunch wallet
- Wait for it to resync the chain from scratch
If none of this works, just wait a few days for the network to sort itself out, then open an issue on the github.
Alright, from what i'm seeing there's one of 3 problems going on at the moment.
1. Cryptsy is outdated and everyone who is reporting successful transactions is too.
2. There's a fork.
3. Uhhh, I forgot what this one was.
|
|
|
|
The_Catman is working on it The_Catman has no idea wtf he's doing. Way to "fix" the coin... Time to find a real dev to take this coin over!! |
|
|
|
Thanks jedi, I've been waiting for my account over there to be approved for several days now. That's what was making me wonder if he was still away.
I'll take care of it right now for you! |
|
|
|
Hey do you know what would be funny, chicken little's?
If Catman abandoned your Pennies,then chances are you would never get your money back.
So yes, keep on attacking him.
 |
|
|
|
So what are the PoS settings for RAD?
|
|
|
|
|
Epic fail.
I miss shake...
|
|
|
|
lol
i told you what to do a long time ago, people should just revert to the old client and wait a few days while you implement my idea
|
|
|
|
Do you think that's something happen to cryptsy with cent? Like sowen69 say, my account balance display cent value in btc not in xpm, so with 1billion cent, i have an estimated balance at 10btc Wtf? No, that's always been the case as far as I know. It just doesn't know which market to use to calculate the estimated balance so it's calculating off the cent/ltc market rather than the cent/xpm market. They just need to shut the LTC market down already....maybe it's time for a CENT/DOGE market. |
|
|
|
strunberg Try to send some CENTs from inputs older 8 Jan. to Cryptsy. I think you will see the problem.
Calm down  |
|
|
|
Why are people having issues? I'm doing fine, people need to calm down.
Why? Because the dev doesn't know how to properly update and release a coin. Just because you're doing fine doesn't mean others are and anyone who has missing coin has a right to be upset. |
|
|
|
|
This coin is FORKED up!!!
|
|
|
|
I'm not sure why people are getting stuck at 50623, my chain's currently at 242690 and reports that there are currently 243036 blocks in the chain.
I will look into this further.
Because you jacked this coin up to hell and back, that's why. If the you're on a different chain than the MAIN FUCKING EXCHANGE (Cryptsy) then the coin is and will continue to be worthless. Good thing a fucking amateur took over the coin... |
|
|
|
|
So what are the PoS settings for RAD?
|
|
|
|
Price isn't bad but with delivery in April after difficulty has more than doubled....  |
|
|
|
|
Are we ever going to get Drillbit support?
|
|
|
|
If none of this works, just wait a few days for the network to sort itself out, then open an issue on the github.
Hey guys, just restart your computer and everything will work... Great answer. |
|
|
|
|
Can someone post an rPi image with minepeon for this?
Will reward .01 if it works.
|
|
|
|
|
THERE IS AN ISSUE WITH THIS COIN THAT IS APPARENTLY BEING IGNORED.
I AM RUNNING THE MOST RECENT CLIENT, TRANSFERRED OUT OF CRYPTSY AND HAVE RECEIVED NOTHING. YES, THE TRANSACTIONS ARE CONFIRMED WITH TX ID'S. MY WALLET IS 100% SYNC'D.
TIME TO GIVE THE COIN TO A REAL DEV.
|
|
|
|
|
Show Posts
