Search results

Dedicated tMN and tLP updated to v0.12.1.0-0ecc7c6. Synced nmarley sentinel and reindexed both nodes. Should have a little time to test more tomorrow. Quite a few fixes in the pipeline I see. Are we still on schedule for mainnet launch?

I'm going to leave my tMN and tLP on v0.12.1.0-e2eaf1d for now. They're staying synced and seem to be functioning pretty well. I will probably update them in a few hours or so. Maybe by then a few more of those pull requests will be committed to the testing branch. :)

I understand the desire to be able to enforce the receiving of mixed coins, but I don't agree this is a significant issue. One doesn't have to hope they can pass them on to others, they can either choose to mix them at that time or return them. A lot of your commentary as of late seems alarmist...

My tLP running v0.12.1.0-f81ea67 got stuck on block 138287. Updated it to v0.12.1.0-4b7bd6b and created a fresh working directory. Will provide additional debugging data if it gets stuck again.

Dedicated tMN and tLP updated to v0.12.1.0-7e9ad0e and synced nmarley sentinel. Looking pretty healthy so far. Will have more time to test tomorrow. :)

Dedicated tMN and tLP updated to v0.12.1.0-cda28d3. It is interesting to note that a few hours ago (with the previous build) the tLP was able to do 3 PS denominations within the same minute, which didn't seem likely to occur given recent testing and the fact that LPs don't use multi-session. :)

I've been watching the liquidity provider a bit closer now. The latest mixing transaction was 10 confirmations ago, yet I still see the message "Last successful PrivateSend action was too recent."

I don't understand how qwizzie mixed that much, yet my liquidity provider apparently only managed to help with a single transaction (running with -liquidityprovider=1). All my test nodes appear to be staying synced properly, but maybe some tMNs aren't?

I retweeted, but I'm not on slack. Appreciate the tips! Hopefully I'm not the only person interested in reviewing/testing some code today. :)

Dedicated tMN updated to v0.12.1.0-c438e74 and synced nmarley sentinel. Did a few mixing tests with speedy results. Now running a liquidity provider which also appears to be functioning properly. Is there any specific area that core devs feel we should be focusing on testing right now?

Dedicated tMN updated to v0.12.1.0-8fc8e6c and synced nmarley sentinel. Looking pretty healthy so far. Should have time to do some proper testing tomorrow. Hopefully most of the tMNs will be running the latest code by then. :)

Dedicated tMN updated to v0.12.1.0-1b90d66. Unfortunately, I don't have much free time this week. Should be able to do some testing on Sunday though. Happy Thanksgiving! I'm thankful to be a part of this increasingly strong project and team! :)

Is there a reason we haven't done the protocol bump yet? I think it's very important that we make sure mixing works extremely well in v0.12.1.

I saw the posts about that, but it apparently wasn't done building yet (always test using the latest successful builds lately). Updated to v0.12.1.0-7a005a9 now. Will test more tomorrow.

Updated dedicated tMN to v0.12.1.0-5128085 and synced nmarley sentinel. Will have some time to do testing tomorrow. Hopefully the code is about ready for a real beating! :D

Dedicated tMN updated to v0.12.1.0-0199027 and synced nmarley sentinel. Don't have time to help more than that right now. Hopefully Wednesday. Good luck all! :)

I may be shooting myself in the foot a bit here, but I feel it's worth pointing out that everyone is always welcome on IRC (Freenode #dashpay). It's pretty quiet, but we all seem to get along quite well. Every once in a while our resident troll (dnaleor) tries to get us to feed him, but since he...

I've been using this tag almost exclusively for a very long time. IIRC, I looked into it back when Tao came up with the #DashDC tag. I suppose I should have said something back then, but I figured given how many of you follow me that I didn't need to. Oh well, no big deal. Glad this is being...

Updated my dedicated tMN to v0.12.1.0-1eb399c. Seeing lots of nodes attempting to mix with the old protocol version, but otherwise debug.log is looking pretty healthy. Can make ~2 hours to help test today, but it would be nice to get some direction from the core devs before doing so.

Dedicated tMN updated to v0.12.1.0-0d324ea. Seeing quite a bit of "last dsq too recent, must wait" messages in the debug.log. Is the problem with mixing really related to tMNs running old code? Seems we have a lot more tMNs than usual, so isn't it a pretty safe assumption that most of them are...