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. |
|
|
|
|
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.
|
|
|
|
|
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.
|
|
|
|
|
Its happening again ...
{
"blocks" : 15931,
it was 16xxx...
|
|
|
|
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. |
|
|
|
sandor is you pool down?
Its not, you need to use the new ddos protected domain : pool.slimcoinpool.com:3333 |
|
|
|
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 |
|
|
|
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. |
|
|
|
|
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...
|
|
|
|
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. |
|
|
|
Can somone post the LATEST config?
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 |
|
|
|
Proof burn should be "killing" bitcoins by sending them to a non-spendable address.
Yes. Combine that with PoS and you get PoB |
|
|
|
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 |
|
|
|
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) |
|
|
|
|
I have put up a new super-node for syncing as the first one is currently syncing over 100 connections.
before syncing remove addr.dat
make sure you have the following in the confi file :
bantime=1
banscore=11111111
connect=148.251.246.49
remove the connect= flag once fully synced
|
|
|
|
{
"blocks" : 15260,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00024414,
"errors" : "",
"generate" : true,
"genproclimit" : 8,
"hashespersec" : 2847,
"networkghps" : 0.00000309,
"pooledtx" : 0,
"testnet" : false
}
im only 15260
That can happen... WHEN YOU MINE AND SYNC at the same time!! "genproclimit" : 8, |
|
|
|
|
Its working not because of the new wallet but because of my node at connect=148.251.7.102 which was configured to overcome some wallet bugs (bantime/banscore, latency,etc.)
If you want a fast sync only add connect= without addnodes. once fully synced remove the connect and add normal addnodes
|
|
|
|
|
Why is difficulty algo not adjusting, pool is finding blocks every couple sec.
|
|
|
|
still at the block but debug.log says
connected 148.251.7.102:41682
Added time data, samples 2, offset -3 (+0 minutes)
version message: version 60003, blocks=15308
0 addresses found from DNS seeds
ThreadDNSAddressSeed exiting
Ok good, now wait. lots of orphans and errors i don't have ban stuff configured thru ProcessBlock: ORPHAN BLOCK, prev=000000041ebd12036dca ERROR: CheckProofOfBurn() : INFO: prev block not found WARNING: ProcessBlock() : check proof-of-burn failed for block e9b185010b8fbe76e97d90c2b8c4a1e22d02b72ac37a1f34a7f3a762f1c6782a maybe the ban configuration isn't good for the blockchain either, just only for syncing up fast Your blockchain is bad and the wallet does not support -rebuild flag. you need to rm -rf blk* addr.dat and reconnect to my node. with ban on: bantime=1 banscore=11111111 Without ban configuration we would be desynced all over. |
|
|
|
still at the block but debug.log says
connected 148.251.7.102:41682
Added time data, samples 2, offset -3 (+0 minutes)
version message: version 60003, blocks=15308
0 addresses found from DNS seeds
ThreadDNSAddressSeed exiting
Ok good, now wait. |
|
|
|
|
Show Posts
