Quote from: darkproton on May 05, 2015, 03:39:57 PM

Quote from: burner640k on May 05, 2015, 03:32:21 PM

OK, so I took a break from looking at it but now am back again trying to figure out why I was not credited Blur for the Crave I burned using darkpoold (block 52061, hash 1a278074b96bc61f913c0df3afca88c5fd0771757e2f02b171adf9bc6553001d, address CDssAhibe5m4hx3yMyi5TuxrqrSDuJRwqk).

I noticed that someone else may have run into the exact same problem as me, though I do not see them posting here. Whoever burned 13.99994986 Crave from address BvEeWXL6qz3YXRmBQbbh25ri4uQudpD67H at block 53204 you did not get any Blur.

In looking at that I noticed that both that person and I did the same thing, we burned all the Crave we had at our address, no change. Every other burn that I see has change. So maybe the bug with darkpoold is that if the burn does not have change it does not get recognized?

That's possibly it. It does need to charge a fee. I would contact counterpartyd guys or their forum. Darkpoold is just a port from dogeparty which is from counterparty.

I did pay the fee, it was higher than most burns since I had quite a few inputs.

I have searched some through counterparties forum to find any hints about this problem not sure how useful posting there would be since their burn has been done for a long time. And their code is quite a bit different from darkpoold now from a quick look at it.

But as I mess with the python in darkpoold it does seem like it is not detecting the burn until it processes the second vout that sends the change back to the original address. It detects the proper destination address in the first vout but then it does not trigger a burn until after the second vout which is change going back to the sender.