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

[primer-]

IF we are on block 16028 now, it worked like a charm.

Just make sure you follow instructions after the sync otherwise my node will crumble and will not sync others.

[primer-]

The latest wallet is also broken, new blocks are not propagating accross the network.

I've got two clients connected to my master node via connect= flag (only one connection, no incoming connections). One wallet is at the current block 16047 and the other at 16032. The master node is also off by one block when compared to slimcoinpool node.

Its a matter of time the network crumbles again. This needs to be fixed ASAP

EDIT: When you replace connect= with addnode= , you wont keep in sync anymore...

[sandor111]

EDIT: When you replace connect= with addnode= , you wont keep in sync anymore...

My nodes are all synced to latest block, using your addnodes.

[AizenSou]

I hope everyone makes a good earning through the mess last night, esp. primer- because he works so hard for this coin. To be honest his style is a little bit rude but I think that comes from his love for the coin, I even think that he loves Slimcoin more than the dev.  
Lastest wallet is still not working properly, indeed.

[bitspender]

The latest wallet is also broken, new blocks are not propagating accross the network.

I've got two clients connected to my master node via connect= flag (only one connection, no incoming connections). One wallet is at the current block 16047 and the other at 16032. The master node is also off by one block when compared to slimcoinpool node.

Its a matter of time the network crumbles again. This needs to be fixed ASAP

EDIT: When you replace connect= with addnode= , you wont keep in sync anymore...

Exactly the same problem here. One wallet | 16033, another @ 16049

[primer-]

EDIT: When you replace connect= with addnode= , you wont keep in sync anymore...

My nodes are all synced to latest block, using your addnodes.

No, my nodes are 'catching up' all the time because new block propagation does not work. You create blocks because you've got the largest hash power and my nodes are always at least 1 block behind your node (when looking at recently found blocks on slimcoinpool). Your node takes a looong time to propagate the new block to the entire network.

[jadefalke]

syncing up with Primers supernode via connect works great but as soon as i add the addnodes from OP im stuck

[primer-]

syncing up with Primers supernode via connect works great but as soon as i add the addnodes from OP im stuck

Yes, and if too many people leave the connect= flag, my node will crash and we'll have a new fork

[jadefalke]

sandor is you pool down?

[primer-]

sandor is you pool down?

Its not, you need to use the new ddos protected domain : pool.slimcoinpool.com:3333

[primer-]

I hope everyone makes a good earning through the mess last night, esp. primer- because he works so hard for this coin. To be honest his style is a little bit rude but I think that comes from his love for the coin, I even think that he loves Slimcoin more than the dev.  
Lastest wallet is still not working properly, indeed.

I'm doing it for the traders who bought 13btc worth of slm from me in the first 48 hours.

[primer-]

Its happening again ...

{
    "blocks" : 15931,


it was 16xxx...

[primer-]

Guys i know you dont want to hear this but i think we should halt everything at block 16000.

Sandor can shut his pool down and provide the dev with his blockchain database. Dev should then fix the wallet, update his OP nodes and release a new client.

[bitspender]

Guys i know you dont want to hear this but i think we should halt everything at block 16000.

Sandor can shut his pool down and provide the dev with his blockchain database. Dev should then fix the wallet, update his OP nodes and release a new client.

+1

[primer-]

No support for the halt@16000 ?

What we have now is one pool creating blocks and instamining. No other pool/solo miner can compete as by the time he receives the current block from the network its already old.
We might as well shut down our wallets and only point slimminer at the pool.

Take a look at blocks found by the pool vs total network hash rate. Network hash rate 4MH/s , pool hash rate 2MH/s. Pool getting 97% of all blocks.

Lets stop this at block 16000, send the dev the blockchain. Once the block propagation is fixed dev can load the blockchain on his OP nodes and release a new wallet.

[rfcdejong]

I agree with a hold until it's fixed, 16000 sounds good.

Anyway just a wild suggestion, we shouldn't touch the banning stuff other than just syncing a wallet which is far behind. Perhaps people are leaving it at 11111111 and 1. It is for banning misbehaving peers, the reason the blocks are jumping back all the time. The banscore should be 100 and bantime should be 86400 (the defaults from litecoin)

[bitspender]

No support for the halt@16000 ?

What we have now is one pool creating blocks and instamining. No other pool/solo miner can compete as by the time he receives the current block from the network its already old.
We might as well shut down our wallets and only point slimminer at the pool.

Take a look at blocks found by the pool vs total network hash rate. Network hash rate 4MH/s , pool hash rate 2MH/s. Pool getting 97% of all blocks.

Lets stop this at block 16000, send the dev the blockchain. Once the block propagation is fixed dev can load the blockchain on his OP nodes and release a new wallet.

I'm in sync with the pool now

[primer-]

I agree with a hold until it's fixed, 16000 sounds good.

Anyway just a wild suggestion, we shouldn't touch the banning stuff other than just syncing a wallet which is far behind. Perhaps people are leaving it at 11111111 and 1. It is for banning misbehaving peers, the reason the blocks are jumping back all the time. The banscore should be 100 and bantime should be 86400 (the defaults from litecoin)

Is a bug in the wallet and the only way to overcome it is by increasing the ban treshhold. No one is misbehaving here, trying to hurt the network, its a bug.

[AizenSou]

No support for the halt@16000 ?

What we have now is one pool creating blocks and instamining. No other pool/solo miner can compete as by the time he receives the current block from the network its already old.
We might as well shut down our wallets and only point slimminer at the pool.

Take a look at blocks found by the pool vs total network hash rate. Network hash rate 4MH/s , pool hash rate 2MH/s. Pool getting 97% of all blocks.

Lets stop this at block 16000, send the dev the blockchain. Once the block propagation is fixed dev can load the blockchain on his OP nodes and release a new wallet.

I agree too. But the problem is there are some monsters still mining at slimcoinpool and I don't think they care enough to check this thread recently.
My wallet stops at 15921 using connect= from primer- . No addnode= is available. Slimcoinpool is already at block 15974. Are we fast enough to stop this? Dev is nowhere to find again.

[bitspender]

I'm at 15978