I was on a big fork until my wallet crashed, high nr of blocks, diff reasonable and networkghps reasonable.
"blocks" : 68556,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.03609960,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkghps" : 0.00108424,
"pooledtx" : 1,
"testnet" : false
}
Topic: [ANN] Slimcoin : Proof of Burn NEW BLOCK GEN, Mineable by low power computer! - page 33. (Read 284948 times)
August 15, 2014, 12:39:31 PM
August 14, 2014, 05:59:50 AM
I think slimcoin went on vacation for a week or maybe two, he doesn't even know about the current forks.
Last Active: August 08, 2014, 12:38:00 PM
And perhaps his nodes went down as well..
Last Active: August 08, 2014, 12:38:00 PM
And perhaps his nodes went down as well..
I think too. I am working on PoB pool and he stop reply to my questions from 8th August. Anyway, the code is almost done, I am looking for testers
August 13, 2014, 03:20:49 PM
I think slimcoin went on vacation for a week or maybe two, he doesn't even know about the current forks.
Last Active: August 08, 2014, 12:38:00 PM
And perhaps his nodes went down as well..
Last Active: August 08, 2014, 12:38:00 PM
And perhaps his nodes went down as well..
August 13, 2014, 01:35:26 PM
Block propagation in slimcoin is broken, always was. Even if you all sync up to the same chain (very unlikely as there are over 100 forks), it will fork again.
Bulgarian hardcoded node was keeping things in check, the moment it was shut off slim forked.
You will need to fix the block propagation issue first. Good luck!
Bulgarian hardcoded node was keeping things in check, the moment it was shut off slim forked.
You will need to fix the block propagation issue first. Good luck!
You have been saying this for about 20 pages now, the Dev must have got the message by now. You repeat the same things on every page that it is dead and you are moving on. (after you have made profit by dumping slim) yet you continue to follow the thread and post often....good thing you are sticking around to "look out for people". While the coin currently has some problems what is to say a dedicated community cannot overcome these obstacles and get it back on track? Some unique features exist here which makes it worth saving.
Edit: If the Dev doesn't show up to address the situation with the forks it very well could be over. I was just saying it is not over yet and options exist. Dev's can always change hands, example would be what happened with Asiacoin a while back. In an over saturated alt coin market some people may rather move on versus save this. I guess we will see soon.
August 13, 2014, 08:04:59 AM
August 12, 2014, 07:44:39 PM
So, it's best just to solo mine? From the standalone miner or the one in the wallet?
Mining is pot luck at the moment. You could solo mine, but there's no guarantee that the chain you're on will necessarily be accepted (by community consensus and/or the dev) as the official one. Your client could even end up starting its own private fork.
I just restarted the client and it's obvious from the small number of peers I've connected to that there are multiple forks (I've had a go at labelling them below)
Code:
2014-08-13 00:31:54 UTC Slimcoin version v0.3.2.0-g154b52a-alpha ()
2014-08-13 00:32:10 UTC version message: version 60003, blocks=66461 ** (1)
2014-08-13 00:32:39 UTC version message: version 60003, blocks=63435 ** (2)
2014-08-13 00:32:45 UTC version message: version 60003, blocks=16014 ** (3)
2014-08-13 00:35:22 UTC version message: version 60003, blocks=66462 ** (1)
2014-08-13 00:35:47 UTC version message: version 60003, blocks=26934 ** (4)
2014-08-13 00:36:44 UTC version message: version 60003, blocks=30183 ** (5)
2014-08-13 00:38:57 UTC version message: version 60003, blocks=66465 ** (1)
2014-08-13 00:39:23 UTC version message: version 60003, blocks=15164 ** (6)
2014-08-13 00:43:52 UTC version message: version 60003, blocks=64907 ** (7)
2014-08-13 00:46:49 UTC version message: version 60003, blocks=26940 ** (4)
August 12, 2014, 04:03:39 PM
I cannot connect to 112.113.96.138 on any port so I guess you use only 54.191.247.114 node. All 3 pools linked from the start page are offline so let's keep them out of equation.
Understood, someone should try to pick up the task to repair it.
I ended up using these nodes and sync fine, seem like the pools aren't on the same fork.
Block propagation in slimcoin is broken, always was. Even if you all sync up to the same chain (very unlikely as there are over 100 forks), it will fork again.
Bulgarian hardcoded node was keeping things in check, the moment it was shut off slim forked.
You will need to fix the block propagation issue first. Good luck!
Bulgarian hardcoded node was keeping things in check, the moment it was shut off slim forked.
You will need to fix the block propagation issue first. Good luck!
Understood, someone should try to pick up the task to repair it.
I checked the nodes posted above:
54.191.247.114 is at 66270
69.172.231.56 stuck at 65494 few hours ago on other fork.
Other nodes are offline.
If you know other forks at similar height and trust value - post their nodes.
54.191.247.114 is at 66270
Code:
SetBestChain: new best=60133ce7ffbf9f49b6f6 height=66270 trust=112643180633 moneysupply=624240.386373 nEffectiveBurnCoins=200544.329924
69.172.231.56 stuck at 65494 few hours ago on other fork.
Other nodes are offline.
If you know other forks at similar height and trust value - post their nodes.
Code:
addnode=54.191.247.114
addnode=112.113.96.138:41682
addnode=112.113.96.138:41683
addnode=112.113.96.138:41686
I ended up using these nodes and sync fine, seem like the pools aren't on the same fork.
So, it's best just to solo mine? From the standalone miner or the one in the wallet?
August 12, 2014, 03:05:06 PM
I cannot connect to 112.113.96.138 on any port so I guess you use only 54.191.247.114 node. All 3 pools linked from the start page are offline so let's keep them out of equation.
Understood, someone should try to pick up the task to repair it.
I ended up using these nodes and sync fine, seem like the pools aren't on the same fork.
Block propagation in slimcoin is broken, always was. Even if you all sync up to the same chain (very unlikely as there are over 100 forks), it will fork again.
Bulgarian hardcoded node was keeping things in check, the moment it was shut off slim forked.
You will need to fix the block propagation issue first. Good luck!
Bulgarian hardcoded node was keeping things in check, the moment it was shut off slim forked.
You will need to fix the block propagation issue first. Good luck!
Understood, someone should try to pick up the task to repair it.
I checked the nodes posted above:
54.191.247.114 is at 66270
69.172.231.56 stuck at 65494 few hours ago on other fork.
Other nodes are offline.
If you know other forks at similar height and trust value - post their nodes.
54.191.247.114 is at 66270
Code:
SetBestChain: new best=60133ce7ffbf9f49b6f6 height=66270 trust=112643180633 moneysupply=624240.386373 nEffectiveBurnCoins=200544.329924
69.172.231.56 stuck at 65494 few hours ago on other fork.
Other nodes are offline.
If you know other forks at similar height and trust value - post their nodes.
Code:
addnode=54.191.247.114
addnode=112.113.96.138:41682
addnode=112.113.96.138:41683
addnode=112.113.96.138:41686
I ended up using these nodes and sync fine, seem like the pools aren't on the same fork.
August 12, 2014, 02:27:29 PM
Block propagation in slimcoin is broken, always was. Even if you all sync up to the same chain (very unlikely as there are over 100 forks), it will fork again.
Bulgarian hardcoded node was keeping things in check, the moment it was shut off slim forked.
You will need to fix the block propagation issue first. Good luck!
Bulgarian hardcoded node was keeping things in check, the moment it was shut off slim forked.
You will need to fix the block propagation issue first. Good luck!
Understood, someone should try to pick up the task to repair it.
I checked the nodes posted above:
54.191.247.114 is at 66270
69.172.231.56 stuck at 65494 few hours ago on other fork.
Other nodes are offline.
If you know other forks at similar height and trust value - post their nodes.
54.191.247.114 is at 66270
Code:
SetBestChain: new best=60133ce7ffbf9f49b6f6 height=66270 trust=112643180633 moneysupply=624240.386373 nEffectiveBurnCoins=200544.329924
69.172.231.56 stuck at 65494 few hours ago on other fork.
Other nodes are offline.
If you know other forks at similar height and trust value - post their nodes.
Code:
addnode=54.191.247.114
addnode=112.113.96.138:41682
addnode=112.113.96.138:41683
addnode=112.113.96.138:41686
I ended up using these nodes and sync fine, seem like the pools aren't on the same fork.
August 12, 2014, 02:12:28 PM
I checked the nodes posted above:
54.191.247.114 is at 66270
69.172.231.56 stuck at 65494 few hours ago on other fork.
Other nodes are offline.
If you know other forks at similar height and trust value - post their nodes.
54.191.247.114 is at 66270
Code:
SetBestChain: new best=60133ce7ffbf9f49b6f6 height=66270 trust=112643180633 moneysupply=624240.386373 nEffectiveBurnCoins=200544.329924
69.172.231.56 stuck at 65494 few hours ago on other fork.
Other nodes are offline.
If you know other forks at similar height and trust value - post their nodes.
August 12, 2014, 02:05:11 PM
Block propagation in slimcoin is broken, always was. Even if you all sync up to the same chain (very unlikely as there are over 100 forks), it will fork again.
Bulgarian hardcoded node was keeping things in check, the moment it was shut off slim forked.
You will need to fix the block propagation issue first. Good luck!
Bulgarian hardcoded node was keeping things in check, the moment it was shut off slim forked.
You will need to fix the block propagation issue first. Good luck!
August 12, 2014, 01:55:18 PM
Guys... you need to do more than use addnode. This only adds the IPs to the peer list, so the client will probably connect to them, but it doesn't limit the client connecting to other peers (or other peers connecting to you)
The way to tie yourself to specific nodes is to use connect= and listen=0. This will connect ONLY to the specified nodes, and in addition, disallow any inbound connects. For example, in the .conf:
connect=54.191.247.114
listen=0
Or on the commandline:
slimcoin-qt.exe -connect=54.191.247.114 -listen=0
(I can't vouch for the node 54.191.247.114, I'm just using it as an example.)
Without this explicit config you'll just end up connected to a bunch of different peers on different forks, and your client will probably end up confused.
The way to tie yourself to specific nodes is to use connect= and listen=0. This will connect ONLY to the specified nodes, and in addition, disallow any inbound connects. For example, in the .conf:
connect=54.191.247.114
listen=0
Or on the commandline:
slimcoin-qt.exe -connect=54.191.247.114 -listen=0
(I can't vouch for the node 54.191.247.114, I'm just using it as an example.)
Without this explicit config you'll just end up connected to a bunch of different peers on different forks, and your client will probably end up confused.
That is understood, but which node(s) are the proper ones. Seem like nodes are just being thrown around without any form of validity.
August 12, 2014, 08:44:29 AM
Guys... you need to do more than use addnode. This only adds the IPs to the peer list, so the client will probably connect to them, but it doesn't limit the client connecting to other peers (or other peers connecting to you)
The way to tie yourself to specific nodes is to use connect= and listen=0. This will connect ONLY to the specified nodes, and in addition, disallow any inbound connects. For example, in the .conf:
connect=54.191.247.114
listen=0
Or on the commandline:
slimcoin-qt.exe -connect=54.191.247.114 -listen=0
(I can't vouch for the node 54.191.247.114, I'm just using it as an example.)
Without this explicit config you'll just end up connected to a bunch of different peers on different forks, and your client will probably end up confused.
The way to tie yourself to specific nodes is to use connect= and listen=0. This will connect ONLY to the specified nodes, and in addition, disallow any inbound connects. For example, in the .conf:
connect=54.191.247.114
listen=0
Or on the commandline:
slimcoin-qt.exe -connect=54.191.247.114 -listen=0
(I can't vouch for the node 54.191.247.114, I'm just using it as an example.)
Without this explicit config you'll just end up connected to a bunch of different peers on different forks, and your client will probably end up confused.
August 12, 2014, 07:27:36 AM
These nodes at the same blockchain.
See:
https://bitcointalksearch.org/topic/m.8299703
https://bitcointalksearch.org/topic/m.8301866
Code:
addnode=54.191.247.114
addnode=112.113.96.138:41682
addnode=112.113.96.138:41683
addnode=112.113.96.138:41686
https://bitcointalksearch.org/topic/m.8299703
https://bitcointalksearch.org/topic/m.8301866
Are these the proper nodes then?
addnode=112.113.96.138:41682
addnode=112.113.96.138:41683
addnode=112.113.96.138:41686
addnode=89.182.170.221:41682
addnode=69.172.231.56:41682
addnode=54.191.247.114
Also, have any of the pools been contacted if they are on the right chain?
August 12, 2014, 06:16:55 AM
The king of the solo?
54.191.247.114
54.191.247.114
August 12, 2014, 06:15:01 AM
These nodes at the same blockchain.
See:
https://bitcointalksearch.org/topic/m.8299703
https://bitcointalksearch.org/topic/m.8301866
Code:
addnode=54.191.247.114
addnode=112.113.96.138:41682
addnode=112.113.96.138:41683
addnode=112.113.96.138:41686
https://bitcointalksearch.org/topic/m.8299703
https://bitcointalksearch.org/topic/m.8301866
August 12, 2014, 04:58:09 AM
Current state for node 54.191.247.114 (other nodes posted in this thread are on other forks so don't mix them).
Code:
SetBestChain: new best=00000006eff4be409fec height=65928 trust=105709355121 moneysupply=619565.663472 nEffectiveBurnCoins=200456.503543
{
"blocks" : 65928,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.06259049,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkghps" : 0.00331882,
"pooledtx" : 0,
"testnet" : false
}
August 12, 2014, 03:54:10 AM
New nodes(updating):
Code:
addnode=112.113.96.138:41682
addnode=112.113.96.138:41683
addnode=112.113.96.138:41686
addnode=89.182.170.221:41682
addnode=69.172.231.56:41682
The chain is at block 65525 with 3Mhs of hash power. To choose it: -connect=54.191.247.114.


Code:
{
"blocks" : 65525,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.05411402,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkghps" : 0.00297972,
"pooledtx" : 0,
"testnet" : false
}
Does that addnode work with the one's ynyjl posted or on it's own?
The wallet seems to crash once in a while.
I don't mining, I'm just trying to safeguard it.
Node 154.191.247.114 is not stable
You got the wrong node I am referring too and I highlighted it in red.
I can't get my wallet to sync to that latest block height and it has a message on the bottom saying; "Checkpoint is too old......"
The wallet needs to be hard coded with the new nodes after the fork issue.
August 11, 2014, 11:36:13 PM
11:52:18

{
"synccheckpoint" : "0000000f4b51b2dc9b43369bf66808f07e74dbcc3154cf3ccd9fb94e2121d37f",
"height" : 9600,
"timestamp" : "2014-06-08 15:34:42 UTC"
}

{
"synccheckpoint" : "0000000f4b51b2dc9b43369bf66808f07e74dbcc3154cf3ccd9fb94e2121d37f",
"height" : 9600,
"timestamp" : "2014-06-08 15:34:42 UTC"
}
There are actually hardened checkpoints in the source code (checkpoints.cpp) well past that. I think it's a bug with the checkpointing code; I've seen other coins get stuck on older hardened checkpoints too. ('getcheckpoint' returns the genesis block 0 for me!)
Code:
( 0, hashGenesisBlockOfficial )
( 9012, uint256("0x00000006b2c364c71c279977abc8adf528d25263fb3b4fa623a309745d9f6246"))
( 9013, uint256("0x000000064ce948cdba2c2223dd75c3677847a00daded6be78a097db82d616eee"))
( 9201, uint256("0x0000000ab86098c475566cf8f494d131c4d17aa18a26e946f6b6143be4989d43"))
( 9401, uint256("0x0000000538be9059aa111cdee43d7f6c5c4e6581073af1f4478a8705f5817f3b"))
( 10198, uint256("0x000000086631340ce44f7ee72e7125654eef62181a08bacf69b42f797fd7bb4c"))
( 10503, uint256("0x1a433766560d719d5ece18aa190b00fd503d733e2162e511df0998df5c8680f5"))
( 15165, uint256("0x0000017fba5ef709509c7380e3e128a69a5ab3c60b526c8345aff592dc8d8f81"))
( 15935, uint256("0xaf377a2f3be16d3c3d82ad9158a3c24b5e8a7a1af6e315b486a390c651d70ff5"))
( 15936, uint256("0x0000002a4ba8fac73286a3cbcac76610a11f3faebec4ce19c13aca30990684f4"))
( 35587, uint256("0x07450307a456afcbc62d8414913a8b4497f4dc13629337b7db5658aa52877155"))
( 43685, uint256("0xa91550beeed702374a01bd8999669cc9dc6952752f2ede01ef446cb0d2113e6f"))
August 11, 2014, 10:55:46 PM
11:49:27

getblockcount
11:49:27

65688
11:52:18

getcheckpoint
11:52:18

{
"synccheckpoint" : "0000000f4b51b2dc9b43369bf66808f07e74dbcc3154cf3ccd9fb94e2121d37f",
"height" : 9600,
"timestamp" : "2014-06-08 15:34:42 UTC"
}
Jump to: