Pages:
Author

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

member
Activity: 98
Merit: 10
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. Wink
I will ask my friend dcct about the ROI calculator for PoB.

Your friend is doing a lot Smiley

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 Cheesy
hero member
Activity: 938
Merit: 1000
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. Wink
I will ask my friend dcct about the ROI calculator for PoB.
legendary
Activity: 1456
Merit: 1014
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."
}
newbie
Activity: 33
Merit: 0
The mine pool built what time Huh
member
Activity: 98
Merit: 10
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. Smiley

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 Smiley

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 Cheesy
member
Activity: 98
Merit: 10
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?
sr. member
Activity: 826
Merit: 263
full member
Activity: 236
Merit: 100
Nice concept for mining...
legendary
Activity: 1456
Merit: 1014
the static nodes work perfect first time i was able to sync up without any special Settigs Wink
newbie
Activity: 21
Merit: 0
Thanks a123, I just got into Slimcoin after reading about PoB 'mining' and being fascinated by the concept. So glad to see the coin being resurrected now. And your updated wallet seems to use so much less CPU -- previously I had two generate threads maxing out my CPU (quad-core), whereas now they only take it to about 80-85%. (Including other things running besides slimcoin.)

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

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

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


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.)
hero member
Activity: 938
Merit: 1000
Any way to promo SLIM?

Maybe do giveaways or at least try to get people write a blog about SLIM, get it on polo, get an IRC channel with tipbot etc

PS: Thanks a123, great job done already!

Yep on polo would be nice. Unfortunately I don't know busoni.
My friend dcct would provide us soon a complete package of block explorer, richlist and faucet.
hero member
Activity: 798
Merit: 500
Any way to promo SLIM?

Maybe do giveaways or at least try to get people write a blog about SLIM, get it on polo, get an IRC channel with tipbot etc

PS: Thanks a123, great job done already!
hero member
Activity: 881
Merit: 501
What's happening here is amazing. I like it very much.

member
Activity: 98
Merit: 10
Ooh p2pool is in python, I'll try to get it working Smiley
member
Activity: 63
Merit: 10
Thanks for saving this thing! My subscription to the thread apparently died, so it was exciting to come back and see all the new developments
hero member
Activity: 938
Merit: 1000
a123 could you consider to create a new thread if the old dev won't respond ?

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 best to host such information (:

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

Yes I did contact blockquarry through the contact page but still no response. If any of you knows how to contact him directly it would be nice.
Pure PoW/PoB hybrid is amazing. 4k sat is still to cheap now. If I remember correctly it reached 100k sat before.
> 4BTC buy wall just because of the news that you continue to develop the coin, amazing.
member
Activity: 98
Merit: 10
a123 could you consider to create a new thread if the old dev won't respond ?

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 Cheesy Price action tends to attract adopters so things are definitely looking up!
hero member
Activity: 938
Merit: 1000
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!

Nice. Thanks dev. I just sent blockquarry admin a mail asking for the pool. Let's see.

Has anybody been in touch with the original dev?  At some point, either the OP will need to be updated, or a new thread will need to be created.  Looking good though!  


a123 could you consider to create a new thread if the old dev won't respond ?
sr. member
Activity: 280
Merit: 250
Pages:
Jump to: