Search results

I started a fresh masternode, and right after i made the 1000drk vout, a message appeared in the log (before any confirmations): CActiveMasternode::ManageStatus() - Input must have least 15 confirmations - -2147468777 confirmations just a cosmetic log bug, but eh! Another one is when the...

I just fired up my p2pool server for the first time this year from the latest vertoe git version, and I noticed that the p2pool server drops the p2p connection to the daemon every time a new block is received. It reconnects immediately so it doesn't seem to be causing any problems with getting...

Thanks!

Wow, net hasrate is over 9M! I guess i could use some tdrk: xxgoRkF8ccm9jFgso4DjZ2QmbFpqNiWaMy

I left my masternode up since last night, so it seems to be banned on all nodes with the new chain. I get disconnected from all the addnodes listed in the new chain post, and I haven't been able to sync up for the past 15 minutes. ----------------- Just had to give it a few more minutes...

My 11.1.13 MN crashed earlier with this message last in the log: Its on mingw64 and it was also mining with 1 thread at the time, I don't have a dump of it. : CreateNewLock - New Transaction Lock bdf545eb542d29a1457868ec0775cd325344488ad416d7090b4d853010f4e316 ! Masternode payment to...

DrkMNPortChecker appears to have a gigantic time offset, is its clock set to the wrong century? Also I got a Qt build environment set up, and I tried some IX tests, but currently I'm getting a verification failure (4 of 20 signatures after starting without any increase in signatures until timeout.

I have been building only the CLI programs since I don't have a Qt build environment setup, so if you could double-check if it's possible i'd appreciate it.

Ah, I meant using the darkcoin-cli command line program, not darkcoin-qt.

I didn't see a way to perform an IX without using the GUI, and it's not listed in the commandline help. Did I overlook something?

I'm seeing some nodes connect with 59 minutes of time offset. This is due to the daylight savings time rules on un-updated windows versions.

I also get stuck in state 7 if "no matching denomiations" happens. to fix it, in the check "CDarkSendPool::CheckTimeout() -- Session timed out (30s).." I had to chage the UpdateState(POOL_STATUS_ERROR) line to if(fMasterNode) UpdateState(POOL_STATUS_ERROR) in order to get the timeout to kick...

Thanks for the explanation of how collateral works! Since you're wrapping it up, here's some trivial stuff: I noticed in processmessage() for "dsa", there's a version check: pfrom->nVersion != darkSendPool.MIN_PEER_PROTO_VERSION with a constant that is a bit confusingly named, maybe it should...

it seems like I'm still having a problem with the IsCompatibleWithSession check. When doing IsCollateralValid, most of the time txCollateral.vout.size is less than 1 so I get "not compatible with existing transactions!" a lot. <edit> it looks like in CreateCollateralTransaction, the fee is set...

I've been building these test releases in daemon mode, but I haven't had any luck getting my test masternode to work. I get clients connecting for iscollateralvalid() that list dozens of 0.4tdrk inputs which causes the CTransaction::CheckTransaction() : duplicate inputs error to appear. I made...

The download server seems much slower than usual lately.

Is anyone running 9.12.6 getting this in their logs: CDarkSendPool::GetCurrentMasterNodeConsessus : No consessus information for block 3905 CreateNewBlock - network could not reach consessus on payee for block 3905 every block, and bunches of these frequently: ProcessMessage(dmcv, 156 bytes)...

compile error with msys-mingw64 in main.cpp function GetMasternodeRank uint isn't a defined type, had to change to unsigned int

Seems like it would be best if mostly everyone solomined with just 1 cpu core, that way the hashrate would be spread evenly so every tester would have an equal chance of hitting a block. This would also allow usefully stacking many mining-daemons on multicore machines. Maybe blocktimes could...

Somebody should probably hack up a daemon to try intentionally breaking things on testnet, to make sure all types of misbehavior is detected for node banning. Also, the github source is still at v9.5.3