Search results

There aren't many mistakes I haven't made! :smile:

Probably because they are v16 according to https://test.drk.mn/masternodes.html

Nope. MN: { "50.254.73.148:19999" : 1, "176.126.241.100:19999" : 1, "64.251.69.134:19999" : 1, "50.254.73.149:19999" : 1, "50.254.73.147:19999" : 1, "188.226.225.170:19999" : 1, "178.62.203.249:19999" : 1, "107.170.168.162:19999" : 1 } Local: { "50.254.73.148:19999" : 1...

Post your local and remote darkcoin.conf files, we might be able to help. The error you mention usually means you haven't opened 19999 on yout MN or there's a typo in a conf somewhere.

--instantxdepth=6 was what Evan used in his demonstration video. I don't think we can IX yet though, MN's don't seem to be networking too well. Seeing some IX type stuff on stdout though: ProcessMessageInstantX::txlreq signing strMessage...

Well, I've been using spew.py a bit more, my wallet.dat has grown to 35MB and the QT client hasn't seized up yet. :smile: Sadly all those tx's aren't appearing on the blockchain in any reasonable amount of time, despite me paying a 0.1DRK fee per tx. "networkhashps" : 15679409 - how many GPUs...

Hmm, don't think I've done anything wrong or different from usual. root@crouton6:~/.darkcoin# ./darkcoind masternode start successfully started masternode root@crouton6:~/.darkcoin# ./darkcoind masternode list { "64.251.69.134:19999" : 1, "50.254.73.146:19999" : 1, "50.254.73.147:19999"...

Can anyone else see MN 176.126.241.100? It thinks it's valid and it's on its own list, but my local QT isn't picking it up.

Should be another tMN online shortly, just waiting for it to sync.

Yeah I should probably make sure I run settxfee first before I do that again. edit: do fees apply to IX's? If so, who gets them?

Had to pop out for half an hour, most of them seem to have confirmed now on my end.

Yeah those spam-tx's I sent to yidakee are all still zero confirms on my end. I've broken testnet.

Nope yidakee just sent you another 1000DRK in 100 chunks. Apologies, will stop now! Oddly, can't see any of my txspam on the explorer, a few recent blocks should have hundreds of transactions. http://test.explorer.darkcoin.fr/chain/tDarkcoin

Actually it was 1DRK split into 50 random chunks. Will now send you 100 split into 27... When there are a few more MNs up I am going to see what it takes to cook them. Seeing lots of this on stdout: ProcessMessageInstantX::txlreq - Already Have Transaction Lock Request: 23.23.186.131:19999...

Testing my new spam-tx script yidakee, I am calling it 'spew' :cool: Is it showing as confirmed in your overviewpage? edit: how does one get confirmed balance via the CLI?

Incoming ... in 50 dribbles, just for fun.

Propulsion sent 1DRK from the QT started with --instantxdepth=6 to mtuET9MwFsL5jMWXwiN3Rdo1WyND7uG99q edit: recieved a bunch back, only 1 an an IX I think, QT still showing ? in no.of confirms...

QT and daemon compile just fine, DIY chaps... :grin: edit: mhdwmP5F7mpmkMY2xW46SVPxZVUFtW14yJ

The dead change issue seems easily fixable by denominating to 0.1 or preferably 0.01, putting some smarter logic in the wallet to select inputs as close to the send amount as possible, making coin control more obviously accessible, and calling the change a fee. Oh and UdjinM6's...

Looks fine from my local daemon and the one MN I checked on too. Do your VPS logs/stats show any outages? I'm wondering if your MN went down temporarily for some reason at the wrong time and missed its payment 'slot' ?