Search results

Anyone aware of the current average payout per node? Figures had hit rock-bottom when service was suspended.

I am not entirely sure about the best time to spread the promised news. We´ve had frustrating weeks of slipping downwards, now big hit in the face for the entire market. -> Lots of people busy licking their wounds, maybe not giving a damn. On the other hand, overall network health needs to be...

For my wallets eventually smooth sailing with build .31 - good show Evan (Almighty)!

Hmm. Apparently 10.12.30 still very rough around the edges. Happily eating 0.0125 fees for a wallet holding only approx 4 DRK. Two Darksend rounds configured, but not reaching them.

That one looks a little bit better - but wallet still got locked later in the process: Recap (chronological): Password prompt for first "Payment to yourself" transaction No password prompt for first "Darksend denominate" transaction Password prompt for second "Darksend denominate"...

Issued, locking again right away. I´d say denom work is *not* done, but wallet thinks differently: 2014-08-11 17:39:46 Darksend is complete, locking wallet. 2014-08-11 17:46:56 Darksend is complete, locking wallet. 2014-08-11 18:43:07 Darksend is complete, locking wallet. 2014-08-11 18:54:00...

Encrypted wallet v0.10.12.20 (on Ubuntu 14.04.1) locking itself again and again. Making auto-denom a very bumpy ride. Did not see this during the last few builds... Only for me? Update Fresh transaction - and again wallet immediately locking itself:

ca95419622826915648d31fb367364a8f8e8f717a8666fbf665b5542a0637d6a Duplicate. Sorry, didn´t notice someone else did.

Approx. 1.5h since first round finished - had three password prompts but no visible progress:

Come on people, leave vertoe a few % - there´s kids to feed :grin:

No, first round started automatically. A new password prompt appeared moments ago, although it did not lead to a new (visible) transaction. Will give it a few more minutes. If this is ecpected behavior, I can only say it´s not too comfortable to sit there and babysit the client for potential...

Most likely it´s me, but: If I remember correctly, default rounds would be 2. Correct? So in my case I´d expect another run, which does not take place. Debug log insists on "DoAutomaticDenominating : No funds detected in need of denominating".

New (encrypted) wallet & freshly synced x.12.14 client: 1000 tDRK initial balance, Denominating processed one time. Had repeated password prompts (1x "Payment to yoursel"f, 1x "Darksend denominate"). Debug log now states: "DoAutomaticDenominating : No funds detected in need of denominating"...

Didn´t you post your wallet some time ago? Maybe someone grabbed it.

Status: 0/unconfirmed, broadcast through 6 nodes Date: 03.08.14 22:30 To: mi6a57MW3G9RDMVrsZv5oPmiJzNcsho94P Debit: -1234.5678 DRK Net amount: -1234.5678 DRK Transaction ID: 6688d7abb613b27d0c21eb94f89e968a65e013629274765b4f65fe6cae186d10 And /me is mgfUCFmjMxZJAzE6zck5to5YE9xUEtUxpy

Yeah. Makes the whole thing feel fishy. Really hope this was done by mistake and the fees will not stay hidden this way.

I´ll second that. Mixing my approx. 5000 tDRK wallet has eaten quite a bit of fees (ignoring the portion caused by the collateral bug). It´s peanuts but it does not feel quite right - especially because it´s happening automated and without user intervention or upfront notice.

3333.3333 sent to msyfd8gBFQuNoKf2deUvTEGpQeDZzXz5uR 8871f6a19f81c1914c5c951c7786e955cb16658fe358e7c857f11739a15d90d9

Testnet blockchain had to be restarted, flare´s hint should sort things out...