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

[SpeedDemon13]

Block propagation in slimcoin is broken, always was. Even if you all sync up to the same chain (very unlikely as there are over 100 forks), it will fork again.
Bulgarian hardcoded node was keeping things in check, the moment it was shut off slim forked.

You will need to fix the block propagation issue first. Good luck!

Understood, someone should try to pick up the task to repair it.

I checked the nodes posted above:
54.191.247.114 is at 66270

Code:

SetBestChain: new best=60133ce7ffbf9f49b6f6  height=66270  trust=112643180633  moneysupply=624240.386373 nEffectiveBurnCoins=200544.329924

69.172.231.56 stuck at 65494 few hours ago on other fork.
Other nodes are offline.

If you know other forks at similar height and trust value - post their nodes.

Code:

addnode=54.191.247.114
addnode=112.113.96.138:41682
addnode=112.113.96.138:41683
addnode=112.113.96.138:41686

I ended up using these nodes and sync fine, seem like the pools aren't on the same fork.

[mbk]

I cannot connect to 112.113.96.138 on any port so I guess you use only 54.191.247.114 node. All 3 pools linked from the start page are offline so let's keep them out of equation.

Block propagation in slimcoin is broken, always was. Even if you all sync up to the same chain (very unlikely as there are over 100 forks), it will fork again.
Bulgarian hardcoded node was keeping things in check, the moment it was shut off slim forked.

You will need to fix the block propagation issue first. Good luck!

Understood, someone should try to pick up the task to repair it.

I checked the nodes posted above:
54.191.247.114 is at 66270

Code:

SetBestChain: new best=60133ce7ffbf9f49b6f6  height=66270  trust=112643180633  moneysupply=624240.386373 nEffectiveBurnCoins=200544.329924

69.172.231.56 stuck at 65494 few hours ago on other fork.
Other nodes are offline.

If you know other forks at similar height and trust value - post their nodes.

Code:

addnode=54.191.247.114
addnode=112.113.96.138:41682
addnode=112.113.96.138:41683
addnode=112.113.96.138:41686

I ended up using these nodes and sync fine, seem like the pools aren't on the same fork.

[SpeedDemon13]

I cannot connect to 112.113.96.138 on any port so I guess you use only 54.191.247.114 node. All 3 pools linked from the start page are offline so let's keep them out of equation.

Block propagation in slimcoin is broken, always was. Even if you all sync up to the same chain (very unlikely as there are over 100 forks), it will fork again.
Bulgarian hardcoded node was keeping things in check, the moment it was shut off slim forked.

You will need to fix the block propagation issue first. Good luck!

Understood, someone should try to pick up the task to repair it.

I checked the nodes posted above:
54.191.247.114 is at 66270

Code:

SetBestChain: new best=60133ce7ffbf9f49b6f6  height=66270  trust=112643180633  moneysupply=624240.386373 nEffectiveBurnCoins=200544.329924

69.172.231.56 stuck at 65494 few hours ago on other fork.
Other nodes are offline.

If you know other forks at similar height and trust value - post their nodes.

Code:

addnode=54.191.247.114
addnode=112.113.96.138:41682
addnode=112.113.96.138:41683
addnode=112.113.96.138:41686

I ended up using these nodes and sync fine, seem like the pools aren't on the same fork.

So, it's best just to solo mine? From the standalone miner or the one in the wallet?

[almightyruler]

So, it's best just to solo mine? From the standalone miner or the one in the wallet?

Mining is pot luck at the moment. You could solo mine, but there's no guarantee that the chain you're on will necessarily be accepted (by community consensus and/or the dev) as the official one. Your client could even end up starting its own private fork.

