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

[a123]

After 1 week of PoB, I've lost 449.6 SLMs to decay but gained 3719.9 from PoB, so that's a rather respectable 8.27x gain ratio. As more people burn this ratio will go down, of course. I assume this would tend to 1 in the long run, though people aren't likely to burn if the return is like just 2x or 3x, unless we get a lot of transaction fees.

That's also roughly equivalent to a PoW hash rate of 750KHs, based on the current hash rate and difficulty. That's like around 600 CPU cores, running off an initial 49152 SLM investment and a 32USD Raspberry Pi.

Thought this might be useful snapshot to paint the potential of PoB!

[AizenSou]

After 1 week of PoB, I've lost 449.6 SLMs to decay but gained 3719.9 from PoB, so that's a rather respectable 8.27x gain ratio. As more people burn this ratio will go down, of course. I assume this would tend to 1 in the long run, though people aren't likely to burn if the return is like just 2x or 3x, unless we get a lot of transaction fees.

That's also roughly equivalent to a PoW hash rate of 750KHs, based on the current hash rate and difficulty. That's like around 600 CPU cores, running off an initial 49152 SLM investment and a 32USD Raspberry Pi.

Thought this might be useful snapshot to paint the potential of PoB!

And the price tends to rise back to it's former height too.
You can't simply buy 50k SLM from exchange now without pushing the price to 2,3x.

[a123]

Just an update, PM exchange with Dev (timestamps are accurate):

hi slimcoin dev,

there is still a huge interest in the novelty of your coin, hash rate is at a peak, bter has been on an uprise, and the community clearly believes there's room for growth.

so far there has been 2 other devs who already contributed code and effort to improve the client. we've also raised nearly 7K SLM for bounties and giveaways.

