I have another theory, based purely on observation - and possibly a naive belief that people are good.
Used to run a number of masternodes, and a staking wallet. All on non-standard ports (ie. not 18888), and as time passed, "masternode list" would show fewer and fewer masternodes on the network, and consequently the same - this both on the masternodes and the staking node. Restarting would bring everyone back.
I never observed this behaviour on the masternode running on standard, 18888, and that one got many times more rewards than the other masternodes. Maybe it's as simple as the clients timing out, maybe they actively block masternode ip's.

I want to re-iterate that all this is speculation based on my own observations over time.


On another note, I'm very curious how these 2 masternodes can be "active":
    "192.168.2.208:16666" : 100778,
    "192.168.2.208:15555" : 86384,

Thanks. Using Autotools solved my compile issue, and I finally got your version running

First, thanks brakmic for your work. I am sure it will be advantagous to 8bit that we again have a working wallet outside of Linux.

Tried to get the new code to compile, but so far I have not been successful.


When I get to chainparams I get a bunch of those extended initializer errors.

OS: Ubuntu 16.04 Server

https://www.dropbox.com/s/3m38xdz0wo5uw11/8bit_1807816.zip?dl=0
https://mega.nz/#!miIjHQhR!WYGihFbLnq0aSWpMwomjaQX1nvKBp9SNE8eIK3Uibdk

As requested

Just so I'm sure I do it right, do we need just the blk0001.dat file, or do I need to include txleveldb folder as well?

Still running the "original" code, but chain should (hopefully) be the same

Based on my own experience, you should expect to stake every 4-5 days on average with 100 coins

Just updated wallet - compiled from source. Is the error left-over from testing, or should I roll back to 1.2.2?

The stop at block 858k, often happens at each 1,000 blocks due to miners moving in at blocks ,8xx and ,9xx and then move away when rewards are low for block finds. Since we get started after 858k again, we have been moving nicely along.

Also, Cryptopia wallet is offline due to maintenance, thus block height would be off.
Personally my wallet match up with Cryptoid just fine.

I seem to recall this is an old issue. Looking through the last 20 blocks, it appears it's only some (most) blocks that don't pay masternodes.

Small typo from Tranz, I'm sure he meant to type 3,390,000

From src/main.h

Read 3 posts up

Few notes/suggestions for next update.

1) Include address/account for "generate" + "immature" in listtransactions.
Now:
For comparison, on "normal" transactions:

2) Include wallet's stakeweight in getmininginfo
3) Stakeinterest in getmininginfo currently shows 0

Other than that the wallet appears to be working well, both mining and staking works as expected

12.12.17 is now 42 minutes old (where I am). Perhaps a time zone could be useful?

Works just fine here.

Fully synched chain as of ~20 minutes ago.
https://www.dropbox.com/s/27wkrxyuaxbvk83/swing_652751.7z?dl=0

Addnodes, courtesy of https://www.cryptopia.co.nz/CoinInfo/?coin=SWING

Here's a few nodes that I am currently connected to

My 2 masternodes averages around 150 each per month.

Something to get you started. It's not exactly automated, but shouldn't take too much extra work to get it that step further.

coincontrol.php will give you an overview of all blocks in a wallet, and let you select which blocks to include in a transaction, as well as define an output address.
This will be passed on to createraw.php which will create the "createrawtransaction" string. NB This script will only display the transaction string. You will have to manually run the "createrawtransaction" string on the daemon (followed, of course, by "signrawtransaction" and "sendrawtransaction").

Code is provided as-is. Hope it helps.

coincontrol.php

createraw.php

What is the deadline for reporting additional addresses?
I will try and consolidate as they stake, but currently I sit on ~40 addresses with less than 40k