I've cloned the ANN from Slimcoin to https://github.com/kryptoslab/slimcoin/wiki/Reannouncement. I've updated the details, but I would invite your edits to brand or market it better This would be the basis for the ReANN after the fork in a couple of weeks time.

I'm also putting up a bounty, which is also in the Reannouncement.
Thanks to the generous donations from hankrules, AizenSou and BitcoinFX, I'm putting 530 SLMs into giveaways and mining faucet, and 5000 SLMs for the bounty.

I think a primary need for us now is for experienced pool operators to run a Dcrypt mining pool, so am planning to offer the following, I'm open further suggestions (particularly from the donors!)

• First working pool : 2500 SLM
• First pool to host a total of 2MH/s: 2500 SLM

Do help reach out to pool operators whom you think might be interested!

Donation Address for Bounties: Sg72f5icXXAjrdV7o15ZrFdj9CvNaTZwS1
Donation Address for Giveaways and Slimcoin.club Mining Faucet: SeCZAzhRkC8VxdqYfbcvgTVkN3RoLzNoYy

To check the amount collected so far, I've set up a live progress collection counter on my site: http://www.slimcoin.club/#donate

I'm pledging a SLM for a SLM, for every donor from now on who posts about their donation here (so I can match it up to the person), up to 5K for bounties and 1K for Giveaways.

Gosh somehow my dedicated Centos 7 server just rebooted itself and reconfigured its firewall to firewalld instead of iptables. Just reconfigured it to bring slimcoin.club back up!

Just a musing on the current implementation of Slimcoin.

Based on the burn decay rate of 0.001427 / day, as we approach 1.6 million coins burnt, the rewards tends to zero as the decay rate equals reward rate. The only reward would be from fees.

At such a burn decay rate, 2342 coins will decay, which would equal the PoW generation rate if the difficulty is 10 (3.5 SLM block reward * 720 / day), which is roughly 1Ghs, thus achieving kind of an equilibrium.

It provides quite an interesting dynamic circulation ceiling which tends to 1.6 million SLMs with heavy usage, yet increases gradually to 250 million with low volume.

I'm not too clear, but I don't think PoB can help defend against PoW 51% attacks. PoB does increase trust score of a chain for resolving forks but might not kick in in time for double-spend attacks?

As far as I understand, nothing at stake is a phenomenon that applies to pure PoS altcoins. PoB always depend on a preceding PoW which has a cost to mine (aka something-at-stake), so you can't chain PoBs consecutively to perform the N@S attacks.

Oops  

Yeap PMed you re the Amazon EC2 build environment!

Updated https://github.com/kryptoslab/slimcoin/releases/tag/v0.3.2.1

Changes:

From hankrules: Added 2 dnsseed servers
From Mr T:       Fixed display bug for transactions in PoB blocks
From a123:       Fixed versioning, disabled sync checkpoint errors, added new RPC command "getsubsidy" to find out current PoW (for pool use)

(pi's version is still compiling...)

Ok fix confirmed, thanks Mr E! Will update the binaries soon

Hmm I was quite hoping it is truly resistant to GPU mining, similar to how Cryptonite has almost very little advantage over CPUs (assumption based on http://cpucoinlist.com/). Anyone has any insights on how Dcrypt holds up? Being a CPU-only coin has a certain appeal, and it might not be too late to switch to another algo in time for the fork.


Awesome! I'm testing it out right now, am spamming myself with 0.01 SLMs in hope of catching a PoB block. I'll PM you on regarding the Amazon EC2 build environment I compiled the Slim-Qt on

I've received 5530 SLMs for donations and bounties to give away so far, think I'll organise a way to let donors vote where the SLMs go.

I've coded up a simple calculator while we wait for better ones, it's available in the Brain Wallet section of my slimcoin.club website, under "Burning SLM". A 50000 SLM burn currently gives an estimate of "482.056151 SLMS GENERATED PER DAY, 71.35 SLMS DECAYED.".

Actually I have this issue too. Will fix this up in the next release! Created an issue on the tracker.


Your friend is doing a lot

Yea I dumped most of my SLMs at it. Difficulty is getting high for dcrypt mining and I'm all in on SLMs - a good and verifiable show of confidence

I haven't quite figured out the versioning system actually. But will look into fixing it! (added to Issues on Github)


Still new to this and will be throwing out requests for help, so if it happens and you have time please do take a look


That's be quite cool, since these devices run all the time anyway, would be a good place  to burn coins.


Hmm ok noted this, will see if I can fix it. I don't use the qt client so I didn't realise this. (added to Issues on Github)


Quite like the hype by the Twitterer

Configured the P2Pool, and added the custom Proof of Burn block headers, but got it stuck at the get_block_header polling phase. Apparently the block header for SLM isn't hashed by sha256 but by Dcrypt? Don't think this was supposed to be the case according to the SLM whitepaper, since Dcrypt for hashing block headers would be unnecessarily intensive, will look into it further and propose changes for the upcoming hard fork if necessary.

Also glad to report that Slimcoind has also been running smoothly on the Raspberry Pi for the past 3 days, no crashes, using only 106MB out of the 496MB total. Load average between 0.2 to 0.4. Out of the 49152 coins I burnt, 236 has already decayed. But that produced 2093 coins, so that still seems quite productive.

Think we need a burn calculator of sorts, to get a sense of the ROI. Will work on it, though anyone is keen or exploring the idea or have already built one?

Ooh p2pool is in python, I'll try to get it working

I would try to contact him first. This is really mostly his work, still. But if there's no response I can start a new thread.

I propose in the continued absence of the main dev, we do a hard fork once
1) PoS is removed
2) we obtain a pool operator or two
3) centralised sync checkpointing is removed (anyone has an opinion on this?)

If no one is against PoS removal, I will just code it such that all PoS blocks after the hard fork will be rejected (for instance, a Block's IsProofOfStake() will always resolve to False if height > forkheight.).

For centralised sync checkpointing, I'll just turn the hardcoded public key into maybe all zeroes or even the SLM burning address, and turn the warnings off (or make the last syncpoint's expiry never expire)

Anything else to be done? I remember reading something about P2Pool needing a few fixes to be operable with Slimcoin. Anyone has details on this?

Hard fork will reject all old clients from connecting and be pure PoW/PoB hybrid.

In the meantime, we could do a community wiki to start collating all the SLM information (such as compilation instructions, installation instructions, PoB theory, etc) so as to help, as well as to start looking for issues / improvements for SLM.

I have enabled the Wiki and Issues tracking feature on my Github page for Slimcoin: https://github.com/kryptoslab/slimcoin, but would be open to suggestions as to where else best to host such information (:

Whoever built the 116k SLM buy wall, that's amazing Price action tends to attract adopters so things are definitely looking up!

Just an update,

https://github.com/kryptoslab/slimcoin/releases/tag/v0.3.2.1
Release has been updated with Linux and Raspberry Pi binaries, as well as a blockchain snapshot at 126100.

That's right, the Pi binaries are finally up as well! To celebrate I just burned a huge chunk of my SLMs on the Pi!

Thanks! Included a link from the slimcoin.club site.

Just happened to see it as it was sent! Received

Oh hmm that's strange, the error showed up for my Windows exe after fully syncing. I'll go check if I compiled the right version!

[edit]
Yea the files I compiled contained the checkpoints, hmm. Not sure the qt side includes any other checks?
[/edit]

I noticed it as well, and realised the checkpoint error needs to be cleared with @slimcoin's private key encoding the sync checkpoints. The corresponding public key is hard coded into the source. The checkpoints we added will not remove the error message.

This seems to be a feature of the Peercoin; though it appears more applicable as a defensive mechanism on a pure PoS. I'm actually kinda uncomfortable with this checkpointing system, which seems kinda antithetical to the purpose of cryptocurrencies.

I could disable it, any thoughts on this though?