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

primer-

legendary

Activity: 1092

Merit: 1000

Quote from: silicon_chip on June 15, 2014, 08:09:27 AM

Quote from: primer- on June 15, 2014, 08:04:21 AM

I will be shutting off my nodes at block 16000. I'll archive it and keep it for the dev if he requests a copy. I would like to see sandor do the same, what we have now is just nonsense.

Time for a shutdown and rebuild.
What you have now is just another disaster in the making.
Power it down, hard fork it, then sync it back up. (After testing it properly.)

+1

silicon_chip

member

Activity: 64

Merit: 10

Quote from: primer- on June 15, 2014, 08:04:21 AM

I will be shutting off my nodes at block 16000. I'll archive it and keep it for the dev if he requests a copy. I would like to see sandor do the same, what we have now is just nonsense.

Time for a shutdown and rebuild.
What you have now is just another disaster in the making.
Power it down, hard fork it, then sync it back up. (After testing it properly.)

primer-

legendary

Activity: 1092

Merit: 1000

Quote from: rfcdejong on June 15, 2014, 08:08:35 AM

it seems the fix of the dev kicks in at block 17000 ?

+#define BURN_INTERMEDIATE_HEIGHT 17000

the question is what that really does, intermediate burn fix.

Probably NOTHING...

rfcdejong

hero member

Activity: 798

Merit: 500

it seems the fix of the dev kicks in at block 17000 ?

#define BURN_INTERMEDIATE_HEIGHT 17000

the question is what that really does, intermediate burn fix.

bitspender

hero member

Activity: 658

Merit: 500

Quote from: primer- on June 15, 2014, 08:04:21 AM

I will be shutting off my nodes at block 16000. I'll archive it and keep it for the dev if he requests a copy. I would like to see sandor do the same, what we have now is just nonsense.

3 wallets, all in perfect sync @ 15994..
So i should not shut it down yet

primer-

legendary

Activity: 1092

Merit: 1000

I will be shutting off my nodes at block 16000. I'll archive it and keep it for the dev if he requests a copy. I would like to see sandor do the same, what we have now is just nonsense.

AizenSou

hero member

Activity: 938

Merit: 1000

Quote from: bitspender on June 15, 2014, 07:59:06 AM

Who is the new monster with 1.01Mh at the pool???

Chinese farm according to sandor111.

bitspender

hero member

Activity: 658

Merit: 500

Who is the new monster with 1.01Mh at the pool???

primer-

legendary

Activity: 1092

Merit: 1000

Quote from: bitspender on June 15, 2014, 07:58:07 AM

I'm at 15978

You are there now but you will go out of sync sooner or later.

bitspender

hero member

Activity: 658

Merit: 500

I'm at 15978

AizenSou

hero member

Activity: 938

Merit: 1000

Quote from: primer- on June 15, 2014, 07:47:24 AM

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.

primer-

legendary

Activity: 1092

Merit: 1000

Quote from: rfcdejong on June 15, 2014, 07:53:53 AM

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.

bitspender

hero member

Activity: 658

Merit: 500

Quote from: primer- on June 15, 2014, 07:47:24 AM

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

rfcdejong

hero member

Activity: 798

Merit: 500

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)

primer-

legendary

Activity: 1092

Merit: 1000

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.

bitspender

hero member

Activity: 658

Merit: 500

Quote from: primer- on June 15, 2014, 07:26:08 AM

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-

legendary

Activity: 1092

Merit: 1000

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.

primer-

legendary

Activity: 1092

Merit: 1000

Its happening again ...

{
"blocks" : 15931,

it was 16xxx...

primer-

legendary

Activity: 1092

Merit: 1000

Quote from: AizenSou on June 15, 2014, 07:09:10 AM

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. Grin

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-

legendary

Activity: 1092

Merit: 1000

Quote from: jadefalke on June 15, 2014, 07:17:52 AM

sandor is you pool down?

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

Topic: [ANN] Slimcoin : Proof of Burn NEW BLOCK GEN, Mineable by low power computer! - page 98. (Read 284956 times)