Search results

IX working again, but I see this discrepancy on one side (sender) receiver: Status: 5/confirmed (verified via instantx)Date: 2/2/2015 15:51From: unknownTo: y9M7fNprirFG97WxcrYSqSVU2Zfa7cdp5g (own address, label: test1)Credit: 200.00 tDRKNet amount: +200.00 tDRKTransaction ID...

Wonder if that's by design or not.. Or just a bug.

Now the real question is... Can this withstand double spends.. What happens when someone would try to spend the same coins to a different address? Does it poll the masternodes to see if the funds were sent previously? How does it stand up to attacks?

hmm evan82 as your username? Are you Evan? Lol

working better and better! It feels like taking candy from a baby!

another one moli... From MN: 2015-02-02 02:33:21 InstantX::ProcessConsensusVote - Transaction Lock Is Complete a76da3b35fccedaa9128205a4cc30c2221b187f4c6b146fc64445ffdd3f545a0 ! from wallet: Status: 5/confirmed (verified via instantx), broadcast through 2 node(s)Date: 2/1/2015 21:33To: moli...

that was me! Status: 5/confirmed (verified via instantx), broadcast through 2 node(s)Date: 2/1/2015 21:25To: moli y8ef7uPVXRkQghB4uC5KZZnjxcxk3VVN79Debit: -5.10 tDRKTransaction fee: -0.009 tDRKNet amount: -5.109 tDRKTransaction ID...

we may not have enough MNs on latest version and may not have enough hashing power...

seeing this in debug... 15-02-02 02:16:42 InstantX::ProcessConsensusVote - Incomplete TX Lock 7 794876dcf4f9a469001a44f7aa072d1c9e3aa81e79e1825fd7335e1915d80bb8 2015-02-02 02:16:42 InstantX::ProcessConsensusVote - Incomplete TX Lock 7...

just started up a tMN also...will play around with some wallets txs as well.

Just rec MN payment of ~1drk... Of course I get spanked lol... Some miner with bad block reward. Mns showing on DRK.MN now

Im on 207370 on 5 clients...error is gone from MNs now. Didn't do anything to make that happen.

I'll reindex on 11.0.7 now...reindexed on 6 and it was stuck on block 703

anyone stuck on 703 now?

I believe this has to do with the reference node people speak of..and I know Evan is aware and working on a solution to remove the reference node all together.

And now I have a node that hasn't been paid in ~2300 blocks after getting paid twice regularly. Something is clearly not right.

After having some issues with masternode payments, my 2 nodes have gotten paid 2 times each in past 2 days. The updates probably helped this and knocked off those who weren't updated.

and this guy gets 2 payments in 1 day... http://explorer.darkcoin.fr/address/Xx5mSahUdvVduSej2E4cAY4h1FN5iCF4H7

The same thing happened to me, I sent you an email about it. was hit with Large Payment split up fee 2x and collateral..not even using DS at all...

Now back to instantX testing with a better network..who's ready?