Topic: [ANN] Slimcoin : Proof of Burn NEW BLOCK GEN, Mineable by low power computer! - page 22. (Read 284974 times)

Took forever, but I finally managed to compile both slimcoin-qt and slimcoind on Windows.

Latest commit:

Added 5 hard-coded seed nodes: [37.187.100.75, 5.9.81.9, 192.3.21.71, 107.181.250.216, 107.181.250.217]
Fixed some header issues (not sure if bug or just my configuration)

Release Notes:

Incorporated all of Slimcoin's changes since last release: Improved PoS cpu usage, Disk read efficiency, Reduced mem requirements, RPC improvements
Incorporated some of my changes: Bans misbehaving old clients, added checkpoints, added seed nodes, turned off PoS by default

You can download the Windows-Qt release at https://github.com/kryptoslab/slimcoin/releases

MailBigFile is quite good - https://www.mailbigfile.com/

Is there a way to upload on pastebin rather than ctrl-v? I won't send the entire log (180MB!) but I have noticed something interesting... my client seems to have stopped processing blocks after 2014-10-12 17:56:57 UTC. For around the next 5 1/2 hours - until I killed it - no further blocks were processed, although it was still trying to connect to peers. The client was also unresponsive to RPC commands.

The last block both received and accepted was ec8547a35327162b8284 at 2014-10-12 17:56:57 UTC. Client was killed at 23:35:09 UTC.

Good point actually. I've pushed a commit that makes it reservebalance=1000000 by default, so PoS will be opt-in for now.


Added these nodes to the peer list of the block explorer.

Could you dump the debug.log onto pastebin and post us the link?

My slimcoin client was taking nearly 300% CPU when I killed it. I have staking disabled and it has been running fine for weeks. Any ideas why it went crazy?

Nodes back up and fully synced to the ones shown at http://www.slimcoin.club/ - hopefully stable.

Just a quick update,

I've forked slimcoin to https://github.com/kryptoslab/slimcoin. I pushed a couple of changes here which focuses on gradually banning clients that are stuck at 15164 or keep requesting for blocks between 30k to 60k, while not keeping legitimate users away. If you have memory concerns, this would be quite useful; my clients now run consistently at a lower RAM utilisation and uses much less bandwidth - the old code really can eat up gigabytes of both RAM and bandwidth every day.

Also, hankrules suggested a checkpoint which I incorporated into the code. He is also offering to work on a dnsseed node.

Currently I'm about a quarter done into browser-based burning. I quite like the convenience of the idea here and I do intend for it to visually show how mining and burning works in an interactive fashion, so as to educate and encourage the uptake of SLM.


The rates of SLM minting for PoW and PoB are inversely linked to the difficulty, so I guess the minting rate is much higher. A month back it was like, 8 SLMs minted every PoW block but now it's 12 to 13.


I'm also quite ambivalent about PoS removal. PoB in this current implementation does not secure the blockchain, and the design of SLM actively discourages mining, so it might make Slimcoin vulnerable to 51% attacks if it's PoW/PoB only.

I'll explore 2 methods of fixing the PoS issue on a testnet branch and will update here once I get the code up; hopefully everyone can run a copy to test and we can be rich in test-SLMs for a bit.

I intend to check/change the hashing function (slimcoin himself did note that this is quite intensive and he tried to fix it), as well as simulate and re-weigh the values for PoS, PoB and PoW. If all these fail, then I'll disable PoS and we can see if it helps stability (compared to the main fork).

If all goes well, we can then have a hard fork implementing these PoS changes and disabling access from old clients.

In the background, we should still see if there are any skilled devs willing to port it to a newer code-base. Slimcoin did mention he was interested in this approach though he remains busy.


I am planning to give SLMs away faucet-style, but tied to IP and the web-wallet mining itself (ala lucky draw while browser mining), so will welcome donations for spreading more SLMs around and get people excited about it. You can donate SLMs to Sg72f5icXXAjrdV7o15ZrFdj9CvNaTZwS1; this is what feeds the browser mining rewards (besides the rewards from mining, that is).

@a123: Great news! Will try your site when I have some time.

My problem with the high proof-of-stake reward is basically that it rewards the greatest SLM holders only, as the difficulty is so high that minting isn't possible for little SLM holders. That could lead to a scenario with centralized PoS pools, or even worse, with only the largest users minting PoS and the rest turning off the client.

A network with only a few entities minting PoS would make SLM vulnerable to 51%-PoS-attacks, as most little holders would not even try to mint and so the "staking" coins would be only a little percentage of total supply. In the Peercoin community we try to get the majority of PPC users to mint, so the network keeps descentralized and such attacks are as expensive as possible. The upcoming "cold locked minting" feature (in 0,5) is another step in that direction.

Also, I have noted that since the change the supply of SLM has grown much faster than before. I know, in theory it should be the same like before because of the diff adjustment for PoS. Perhaps it is related to the PoW changes, I don't know.

