Slimcoin | First Proof of Burn currency | Decentralized Web

[johnwhitestar]

why dont u start paying gjhiggins guy for his work? This walton goggins fellow, or call him walton higgins, he is here to donate his life to u.

Had you more respect/regard, you might have questioned the reliability of your assumptions. I'm not for hire.

I thought so, this guy has made obviously some casual comment provided he is not a bot. 

[1715067583]

1715067583

[1715067583]

1715067583

[1715067583]

1715067583

[PeterColumboFalk]

I'm hosting slimcoin 0.6.0 on ubuntu 18.04.5 LTS now. Syncing was fast at the beginning, but now is stalling. This is the result of getpeerinfo. Very confusing, if I compare "hight" and "subver", for example. It's 21 active connections. Often there is hight 2277690, but some newer versions are ahead of this. chainz.cryptoid.info is on hight 2278847. None of my peers has the hight of cryptoid.

[
    {
        "addr" : "145.239.189.106:41682",
        "services" : "00000001",
        "lastsend" : 1606770016,
        "lastrecv" : 1606770016,
        "conntime" : 1606654945,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(SLMv0.5.0-50-g3c9b8e9-dirty-alpha)/",
        "inbound" : false,
        "releasetime" : 0,
        "height" : 2277690,
        "banscore" : 0
    },
    {
        "addr" : "185.68.67.37:43372",
        "services" : "00000001",
        "lastsend" : 1606770037,
        "lastrecv" : 1606770037,
        "conntime" : 1606655158,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(SLMv0.5.0-15-g2668a530-alpha)/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 2277690,
        "banscore" : 0
    },
    {
        "addr" : "116.63.151.19:40686",
        "services" : "00000001",
        "lastsend" : 1606770012,
        "lastrecv" : 1606770012,
        "conntime" : 1606655222,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.5/SLIMCoin:0.6.0(SLMv0.5.0-253-gdffb8f2-alpha)/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 2197245,
        "banscore" : 0
    },
    {
        "addr" : "173.249.10.97:48492",
        "services" : "00000001",
        "lastsend" : 1606769996,
        "lastrecv" : 1606769996,
        "conntime" : 1606666530,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 2277690,
        "banscore" : 0
    },
    {
        "addr" : "185.79.5.221:52597",
        "services" : "00000001",
        "lastsend" : 1606770000,
        "lastrecv" : 1606770000,
        "conntime" : 1606666872,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/SLIMCoin:0.4.0(v0.4.0.0-g154b52a-alpha)/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 2277690,
        "banscore" : 0
    },
    {
        "addr" : "178.220.205.186:57423",
        "services" : "00000001",
        "lastsend" : 1606769994,
        "lastrecv" : 1606769994,
        "conntime" : 1606687588,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 2277690,
        "banscore" : 0
    },
    {
        "addr" : "154.21.21.28:56305",
        "services" : "00000001",
        "lastsend" : 1606769995,
        "lastrecv" : 1606769995,
        "conntime" : 1606687611,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 2277690,
        "banscore" : 0
    },
    {
        "addr" : "165.228.111.200:47020",
        "services" : "00000001",
        "lastsend" : 1606769996,
        "lastrecv" : 1606769995,
        "conntime" : 1606696735,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(SLMv0.5.0-51-g5b12990-dirty-alpha)/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 2277690,
        "banscore" : 0
    },
    {
        "addr" : "193.148.18.59:26443",
        "services" : "00000001",
        "lastsend" : 1606770045,
        "lastrecv" : 1606770045,
        "conntime" : 1606698717,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 2277690,
        "banscore" : 0
    },
    {
        "addr" : "212.125.247.58:49283",
        "services" : "00000001",
        "lastsend" : 1606769994,
        "lastrecv" : 1606769994,
        "conntime" : 1606709552,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 2278005,
        "banscore" : 0
    },
    {
        "addr" : "144.76.118.44:50404",
        "services" : "00000001",
        "lastsend" : 1606768401,
        "lastrecv" : 1606768401,
        "conntime" : 1606714048,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.6/SLIMCoin:0.6.0(SLMv0.5.0-253-gdffb8f27-dirty-alpha)/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 2278011,
        "banscore" : 0
    },
    {
        "addr" : "79.101.173.253:57633",
        "services" : "00000001",
        "lastsend" : 1606769993,
        "lastrecv" : 1606769993,
        "conntime" : 1606714066,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 2278090,
        "banscore" : 0
    },
    {
        "addr" : "91.250.62.26:56312",
        "services" : "00000001",
        "lastsend" : 1606769995,
        "lastrecv" : 1606769995,
        "conntime" : 1606717314,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 2277687,
        "banscore" : 0
    },
    {
        "addr" : "90.188.3.212:57310",
        "services" : "00000001",
        "lastsend" : 1606769999,
        "lastrecv" : 1606769999,
        "conntime" : 1606736488,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 2278408,
        "banscore" : 0
    },
    {
        "addr" : "141.98.254.131:62510",
        "services" : "00000001",
        "lastsend" : 1606769075,
        "lastrecv" : 1606769075,
        "conntime" : 1606754662,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.5/SLIMCoin:0.6.0(v0.6.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 2278011,
        "banscore" : 0
    },
    {
        "addr" : "91.250.62.26:57038",
        "services" : "00000001",
        "lastsend" : 1606770011,
        "lastrecv" : 1606770004,
        "conntime" : 1606758365,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.5/SLIMCoin:0.6.0(v0.6.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 1071839,
        "banscore" : 0
    },
    {
        "addr" : "109.10.108.52:50320",
        "services" : "00000001",
        "lastsend" : 1606769995,
        "lastrecv" : 1606769994,
        "conntime" : 1606758932,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.5/SLIMCoin:0.6.0(v0.6.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 2278692,
        "banscore" : 0
    },
    {
        "addr" : "109.10.108.52:50588",
        "services" : "00000001",
        "lastsend" : 1606769995,
        "lastrecv" : 1606769995,
        "conntime" : 1606759030,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.5/SLIMCoin:0.6.0(v0.6.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 2278694,
        "banscore" : 0
    },
    {
        "addr" : "24.232.14.196:50225",
        "services" : "00000001",
        "lastsend" : 1606769995,
        "lastrecv" : 1606769995,
        "conntime" : 1606761464,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.3/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 2278723,
        "banscore" : 0
    },
    {
        "addr" : "46.101.235.143:47336",
        "services" : "00000001",
        "lastsend" : 1606769449,
        "lastrecv" : 1606769453,
        "conntime" : 1606765803,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.5/SLIMCoin:0.6.0(SLMv0.5.0-247-g242a106-alpha)/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 2197245,
        "banscore" : 0
    },
    {
        "addr" : "45.134.3.82:38166",
        "services" : "00000001",
        "lastsend" : 1606769919,
        "lastrecv" : 1606769919,
        "conntime" : 1606768115,
        "version" : 60003,
        "subver" : "/Satoshi:0.6.5/SLIMCoin:0.6.0(v0.6.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "releasetime" : 0,
        "height" : 2278011,
        "banscore" : 0
    }
]

[johnwhitestar]

I'm hosting slimcoin 0.6.0 on ubuntu 18.04.5 LTS now. Syncing was fast at the beginning, but now is stalling. This is the result of getpeerinfo. Very confusing, if I compare "hight" and "subver", for example. It's 21 active connections. Often there is hight 2277690, but some newer versions are ahead of this. chainz.cryptoid.info is on hight 2278847. None of my peers has the hight of cryptoid.

In my experience when you sync, the synchronization got stuck at some point and before it becomes more and more slow.

To avoid the issue I have a script that shuts down the wallet each hour and reopens it.

When the blockchain is synchronized there is no need to restart the wallet each hour, so my script just checks each hour whether the blockchain height has changed if it's the same then I restart the wallet.

You need to have enough RAM to do the above things, because with insufficient RAM it's possible your wallet won't even open in one hour (if you opt for restarting it each hour).
 

[casper77]

I'm hosting slimcoin 0.6.0 on ubuntu 18.04.5 LTS now. Syncing was fast at the beginning, but now is stalling. This is the result of getpeerinfo. Very confusing, if I compare "hight" and "subver", for example. It's 21 active connections. Often there is hight 2277690, but some newer versions are ahead of this. chainz.cryptoid.info is on hight 2278847. None of my peers has the hight of cryptoid.

In my experience when you sync, the synchronization got stuck at some point and before it becomes more and more slow.

To avoid the issue I have a script that shuts down the wallet each hour and reopens it.

When the blockchain is synchronized there is no need to restart the wallet each hour, so my script just checks each hour whether the blockchain height has changed if it's the same then I restart the wallet.

You need to have enough RAM to do the above things, because with insufficient RAM it's possible your wallet won't even open in one hour (if you opt for restarting it each hour).
 

it's time to share it

[PeterColumboFalk]

A script can be a workaround only. There must be a reason for such different heights, better to go deep into this. I wonder how exchange wirthdraws and deposits can be stable. Is it sure, that the freiexchange wallet is on the right chain?

I not yet had larger time lags on startup.

Indeed, restart helps, the blockchain download continues. I can serve a blockchain upload with an anonymous FTP server from my host now, in the format of a tar gzip.

Code:

ftp://185.150.190.19/chain-slm.slimcoin_v0.6.0_height-864618.tgz

The README file contains the md5sum for each file. The ftp URL becomes destructed by this forum software, so I show it as code. Copy and paste it into your internet browser simply.

[johnwhitestar]

A script can be a workaround only. There must be a reason for such different hights, better to go deep into this. I wonder how exchange wirthdraws and deposits can be stable. Is it sure, that the freiexchange wallet is on the right chain?

I not yet had larger time lags on startup.

I don't think the blockchain is splitting it's just a wallet issue - the wallet goes to "sleep" at some point, that's why restarting it makes it work again as it should.

This issue needs to be inspected into depth, I agree with you, but we don't have the core developer here, only contributors (formally) that are doing things when they feel stimulated somehow.

I'm looking for a dev and I'm ready to pay for his work, but for the moment apparently we've got no success with it.

it's time to share it

The code is very simple, I've created it for slimcoind, but I think it can be adopted for slimcoin-qt as well. Tell me if you need it adopted for slimcoin-qt.

Code:

#!/bin/bash

a=$(/root/Slimcoin/src/./slimcoind getinfo | grep blocks)
b=$(cat /home/stop_check)

if [[ "$a" == "$b" ]] 
then
/root/Slimcoin/src/./slimcoind stop 
fi
echo "$a" > /home/stop_check

The name of this script is slm-stop in my context and I have it in my home folder, so I've added the following line to crontab in order to activate it each hour:

Code:

5 * * * * /home/slm-stop

The above script closes slimcoind if it's stuck, the following one relaunches it, if it's down:

Code:

#!/bin/bash
PROCESSCOUNT=$(ps -ef |grep -v grep |grep -cw slimcoind)
if [ $PROCESSCOUNT -eq 0 ]; then
/root/Slimcoin/src/./slimcoind
fi

In my context its name is slm-check and I have it in my home folder.

To make it work I have the following line in crontab:

Code:

* * * * * /home/slm-check

It checks each minute whether slimcoind is up and relaunches it if it's not.

Indeed, restart helps, the blockchain download continues. I can serve a blockchain upload with an anonymous FTP server from my host now, in the format of a tar gzip.

Code:

ftp://185.150.190.19/chain-slm.slimcoin_v0.6.0_height-864618.tgz

The README file contains the md5sum for each file.

Thank you very much!

I'm not able to see the README file inside the compressed file you've mentioned. Am I missing something?

[johnwhitestar]

↑ Added the last line

[PeterColumboFalk]

↑ Added the last line

Move one directory up, there you find README and some other chains.

Code:

ftp://185.150.190.19/

I tried to use the windows chain with linux, but because of some database? incompatibilities it fails. This, the chains are for linux users primarily.

This is the most current slim chain:

Code:

ftp://185.150.190.19/chain-slm.slimcoin_v0.6.0_height-1212298.tgz

[casper77]

? ? ?

[johnwhitestar]

? ? ?

I'm probably not able to see the whole image and on bb.co it doesn't load from here, but seem like there is written "not enough space", right?

[casper77]

? ? ?

I'm probably not able to see the whole image and on bb.co it doesn't load from here, but seem like there is written "not enough space", right?

yes

[johnwhitestar]

? ? ?

I'm probably not able to see the whole image and on bb.co it doesn't load from here, but seem like there is written "not enough space", right?

yes

Do you have enough space on your disk?

[casper77]

? ? ?

I'm probably not able to see the whole image and on bb.co it doesn't load from here, but seem like there is written "not enough space", right?

yes

Do you have enough space on your disk?

i am asking on forum first, then i checking free space on hdd
just joke

7Gb is enough ?

[johnwhitestar]

It should be enough, still would you make an attempt to free a bit of space on your disk to see whether the issue is there?

Would you please copy-paste here the exact message you are seeing?

[casper77]

It should be enough, still would you make an attempt to free a bit of space on your disk to see whether the issue is there?

Would you please copy-paste here the exact message you are seeing?

EXCEPTION: 11DbException
Db::get: Not enough space
<path-to-exe> in ProcessMessages()

[johnwhitestar]

It should be enough, still would you make an attempt to free a bit of space on your disk to see whether the issue is there?

Would you please copy-paste here the exact message you are seeing?

EXCEPTION: 11DbException
Db::get: Not enough space
<path-to-exe> in ProcessMessages()

Is it possible that you were running another app that was using much RAM when you launched the wallet?

[casper77]

It should be enough, still would you make an attempt to free a bit of space on your disk to see whether the issue is there?
Would you please copy-paste here the exact message you are seeing?

EXCEPTION: 11DbException
Db::get: Not enough space
<path-to-exe> in ProcessMessages()

Is it possible that you were running another app that was using much RAM when you launched the wallet?

i confirm that the wallet consumes too many resources: CPU from time to time (especially during sync), RAM constantly (about 0.8 Gb)
i even forcibly limited its cpu priority
complaining about other applications is a big impudence on its part 

[johnwhitestar]

It should be enough, still would you make an attempt to free a bit of space on your disk to see whether the issue is there?
Would you please copy-paste here the exact message you are seeing?

EXCEPTION: 11DbException
Db::get: Not enough space
<path-to-exe> in ProcessMessages()

Is it possible that you were running another app that was using much RAM when you launched the wallet?

i confirm that the wallet consumes too many resources: CPU from time to time (especially during sync), RAM constantly (about 0.8 Gb)
i even forcibly limited its cpu priority
complaining about other applications is a big impudence on its part  

Yes the sync process is quite resource consuming, that's why using a snapshot is very useful here. Limiting resources doesn't help and leads to the messages you mentioned.

EDIT: you can limit resources your slimcoind (and even slimcoin-qt) uses by installing it in docker container.
I've just published the code on our discord channel, if you are curios:
slimcoind runs fine with 3 GB of RAM limit + 1 additional GB of swap (see on discord).
I guess slimcoin-qt would work fine with the same resources allocation as well.

[PeterColumboFalk]

This is the most current slim chain for linux, block 2290244 in accordance to the cryptoID explorer:

Code:

ftp://185.150.190.19/chain-slm.slimcoin_v0.6.0_20-12-12.tgz

[johnwhitestar]

This is the most current slim chain for linux, block 2290244 in accordance to the cryptoID explorer:

Code:

ftp://185.150.190.19/chain-slm.slimcoin_v0.6.0_20-12-12.tgz

Thank you! I was having some issue with synchronising these days. My node was stuck no matter how much I would restart it and even my own snapshots were not able to help me out.