Quote from: antonio8 on February 08, 2015, 08:21:51 pm

Maybe I am missing something but why are people creating MN with 200, 500 coins in the MN?

Isn't the idea this round to get the 1,440 MN up and running? Shouldn't we just be creating MN with 100 in each since we can't get kicked during testing?

Or maybe I am missing something.

We want to get more than 1440 masternodes running so we can test booting the weak ones.  As such, we want to have many with more than 100.  Nothing stupid high like 3000 but if everyone just has 100, it could cause some headache I think.

Thanks for that.

Wasn't aware the kicking was happening.

I am going to have to adjust some of my Nodes later. They are still being confirmed.

What would really be best to make sure we don't run out of coins is have people setup masternodes with:

100
100.000001
100.000002
100.000003
----
101.0004

Basically small numbers but in a manner where we can see who is getting booted next easily.

Bug. I've started a bunch of masternodes from spreadcoin.conf on vps, and then:
./spreadcoind getinfo
error: {"code":-1,"message":"map::at"}


I am currently mining to a single tSPR address, but using different computers.
I am also running a bunch of MNs from the same wallet. So they are listed on all my PCes.
So far it works great. Will this be eventually a problem?
(having the same nodes running on different computers)

Okay, I should be able to sustain 4.5Ghz - 4.625Ghz kept locking up while mining tSPR. I'll mine a bunch and then give them out, and make some MNs, of course.

Screenshot (modified spreadcoin-qt, NSFW): https://ottrbutt.com/miner/spreadcoinwalletminer.png

Also, is anyone else getting the wallet whacked by the OOM killer while mining using it?

EDIT: Scratch that, forgot to free some stuff in my SIMD code. Come to think of it, I should just put that on the stack...

Quote from: GilAlexander on February 08, 2015, 09:05:58 pm

Bug. I've started a bunch of masternodes from spreadcoin.conf on vps, and then:

Code: [Select]

./spreadcoind getinfo
error: {"code":-1,"message":"map::at"}


Same here.

'./spreadcoind mnlist' shows me all my masternodes but 'running: "false"'

'./spreadcoind mnmy' gives me an empty list, but maybe they need to be elected first?

Yes, there is no elected masternode yet, although we have >300 mns in the list.
If you start your wallet/deamon it might take a few minutes before the mnlist is uptodate

At what point should we be seeing elected masternodes?

Quote from: MyFarm on February 08, 2015, 10:30:35 pm

At what point should we be seeing elected masternodes?

Took about 3 to 3.5 hrs or so to get elected. last test. Hopefully its the same this time around.

The first masternode went live about 4 hours and 20 minutes ago by my calculation.