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

[cassimares]

Nice concept for mining...

[1715193097]

1715193097

[1715193097]

1715193097

[1715193097]

1715193097

[1715193097]

1715193097

[1715193097]

1715193097

[1715193097]

1715193097

[reflector]

Active slimcoin twitter: https://twitter.com/SlimcoinProject

[EPayDev]

Nice concept for mining...

[a123]

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?

[a123]

One thing though, it seems the version number in the 'about slimcoin-qt' still displays 0.3.2.0?

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

Finally: I have some dev experience, and am happy to help out with a bit of testing / debugging if anything comes up, though I can't promise to have a lot of time for it. But so far you seem to be on top of things anyway.

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

If this continues to go well, when I have some time I might try to look at building a wallet that can run in the background in a FreeNAS server jail, since I've got one of those running anyway...

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

Edit: So clearly the GUI 'fake mint-by-burn' bug hasn't been fixed so far. I just requested 0.01slm from multifaucet, and it appeared in my transaction tab as a +193slm mint-by-burn. (However the correct details show when I double-click it for details or do listtransactions.)

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)

Active slimcoin twitter: https://twitter.com/SlimcoinProject

Quite like the hype by the Twitterer

[oveeps]

The mine pool built what time

[jadefalke]

just tried the linux version and it's complaining that the checkpoint is to old,but it's the actual block


    "version" : "v0.3.2.0-13-gd9fad6e-dirty-alpha",
    "protocolversion" : 60003,
    "walletversion" : 60000,
    "balance" : 11.49321700,
    "newmint" : 0.00000000,
    "stake" : 0.00000000,
    "blocks" : 129799,
    "moneysupply" : 1422694.87684600,
    "connections" : 7,
    "proxy" : "",
    "ip" : "54.186.230.xxx",
    "difficulty" : 0.14805084,
    "testnet" : false,
    "keypoololdest" : 1401555201,
    "keypoolsize" : 103,
    "paytxfee" : 0.01000000,
    "errors" : "WARNING: Checkpoint is too old. Wait for block chain to download, or notify developers of the issue."
}

[AizenSou]

just tried the linux version and it's complaining that the checkpoint is to old,but it's the actual block


    "version" : "v0.3.2.0-13-gd9fad6e-dirty-alpha",
    "protocolversion" : 60003,
    "walletversion" : 60000,
    "balance" : 11.49321700,
    "newmint" : 0.00000000,
    "stake" : 0.00000000,
    "blocks" : 129799,
    "moneysupply" : 1422694.87684600,
    "connections" : 7,
    "proxy" : "",
    "ip" : "54.186.230.xxx",
    "difficulty" : 0.14805084,
    "testnet" : false,
    "keypoololdest" : 1401555201,
    "keypoolsize" : 103,
    "paytxfee" : 0.01000000,
    "errors" : "WARNING: Checkpoint is too old. Wait for block chain to download, or notify developers of the issue."
}

Did you resync from the start, jade ?

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?

50k SLM burnt? LOL quite a number of burning money.
I will ask my friend dcct about the ROI calculator for PoB.

[a123]

just tried the linux version and it's complaining that the checkpoint is to old,but it's the actual block

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

50k SLM burnt? LOL quite a number of burning money.
I will ask my friend dcct about the ROI calculator for PoB.

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

[AizenSou]

just tried the linux version and it's complaining that the checkpoint is to old,but it's the actual block

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

50k SLM burnt? LOL quite a number of burning money.
I will ask my friend dcct about the ROI calculator for PoB.

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 sent him 300SLMs for his explorer work and if you could send him some for the bounty he will be happy about this. SLM is one of hidden gems in cryptoworld now. Let's us accumulating alot more before it explodes

[a123]

I sent him 300SLMs for his explorer work and if you could send him some for the bounty he will be happy about this. SLM is one of hidden gems in cryptoworld now. Let's us accumulating alot more before it explodes

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.".

[Mr E]

I believe I've managed to chase down the bug causing transactions to show up as "Mint by burn" when they actually weren't.

