[ANN] RazorLove Cryptocurrency Services - DBL, CENT, & FOO/BAR Updates

[J.B.O]

my pennies wallet can't to sync. stuck on 240792 of 244680
how to fix it?

The_Catman is working on it

[daemonfox]

I was having ZERO issues in my wallet except for the stakes showing as zero until I closed and then relaunched, at which point every one of them populated a value... quirky little bug.

Anyhow, I know a lot of the issues reported stem from how many inputs are in the wallets so, given stake was adjusted, I went to consolidate into new 500M sized blocks by sending them to a second address generated in the same wallet. When I hit send, error and the client bombed out.

I am in the midst of a relaunch but it seems to be hung, so not looking good... I will report more when I see more, but for now... I seem to have broken mine.

I had some 30+ inputs of nearly 250M from stake splits and one last block of just under 500M that had not staked just yet... was my only non staked input so far, so I used coin control to only include the newest blocks. Do not know if that was part of the crash reason.

UPDATE: Relaunch failed with an error talking about addresses and transactions not matching what was in the wallet. Last time this happened I ran piggybank.exe -salvagewallet in a cmd prompt in the Pennies directory (I keep my QT files in the same appdata folder for ease of use) and all was fine after an hour or so. Will report back later on the results.

[lajz99]

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!!

[alivecrypto]

my pennies wallet can't to sync. stuck on 240792 of 244680
how to fix it?

Your Wallet is atleast stuck in 244K my wallet is stuck in 50K i am trying to delete everything and tried backing up also but nothing happened. I am waiting some information from members. Lets hope ho get.

[artiface]

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 knows what the problem is. Give him time to fix it and STFU.

The_Catman took over this coin because the original developer was going to just let it die.  If you don't like they way he's fixing it, it's open source you can fork it and fix it your self.

[lajz99]

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.

[PoolMinor]

  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.

It is funny what you consider working perfectly fine. Do you really need someone to blame? Blame this person  here for introducing the coin to Bitcointalk in the first place and then read a few posts later in this thread  Pennies launched about why Shake did not publish the coin here.

As far as it being fine before The_Catman took it over is complete bullshit, if you mean it was ready to die, then yes you are correct. I don't think anyone should have intervened, I gave this coin 3 weeks (time to live), on  December 22, 2013, looks like it has happened a few days earlier.

[Beoga]

May be the problem is occurred because a lot of inputs was unable to generate POS before 8 Jan. Because the size of their POS blocks would be more then 1 billion. But all of them was active to generate POS. But after 8 Jan the condition was changed and the POS block size of these inputs became satisfy the constraint of 1 billion.
Thus there was an explosive growth of POS, but the difficulty was not changed fast enough. So it was a reason of fork.
Sorry for my English, hope you can understand my idea.

[Jakal]

What does it mean?

http://imageshack.com/a/img202/1673/hw8o.jpg

I have a long cue of these 0 transactions...

It means you are getting stakes... lucky you!!

And why all are 0??

That's stake I believe. Click on the transactions.

I restarted the wallet and now I have some stake instead of 0, but savings is still the same amount...ideas?

[The_Catman]

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.

No, shake abandoned it because it was broken in the first place, I didn't manufacture the problem.

And btw, there aren't really any forks, the entire chain is stalled because all the blocks containing stake before the last attempted fix were invalidated due to an oversight.

It should be noted that what i'm attempting to do is something the PoS system was not designed for, it's like trying to change the design of a roller coaster while it's actively running. Course, if you want the inflation to continue I could just revert everything back to the way it was before and wait for the blockchain to become so bloated the client never boots again, ever.

[daemonfox]

I was having ZERO issues in my wallet except for the stakes showing as zero until I closed and then relaunched, at which point every one of them populated a value... quirky little bug.

Anyhow, I know a lot of the issues reported stem from how many inputs are in the wallets so, given stake was adjusted, I went to consolidate into new 500M sized blocks by sending them to a second address generated in the same wallet. When I hit send, error and the client bombed out.

I am in the midst of a relaunch but it seems to be hung, so not looking good... I will report more when I see more, but for now... I seem to have broken mine.

I had some 30+ inputs of nearly 250M from stake splits and one last block of just under 500M that had not staked just yet... was my only non staked input so far, so I used coin control to only include the newest blocks. Do not know if that was part of the crash reason.

UPDATE: Relaunch failed with an error talking about addresses and transactions not matching what was in the wallet. Last time this happened I ran piggybank.exe -salvagewallet in a cmd prompt in the Pennies directory (I keep my QT files in the same appdata folder for ease of use) and all was fine after an hour or so. Will report back later on the results.

UPDATE: All of my zeros are stakes now, and the wallet is functioning just fine. It looks like the 500M send would not go because that one block that had not staked yet, was in mid stake... it no longer existed when I got this open again and I had my 100M+ total stake added to my previous balance.

I would have to say, a lot of these issues we are seeing are due to a few factors, not only does the sheer amount of inputs seem to be a problem for now, the date of blocks that were trying to stake prior to the 8th but hadn't are likely making problems, plus, every peer in my getpeerinfo seeming to be on a different block height... its like people have wallets open with every input able to stake and trying to, but they aren't even up to the current block so their processor can't pick what the fuck is more important.

I am starting to wonder if people who can't sync set their wallets to NOT STAKE, if they would indeed start to sync properly, and then after, run the command to allow stake again.

