[ANN] Slimcoin : Proof of Burn NEW BLOCK GEN, Mineable by low power computer!

[pantheist]

So, I feel like I'm broaching something a little taboo, but I have to ask.  It seems like no one really knows how slimcoin works, but every now and then someone buys a few hundred bucks worth of it. Why?

[masterOfDisaster]

So, I feel like I'm broaching something a little taboo, but I have to ask.  It seems like no one really knows how slimcoin works, but every now and then someone buys a few hundred bucks worth of it. Why?

There are some who know very well how Slimcoin works - ask "Slimcoin" or a123 for example.
Everyone one who is interested and has the skill can find out as well - the code is open source.
That's what "Mr E" did and - boom! - there's another one who knows how it works.

The interaction between the different processes and their difficulty adjustment is for sure something that needs to be watched closely or even tuned.
But I need to underline it:
Slimcoin is working. It's still running. The block chain is safe. Forking seems to be no longer a problem.
Although it's not maintained for some months the last updates by a123 seem to have kept Slimcoin alive.

Why do people buy coins? Because the speculate on price development, because they like to play with their features, because they want to know how things work.
I have Peercoins, because I want to play with minting.
I have Emercoins, because I wanted to play with the DNS and PKI features.
I have NuShares, because I wanted to play with voting.
I have had Slimcoins, because I wanted to play with burning - which was quite successful

Slimcoin is very experimental. Proof of Burn to secure a block chain is unique.
What's intriguing is that it's working!
And it solves one of the problems PoS processes face: after the SLM have been burned, you have a (strong!) incentive to mint continuously, because the decay whether or not you mint with them.

Slimcoin is a great experiment. It would be nice to see that continued, which would be a reason for speculators to buy low these days

[Mr E]

So, I feel like I'm broaching something a little taboo, but I have to ask.  It seems like no one really knows how slimcoin works, but every now and then someone buys a few hundred bucks worth of it. Why?

Why do people buy coins? Because the speculate on price development, because they like to play with their features, because they want to know how things work.
I have Peercoins, because I want to play with minting.
I have Emercoins, because I wanted to play with the DNS and PKI features.
I have NuShares, because I wanted to play with voting.
I have had Slimcoins, because I wanted to play with burning - which was quite successful

...
Slimcoin is a great experiment. It would be nice to see that continued, which would be a reason for speculators to buy low these days

Ditto that. I've been buying the odd SLM here and there when the price is low, mainly because it's a really interesting concept and I hope to see it grow. And if it does grow, then the price will (hopefully?) go up... so kind of like investing in a start-up company in the hope that it will become popular. (And, of course, I need actual coins to burn in order to try out PoB.)

There are some who know very well how Slimcoin works - ask "Slimcoin" or a123 for example.
Everyone one who is interested and has the skill can find out as well - the code is open source.
That's what "Mr E" did and - boom! - there's another one who knows how it works.

Heh, I'm not sure I know exactly how it works just yet, but the source code is right there, and there's a lot of information back in this thread if you have the time to read through it (look for posts from 'slimcoin', the original dev). The principle is not that complicated -- burn coins to 'buy' virtual burn-mining 'hardware', and then keep your client running to mint coins -- but how that interacts with Proof of Work and Proof of Stake seems to have caused some issues in the past.


Even in the absence of a main dev right now, I'm confident the network's stable enough to keep running as long as there are people who still want to run it.

[d5000]

That's good to hear. Did you pull my whole github fork, or just make the change I gave to a123's version?

Yes, I pulled the whole fork. But I'm not using it productively still (that is still one of the last of a123's versions). Will try it out these days.

I followed the advice of some of you and have re-enabled PoS - without problems so far. And I got my first PoB block, with only 20 SLM burnt so far Will burn some more now and play around.

I seem to have gotten rid of the slimcoin-qt crashes by compiling a version which is more aggressive at banning 'old version' clients (ones that keep spamming getblocks requests). This suggests that the crash is due to dealing with large numbers of requests in close proximity or something similar - which would be consistent with what I've seen where the memory usage suddenly spikes upwards before a crash. I'm just not sure about pushing that pach out widely, since I don't know what the chances are of it banning a legitimate node by accident. I am still showing 27 active connections, though, which suggests it hasn't banned everyone (yet?).

I don't know if slimcoin on linux has the same problem; as far as I know, I'm the only one reporting issues with this and I'm mainly running the Windows client. (I should try running a linux one too and see how it goes.)

I'm running the linux version (without gui) and I get the errors and crashes only when I run it with too low memory / swap space (512 MB seems to be too low, for example). But here I can't help you because I'm not so much of a techie ...