The code that did up the transaction list checked whether the transaction was in a PoB block, but forgot to check whether it was the coinbase transaction, with the result that all transactions in PoB blocks would show up as "Mint by burn". I'm not quite sure why the incorrect amount appeared in the list -- but try my patch and see if it fixes the GUI bug. (Or if you don't have a gui environment to test it on, I can do it if you compile an updated windows client. Haven't got a build environment of my own yet...)

(BTW, it looks like even the check for PoB block is kind of hacky -- the check for PoS blocks calls a wtx.IsCoinStake() function, but the check for PoB is implemented as a boolean flag passed in to the function by the caller... kind of ugly...)

[oveeps]

What time GPU miners coming

[a123]

What time GPU miners coming

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.

I believe I've managed to chase down the bug causing transactions to show up as "Mint by burn" when they actually weren't.

The code that did up the transaction list checked whether the transaction was in a PoB block, but forgot to check whether it was the coinbase transaction, with the result that all transactions in PoB blocks would show up as "Mint by burn". I'm not quite sure why the incorrect amount appeared in the list -- but try my patch and see if it fixes the GUI bug. (Or if you don't have a gui environment to test it on, I can do it if you compile an updated windows client. Haven't got a build environment of my own yet...)

(BTW, it looks like even the check for PoB block is kind of hacky -- the check for PoS blocks calls a wtx.IsCoinStake() function, but the check for PoB is implemented as a boolean flag passed in to the function by the caller... kind of ugly...)

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

[a123]

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

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

[hankrules]

What time GPU miners coming

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.

Not insight, but from the whitepaper:

The Dcrypt algorithm is a “front-end” to the SHA256 hashing algorithm. Its main purpose is to prevent an ASIC dominated
proof-of-work mining scheme from occurring in Slimcoin. Allowing Slimcoin to become ASIC minable will overshadow
the proof-of-burn and proof-of-stake aspects of the coin. Dcrypt is made to be difficult to parallelize, require significant
amounts of memory, require significant amounts of reading/writing to/from memory. Also, the amount of memory required
is not a predetermined size. The hashing algorithm loops until a specific condition is met and for each loop, the size
increases.

It goes into more detail that quickly becomes beyond my comprehension   http://www.slimcoin.club/whitepaper.pdf

[a123]

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...)

[rfcdejong]

Difficulty is rising, it's back at what it used to be when the pools were active.

Are there any pools now? If this difficulty is done without ANY pool then it's insane!

"difficulty" : 0.20134940,

PS: I have a large amount of burn coins as well, over 2% of the total amount, but that is because i never stopped mining and when the diff was low i got many

"Net Burnt Coins" : 8074.81369400,
"Effective Burnt Coins" : 7389.20701100,
"Immature Burnt Coins" : 111.67010000,
"Decayed Burnt Coins" : 523.93658300

[BitcoinFX]

What time GPU miners coming

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.

Not insight, but from the whitepaper:

The Dcrypt algorithm is a “front-end” to the SHA256 hashing algorithm. Its main purpose is to prevent an ASIC dominated
proof-of-work mining scheme from occurring in Slimcoin. Allowing Slimcoin to become ASIC minable will overshadow
the proof-of-burn and proof-of-stake aspects of the coin. Dcrypt is made to be difficult to parallelize, require significant
amounts of memory, require significant amounts of reading/writing to/from memory. Also, the amount of memory required
is not a predetermined size. The hashing algorithm loops until a specific condition is met and for each loop, the size
increases.

It goes into more detail that quickly becomes beyond my comprehension   http://www.slimcoin.club/whitepaper.pdf

Indeed. Slimcoin is certainly not just a 'copy and paste' coin and has many innovative features.

Its quite remarkable that Slimcoin has had a relatively limited following up until now and that it was almost left to just crash and burn. (pun intended)

[BitcoinFX]

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...)

Coolio. Update my nodes without a hitch. Good progress.

~ Raspberry of approval from our mascot

P.O.B. https://www.youtube.com/watch?v=3dqxZo_myyA