|
Sandor, can you sync him to 15934 ? I am afraid couple of nodes that connected with the dev overwrote my database. New sync should be performed 1-1, listen=0 on dev side and you sandor change port(port=xxxxx) so no one connects to you.
|
|
|
|
|
I told the dev to delete addr.dat and to change his listening port or change listen to 0 so no one connects while he syncs up. He did not. I see around 10 connections to my node now and i am at block "blocks" : 16395.
I have no idea if the 'network' overwrote blocks below 15942, which could have happened as they had more 'synced nodes'
|
|
|
|
Since when did: "Can I have your addnode address?" mean Slimcoin is turning back to 15000?
We are now at block "blocks" : 16384, I dont know where the 400+ blocks came from so they should ALL be discarded. We should hard-fork at block 15942. Everything above that was not created by the network. If dev starts at 16000 instead i'd find it suspicious, UNLESS someone reputable syncs him with a 16k blockchain. I cant because 4 of my databases stopped at block 16003 and 16005 are corrupted. My working database syncs at 15942 |
|
|
|
Why not roll back to 1500 when all the major issues started?
Because then not only bitspender will be the one against the 'relaunch' idea... lots of miners paid contracts, AWS 32 core instance can be expensive with 50 dollar a day, even with spot instances. Oke this coin is a risk, so are most coins. If Slimcoin goes back to 15000 instead of near 16000 i will be against as well, while i'm oke with 16000. I think james wants to go back all the way to 1500  |
|
|
|
Turn your node back on.
Up now |
|
|
|
Dev is synced up to block "blocks" : 15942, !! Good enough, hoping for a re-launch soon!!!  |
|
|
|
|
Seems like dev gave up, i have not seen a single connection from his IP (76.127.202.17)
|
|
|
|
I just tried it and it does not work, I need a node.
Ok, i will run it via wine, 1 minute.. use connect=144.76.139.111:19191 bantime=1 banscore=11111111 NOTICE = DO NOT CONNECT IF YOU ARE NOT THE DEV!! YOU MIGHT FUCK UP MY BLOCKCHAIN!! Dev, delete addr files before syncing to me, i dont want any 'dirty nodes' passed on... EDIT: listen was 0, 30 secs. EDIT2 : Up now. |
|
|
|
I just tried it and it does not work, I need a node.
Ok, i will run it via wine, 1 minute.. |
|
|
|
I want to test this, I cannot make any promises, but it probably will not be tomorrow.
Also, I need a node to sync from that is on a blockchain of height >= 16000. Coping the files does not work.
It does not work probably because of the database format. Not sure which berkeleyDB i've got running on my centos boxes. Anyone else synced above 16000 ? bitspender ? EDIT : OK, this is my windows blockchain at 16005, this has to work. http://144.76.30.136/blk0001.zipHe needs a node to sync from, not the actual db files. He can run it off his own box. |
|
|
|
I want to test this, I cannot make any promises, but it probably will not be tomorrow.
Also, I need a node to sync from that is on a blockchain of height >= 16000. Coping the files does not work.
It does not work probably because of the database format. Not sure which berkeleyDB i've got running on my centos boxes. Anyone else synced above 16000 ? bitspender ? EDIT : OK, this is my windows blockchain at 16005, this has to work. http://144.76.30.136/blk0001.zip |
|
|
|
|
When is the relaunch scheduled for, today or within a week ?
|
|
|
|
Try it, that is a bug that I fixed already and will release when everything is working at the relaunch.
LoadBlockIndex(): hashBestChain=000000140ef530c4a7c0 height=15942 trust=44832371 This one loads up. Block 15942 http://144.76.30.136/slimcoinblockchain.tgz |
|
|
|
I need a sync node that is past block 16000, please give me your addnode address.
Give me 5 minutes. For some reason i'm getting a corrupt database error on all nodes that were stopped at block 16003. I could gzip and upload it ? |
|
|
|
I need a sync node that is past block 16000, please give me your addnode address.
Give me 5 minutes. |
|
|
|
|
I'd like to see mumus and other developers go through the source code and make sure no coins were premined by the developer. I'd also like to know if there is a chance the BURN address actually spends coins - if so that should also be addressed in the hard fork.
|
|
|
|
the burn time is too long,someone can tell me why?
Read the last two pages ? |
|
|
|
|
Dev needs to post when he is expecting to re-launch.
|
|
|
|
Don't be selfish, it was agreed upon that we will relaunch the coin at block 16000. There is about 5k coins lost in my pool due to this.
It was agreed by those 2 forum members, the only two on this planet that can benefit from this. Where is the official announcement from the dev about this? Come on I think primer- has even wasted more of his hashrate than yours on this coin. Don't be angry about merely 350 SLMs. I have even lost more than you. Primer- made 13 BTC after launch, i INVESTED 10 BTC in this coin, that's the difference. It's not up to two individuals to deceide if i continue to mine this coin or not. Period. Please continue mining on your fork and dont look back. |
|
|
|
WHAT HAPPENS WITH OUR CURRENT COINS AT RELAUNCH???
YOU GET TO KEEP EVERYTHING YOU MADE UP TO BLOCK 16000!!! |
|
|
|
|
Show Posts