[gjhiggins]

Even in the absence of a main dev right now, I'm confident the network's stable enough to keep running as long as there are people who still want to run it.

I've been doing some integration work on the quiet. I intended to do more testing before announcing the results of my efforts but contemporaneity trumps caution.

I've been hacking around with the PPCoin git repos and (with a bit of judicious conflict resolution) have been able to retrofit SLIMCoin as a branch , thereby recruiting the full PPCoin commit history as the base for “John Smith’s” SLM initial commit and subsequent commit history.

I was able to merge all the way up to the latest commit of the standard PPCoin master (not the more extensive “develop” branch tho' which is a shame because it integrates the 0.8.6 codebase, leveldb, coincontrol and all).

I've also integrated all the contributions from the recent changes in the three extant forks

TBH, I'm mainly interested in getting a better understanding of the PoB element of SLIMCoin and (for me, at least) a coherent, detailed commit history is essential.

The exercise has made the SLIMCoin codebase much more amenable to inspection with a 3-way diff tool such as meld and (for instance), when compared with the original PPCoin codebase, better reveals the PoB-related code.

Whilst I was engaged, I spruced up the graphics and added a couple of features to assist with my analysis; an in-wallet block explorer and a difficulty plot.

At the moment, the repos is under my personal GitHub a/c and I've taken the liberty of adding the other forkers as collaborators:

https://github.com/gjhiggins/SLIMCoin




* The master, develop and sunny branches are contemporary PPCoin.
* The primary branch for SLIMCoin work is slimcoin.
* prerelease has all feature.* merged in for one-stop convenience.


N.B. I've barely begun to test the code, in the interim please consider it as an inspection device.


Overview page with diffplot:




* I chose to roll with the PPCoin switch to protocol v4, hence the spurious 0.4 upgrade deadline warning.
* I've only just begun to investigate the plunges in diff, they're probably PoS blocks.
* If they are, then I'm tempted to call it a “feature” as it usefully indicates PoS/PoW proportion.


Block browser page:



HTH

Cheers

Graham

[BitcoinFX]

Even in the absence of a main dev right now, I'm confident the network's stable enough to keep running as long as there are people who still want to run it.

I've been doing some integration work on the quiet. I intended to do more testing before announcing the results of my efforts but contemporaneity trumps caution.

I've been hacking around with the PPCoin git repos and (with a bit of judicious conflict resolution) have been able to retrofit SLIMCoin as a branch , thereby recruiting the full PPCoin commit history as the base for “John Smith’s” SLM initial commit and subsequent commit history.

I was able to merge all the way up to the latest commit of the standard PPCoin master (not the more extensive “develop” branch tho' which is a shame because it integrates the 0.8.6 codebase, leveldb, coincontrol and all).

I've also integrated all the contributions from the recent changes in the three extant forks

TBH, I'm mainly interested in getting a better understanding of the PoB element of SLIMCoin and (for me, at least) a coherent, detailed commit history is essential.

The exercise has made the SLIMCoin codebase much more amenable to inspection with a 3-way diff tool such as meld and (for instance), when compared with the original PPCoin codebase, better reveals the PoB-related code.

Whilst I was engaged, I spruced up the graphics and added a couple of features to assist with my analysis; an in-wallet block explorer and a difficulty plot.

At the moment, the repos is under my personal GitHub a/c and I've taken the liberty of adding the other forkers as collaborators:

https://github.com/gjhiggins/SLIMCoin




* The master, develop and sunny branches are contemporary PPCoin.
* The primary branch for SLIMCoin work is slimcoin.
* prerelease has all feature.* merged in for one-stop convenience.


N.B. I've barely begun to test the code, in the interim please consider it as an inspection device.


Overview page with diffplot:




* I chose to roll with the PPCoin switch to protocol v4, hence the spurious 0.4 upgrade deadline warning.
* I've only just begun to investigate the plunges in diff, they're probably PoS blocks.
* If they are, then I'm tempted to call it a “feature” as it usefully indicates PoS/PoW proportion.


Block browser page:



HTH

Cheers

Graham

You Sir become a Slimcoin legend !   

[masterOfDisaster]

Even in the absence of a main dev right now, I'm confident the network's stable enough to keep running as long as there are people who still want to run it.

I've been doing some integration work on the quiet. I intended to do more testing before announcing the results of my efforts but contemporaneity trumps caution.
[...]
Cheers

Graham

Graham, this looks awesome!
I'm very happy to see that Slimcoin is able to intrigue developers.
By making your work public you can count others in for testing!
I'm already cloning your repo and will try to compile slimcoind on Ubuntu and Raspbian.

As the main dev position is still vacant (and as far as I understood "Mr E" he doesn't want to have that), you could think about taking that position. It looks like your work is an application for that position
I don't know how many people are still actively following the Slimcoin development, but are still running nodes.
As development might sooner or later cause a hard fork, it will become important to make sure the "network" is aware of that development.
E.g. bter.com still offers trading of Slimcoin. In case of a hard fork they need to update their wallet.

I'm very excited to see such a progress at Slimcoin.
PoB to secure a block chain is just too interesting to let Slimcoin end.

[rfcdejong]

Sounds good to finally have a true fork from peercoin (and then being able to use peer unity forks as well?). Great job! But testing is really important. A manditory wallet update will make the network weak for a period of time, especially if people don't know in time.

[d5000]

Very interesting developments, thanks gjhiggins!

Now if we decide to hard fork: It's true what rfcdejong says, it could weaken the network. It would be nice to have some kind of "census" of active slimcoin users, or even better, to have an own forum to coordinate the protocol switch. Well, at least we have a reddit, it's pretty inactive but could be used for these cases: http://www.reddit.com/r/slimcoin/ I've seen at least some recent post have been made ... things are getting better.

I am a bit delayed with my little "PoB report" project but expect to launch it next week. Will announce it here and at Reddit.

[Superxfast]

Dear all,

Can you share me some nodes to add. My nodes can not finish syncing.

Rgrds,

[hankrules]

Dear all,

Can you share me some nodes to add. My nodes can not finish syncing.

Rgrds,

getpeerinfo
[
    {
        "addr" : "106.186.126.57:44352",
        "services" : "00000001",
        "lastsend" : 1422946703,
        "lastrecv" : 1422946703,
        "conntime" : 1416736361,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 162261,
        "banscore" : 0
    },
    {
        "addr" : "37.187.100.75:41748",
        "services" : "00000001",
        "lastsend" : 1422946703,
        "lastrecv" : 1422946703,
        "conntime" : 1417086229,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 166191,
        "banscore" : 0
    },
    {
        "addr" : "144.76.118.179:52210",
        "services" : "00000001",
        "lastsend" : 1422946703,
        "lastrecv" : 1422946668,
        "conntime" : 1417832829,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 174387,
        "banscore" : 0
    },
    {
        "addr" : "106.186.126.61:43879",
        "services" : "00000001",
        "lastsend" : 1422946703,
        "lastrecv" : 1422946703,
        "conntime" : 1420686662,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 183991,
        "banscore" : 0
    },
    {
        "addr" : "106.187.88.14:56517",
        "services" : "00000001",
        "lastsend" : 1422946703,
        "lastrecv" : 1422946525,
        "conntime" : 1420814478,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 207301,
        "banscore" : 0
    },
    {
        "addr" : "176.31.9.212:50587",
        "services" : "00000001",
        "lastsend" : 1422946703,
        "lastrecv" : 1422946525,
        "conntime" : 1421178193,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 211286,
        "banscore" : 0
    },
    {
        "addr" : "222.190.105.10:38786",
        "services" : "00000001",
        "lastsend" : 1422946703,
        "lastrecv" : 1422946704,
        "conntime" : 1421564335,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 215563,
        "banscore" : 0
    },
    {
        "addr" : "5.9.81.9:50921",
        "services" : "00000001",
        "lastsend" : 1422946702,
        "lastrecv" : 1422946702,
        "conntime" : 1421679997,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 216771,
        "banscore" : 0
    },
    {
        "addr" : "37.187.176.184:45233",
        "services" : "00000001",
        "lastsend" : 1422946703,
        "lastrecv" : 1422946703,
        "conntime" : 1421918405,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 217942,
        "banscore" : 0
    },
    {
        "addr" : "146.199.109.85:63310",
        "services" : "00000001",
        "lastsend" : 1422946703,
        "lastrecv" : 1422946524,
        "conntime" : 1421940752,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 219692,
        "banscore" : 0
    },
    {
        "addr" : "37.187.100.75:46031",
        "services" : "00000001",
        "lastsend" : 1422946703,
        "lastrecv" : 1422946703,
        "conntime" : 1422092953,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 221302,
        "banscore" : 0
    },
    {
        "addr" : "5.9.39.9:39943",
        "services" : "00000001",
        "lastsend" : 1422946703,
        "lastrecv" : 1422946703,
        "conntime" : 1422322693,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 223908,
        "banscore" : 0
    },
    {
        "addr" : "123.2.121.70:61150",
        "services" : "00000001",
        "lastsend" : 1422946703,
        "lastrecv" : 1422946480,
        "conntime" : 1422634849,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 227384,
        "banscore" : 0
    },
    {
        "addr" : "217.65.8.75:40780",
        "services" : "00000001",
        "lastsend" : 1422946703,
        "lastrecv" : 1422946434,
        "conntime" : 1422640432,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 227434,
        "banscore" : 0
    },
    {
        "addr" : "95.90.206.213:3445",
        "services" : "00000001",
        "lastsend" : 1422946703,
        "lastrecv" : 1422946702,
        "conntime" : 1422750836,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 228587,
        "banscore" : 0
    },
    {
        "addr" : "54.191.21.109:56601",
        "services" : "00000001",
        "lastsend" : 1422946703,
        "lastrecv" : 1422946525,
        "conntime" : 1422784817,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 228982,
        "banscore" : 0
    },
    {
        "addr" : "72.174.193.254:57577",
        "services" : "00000001",
        "lastsend" : 1422946703,
        "lastrecv" : 1422946703,
        "conntime" : 1422849250,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 229727,
        "banscore" : 0
    },
    {
        "addr" : "141.48.30.99:34811",
        "services" : "00000001",
        "lastsend" : 1422946703,
        "lastrecv" : 1422946703,
        "conntime" : 1422875233,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 229131,
        "banscore" : 0
    },
    {
        "addr" : "203.217.58.32:60094",
        "services" : "00000001",
        "lastsend" : 1422946703,
        "lastrecv" : 1422946434,
        "conntime" : 1422882898,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 230123,
        "banscore" : 0
    },
    {
        "addr" : "85.152.4.141:41682",
        "services" : "00000001",
        "lastsend" : 1422946703,
        "lastrecv" : 1422945047,
        "conntime" : 1422908311,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : false,
        "releasetime" : 0,
        "height" : 43592,
        "banscore" : 68
    },
    {
        "addr" : "178.222.74.174:15963",
        "services" : "00000001",
        "lastsend" : 1422946703,
        "lastrecv" : 1422946524,
        "conntime" : 1422910488,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 227992,
        "banscore" : 0
    },
    {
        "addr" : "81.207.93.95:52316",
        "services" : "00000001",
        "lastsend" : 1422946703,
        "lastrecv" : 1422946703,
        "conntime" : 1422915179,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 230489,
        "banscore" : 0
    },
    {
        "addr" : "67.148.153.3:21699",
        "services" : "00000001",
        "lastsend" : 1422946703,
        "lastrecv" : 1422946524,
        "conntime" : 1422924952,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 230583,
        "banscore" : 0
    },
    {
        "addr" : "31.18.103.45:58896",
        "services" : "00000001",
        "lastsend" : 1422946703,
        "lastrecv" : 1422946706,
        "conntime" : 1422926740,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 223632,
        "banscore" : 0
    },
    {
        "addr" : "195.19.128.122:64066",
        "services" : "00000001",
        "lastsend" : 1422946703,
        "lastrecv" : 1422946703,
        "conntime" : 1422940047,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 230739,
        "banscore" : 0
    },
    {
        "addr" : "217.219.253.246:1200",
        "services" : "00000001",
        "lastsend" : 1422946703,
        "lastrecv" : 1422945274,
        "conntime" : 1422941117,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 52461,
        "banscore" : 39
    },
    {
        "addr" : "85.212.91.151:49488",
        "services" : "00000001",
        "lastsend" : 1422946703,
        "lastrecv" : 1422946703,
        "conntime" : 1422941708,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 230263,
        "banscore" : 0
    },
    {
        "addr" : "78.97.211.167:3440",
        "services" : "00000001",
        "lastsend" : 1422946703,
        "lastrecv" : 1422941907,
        "conntime" : 1422941907,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 58409,
        "banscore" : 0
    },
    {
        "addr" : "74.78.123.81:54726",
        "services" : "00000001",
        "lastsend" : 1422946703,
        "lastrecv" : 1422946703,
        "conntime" : 1422943457,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 230759,
        "banscore" : 0
    },
    {
        "addr" : "5.141.226.7:48747",
        "services" : "00000001",
        "lastsend" : 1422946703,
        "lastrecv" : 1422946524,
        "conntime" : 1422943990,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 230785,
        "banscore" : 0
    },
    {
        "addr" : "109.199.64.140:1059",
        "services" : "00000001",
        "lastsend" : 1422946464,
        "lastrecv" : 1422946466,
        "conntime" : 1422945895,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 55588,
        "banscore" : 40
    }
]

[3429z781678124]

Hi Graham,

I got some errors by compiling from github. Please help.

At the moment, the repos is under my personal GitHub a/c and I've taken the liberty of adding the other forkers as collaborators:

https://github.com/gjhiggins/SLIMCoin

Code:

g++ -c -pipe -fstack-protector -D_FORTIFY_SOURCE=2 -static -static-libgcc -static-libstdc++ -O2 -D_REENTRANT -Wall -Wextra -Wformat -Wformat-security -Wno-invalid-offsetof -Wno-sign-compare -Wno-unused-parameter -fdiagnostics-show-option -DQT_GUI -DBOOST_THREAD_USE_LIB -DBOOST_SPIRIT_THREADSAFE -DUSE_UPNP=1 -DSTATICLIB -DHAVE_BUILD_INFO -DLINUX -DQT_NO_DEBUG -DQT_WEBKIT_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++ -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtWebKit -I/usr/include/qt4 -Isrc -Isrc/json -Isrc/qt -I/qt -I/QtGui -Ibuild -Ibuild -o build/overviewpage.o src/qt/overviewpage.cpp
src/qt/overviewpage.cpp:220:40: error: no ‘void OverviewPage::updatePlot(int)’ member function declared in class ‘OverviewPage’
 void OverviewPage::updatePlot(int count)
                                        ^
make: *** [build/overviewpage.o] Fehler 1

[bonipper]

Very interesting developments, thanks gjhiggins!

Now if we decide to hard fork: It's true what rfcdejong says, it could weaken the network. It would be nice to have some kind of "census" of active slimcoin users, or even better, to have an own forum to coordinate the protocol switch. Well, at least we have a reddit, it's pretty inactive but could be used for these cases: http://www.reddit.com/r/slimcoin/ I've seen at least some recent post have been made ... things are getting better.

I am a bit delayed with my little "PoB report" project but expect to launch it next week. Will announce it here and at Reddit.

A forum would be good but I bet most people would look here first for any important updates.

[pantheist]

Very interesting developments, thanks gjhiggins!

Now if we decide to hard fork: It's true what rfcdejong says, it could weaken the network. It would be nice to have some kind of "census" of active slimcoin users, or even better, to have an own forum to coordinate the protocol switch. Well, at least we have a reddit, it's pretty inactive but could be used for these cases: http://www.reddit.com/r/slimcoin/ I've seen at least some recent post have been made ... things are getting better.

I am a bit delayed with my little "PoB report" project but expect to launch it next week. Will announce it here and at Reddit.

A forum would be good but I bet most people would look here first for any important updates.

Yeah, despite my pessimism sometimes, I still run the client and watch this thread. I'll bet I'm not the only one. Couldn't hurt to post on reddit, but please at least cross-post anything important here.

[3429z781678124]

Which nodes that are currently working?

The peer list on slimcoin.club explorer seems outdated ... 

[rfcdejong]

i cannot wait until the new version is launched, meanwhile still getting more and more coins from my burned stash

[masterOfDisaster]

Which nodes that are currently working?

The peer list on slimcoin.club explorer seems outdated ...  

My current connections:

Code:

getpeerinfo
[...]
        "addr" : "37.187.100.75:41682",
[...]
        "addr" : "5.9.81.9:41682",
[...] 
        "addr" : "188.16.203.240:41682",
[...]

[d5000]

A forum would be good but I bet most people would look here first for any important updates.

Obviously this thread would continue to be an important communication channel. But a forum enables to coordinate development, marketing etc. much better. I remember the experience of Peercoin: Before they got a forum (Peercointalk) it was more-or-less a one-man project. When the forum opened, soon there emerged discussions about future developments and a marketing team was formed, which drove attention to the coin and made it a top-5 coin for most of 2013 and 2014.

I have currently syncing problems at block 228116. Somebody knows what to do? The last block seems to be on the main chain, at least it has the same block hash as 228116 on the bchain.info block explorer. Have redownloaded blockchain from an earlier snapshot three times now, without luck. Looking at debug.log I see a "Check proof-of-burn error", probably caused by an orphan block.

[BitcoinFX]

Syncing a new node:

addnode=108.61.197.252
 

[gjhiggins]

I got some errors by compiling from github. Please help.

error: no ‘void OverviewPage::updatePlot(int)’ member function declared in class ‘OverviewPage’

I do apologise, for some reason I missed your post.

Mea culpa. I managed to add a fragment of the diffplot code to the vanilla wallet.

Fixed in commit 61c7314, along with a couple of other header declaration omissions. I can confirm that the vanilla wallet compiles without problems on Ubuntu 14.04 at least.

Cheers

Graham