I would suggest having someone update the core codebase to as latest as possible and then attempting to launch service nodes.
Chaincoin acquired masternodes in its upgrade to 0.9, the most recent Core version that doesn't necessitate a hard fork of the blockchain, c.f. the Bitcoin 0.10 release notes:
Because release 0.10.0 makes use of headers-first synchronization and parallel block download (see further), the block files and databases are not backwards-compatible with older versions of Bitcoin Core or other software:
A hard fork creates a forced choice, upgrade to the new client/blockchain / stay with the old client/blockchain. A consensus will become evident but that in itself will not necessarily result in a single blockchain - both old and new chains can exist separately and simultaneously.
However, an upgrade to 0.9 falls well short of defunctec's (eminently pragmatic) criterion of “latest as possible” and also misses out on the improvements that the 10-13 versions bring. From a maintenance perspective, going to 0.9 is hardly worth the effort, given the (un-guessable, even) risk of dividing the community --- it cannot be ignored that such a move could result in georgem's miner and blockexplorer work being effectively isolated if he was minded to maintain his insular stance.
<digression>
This thread has been useful in prompting me to go back and refresh my memory of events. I
bailed in late April 2015, eventually observing “in several areas my perceptions are starting to differ sufficiently from (what I perceive to be) the consensus that it basically renders irrelevant any contribution I might make in that context, so I'm opting to keep my own counsel there.” The subtext was: “Nope, that ain't gonna work. Bugger this for a game of soldiers, I'm slinging my hook” (high and low registers, right?)
Anyway, I had to check back on coins101's apparent understanding “That's along the lines I was thinking of broadcasting messages” because my model had Mr Spread's description placed in early 2015 with late spring for coins101/georgem's development project for Bitcoin node support. So I had to check - which was useful because in the process of refreshing my memory, I was confronted with a use case discussion that I had completely forgotten about but the content of which later significantly informed my understanding - so props to thelonecrouton and Anothernode for spelling it out - details later ..
</digression>
There's a raft of 0.10 coins, just search on Github for
"Bitcoin Core version 0.10.0 is now available from:"There are markedly fewer
0.11 coins aaand (for completeness)
0.12 and
0.13I can't tell offhand which of the Core versions have overlay networks but there aren't many. I think bitcredits got to 0.12 and had an overlay network, that might be a sensible place in which to start looking. Upgrading that to 0.13 will still be effortful, btw.
It would have to be a long running jump and grab to 0.12/0.13 and even then Spreadcoin could end up like iXCoin, all synched up and nowhere to go.
Anyway, time to return to the Anothernode/thelonecrouton discussion. I'm not going to re-post the discussion, just the pointers:
my post:
https://bitcointalk.org/index.php?topic=715435.msg10973864#msg10973864thelonecrouton's response:
https://bitcointalk.org/index.php?topic=715435.msg10975747#msg10975747anothernode's refinement:
https://bitcointalk.org/index.php?topic=715435.msg10976140#msg10976140The key insight is thelonecrouton's “using the MN network as a consensus mechanism for choosing the locus/loci”. It's relevance didn't strike me until I found myself reading:
The group is initialized by either a trusted dealer or a set of founding members. The dealer or founding members initialize the group by choosing a group secret key, and computing and publishing the corresponding public parameters in the group certificate. The group secret is shared among the founding member(s) using either Shamir’s threshold secret sharing (TSS) or joint secret sharing (JSS) techniques
Threshold cryptography in P2P and MANETs: The case of access controland I realised that “initialize the group by choosing a group secret key” can be mapped to “a consensus mechanism for choosing the locus/loci”
Which brings us smartly to the key question: is the overlay network capable of ephemeral knowledge of a secret and thereby capable of offering trustworthy cryptography?
Using an overlay network to mediate threshold cryptography is not a done deal by any means - see Chen and Wu's review of the field:
A Survey on Cryptography Applied to
Secure Mobile Ad Hoc Networks and Wireless Sensor Networks (PDF).
I just thought I'd chuck that into the mix.
Also, coins101 put a lot of effort into detailing the other possibilities for exploiting the advantages of an overlay network, shouldn't be overlooked at this point:
https://bitcointalk.org/index.php?topic=976031.msg10656234#msg10656234Cheers
Graham