Anyways, I am done rambling... my shit is in order, and thus far my only issue has been 2 crashes that required a salvage operation which both ended properly with my coins intact.

Current height 247822

[PoolMinor]

For shits and giggles I started a new wallet and this is the getpeerinfo:

Code:

17:58:44

getpeerinfo


17:58:44

[
{
"addr" : "72.199.125.208:1910",
"services" : "00000001",
"lastsend" : 1389405517,
"lastrecv" : 1389405517,
"conntime" : 1389399965,
"version" : 70000,
"subver" : "/Pennies:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 247782,
"banscore" : 0
},
{
"addr" : "84.94.165.212:1910",
"services" : "00000001",
"lastsend" : 1389405486,
"lastrecv" : 1389405452,
"conntime" : 1389400018,
"version" : 70000,
"subver" : "/Pennies:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 247784,
"banscore" : 0
},
{
"addr" : "115.28.15.70:1910",
"services" : "00000001",
"lastsend" : 1389405520,
"lastrecv" : 1389405519,
"conntime" : 1389400045,
"version" : 70000,
"subver" : "/Pennies:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 247784,
"banscore" : 0
},
{
"addr" : "75.141.91.56:1910",
"services" : "00000001",
"lastsend" : 1389405520,
"lastrecv" : 1389405520,
"conntime" : 1389400172,
"version" : 70000,
"subver" : "/Pennies:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 247785,
"banscore" : 0
},
{
"addr" : "114.145.117.253:1910",
"services" : "00000001",
"lastsend" : 1389404921,
"lastrecv" : 1389404384,
"conntime" : 1389400781,
"version" : 70000,
"subver" : "/Pennies:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 50623,
"banscore" : 0
},
{
"addr" : "27.33.253.164:1910",
"services" : "00000001",
"lastsend" : 1389405521,
"lastrecv" : 1389405521,
"conntime" : 1389401071,
"version" : 70000,
"subver" : "/Pennies:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 247802,
"banscore" : 0
},
{
"addr" : "81.104.23.219:1910",
"services" : "00000001",
"lastsend" : 1389405521,
"lastrecv" : 1389405521,
"conntime" : 1389401297,
"version" : 70000,
"subver" : "/Pennies:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 247806,
"banscore" : 0
},
{
"addr" : "86.13.4.140:1910",
"services" : "00000001",
"lastsend" : 1389405520,
"lastrecv" : 1389405520,
"conntime" : 1389402952,
"version" : 70000,
"subver" : "/Pennies:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 247824,
"banscore" : 0
}
]

A screenshot shows even without any possibility of stake interrupting the syncing of this wallet, it does not sync. I realize that the issue is not on the side of the wallet but the block chain instead.

Course, if you want the inflation to continue I could just revert everything back to the way it was before and wait for the blockchain to become so bloated the client never boots again, ever.

I vote we revert, and then nobody can bitch about whether or not there was damage caused by changes.

[bg6471]

For shits and giggles I started a new wallet and this is the getpeerinfo:


etc etc

What version of the wallet are you using? Looks strange.

The peers are using version 0.7.2?

[PoolMinor]

For shits and giggles I started a new wallet and this is the getpeerinfo:


etc etc

What version of the wallet are you using? Looks strange.

The peers are using version 0.7.2?

https://github.com/RazorLove/pennies/blob/master/src/clientversion.h

Edit:

Yes I am using lower settings for ability to mine while using computer. It is not necessary, but it keeps comp running smoother.

[The_Catman]

For shits and giggles I started a new wallet and this is the getpeerinfo:


etc etc

What version of the wallet are you using? Looks strange.

The peers are using version 0.7.2?

The clientversion file never got updated because it's only ever referenced in peer info and it was forgotten.

It looks strange because he's either running on win98 or earlier, or classic mode on winxp and newer.

[daemonfox]

For shits and giggles I started a new wallet and this is the getpeerinfo:


etc etc

What version of the wallet are you using? Looks strange.

The peers are using version 0.7.2?

The clientversion file never got updated because it's only ever referenced in peer info and it was forgotten.

It looks strange because he's either running on win98 or earlier, or classic mode on winxp and newer.

Actually his matches mine to the T... I run mine on a Win 7 Enterprise Edition and I use an RDP session to remote in, which likely causes the exact same low settings environment he has manually set so he can use the PC and mine.

[The_Catman]

Good news everyone! I think I have the fix!

I need to give it more time to sync, run some more tests, and clean up the code, but if all goes well it should be released tomorrow!

yay!

[Beoga]

Good news everyone! I think I have the fix!
I need to give it more time to sync, run some more tests, and clean up the code, but if all goes well it should be released tomorrow!
yay!

glad to see that

one more info - I have a few wallets on different computers. No problem if I send CENTS between. No matter is it from new stakes (after 0:00:00 8Jan) or old one.
But if send CENTs to Cryptsy only CENTs from old stakes are received.

[arnoo]

Good news everyone! I think I have the fix!

I need to give it more time to sync, run some more tests, and clean up the code, but if all goes well it should be released tomorrow!

yay!

nice to hear it. all hopes to you 

[kcanup]

Good news everyone! I think I have the fix!

I need to give it more time to sync, run some more tests, and clean up the code, but if all goes well it should be released tomorrow!

yay!

Yay!!  Cool