Sorry not yet. My priority was figuring why the hell the daemon still hasn't released our 1000DRK from RC2 Node 1 and then getting the other 3 nodes fully running and payments started before I worked on less pressing matters like spreadsheets. I thought I had a bit more time to figure out this problem as the orig. estimate was a 2-3 week delay.

As you can imagine: there's a bit of angst and concern about this 1000DRK since that was set up with the old hot wallet method and I sent that payment with an older v.09 client. I had enough concern that I just messaged Evan on the DRK forum about the problems I was seeing and how community responses I was receiving weren't helpful. (BTW, these problems are *just* with RC2 Node 1 set up with the old wallet client; the other community nodes were set up with the RC3 cold wallet method and the deposit to the associated getaddress 0 happily shows up as a self-payment of 0). It was suggested that the node could be on the wrong blockchain with RC2 software which could account for the problem I saw; that it could be because Node 1 was running RC2 and I didn't update it to RC3 when they halted the June 20 launch.

Hoping the software updates I apply tomorrow will sort all this out so I can start chipping away at the backlog.