I am neutral regarding PoS removal. Note that PoS in PPC is the main security mechanism, with PoW having almost no importance. So in a PPC-based PoW/PoB coin without changing this, the PoB algorithm (which is the most experimental part of the coin) would carry "most responsibility" for blockchain security. But I am not an expert on this issue, only read this in the PPC forums, as I am not a programmer.

someone can give me a good nodes to sync my wallet plzz !!!!


P.S this nodes work

addnode=192.3.21.71:41682
addnode=37.187.100.75:41682
addnode=203.20.114.252:41682
addnode=5.9.81.9:41682

I enjoyed reading both posts, thank you

For the client itself, I will hope that improved awareness and better prices will also bring in developer interest (perhaps the original dev's interest too?). In the meantime, I think we can start building up a list of things to fix specifically, perhaps by listing them as issues on github. If no one steps up, I'll fork and make changes to the slimcoin code-base.

The latest version for github is actually quite stable: 3.2.0.6. So far for me, the high cpu/memory usage stems from 2 issues: PoS and bad nodes. Because the version numbers have not changed, older incompatible nodes are freely connecting and repeatedly downloading the blockchain data which fails their verification; I had to block each ip/ip range one by one.

I usually disable PoS cos it sucks my cpu, but PoS itself doesn't really contribute much to the growth. d5000 mentioned that previously there was bump in the reward, but it was also met with a corresponding 10x increase in difficulty which should cancel out: this change was to reduce the number of PoS blocks generated then, which was overwhelming the PoW/PoB blocks.

PoS also appears to be the cause of some block sync and distribution issue: Primer- had mentioned it quite regularly back then, and I also had the same experience. I also noticed that in the past consecutive PoS blocks actually caused my nodes to reject the chain thus orphaning it, though it could also have been an effect of the automatic checkpointing server which seems down now.

I'm still in favour of PoS actually, as long as the bugs can be fixed. Think one of the main issue could also be that dcrypt instead of dbl-sha256 is used for PoS blocks, and that is really really intensive (which can lead to unresponsiveness with a lot of transactions), so that can be an avenue of exploration.

I don't encounter these problems now; but as BitcoinFX mentioned, this could be because of the small number of active nodes.

Needed Changes
1. Add checkpoints
2. Remove PoS or Fix PoS
3. Hardfork with new Protocol Version to reject all older clients

Slimcoin still appears very promising to me but it lacked marketing and awareness, and is also difficult to set up and learn about the various innovations.

I thus spent sometime deciphering the slimcoin source and built this site http://www.slimcoin.club/. It has a brain wallet with mining, transaction and burning built in; all transactions and blocks are signed locally (I never see your key) then sent to one of my nodes for broadcasting.  

(oh yea while burning coins is ok, burnt-coin mining on browser is still buggy; that'll be my next to fix. mining works but is very slow, so i'm thinking of using it more for faucet and coin distribution and to introduce the concept of mining)

I plan to make the page the on-board ramp to get people interested and learn about slimcoin mining, transactions, burning, and to eventually install the client full-time; but yet remain completely functional for those who aren't into running the full client (assuming my nodes remain up).

Also, for us slmers there's a rudimentary block explorer.

Everything's still very alpha and I'm open to your suggestions and your help.

I have started a thread about Slimcoin in Peercointalk forum:

http://www.peercointalk.org/index.php?topic=3461.msg33518;topicseen#msg33518

I probably will also a separate thread about proof of burn in one of the main sections, as the block generation method even can be useful for Peercoin or NuBits in the future.

Sadly i'm not a coin dev and i don't have time either.
A dev or better a team of dev's that take over this coin would be best.

ps: slimcoin never really left, he is just very inactive and that is what he said, he will help in time of need but won't actively develop
ps2: slimcoin, there is a checkpoint needed!

I don't mean you have the magic to resurrect a coin My point is you might know a lot of things and have a lot contacts in this forum, so by any chance that you know some devs? I did try to find a core dev for my own project since three months and the only one I could find is bushstar.

@d5000: You are right in regards to the Peercoin version releases. What is interesting is that the 1st Slimcoin release was seemingly quite 'stable' in comparison to now.

Having three algorithms for block generation is partly causing these network propagation issues. Its possible that these issues were somewhat unrealized with fewer networked nodes and less of a blockchain.

It is not going to be easy to fix this and it may be better to try a different or similar PoB implementation altogether. Again, a coder with an extensive working knowledge of the Peercoin base is the best option to provide advice on whats possible here - I'd imagine. I do have an account on the peercoin forums, but I've not logged-in for a while, so as you are a mod. then go-for-it.  

@AizenSou: Being a 'Hero' member on this forum, sadly does not make us magic men. The term 'Hero' is used to much these days imho.

Although, lots of us have put time and resources into mining and supporting Slimcoin, so it would be a shame to see all that just go to waste.

I did suggest remove PoS from Slimcoin long time ago because it's sure the source of bugs.

Only if we could find a dev who could remove PoS entirely from Slimcoin and fix the bugs. BitcoinFX and d5000 since you two are hero member, do you know some good devs?