Quote from: dave_bbp on March 04, 2019, 04:42:18 PM

Quote from: bible_pay on March 03, 2019, 09:45:57 PM

Quote from: dave_bbp on March 03, 2019, 08:43:25 PM

Quote from: bible_pay on March 03, 2019, 08:32:59 PM

Please try forcing a podcupdate 'exec podcupdate true' then check your rac.
This is existing behavior - this is that if you miss a podcupdate (yours looks missing for 24 hrs) it queries 0 rac from wcg until you send a new podcupdate.

Yes I know, but the last output I posted is actually the answer for the forced PODC update (tried that several times):

Code:

21:42:21

exec podcupdate true

21:42:21

{
"Command": "podcupdate",
"PODCUpdate": "Processed (1) over 0 CPID(s) successfully."
}

Please try 'exec associate user pass true' then wait til the 5 confirms hits, then try again, and please, let us know that its fixed.

I finally managed to do the reassociation (after my wallet completely crashing and messing up the blockchain data on a former attempt). I didn't have time to wait for the confirmation, but when I came back home I now I saw that my wallet had sent a PODCupdate and everything seems to be back in order right now.

Quote from: bible_pay on March 03, 2019, 09:45:57 PM

For the naysayers, Yes, I want to try this. This is because cpids' over 6 months old expire in the chain. We need non-expired DCC associations in the chain with valid wallet sigs.

This is just a coincidence of the timing, but the new wallet requires all of the elements to be present (IE I dont think its a bug).

I honestly have no idea what you even mean by that ...

Thanks, that comment was not meant for you- it was because people seemed to be questioning my suggestion to 'exec associate' again on the existing cpid.

What I wanted to explain yesterday was that the original DCC association record with the original CPID signature expired after 6 months, and anyone who received "invalid destination" should re-associate the CPID with the latest wallet. (No, the CPID itself does not expire).