Slimcoin | First Proof of Burn currency | Decentralized Web

[gavrilo77]

Vote for SLM https://www.tradesatoshi.com/Vote

I have wrote them yesterday and they put SLM on voting list. I was using recently tradesatoshi, they are OK exchange

[1714025050]

1714025050

[1714025050]

1714025050

[almightyruler]

I haven't been involved with Slimcoin for a couple of years.

Has there been a hard fork since then? My (old) client is syncing (slowly) but if there's been a hard fork there's not much point.

Is this the correct git rep? https://github.com/slimcoin-project/Slimcoin/

(The hardened checkpoints in this source are very old.)

BTW, the client seems to be using a crapload of CPU. Load was past 9 on a four core server (that's more than 200% load). Once I stopped slimcoind it went back down to 2.5 (62.5% load). Is this improved in the newer client source and/or is there a way to limit it to using one core only?

Thanks!

[gavrilo77]

I haven't been involved with Slimcoin for a couple of years.

Has there been a hard fork since then? My (old) client is syncing (slowly) but if there's been a hard fork there's not much point.

Is this the correct git rep? https://github.com/slimcoin-project/Slimcoin/

(The hardened checkpoints in this source are very old.)

BTW, the client seems to be using a crapload of CPU. Load was past 9 on a four core server (that's more than 200% load). Once I stopped slimcoind it went back down to 2.5 (62.5% load). Is this improved in the newer client source and/or is there a way to limit it to using one core only?

Thanks!

The last one client https://minkiz.co/noodlings/slm/slimcoin-qt-v0.5.1-win32.zip

Source should be https://github.com/slimcoin-project/Slimcoin/tree/master

CPU load in my case is 1 %. If you use PoS than client is CPU intensive

[gavrilo77]

Answer from Tradesatoshi

"Hi gavrilo77,

Direct coin listing fee its 0.5 BTC. The coin needs to be a bitcoin clone with similar RPC api. Coins with different APIs has other prices"

[Sam123]

How can I staking ?
I have coins in my wallet (open) but I was never able to stake.
I already did in the console  and type "walletpassphrase yourpass 999999999999"

[gavrilo77]

How can I staking ?
I have coins in my wallet (open) but I was never able to stake.
I already did in the console  and type "walletpassphrase yourpass 999999999999"

put in console "reservebalance true 1" for example

[eddycurrent]

Hello all,

Here is the link for the latest ARMv7 binarys:

https://drive.google.com/open?id=1IDaf4BD2SL0_RJxdp0CZNU7-4aR0EL5x

Regards

[almightyruler]

How can I staking ?
I have coins in my wallet (open) but I was never able to stake.
I already did in the console  and type "walletpassphrase yourpass 999999999999"

put in console "reservebalance true 1" for example

Unless slimcoin does it differently, the correct command would be "reservebalance false"

[d5000]

Has there been a hard fork since then? My (old) client is syncing (slowly) but if there's been a hard fork there's not much point.

If you are using version 0.2, I mean to remember there was a hard fork to transition to 0.3 because the consensus algorithm was changed - however, I'm not sure. Version 0.3 is the last one published by the "original developer" in 2014. Since then, there were no hard forks - only soft forks. So with 0.3.x you should be fine - however, at least with Linux I have sync problems with this client, and with 0.4 and 0.5 this has definitively improved.

Is this the correct git rep? https://github.com/slimcoin-project/Slimcoin/

Yes. The most recent code is on the "master" branch. (There is an experimental 0.6 version but I think it's far from ready.)

(The hardened checkpoints in this source are very old.)

Thanks for reminding that. I could try to update it, but maybe gjhiggins (our current "main developer") anyway wants to renew it for the next version.

BTW, the client seems to be using a crapload of CPU. Load was past 9 on a four core server (that's more than 200% load). Once I stopped slimcoind it went back down to 2.5 (62.5% load). Is this improved in the newer client source and/or is there a way to limit it to using one core only?

Yep, that is a known problem - staking needs much CPU power. You can set a high reservebalance to disable staking (at least temporarily) if the performance is a problem.

[almightyruler]

BTW, the client seems to be using a crapload of CPU. Load was past 9 on a four core server (that's more than 200% load). Once I stopped slimcoind it went back down to 2.5 (62.5% load). Is this improved in the newer client source and/or is there a way to limit it to using one core only?

Yep, that is a known problem - staking needs much CPU power. You can set a high reservebalance to disable staking (at least temporarily) if the performance is a problem.

No, this is with staking disabled. Looks like I had the same problem 3 years ago - just forgot I'd already experienced it.

https://bitcointalk.org/index.php?topic=613213.msg9182002#msg9182002

The client was basically taking over the entire server.

I'll give the current source a go.

[gavrilo77]

I am using two clients on one PC. CPU load 0.5-1.0%. One of the client is dedicated only for PoB
On second PC CPU load is max 0.5%
On third PC CPU load is max 0.5%
I am using the last build without staking

[gjhiggins]

I'll give the current source a go.

You might be able to speed up the syncing by moving your existing wallet to one side and letting it sync with an empty wallet. Otherwise, there is a nighlty datadir snapshot which might work (experiences vary):

https://minkiz.co/noodlings/slm/slm-datadir-snapshot.zip

The current version remains on test to allow me to discover all the bugs I've introduced.

Cheers

Graham

[eddycurrent]

Hello again,

ARMv5 binarys are up now (see link above)

Regards

[almightyruler]

I upgraded to the new source (master branch), and I'm now seeing this error when doing 'getinfo':

WARNING: Blockchain redownload required approaching or past v0.4 upgrade deadline.

This seems to imply there has been a hard fork since 0.3.x?

Current version is reported in a somewhat unusual way:

Slimcoin version vSLMCOIN_VERSION_MAJOR.SLMCOIN_VERSION_MINOR.SLMCOIN_VERSION_REVISION.SLMCOIN_V ERSION_BUILD-g154b52a-alpha ()

[gavrilo77]

I upgraded to the new source (master branch), and I'm now seeing this error when doing 'getinfo':

WARNING: Blockchain redownload required approaching or past v0.4 upgrade deadline.

This seems to imply there has been a hard fork since 0.3.x?

Current version is reported in a somewhat unusual way:

Slimcoin version vSLMCOIN_VERSION_MAJOR.SLMCOIN_VERSION_MINOR.SLMCOIN_VERSION_REVISION.SLMCOIN_V ERSION_BUILD-g154b52a-alpha ()

You should see something like this v0.5.0.0-g8e9fe2c-alpha. Do you use Windows or Linux?

[almightyruler]

You should see something like this v0.5.0.0-g8e9fe2c-alpha. Do you use Windows or Linux?

FreeBSD, compiled from source. I downloaded https://github.com/slimcoin-project/Slimcoin/archive/slimcoin.zip about half a day ago.

I restored the blockchain from a backup done in January 2015, but it's still showing the message. Guess I need to resync from scratch.

[GTTIGER]

Slim can use the HEAT exchange is someone knows how to set it up. https://bitcointalk.org/index.php?topic=1959885

[almightyruler]

I'm trying to sync from scratch with the current master, but my client seems to be progressively banning every node, because of errors like this:

Code:

2017-11-14 15:48:55 UTC received block 20f4e74f88f6f3b8a7bc
2017-11-14 15:48:55 UTC CBlock(hash=20f4e74f88f6f3b8a7bc, ver=1, hashPrevBlock=0000000fa61257904829, hashMerkleRoot=75e63f919b, nTime=1401358630, nBits=1d2eb643, nNonce=0, vtx=1, vchBlockSig=304402201ede3d80083db34e712389ba2a0d3ebfb27262341bba1cd59adccae30fc69217022069b8dec9b062db5046e0281c2264d8c28974c84a58cdf707f72e74d71d8dcc48)
2017-11-14 15:48:55 UTC CBlock General PoB(nBurnBits=1e243c7f nEffectiveBurnCoins=23149722 (formatted 23.149722))
2017-11-14 15:48:55 UTC CBlock Specific PoB(fProofOfBurn true, burnBlkHeight 523, burnCTx 6, burnCTxOut 1)
2017-11-14 15:48:55 UTC   Coinbase(hash=75e63f919b, nTime=1401358630, ver=1, vin.size=1, vout.size=1, nLockTime=0)
    CTxIn(COutPoint(0000000000, -1), coinbase 04260987530102062f503253482f)
    CTxOut(nValue=153.34, scriptPubKey=02734c43be100f26664777b5473adadc666798241d7d7e0daaf85c65797c5eb99a OP_CHECKSIG)
  vMerkleTree:
2017-11-14 15:48:55 UTC ERROR: CheckBlock() : coinbase reward exceeded 153.34 > 50.00
2017-11-14 15:48:55 UTC ERROR: ProcessBlock() : CheckBlock FAILED
2017-11-14 15:48:55 UTC disconnecting node 203.59.19.234:58643
2017-11-14 15:48:55 UTC socket select error 9
2017-11-14 15:48:55 UTC Disconnected 203.59.19.234:58643 for misbehavior (score=100)

It has banned 20 different peers so far. It has only synced 530 blocks in 2 hours.

I'm not sure if (for example) 20f4e74f88f6f3b8a7bc is a block at the very start of the chain, or it's a peer offering a current block, which may be why it is being rejected. Could there be an issue with the code verifying very old blocks, performing post-0.4 validation on pre-0.4 blocks? Has anyone tried a sync from scratch with the current code?


----


Update: deleted the blockchain, it has stalled again at block 530:

Code:

2017-11-14 16:07:32 UTC SetBestChain: new best=0000000c805e33073348  height=530  trust=531  moneysupply=10490.80 nEffectiveBurnCoins=7.109914
2017-11-14 16:07:32 UTC ProcessBlock: ACCEPTED
2017-11-14 16:07:32 UTC received block cb1adbc10b7df830d01b
2017-11-14 16:07:32 UTC CBlock(hash=cb1adbc10b7df830d01b, ver=1, hashPrevBlock=0000000c805e33073348, hashMerkleRoot=e7a965efef, nTime=1401357962, nBits=1d331d49, nNonce=0, vtx=1, vchBlockSig=304402200cf99e01f0ff2beb278a549d59fff05132bf8c5b1d2102d84d135f8c58ed780d02206ab3fe330fb43e100d51afc732b9f71fa73d47e41277c7074191a18e5f3e025a)
2017-11-14 16:07:32 UTC CBlock General PoB(nBurnBits=1e75fc12 nEffectiveBurnCoins=7109914 (formatted 7.109914))
2017-11-14 16:07:32 UTC CBlock Specific PoB(fProofOfBurn true, burnBlkHeight 523, burnCTx 1, burnCTxOut 1)
2017-11-14 16:07:32 UTC   Coinbase(hash=e7a965efef, nTime=1401357962, ver=1, vin.size=1, vout.size=1, nLockTime=0)
    CTxIn(COutPoint(0000000000, -1), coinbase 048a0687530101062f503253482f)
    CTxOut(nValue=205.98, scriptPubKey=038a52f85595a8d8e7c1d8c256baeee2c9ea7ad0bf7fe534575be4eb47cdbf18f6 OP_CHECKSIG)
  vMerkleTree:
2017-11-14 16:07:32 UTC ERROR: CheckBlock() : coinbase reward exceeded 205.98 > 50.00
2017-11-14 16:07:32 UTC ERROR: ProcessBlock() : CheckBlock FAILED

The following block seems to link back to 530 (hashPrevBlock=0000000c805e33073348) but it is rejected by CheckBlock()

[gjhiggins]

Slimcoin version vSLMCOIN_VERSION_MAJOR.SLMCOIN_VERSION_MINOR.SLMCOIN_VERSION_REVISION.SLMCOIN_V ERSION_BUILD-g154b52a-alpha ()

The good news is that the above confirms you haven't actually been using the latest sources to compile from, which is possibly why the issues look familiar - we have an entirely different, fresh set of issues today .

git log should show the last commit hash as 7d4cacc05c31b3746a349923293cfe4358693e9c - the github default is unusual in that it isn't the master.

Cheers

Graham

[gjhiggins]

once i place the content of slm-datadir-blockfiles.zip in datadir , i cannot examine pocket book or do something , it states: Inchblockchain obtain requiredInch , there is a method to repair it?

Are you using: https://minkiz.co/noodlings/slm/slimcoin-qt-v0.5.1-win32.zip

Cheers

Graham