Slimcoin | First Proof of Burn currency | Decentralized Web

[d5000]

Tomorrow night (30/01) I'll start a testing round with the Proof of Donation token on the Peercoin testnet (Slimcoin port will be available as soon as I know if the SLM protocol will be updated to newer Bitcoin versions), which will last the whole next week at least, so there is plenty of time to participate. Those active at Discord will already know about it.

If someone more wants to participate: You need, for now, a Peercoin client (0.9) and sync the Testnet, Python 3.6+ (preferrably 3.9+) and preferrably a Linux/Unix system as in this case I can help more with the commands. I need one Peercoin Testnet address from you to send you a specific token so you can participate.

The client for the token is still command line only.

Instructions will be soon ready. More info in the Discord #token-concept channel.

[1714867629]

1714867629

[1714867629]

1714867629

[johnwhitestar]

More info in the Discord #token-concept channel.

Just a quick update: I've changed the name of the above mentioned channel from #token-concept into #pod-token.
The PoD token is not just a concept any more!

[keliokan]

Hi all,
Would it be possible to get a backup of the blockchain (last 24h).
Cannot get a sync on the proper chain since 2 days...

thanks for all

K.

[PeterColumboFalk]

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

Code:

ftp://185.150.190.19/chain-slm.slimcoin_v0.6.0_d21-02-23.tgz

[keliokan]

thanks ,
but i am still stuck... on the wrong fork ...

version" : "v0.6.0.0-g8e9fe2c-alpha",
"protocolversion" : 60003,
"walletversion" : 60000,
"balance" : 0.00000000,
"newmint" : 0.00000000,
"stake" : 0.00000000,
"blocks" : 2361332,
"moneysupply" : 31269419.60113800,
"burnt" : 3294521.17335400,
"connections" : 5,
"proxy" : "",
"ip" : "",
"difficulty" : 0.00028735,
"testnet" : false,
"keypoololdest" : 1614100772,
"keypoolsize" : 101,
"paytxfee" : 0.10000000,
"errors" : ""
}

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

Code:

ftp://185.150.190.19/chain-slm.slimcoin_v0.6.0_d21-02-23.tgz

[johnwhitestar]

thanks ,
but i am still stuck... on the wrong fork ...

Sorry I haven't seen your message here, but have answered you on Discord.

Hope you've solved  

[keliokan]

Hello,
Actually there is two blockchain

And the fork occured on the block 2359430

CRYPTOID up to block 2363850