we are planning to perform a hard fork soon to disable PoS and sync-checkpoints, increment the protocol version to kick out misbehaving clients (this has been identified as a major bugbear on resources and we've issued a temporary fix), and to update a miscellany of issues that has been identified since. you can check out our fork and commits at github.com/kryptoslab/slimcoin.

also, at the point of the hard fork I will likely issue a ReAnn so that I can edit the OP, and work on rallying the community to continue the development.

would like to know your plans for SLM so we can synchronise our efforts!

Hello,

  As I have posted before, the reason I "left" this project is some other stuff came up. I say "left" as I still follow its development on the forum. I did state I could do basic maintenance, of which was to hold the central sync node up. I have absolutely no problems with you forking this project, in fact, it would be of great delight to me if you did so. I can offer you assistance in navigating the PoB code and making you a reddit administrator for /r/Slimcoin. As for development, I have nothing much planned in the short termed future.

-P4Titan

[AizenSou]

Just an update, PM exchange with Dev (timestamps are accurate):

hi slimcoin dev,

there is still a huge interest in the novelty of your coin, hash rate is at a peak, bter has been on an uprise, and the community clearly believes there's room for growth.

so far there has been 2 other devs who already contributed code and effort to improve the client. we've also raised nearly 7K SLM for bounties and giveaways.

we are planning to perform a hard fork soon to disable PoS and sync-checkpoints, increment the protocol version to kick out misbehaving clients (this has been identified as a major bugbear on resources and we've issued a temporary fix), and to update a miscellany of issues that has been identified since. you can check out our fork and commits at github.com/kryptoslab/slimcoin.

also, at the point of the hard fork I will likely issue a ReAnn so that I can edit the OP, and work on rallying the community to continue the development.

would like to know your plans for SLM so we can synchronise our efforts!

Hello,

  As I have posted before, the reason I "left" this project is some other stuff came up. I say "left" as I still follow its development on the forum. I did state I could do basic maintenance, of which was to hold the central sync node up. I have absolutely no problems with you forking this project, in fact, it would be of great delight to me if you did so. I can offer you assistance in navigating the PoB code and making you a reddit administrator for /r/Slimcoin. As for development, I have nothing much planned in the short termed future.

-P4Titan

Nice. It would be the best if slimcoin old dev could give you the login data so you could freely change the content of the OP. I'm looking forward for the future of Slimcoin.

[a123]

Nice. It would be the best if slimcoin old dev could give you the login data so you could freely change the content of the OP. I'm looking forward for the future of Slimcoin.

I offered to edit and send @slimcoin the updated OP contents whenever it needs to be updated, and he was ok with updating the OP with that. Will see how this arrangement works out!

[a123]

was just discussing with hankrules on our plans for slim and i thought ill also post mine here to get some thoughts

haha yea actually i do feel pob in its current incarnation isnt very optimal yet, and ideally it shd decouple from pow and serve to secure the blockchain. this will be a long term goal for pob for me

im also discussing with @slimcoin on the scalability of slimcoin, and might make some changes to the burn decay rates to make it viable in the long run

in the short run i will probably just get the nomp pools ready by inserting the dcrypt algorithm and the slimcoin param, and try to get some experienced pool operators to handle the day 2 day routines.. i am also working w some partners to improve the visual branding and marketing to better convey what Slimcoin offers

[jadefalke]

wow the diff is so high! did not find a POW Block in one Day with 50 Digital Ocean Instances.

[a123]

wow the diff is so high! did not find a POW Block in one Day with 50 Digital Ocean Instances.

just curious, how much is tt in terms of hash power?

[jadefalke]

wow the diff is so high! did not find a POW Block in one Day with 50 Digital Ocean Instances.

just curious, how much is tt in terms of hash power?

honestly spoken not that much, 10-12 KH/s per instance.

[BitcoinFX]

wow the diff is so high! did not find a POW Block in one Day with 50 Digital Ocean Instances.

just curious, how much is tt in terms of hash power?

honestly spoken not that much, 10-12 KH/s per instance.

At this difficulty we really need to have a working pool set-up again.

You could try cloud mining at VULTR instead. They currently provide cloud servers with (at least) x2 the cpu power per. core and more RAM.

They also accept Bitcoin - https://www.vultr.com/news/45/Now-Accepting-Bitcoin!

Did anyone try contacting sandor111 ? as they set-up the original Slimcoin NOMP based pool I think.

[oveeps]

In urgent need of  pool

[jonnylatte]

I wrote a program to examine The Dcrypt Algorithm just out of curiosity. I wanted to know how much memory it uses on average. Internally in the mixing hash function it has a scratch pad that exists as multiples of 64 bytes plus the original size of the data being hashed and some fixed sized scratch pads. The variable size buffer is what is of interest because that what is supposed to fight against GPU and ASIC miners.

After hashing 100K times I got the following result for the multiple:

average 1026    <10 0.683007%   <100 8.99509%   <500 38.3704%

So on average the function used 65,664 bytes for the variable sized buffer but 0.68% it used less than 640 bytes.

I though this is interesting and it should be possible to see if anyone has a miner that aborts hashing if the memory size of the hash function is over a certain size.

[sparkster]

Wallet window is too big (vertical size) for 768p. And yes, some laptops still have it.

Also, zero connections (3.2.1 from climcoin.club). Any nodes?

[AizenSou]

I wrote a program to examine The Dcrypt Algorithm just out of curiosity. I wanted to know how much memory it uses on average. Internally in the mixing hash function it has a scratch pad that exists as multiples of 64 bytes plus the original size of the data being hashed and some fixed sized scratch pads. The variable size buffer is what is of interest because that what is supposed to fight against GPU and ASIC miners.

After hashing 100K times I got the following result for the multiple:

average 1026    <10 0.683007%   <100 8.99509%   <500 38.3704%

So on average the function used 65,664 bytes for the variable sized buffer but 0.68% it used less than 640 bytes.

I though this is interesting and it should be possible to see if anyone has a miner that aborts hashing if the memory size of the hash function is over a certain size.

If you could set up the pool, it would be awesome. Remember bounty for the pool is 2500 SLM if I remember correctly.

Btw, are we on page 200 yet?

[ocminer]

Hey guys,

whats the maximum block height currently ?

[oveeps]

Hey guys,

whats the maximum block height currently ?

We need to pool

[ocminer]

Hey guys,

whats the maximum block height currently ?

We need to pool

I'm building one, but I need to download the whole blockchain before.. i'm on block 3300 now

[oveeps]

Hey guys,

whats the maximum block height currently ?

We need to pool

I'm building one, but I need to download the whole blockchain before.. i'm on block 3300 now

Thank you  Waiting for a long time.

[BitcoinFX]

Hey guys,

whats the maximum block height currently ?

We need to pool

I'm building one, but I need to download the whole blockchain before.. i'm on block 3300 now

Current number of blocks  134905

[ocminer]

Hey guys,

whats the maximum block height currently ?

We need to pool

I'm building one, but I need to download the whole blockchain before.. i'm on block 3300 now

Current number of blocks  134905

I'm at 35k now.. will take some time..