Topic: [ANN] Slimcoin : Proof of Burn NEW BLOCK GEN, Mineable by low power computer! - page 99. (Read 284956 times)
June 15, 2014, 07:17:52 AM
sandor is you pool down?
June 15, 2014, 07:17:21 AM
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
June 15, 2014, 07:15:24 AM
syncing up with Primers supernode via connect works great but as soon as i add the addnodes from OP im stuck
June 15, 2014, 07:13:27 AM
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.
June 15, 2014, 07:13:22 AM
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...
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
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. 
Lastest wallet is still not working properly, indeed.
Lastest wallet is still not working properly, indeed.
June 15, 2014, 07:08:52 AM
EDIT: When you replace connect= with addnode= , you wont keep in sync anymore...
My nodes are all synced to latest block, using your addnodes.
June 15, 2014, 07:01:35 AM
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...
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...
June 15, 2014, 06:47:59 AM
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.
June 15, 2014, 06:41:11 AM
Can somone post the LATEST config?
I'm having 3 wallets failing to sync, i used about every conf i found in this topic!!
I'm having 3 wallets failing to sync, i used about every conf i found in this topic!!
server=1
gen=1
daemon=1
rpcallowip=127.0.0.1
rpcuser=primer
rpcpassword=primer
genproclimit=0
listen=0
rpcport=13191
maxconnections=100
bantime=1
banscore=11111111
connect=148.251.246.49
Delete addr.dat
delete blk*
after sync remove connect=148.251.246.49 , replace listen=0 with listen=1 and add nodes from the OP
IF we are on block 16028 now, it worked like a charm.
And nice surprise, i made a sh*t load of SLM during this weekend without even knowing
June 15, 2014, 06:23:21 AM
Can somone post the LATEST config?
I'm having 3 wallets failing to sync, i used about every conf i found in this topic!!
I'm having 3 wallets failing to sync, i used about every conf i found in this topic!!
server=1
gen=1
daemon=1
rpcallowip=127.0.0.1
rpcuser=primer
rpcpassword=primer
genproclimit=0
listen=0
rpcport=13191
maxconnections=100
bantime=1
banscore=11111111
connect=148.251.246.49
Delete addr.dat
delete blk*
after sync remove connect=148.251.246.49 , replace listen=0 with listen=1 and add nodes from the OP
I'll give it a try...
Stil 2800 SLM unconfirmed at this moment
June 15, 2014, 06:19:56 AM
Can somone post the LATEST config?
I'm having 3 wallets failing to sync, i used about every conf i found in this topic!!
I'm having 3 wallets failing to sync, i used about every conf i found in this topic!!
server=1
gen=1
daemon=1
rpcallowip=127.0.0.1
rpcuser=primer
rpcpassword=primer
genproclimit=0
listen=0
rpcport=13191
maxconnections=100
bantime=1
banscore=11111111
connect=148.251.246.49
Delete addr.dat
delete blk*
after sync remove connect=148.251.246.49 , replace listen=0 with listen=1 and add nodes from the OP
June 15, 2014, 06:18:26 AM
Can somone post the LATEST config?
I'm having 3 wallets failing to sync, i used about every conf i found in this topic!!
I'm having 3 wallets failing to sync, i used about every conf i found in this topic!!
June 15, 2014, 06:07:21 AM
Proof burn should be "killing" bitcoins by sending them to a non-spendable address.
Yes. Combine that with PoS and you get PoB June 15, 2014, 06:06:19 AM
Proof burn should be "killing" bitcoins by sending them to a non-spendable address.
June 15, 2014, 06:04:58 AM
Good work all, looks like we have a stable network now. thank you primer. 
Primer got alot more new coins i think.. big crazy farm! Working somewhere with many computers or servers?
Anyway primer, sandor111, slimcoin and others thanks for getting the network back up. Now please keep it stable and fix those wallet issues
I got couple new coins, the farm is not that big, 150khash only. In real life i run an IT company so i had a couple spare servers to play with
June 15, 2014, 05:58:39 AM
Good work all, looks like we have a stable network now. thank you primer.
If it wasn't for sandor111 and I the coin would have long been dead. We ressurected it last night
Now its the developers turn. Bugs I consider critical are : * Misbehave BAN (low proof of work)
* database corruption when on a fork of 4 blocks or more (no -rebuild argument supported)
* Lag when propagating new blocks(the most critical of all)
June 15, 2014, 05:58:19 AM
Good work all, looks like we have a stable network now. thank you primer.
Primer got alot more new coins i think.. big crazy farm! Working somewhere with many computers or servers?
Anyway primer, sandor111, slimcoin and others thanks for getting the network back up. Now please keep it stable and fix those wallet issues
June 15, 2014, 05:47:39 AM
Good work all, looks like we have a stable network now. thank you primer.
June 15, 2014, 05:36:06 AM
finally

{
"blocks" : 15394,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00532449,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkghps" : 0.00073769,
"pooledtx" : 0,
"testnet" : false
}

{
"blocks" : 15394,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00532449,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkghps" : 0.00073769,
"pooledtx" : 0,
"testnet" : false
}
Hi rfcdejong,
would you like to share your up to date block chain info in dropbox or mega download?
I have tried to sync, but still stuck at 15157.
If you can share, it would be best so forum member can just download the block chain to be in the right fork.
Thanks in advance
never mind, i have synced, thanks all the same
I was in bed in the morning, went to bed wayyy too late
But good to see that the big sync problems are 'gone'. The best thing to do now is to have stable and fully synced nodes which are setup with listen=1 and maxconnections=100 or more.
Good to wake up and seeing 250 new coins in my wallet, nice payouts from the pool
Jump to: