|
AsicCoin is a great coin, SHA-256, zero premine, a lot network hashrate.
|
|
|
|
Glad that all the diff retarget mess is behind us, thanks fisheater for the great support of the coin!  |
|
|
|
I like this one  LOL, thanks for that Hazard, old blue Cheetah will always have a soft spot in our hearts. ;-) /FC me too, I like the original one, seriously. Because that reminded me the time where I solo mined it. Why not you put that one for vote too. BTW, I like Hazard too  |
|
|
|
It looks to me the blockchain is very stable now. Earlier sometimes I saw the client switch back and forth to some other chains, all the time it switched back after some time, as other chains are not sync'able. One of the chain is the Litecoin that I can recognize, this is probably that IFC (and many others at that time, such as NBL, FST, ALF etc) did not change the message channel, so it gets sync messages. It is not a problem, you can mine without any issues. As long as you have connections. Here are some of my peers FYI.
Which message channel, do you mean IRC? I don't know the details. I remember at the early stage of IFC sometimes we saw Litecoin upgrade messages. It was disabled in the code later in some fixes, this is not specific to IFC, saw it in many coins. |
|
|
|
|
It looks to me the blockchain is very stable now. Earlier sometimes I saw the client switch back and forth to some other chains, all the time it switched back after some time, as other chains are not sync'able. One of the chain is the Litecoin that I can recognize, this is probably that IFC (and many others at that time, such as NBL, FST, ALF etc) did not change the message channel, so it gets sync messages. It is not a problem, you can mine without any issues. As long as you have connections. Here are some of my peers FYI.
{
"addr" : "75.152.93.200:9321",
"services" : "00000001",
"lastsend" : 1380305794,
"lastrecv" : 1380305782,
"conntime" : 1380305686,
"version" : 60001,
"subver" : "/Satoshi:1.7.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 256456,
"banscore" : 0
},
{
"addr" : "68.42.103.11:9321",
"services" : "00000001",
"lastsend" : 1380305840,
"lastrecv" : 1380305770,
"conntime" : 1380305692,
"version" : 60001,
"subver" : "/Satoshi:1.7.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 256456,
"banscore" : 0
},
{
"addr" : "76.110.255.33:9321",
"services" : "00000001",
"lastsend" : 1380305840,
"lastrecv" : 1380305805,
"conntime" : 1380305693,
"version" : 60001,
"subver" : "/Satoshi:1.7.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 256456,
"banscore" : 0
},
{
"addr" : "5.53.130.92:9321",
"services" : "00000000",
"lastsend" : 1380305840,
"lastrecv" : 0,
"conntime" : 1380305817,
"version" : 0,
"subver" : "",
"inbound" : false,
"releasetime" : 0,
"startingheight" : -1,
"banscore" : 0
},
{
"addr" : "86.132.75.90:9321",
"services" : "00000001",
"lastsend" : 1380305819,
"lastrecv" : 1380305840,
"conntime" : 1380305818,
"version" : 60001,
"subver" : "/Satoshi:1.7.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 256457,
"banscore" : 0
},
{
"addr" : "86.150.227.43:9321",
"services" : "00000001",
"lastsend" : 1380305840,
"lastrecv" : 1380305826,
"conntime" : 1380305819,
"version" : 60001,
"subver" : "/Satoshi:1.7.0/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 256457,
"banscore" : 0
},
{
"addr" : "95.170.82.34:9321",
"services" : "00000001",
"lastsend" : 1380305840,
"lastrecv" : 1380305829,
"conntime" : 1380305825,
"version" : 60001,
"subver" : "/Satoshi:0.6.3/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 254505,
"banscore" : 0
},
{
"addr" : "96.127.231.164:9333",
"services" : "00000001",
"lastsend" : 1380305842,
"lastrecv" : 1380305844,
"conntime" : 1380305840,
"version" : 70002,
"subver" : "/Satoshi:0.8.3.7/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 432199,
"banscore" : 0
}
|
|
|
|
OK I think this is enough. For 3 days, I've been waiting for this super hard block to be solved, and it was not solved, and I don't know how long it will take. The blockchain is jammed. The coin is about to be dead. Thanks to all the attackers to put IFC in this situation. Luckily we have a way to get out of it. I was sync'ed to an apparent forked chain, and I watched it go from block 247330 to block 248722. I started to mine it sometimes ago, it works fine. With version 1.7 and starting from 248000, the diff retarget becomes normal and everything seems working. I will not be stuck at block 246953 in the old chain forever. I am using the new chain. By comparing the forked chain with the one in block explorer, I see it forked out of block 246948, 5 blocks before the one we get stuck. So it is not too bad, only 5 blocks will be lost. You can use 1.7 client and sync from scratch (you need to clean up the config dir, NOT delete wallet and config file, then start to sync with your client), you should get to the forked chain like I did. The sync will take about 3 hours to complete. Or you can download the chain here (pretty big: 228M) : https://mega.co.nz/#!ZghiRIzT!GlZMiA2_Nv7MQ6V4QqwJRzgfSI5IgkKsnvnZbzJ2Pn4 unrar the file, and copy the files into your config dir (please backup your existing chain, so if you don't like it you can go back). Also here are my peers, that you may want to use as addnode. 66.87.67.255 108.62.211.7 66.63.176.231 80.7.165.182 24.144.220.244 192.241.222.102 98.18.252.73 192.249.59.81 75.152.93.200 95.170.82.34 67.177.3.56 80.234.71.58 Note, apparently there are more than one forked chains, but other chains can not be sync up, possibly they violate some constraints such as checkpoints. Once you sync to 2487xx, you should be able to start mining with 1.7 client. |
|
|
|
|
Looks like the chain I sync'ed is a forked chain at block 246948, so it does not violate any checkpoints. If some confirmations are overwritten, will anyone lose coins? Or the transactions will be considered not happened?
If someone will lose big coins, then we better wait. Otherwise we may use the forked chain which will get to the switch point earlier. The problem with block 246953 is that it is at big diff, no idea when it will be solved.
Apparently there's at least one more blockchain at block 254501 now.
|
|
|
|
Dev already changed the diff retarget to the PPCoin algorithm, and set the switch block to be 248000. I think this algorithm should be reliable, as it has been used by all pos coins. The block 248000 may be a little conservative, but if people don't switch then we are in a bigger problem. It really depends on the diff, some cycles the diff did not go very high, but some are really high, it may depends on the hashrate at that time. It was faster a few days ago.
Some people attacked the IFC for sure. Any pow coin with 60 blocks or above retarget diff cycle can be attacked exactly the same way as IFC. That is, use high hash to boost the diff, then leave, then come back at low diff etc. After a few cycles, the coin will likely be blocked due to its high diff. IFC being the first one attacked this way possibly because its popularity.
But it looks like I am in another chain... I am at block 247330 sync'ed.
There maybe multiple chains out there, I saw one at 254488, another at 244999, but these two are not sync'ed though.
246953 looks like the last block. If you sync from scratch with version 1.7, I think you will sync to this chain, which is currently at block 247332, this looks the correct chain to me. I tried it in another computer, I got the same thing. |
|
|
|
|
Dev already changed the diff retarget to the PPCoin algorithm, and set the switch block to be 248000. I think this algorithm should be reliable, as it has been used by all pos coins. The block 248000 may be a little conservative, but if people don't switch then we are in a bigger problem. It really depends on the diff, some cycles the diff did not go very high, but some are really high, it may depends on the hashrate at that time. It was faster a few days ago.
Some people attacked the IFC for sure. Any pow coin with 60 blocks or above retarget diff cycle can be attacked exactly the same way as IFC. That is, use high hash to boost the diff, then leave, then come back at low diff etc. After a few cycles, the coin will likely be blocked due to its high diff. IFC being the first one attacked this way possibly because its popularity.
But it looks like I am in another chain... I am at block 247330 sync'ed.
There maybe multiple chains out there, I saw one at 254488, another at 244999, but these two are not sync'ed though.
|
|
|
|
|
I also had a sync problem. But when I get the version 1.7 and sync'ed from the scratch (delete everything in the config dir except wallet and config files), the sync seems OK. And I sync'ed to block 247330. I am not sure if this is a forked chain or is the good chain. I looked at the block explorer in the OP, and it shows at block 246953 for about 2 days, is the block explorer stuck? or there's a fork?
Anyway, I am glad to get over the block 246953, and be in a block close to the diff retarget switch block of 248000.
|
|
|
|
|
Anyone get the prize? This coin has been quiet lately.
|
|
|
|
|
Weekend again, hope cryptsy will add more coins. Please consider these great non-premine coins:
ASC, LK7, TGC, TEK, NET, SAV.
They all be around for some time and have a broad miner base, they will surely be in active trades!
|
|
|
|
|
Any mining pool up on STR?
|
|
|
|
network hashrate steadily above 500Gh/s, very strong |
|
|
|
Is this pool working correctly? aTriz stratum pool: http://ifc.scryptmining.comstratum+tcp://mine-ifc.scryptmining.com:8112 In the last round of craziness the pool got a lot of blocks, but I see my shares are mostly zero in these blocks, even the one found by myself says zero shares of me, aTriz can you check if the pool working correctly? |
|
|
|
|
Can someone post peers? I can't sync my wallet...
|
|
|
|
I have an issue with the wallet not being opened with the new version.. Any help appreciated: Verifying last 0 blocks at level 1
block index 3ms
Loading wallet...
************************
EXCEPTION: St13runtime_error
CDB() : can't open database file wallet.dat, error 12
StarCoin in AppInit() Did you sync from scratch? You may need to clean up everything in the config dir, except the wallet.dat and config file, then start the sync. I did mine, seems working fine. |
|
|
|
|
Add these no-premine coins: ASC, TGC, TEK, LK7, TIX
|
|
|
|
So AsicCoin block reward halves around Christmas time. Is is possible to tell the exact time this will happen?
Hard to say. It depends on hash power. Reward halves every 259,200 blocks. So you need to check current block at specific time and then calculate how many bloch are remaining before having will happen. depends on the network hashrate, which causes the block time to fluctuate, so it is not possible to determine precisely the time when block will be halved. |
|
|
|
can it paid for solo block I guess only mining in coinex, so they can verify it |
|
|
|
|
Show Posts