I just restarted the client and it's obvious from the small number of peers I've connected to that there are multiple forks (I've had a go at labelling them below)

Code:

2014-08-13 00:31:54 UTC Slimcoin version v0.3.2.0-g154b52a-alpha ()
2014-08-13 00:32:10 UTC version message: version 60003, blocks=66461      ** (1)
2014-08-13 00:32:39 UTC version message: version 60003, blocks=63435      ** (2)
2014-08-13 00:32:45 UTC version message: version 60003, blocks=16014      ** (3)
2014-08-13 00:35:22 UTC version message: version 60003, blocks=66462      ** (1)
2014-08-13 00:35:47 UTC version message: version 60003, blocks=26934      ** (4)
2014-08-13 00:36:44 UTC version message: version 60003, blocks=30183      ** (5)
2014-08-13 00:38:57 UTC version message: version 60003, blocks=66465      ** (1)
2014-08-13 00:39:23 UTC version message: version 60003, blocks=15164      ** (6)
2014-08-13 00:43:52 UTC version message: version 60003, blocks=64907      ** (7)
2014-08-13 00:46:49 UTC version message: version 60003, blocks=26940      ** (4)

[primer-]

[Cobra]

Block propagation in slimcoin is broken, always was. Even if you all sync up to the same chain (very unlikely as there are over 100 forks), it will fork again.
Bulgarian hardcoded node was keeping things in check, the moment it was shut off slim forked.

You will need to fix the block propagation issue first. Good luck!

You have been saying this for about 20 pages now, the Dev must have got the message by now. You repeat the same things on every page that it is dead and you are moving on. (after you have made profit by dumping slim) yet you continue to follow the thread and post often....good thing you are sticking around to "look out for people".  While the coin currently has some problems what is to say a dedicated community cannot overcome these obstacles and get it back on track? Some unique features exist here which makes it worth saving.

Edit: If the Dev doesn't show up to address the situation with the forks it very well could be over. I was just saying it is not over yet and options exist. Dev's can always change hands, example would be what happened with Asiacoin a while back. In an over saturated alt coin market some people may rather move on versus save this.  I guess we will see soon.

[rfcdejong]

I think slimcoin went on vacation for a week or maybe two, he doesn't even know about the current forks.

Last Active:   August 08, 2014, 12:38:00 PM


And perhaps his nodes went down as well..

[95A31]

I think slimcoin went on vacation for a week or maybe two, he doesn't even know about the current forks.

Last Active:   August 08, 2014, 12:38:00 PM


And perhaps his nodes went down as well..

I think too. I am working on PoB pool and he stop reply to my questions from 8th August. Anyway, the code is almost done, I am looking for testers 

[rfcdejong]

I was on a big fork until my wallet crashed, high nr of blocks, diff reasonable and networkghps reasonable.

"blocks" : 68556,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.03609960,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkghps" : 0.00108424,
"pooledtx" : 1,
"testnet" : false
}

[rfcdejong]

Seems the network is stabilizing itself, i don't have any sync problems anymore

01:24:50
{
"blocks" : 69279,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.04104161,
"errors" : "",
"generate" : true,
"genproclimit" : -1,
"hashespersec" : 3234,
"networkghps" : 0.00169493,
"pooledtx" : 1,
"testnet" : false
}

[m5j0r]

My getmininginfo always gives me this:

Code:

{
"blocks" : 69328,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.04002995,
"errors" : "WARNING: Checkpoint is too old. Wait for block chain to download, or notify developers of the issue.",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkghps" : 0.00138651,
"pooledtx" : 1,
"testnet" : false
}

Is that warning okay?

I run with

Code:

-maxconnections=1 -connect=54.191.247.114

for some odd reason it also says I have 0 connections. I seem to get the latest blocks though....

How should you run this now?

[Zels]

Why do you keep trying this coin when DEV run away, fork everywhere, wallet bugs, etc 

[rfcdejong]

Why do you keep trying this coin when DEV run away, fork everywhere, wallet bugs, etc 

DEV seems to be on vacation, maybe it's the same DEV as GUE because he also is away since 8-8 ?
And about the fork, it seems it solved itself, my wallets are all on the same block with just the regular .conf, they aren't out of sync anymore.
A fork won't happen that fast if there are more nodes, people just need to keep their wallets open and turn on listen=1 (if they can keep it open 24/7)

Stability comes when the group is larger, there are less wallet bugs since the last version, slimcoin did a good job except he should communicate more and better.

[primer-]

Why do you keep trying this coin when DEV run away, fork everywhere, wallet bugs, etc 

DEV seems to be on vacation, maybe it's the same DEV as GUE because he also is away since 8-8 ?
And about the fork, it seems it solved itself, my wallets are all on the same block with just the regular .conf, they aren't out of sync anymore.
A fork won't happen that fast if there are more nodes, people just need to keep their wallets open and turn on listen=1 (if they can keep it open 24/7)

Stability comes when the group is larger, there are less wallet bugs since the last version, slimcoin did a good job except he should communicate more and better.

Its over you idiot. Go find some other shitcoin to support, this one is dead.

[-Greed-]

Where are you, dev? We need you to get bugs fixed.

Its over you idiot. Go find some other shitcoin to support, this one is dead.

Welcome to my ignore list! (c) smaragda

[slimcoin]

The reason for my hiatus was that I was indeed away on vacation. I could not take my computer, and subsequently, could not write from there. I am currently investigating the issue with the fork.

I have not abandoned Slimcoin.

[-Greed-]

The reason for my hiatus was that I was indeed away on vacation. I could not take my computer, and subsequently, could not write from there. I am currently investigating the issue with the fork.

I have not abandoned Slimcoin.

Good news. Keep working on SLM.

[m5j0r]

I have tried to send 5 SLM to bter to see if I'm on the right fork. Did not arrive even after 24h.
I have burnt about 7000 SLM and dont get anything out of it. I've wasted money.

@dev: Fix this. Fast. Or you'll lose even the last investor.

[rfcdejong]

I'm still perfectly synced, on a good fork
1 wallet was confused a bit for a hour or two, but it's back on track now.

22:15:19
{
"blocks" : 69854,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.03342591,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkghps" : 0.00105561,
"pooledtx" : 1,
"testnet" : false
}

[m5j0r]

Happy that it works for you but I've lost my whole balance. It's ALL GONE.
If the dev comes up with a solution I would try it, but if not I'm gone and spreading the news so other investors don't get fucked in their arse by an incompetent dev.

Lost about 6000 SLM.