"hash": "00000007c598931395e001b70dd1ead07f608830d6e825e37affad9bf980b926",
"size": 355,
"height": 2359430,
"version": 1,
"merkleroot": "0b13811c847560bcca8755fdab4937d4d1ff6352abbc2fe966bcb8594b9dc3d0",
"time": "2021-02-21 11:10:05 UTC",
"nonce": 2907675455,
"bits": "1d13f3aa",
"difficulty": 0.05011999,
"mint": 13.2,
"burnt": 0,
"previousblockhash": "00000013331b4306bb43e4c7277a23f3451a933b2b05baf3cbe5c771795b96a4",
"nextblockhash": "551a719e41680eb314a9428ad57c3812279ed07c89736665c33c12ea66134107",
"flags": "proof-of-work",
"proofhash": "00000007c598931395e001b70dd1ead07f608830d6e825e37affad9bf980b926",
"entropybit": 0,
"modifier": "2b4d7a5adeb1c95e",
"modifierchecksum": "f5a56730",
"nEffectiveBurnCoins": "930763677620",
"Formatted nEffectiveBurnCoins": "930763.67762",
"nBurnBits": "1d00c247",
"tx": [
"0b13811c847560bcca8755fdab4937d4d1ff6352abbc2fe966bcb8594b9dc3d0"


And my wallet since few days

block 2359430

hash : fda366257a85ce867572807de2f43447464b3ef08e015ecf581d8203e0c22bd5
merkle : 194b80503a8a32a34d356c4953a7b21903f643632ca8dd04cc441cac0e67059d


which one is the good one ??

[johnwhitestar]

Hello,
Actually there is two blockchain

And the fork occured on the block 2359430

CRYPTOID up to block 2363850

"hash": "00000007c598931395e001b70dd1ead07f608830d6e825e37affad9bf980b926",
"size": 355,
"height": 2359430,
"version": 1,
"merkleroot": "0b13811c847560bcca8755fdab4937d4d1ff6352abbc2fe966bcb8594b9dc3d0",
"time": "2021-02-21 11:10:05 UTC",
"nonce": 2907675455,
"bits": "1d13f3aa",
"difficulty": 0.05011999,
"mint": 13.2,
"burnt": 0,
"previousblockhash": "00000013331b4306bb43e4c7277a23f3451a933b2b05baf3cbe5c771795b96a4",
"nextblockhash": "551a719e41680eb314a9428ad57c3812279ed07c89736665c33c12ea66134107",
"flags": "proof-of-work",
"proofhash": "00000007c598931395e001b70dd1ead07f608830d6e825e37affad9bf980b926",
"entropybit": 0,
"modifier": "2b4d7a5adeb1c95e",
"modifierchecksum": "f5a56730",
"nEffectiveBurnCoins": "930763677620",
"Formatted nEffectiveBurnCoins": "930763.67762",
"nBurnBits": "1d00c247",
"tx": [
"0b13811c847560bcca8755fdab4937d4d1ff6352abbc2fe966bcb8594b9dc3d0"


And my wallet since few days

block 2359430

hash : fda366257a85ce867572807de2f43447464b3ef08e015ecf581d8203e0c22bd5
merkle : 194b80503a8a32a34d356c4953a7b21903f643632ca8dd04cc441cac0e67059d


which one is the good one ??

I'm on the block  2362944 but my wallet keeps moving so I suppose it will reach the cryptoID value at some point.

If your wallet doesn't move for more than 48 hours and restarting doesn't help and the snapshots are not of any use, maybe you should resync from zero, deleting the blockchain you have.
Usually I do like that.
Or you can try to synchronize from the oldest snapshot available:

Code:

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

Another idea can be, if my server reaches the cryptoId height maybe you can connect directly? Don't really know whether it can work like that, though.

By the way, is possible that it's a firewall issue?

Which version of wallet do you use?

The blockchain seems to move very fast right now.

Another possible issue can be that you don't have enough resources on your computer. How much RAM do you have?

Seems like you are about 6 days behind. But we are experiencing a sudden drop of difficulty... strange.

[keliokan]

Thanks for your reply,
i do have 16gb of ram so i do not think that is the issue.
It is just that actually none of my blocks correspond to the CryptoID blockchain after 2359429.

So even if in can still catch up i am on the wrong chain will a lot of other users i guess.

I tried many times to resynch but still get to the same chain at the end.



"Seems like you are about 6 days behind. But we are experiencing a sudden drop of difficulty, strange."

Could be because of a fork.

I am pretty sure if you check your blockhash after the block 2359429 they will not fit with the one in CryptoID.

[johnwhitestar]

Thanks for your reply,
i do have 16gb of ram so i do not think that is the issue.
It is just that actually none of my blocks correspond to the CryptoID blockchain after 2359429.

So even if in can still catch up i am on the wrong chain will a lot of other users i guess.

I tried many times to resynch but still get to the same chain at the end.



"Seems like you are about 6 days behind. But we are experiencing a sudden drop of difficulty, strange."

Could be because of a fork.

I am pretty sure if you check your blockhash after the block 2359429 they will not fit with the one in CryptoID.

Usually the longest chain wins, so they should be on the right one and our wallets will need to get there somehow.

But the fact they have 0 difficulty right now means that the miners are on the other chain.

So both hypothesis can be the right ones.

Do you have connections? Your wallet reports to be synchronized? Are you able to send coins?

[keliokan]

Thanks for your reply,
i do have 16gb of ram so i do not think that is the issue.
It is just that actually none of my blocks correspond to the CryptoID blockchain after 2359429.

So even if in can still catch up i am on the wrong chain will a lot of other users i guess.

I tried many times to resynch but still get to the same chain at the end.



"Seems like you are about 6 days behind. But we are experiencing a sudden drop of difficulty, strange."

Could be because of a fork.

I am pretty sure if you check your blockhash after the block 2359429 they will not fit with the one in CryptoID.

Usually the longest chain wins, so they should be on the right one and our wallets will need to get there somehow.

But the fact they have 0 difficulty right now means that the miners are on the other chain.

So both hypothesis can be the right ones.

Do you have connections? Your wallet reports to be synchronized? Are you able to send coins?

I have connection and the wallet is synchronised (2362937) i cannot send coin to freiexchange for example.

[johnwhitestar]

Thanks for your reply,
i do have 16gb of ram so i do not think that is the issue.
It is just that actually none of my blocks correspond to the CryptoID blockchain after 2359429.

So even if in can still catch up i am on the wrong chain will a lot of other users i guess.

I tried many times to resynch but still get to the same chain at the end.



"Seems like you are about 6 days behind. But we are experiencing a sudden drop of difficulty, strange."

Could be because of a fork.

I am pretty sure if you check your blockhash after the block 2359429 they will not fit with the one in CryptoID.

Usually the longest chain wins, so they should be on the right one and our wallets will need to get there somehow.

But the fact they have 0 difficulty right now means that the miners are on the other chain.

So both hypothesis can be the right ones.

Do you have connections? Your wallet reports to be synchronized? Are you able to send coins?

I have connection and the wallet is synchronised (2362937) i cannot send coin to freiexchange for example.

I'll try to start my local wallet to see what will happen.

[keliokan]

Thanks for your help

Thanks for your reply,
i do have 16gb of ram so i do not think that is the issue.
It is just that actually none of my blocks correspond to the CryptoID blockchain after 2359429.

So even if in can still catch up i am on the wrong chain will a lot of other users i guess.

I tried many times to resynch but still get to the same chain at the end.



"Seems like you are about 6 days behind. But we are experiencing a sudden drop of difficulty, strange."

Could be because of a fork.

I am pretty sure if you check your blockhash after the block 2359429 they will not fit with the one in CryptoID.

Usually the longest chain wins, so they should be on the right one and our wallets will need to get there somehow.

But the fact they have 0 difficulty right now means that the miners are on the other chain.

So both hypothesis can be the right ones.

Do you have connections? Your wallet reports to be synchronized? Are you able to send coins?

I have connection and the wallet is synchronised (2362937) i cannot send coin to freiexchange for example.

I'll try to start my local wallet to see what will happen.

[gjhiggins]

Hello,
Actually there is two blockchain

And the fork occured on the block 2359430

which one is the good one ??

It's unclear to say the least. This is the (edited for brevity) result from my server‘s (blockheight 2362964) getpeerinfo:

Code:

[
    {
        "addr" : "185.150.190.19:41682",
        "subver" : "/Satoshi:0.6.5/SLIMCoin:0.6.0(v0.6.0.0-g8e9fe2c-alpha)/",
        "inbound" : false,
        "height" : 2362598,
    },
    {
        "addr" : "185.68.67.37:41682",
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(SLMv0.5.0-15-g2668a530-alpha)/",
        "inbound" : false,
        "height" : 2363859,
    },

    {
        "addr" : "178.223.55.155:53184",
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "height" : 2363828,
    },
    {
        "addr" : "178.223.55.155:56231",
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "height" : 2363843,
    },
    {
        "addr" : "5.39.70.87:33984",
        "subver" : "/Satoshi:0.6.5/SLIMCoin:0.6.0(v0.6.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "height" : 2362598,
    },
    {
        "addr" : "185.79.5.221:53014",
        "subver" : "/Satoshi:0.6.3/SLIMCoin:0.4.0(v0.4.0.0-g154b52a-alpha)/",
        "inbound" : true,
        "height" : 2363717,
    },
    {
        "addr" : "145.239.189.106:53042",
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(SLMv0.5.0-50-g3c9b8e9-dirty-alpha)/",
        "inbound" : true,
        "height" : 2363845,
    },
    {
        "addr" : "178.221.183.154:9715",
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "height" : 2363767,
    },
    {
        "addr" : "212.125.247.58:49560",
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "height" : 2363719,
    },
    {
        "addr" : "178.221.183.154:9964",
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "height" : 2363720,
    },
    {
        "addr" : "46.0.192.98:60366",
        "subver" : "/Satoshi:0.6.5/SLIMCoin:0.6.0(v0.6.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "height" : 2362598,
    },
    {
        "addr" : "109.10.108.52:63146",
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "height" : 1265308,
    },
    {
        "addr" : "178.223.55.155:64890",
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "height" : 2363689,
    },
    {
        "addr" : "178.223.55.155:64902",
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "height" : 2363689,
    },
    {
        "addr" : "94.25.174.181:39989",
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "height" : 2363729,
    },
    {
        "addr" : "91.250.62.26:57117",
        "subver" : "/Satoshi:0.6.5/SLIMCoin:0.6.0(v0.6.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "height" : 2328476,
    },
    {
        "addr" : "18.191.168.158:61845",
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "height" : 2287922,
    },
]

Cheers

Graham

[johnwhitestar]

Hello,
Actually there is two blockchain

And the fork occured on the block 2359430

which one is the good one ??

It's unclear to say the least. This is the (edited for brevity) result from my server‘s (blockheight 2362964) getpeerinfo:

Code:

[
    {
        "addr" : "185.150.190.19:41682",
        "subver" : "/Satoshi:0.6.5/SLIMCoin:0.6.0(v0.6.0.0-g8e9fe2c-alpha)/",
        "inbound" : false,
        "height" : 2362598,
    },
    {
        "addr" : "185.68.67.37:41682",
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(SLMv0.5.0-15-g2668a530-alpha)/",
        "inbound" : false,
        "height" : 2363859,
    },

    {
        "addr" : "178.223.55.155:53184",
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "height" : 2363828,
    },
    {
        "addr" : "178.223.55.155:56231",
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "height" : 2363843,
    },
    {
        "addr" : "5.39.70.87:33984",
        "subver" : "/Satoshi:0.6.5/SLIMCoin:0.6.0(v0.6.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "height" : 2362598,
    },
    {
        "addr" : "185.79.5.221:53014",
        "subver" : "/Satoshi:0.6.3/SLIMCoin:0.4.0(v0.4.0.0-g154b52a-alpha)/",
        "inbound" : true,
        "height" : 2363717,
    },
    {
        "addr" : "145.239.189.106:53042",
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(SLMv0.5.0-50-g3c9b8e9-dirty-alpha)/",
        "inbound" : true,
        "height" : 2363845,
    },
    {
        "addr" : "178.221.183.154:9715",
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "height" : 2363767,
    },
    {
        "addr" : "212.125.247.58:49560",
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "height" : 2363719,
    },
    {
        "addr" : "178.221.183.154:9964",
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "height" : 2363720,
    },
    {
        "addr" : "46.0.192.98:60366",
        "subver" : "/Satoshi:0.6.5/SLIMCoin:0.6.0(v0.6.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "height" : 2362598,
    },
    {
        "addr" : "109.10.108.52:63146",
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "height" : 1265308,
    },
    {
        "addr" : "178.223.55.155:64890",
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "height" : 2363689,
    },
    {
        "addr" : "178.223.55.155:64902",
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "height" : 2363689,
    },
    {
        "addr" : "94.25.174.181:39989",
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "height" : 2363729,
    },
    {
        "addr" : "91.250.62.26:57117",
        "subver" : "/Satoshi:0.6.5/SLIMCoin:0.6.0(v0.6.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "height" : 2328476,
    },
    {
        "addr" : "18.191.168.158:61845",
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(v0.5.0.0-g8e9fe2c-alpha)/",
        "inbound" : true,
        "height" : 2287922,
    },
]

Cheers

Graham

Here is what I have:

Code:

[
    {
        "addr" : "185.150.190.19:41682",
        "subver" : "/Satoshi:0.6.5/SLIMCoin:0.6.0(v0.6.0.0-g8e9fe2c-alpha)/",
        "inbound" : false,
        "height" : 2362151,
    },
    {
        "addr" : "145.239.189.106:41682",
        "subver" : "/Satoshi:0.6.4/SLIMCoin:0.5.0(SLMv0.5.0-50-g3c9b8e9-dirty-alpha)/",
        "height" : 2363689,
        "banscore" : 0
    },
    {
        "addr" : "144.76.118.44:41682",
        "subver" : "/Satoshi:0.6.6/SLIMCoin:0.6.0(SLMv0.5.0-253-gdffb8f27-dirty-alpha)/",
        "inbound" : false,
        "height" : 2362597,
    },
    {
        "addr" : "185.68.67.37:41682",
        "subver" : "",
        "inbound" : false,
        "height" : -1,
    }
]

Seems like cryptoId version of blockchain is far ahead.

They are stuck right now, by the way, since 21 minutes.

Their 0 difficulty blockchain has begun around block 2363620

So it's possible we have 3 blockchains right now, the longest one is that of cryptoId, the second one is around the block 2363689 (I suppose is the right one) and another one @keliokan is stuck on.

The cryptoId blockchain is moving though.

My server seems to be on the same fork @keliokan is, but my blockchain keeps moving.

Maybe the servers will agree at some point which blockchain is the right one.

I'm waiting my local wallet to start, it requires a lot of time, though.

[keliokan]

It has been few days,
It is possible to reach a consensus on different chains so far in time or it is a kind of a hard fork ?

[johnwhitestar]

It has been few days,
It is possible to reach a consensus on different chains so far in time or it is a kind of a hard fork ?

I think the consensus will be reached.

I suppose it's because we don't have many servers constantly online that we have these issues.

I'm going to setup another one these days.

[gjhiggins]

Seems like cryptoId version of blockchain is far ahead.

Interesting that their 2364xxx total blocks doesn't show up for any of my node's peers:

Code:

"addr" : "185.150.190.19:41682",    "height" : 2362598,
"addr" : "185.68.67.37:41682",      "height" : 2363859,
"addr" : "178.223.55.155:53184",    "height" : 2363828,
"addr" : "178.223.55.155:56231",    "height" : 2363843,
"addr" : "5.39.70.87:33984",        "height" : 2362598,
"addr" : "185.79.5.221:53014",      "height" : 2363717,
"addr" : "145.239.189.106:53042",   "height" : 2363845,
"addr" : "178.221.183.154:9715",    "height" : 2363767,
"addr" : "212.125.247.58:49560",    "height" : 2363719,
"addr" : "178.221.183.154:9964",    "height" : 2363720,
"addr" : "46.0.192.98:60366",       "height" : 2362598,
"addr" : "178.223.55.155:64890",    "height" : 2363689,
"addr" : "178.223.55.155:64902",    "height" : 2363689,
"addr" : "94.25.174.181:39989",     "height" : 2363729,
"addr" : "91.250.62.26:57117",      "height" : 2328476,
"addr" : "18.191.168.158:61845",    "height" : 2287922,
"addr" : "144.76.64.49:37520",      "height" : 2361253,
"addr" : "109.10.108.52:56155",     "height" : 1340151,

[johnwhitestar]

Seems like cryptoId version of blockchain is far ahead.

Interesting that their 2364xxx total blocks doesn't show up for any of my node's peers:

Code:

"addr" : "185.150.190.19:41682",    "height" : 2362598,
"addr" : "185.68.67.37:41682",      "height" : 2363859,
"addr" : "178.223.55.155:53184",    "height" : 2363828,
"addr" : "178.223.55.155:56231",    "height" : 2363843,
"addr" : "5.39.70.87:33984",        "height" : 2362598,
"addr" : "185.79.5.221:53014",      "height" : 2363717,
"addr" : "145.239.189.106:53042",   "height" : 2363845,
"addr" : "178.221.183.154:9715",    "height" : 2363767,
"addr" : "212.125.247.58:49560",    "height" : 2363719,
"addr" : "178.221.183.154:9964",    "height" : 2363720,
"addr" : "46.0.192.98:60366",       "height" : 2362598,
"addr" : "178.223.55.155:64890",    "height" : 2363689,
"addr" : "178.223.55.155:64902",    "height" : 2363689,
"addr" : "94.25.174.181:39989",     "height" : 2363729,
"addr" : "91.250.62.26:57117",      "height" : 2328476,
"addr" : "18.191.168.158:61845",    "height" : 2287922,
"addr" : "144.76.64.49:37520",      "height" : 2361253,
"addr" : "109.10.108.52:56155",     "height" : 1340151,

I've noticed it as well. That's why I thought the right chain should be something around 2363689.

@keliokan I've asked Freiexchange to have a look what is their situation, they told me they'll restart their server to see whether you'll be able send funds there.

What version are you using?  

What if you begin from a snapshot again and directly connect your wallet to some of the servers mentioned above? Or at least you can add them as addnode in slimcoin.conf

I have this list in my slimcoin.conf:

Code:

addnode=173.249.10.97
addnode=176.105.8.51
addnode=178.223.23.40
addnode=212.125.247.58
addnode=94.25.169.230
addnode=94.25.171.63
addnode=109.10.108.52
addnode=161.53.40.94
addnode=176.9.139.126
addnode=185.104.185.123
addnode=24.232.14.196
addnode=91.250.62.26
addnode=185.68.67.37
addnode=85.212.150.250
addnode=46.101.235.143

Maybe you can add the following ones as well:

Code:

addnode=185.150.190.19
addnode=178.223.55.155:53184
addnode=185.79.5.221:53014
addnode=145.239.189.106:53042
addnode=178.221.183.154:9715
addnode=46.0.192.98:60366
addnode=94.25.174.181:39989

They are all up to date, but the majority of them are not on the standard ports, that's why maybe we have issues to connect to them.
Don't know whether it's the right thing to add the port in the slimcoin.conf specifically.

I'm restarting my server with this new addnode lines to see whether it will sync. (The local wallet hasn't started yet).

[keliokan]

I am actually using : v0.6.0.0-g8e9fe2c-alpha

K.

Seems like cryptoId version of blockchain is far ahead.

Interesting that their 2364xxx total blocks doesn't show up for any of my node's peers:

Code:

"addr" : "185.150.190.19:41682",    "height" : 2362598,
"addr" : "185.68.67.37:41682",      "height" : 2363859,
"addr" : "178.223.55.155:53184",    "height" : 2363828,
"addr" : "178.223.55.155:56231",    "height" : 2363843,
"addr" : "5.39.70.87:33984",        "height" : 2362598,
"addr" : "185.79.5.221:53014",      "height" : 2363717,
"addr" : "145.239.189.106:53042",   "height" : 2363845,
"addr" : "178.221.183.154:9715",    "height" : 2363767,
"addr" : "212.125.247.58:49560",    "height" : 2363719,
"addr" : "178.221.183.154:9964",    "height" : 2363720,
"addr" : "46.0.192.98:60366",       "height" : 2362598,
"addr" : "178.223.55.155:64890",    "height" : 2363689,
"addr" : "178.223.55.155:64902",    "height" : 2363689,
"addr" : "94.25.174.181:39989",     "height" : 2363729,
"addr" : "91.250.62.26:57117",      "height" : 2328476,
"addr" : "18.191.168.158:61845",    "height" : 2287922,
"addr" : "144.76.64.49:37520",      "height" : 2361253,
"addr" : "109.10.108.52:56155",     "height" : 1340151,

I've noticed it as well. That's why I thought the right chain should be something around 2363689.

@keliokan I've asked Freiexchange to have a look what is their situation, they told me they'll restart their server to see whether you'll be able send funds there.

What version are you using?  What if you begin from a snapshot again and directly connect your wallet to some of the servers mentioned above?