Topic: [RESURRECTION] Taking Astrocoin to the Moon,KGW Implemented + HARD FORK AT 17520 - page 11. (Read 23270 times)

I've updated the conf on the OP with the coin-base node as well as my node with the correct chain from Coin-base.
Do let me know when you've synced my friend also we need more nodes on the new wallet , since it's a cat fight over here lol.

Cheers!
Soopy

Awesome to hear that you are on the right chain , the out of sync message is due to the fact that we need more nodes on the correct chain and also the network is still seem to solving the current block!

KGW Kicks in on the exact forking point and starts to first use of KGW on the next , it's quite simultaneous.

Exactly the same problem... is it safe to withdraw coins while as described above the wallet still says syncing with 0 hours?

the mining will be better.

Can someone give a proper, up-to-date conf file with nodes? All I get is "No block source available....10 weeks behind".

I went looking for block chain explorers for Astrocoin.

Found 2 but they are out of date on old data.


http://altexplorer.net/

AstroCoin   ASR   17533


and,


http://cryptexplorer.com/chain/AstroCoin

Block   
17519

Well nearly there,

It is about 3.30 am here in Australia.

I started the client again after getting the new blockchain zip.

It was very fast in getting the block chain.

My ASR from the pool was in there as well.

I watched the debug window and the coinbase.info ASR pool info window.

I was watching the block chain numbers.

The client said block 20015

The pool info page said block 20016

When that block was done, the client showed it first by changing to 20016 and then the webpage changed to 20017 a few seconds later.

I tested a withdrawal from coinbase.info/astrocoin.

I got those ASR a few seconds later.

BUT.

The wallet still says Wallet (out of sync) and there are 0 hours behind.

So, for all intents and purposes, I seem to be on the correct blockchain.

I only had 1 node line in the astrocoin.conf file.

addnode=astrocoin.no-ip.biz

The only thing I do not understand is why the (out of sync) message remains.

Perhaps it needs more than one node for that to be gone.

Can anyone enlighten us there?

Wallet Synced!

21:28:25

{
"version" : 90000,
"protocolversion" : 70002,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 20007,
"timeoffset" : 0,
"connections" : 2,
"proxy" : "",
"difficulty" : 2.43826461,
"testnet" : false,
"keypoololdest" : 1395331002,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00001000,
"errors" : ""
}


-------------------------------------------

{
"blocks" : 20007,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 2.43826461,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 75477327,
"pooledtx" : 0,
"testnet" : false
}

Peers
-------



[
{
"addr" : "85.25.197.186:22477",
"services" : "00000003",
"lastsend" : 1395331371,
"lastrecv" : 1395331357,
"bytessent" : 6530,
"bytesrecv" : 142609,
"blocksrequested" : 0,
"conntime" : 1395331066,
"version" : 70002,
"subver" : "/Satoshi:0.9.0/",
"inbound" : false,
"startingheight" : 20007,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "221.210.16.66:9333",
"services" : "00000001",
"lastsend" : 1395331362,
"lastrecv" : 1395331316,
"bytessent" : 8247,
"bytesrecv" : 250415,
"blocksrequested" : 0,
"conntime" : 1395331126,
"version" : 70002,
"subver" : "/Satoshi:0.8.5.1/",
"inbound" : false,
"startingheight" : 534040,
"banscore" : 0
},
{
"addr" : "85.199.4.228:9333",
"services" : "00000003",
"lastsend" : 1395331352,
"lastrecv" : 1395331371,
"bytessent" : 2695,
"bytesrecv" : 109412,
"blocksrequested" : 0,
"conntime" : 1395331155,
"version" : 70002,
"subver" : "/Satoshi:0.8.6.1/",
"inbound" : false,
"startingheight" : 534930,
"banscore" : 0
},
{
"addr" : "119.246.18.143:9333",
"services" : "00000001",
"lastsend" : 1395331372,
"lastrecv" : 1395331354,
"bytessent" : 2262,
"bytesrecv" : 96416,
"blocksrequested" : 0,
"conntime" : 1395331161,
"version" : 70002,
"subver" : "/Satoshi:0.8.5.1/",
"inbound" : false,
"startingheight" : 534930,
"banscore" : 0
},
{
"addr" : "109.26.29.213:9333",
"services" : "00000003",
"lastsend" : 1395331357,
"lastrecv" : 1395331369,
"bytessent" : 2329,
"bytesrecv" : 104076,
"blocksrequested" : 0,
"conntime" : 1395331162,
"version" : 70002,
"subver" : "/Satoshi:0.8.6.1/",
"inbound" : false,
"startingheight" : 534930,
"banscore" : 0
},
{
"addr" : "96.248.105.24:9333",
"services" : "00000003",
"lastsend" : 1395331371,
"lastrecv" : 1395331369,
"bytessent" : 1437,
"bytesrecv" : 96547,
"blocksrequested" : 0,
"conntime" : 1395331294,
"version" : 70002,
"subver" : "/Satoshi:0.8.6.2/",
"inbound" : false,
"startingheight" : 534932,
"banscore" : 0
},
{
"addr" : "70.70.44.232:9333",
"services" : "00000003",
"lastsend" : 1395331361,
"lastrecv" : 1395331371,
"bytessent" : 337,
"bytesrecv" : 75724,
"blocksrequested" : 0,
"conntime" : 1395331323,
"version" : 70002,
"subver" : "/Satoshi:0.8.6.1/",
"inbound" : false,
"startingheight" : 534934,
"banscore" : 0
}
]

Setting up a node! Await!

Reply from our very helpful friends at coin-base.info!

I've dowloaded and installed this chain. It looks like they may have forked at the right point, which is good. Bad news is that none of the peers my client is trying to connect to seem to be on this chain - the archive includes peers.dat so I was hoping I'd quickly be able to find such a peer. In addition, astrocoin.no-ip.biz does not appear to be up.

So right now I'm "synced" to block 19882 (minted a little over an hour ago), but since I have no connections to suitable peers I'm effectively stuck in limbo. The chain will never extend. If someone connects to me now and syncs to the chain I have, then starts mining, they will create an additional fork!

I'm not sure how people are withdrawing their coins from the pool, if there's no other peers on the right chain... maybe coin-base is on its own (effectively private) chain? We really need the IP of coin-base's client to properly join the network.

News on coin-base:

I realy like the coin. I like the way it's mined and the price is constantly rising. Please fix it. I will give 1 ASR for the start (when the wallet sinc).

If nothing happens soon there is another option - delete the db and sync from scratch. New clients will reject any blocks after 17520 that were generated by an old client, but will be able to mine from that point, so long as they have at least one active peer. This will kick start the new fork. Note that doing this will negate all of the blocks found by coin-base so it's really a last resort thing.

To get onto their chain all we need is for ONE of us to connect to coin-base's astrocoin client and download the block chain... but coin-base.info is not listening on port 14333. Their client is either using a different P2P port, or another IP. Also heed my warning about private forks if they did not update prior to block 17520; if their chain is to be adopted as the official one but they didn't upgrade before 17520 then the fork point will need to be updated in the client (ie, another release)

Why is it so hard for coin-base.info to cooperate and help get this coin on the track!

not mining right now, since coin-base.info's message is "I disable temporaly the payout. A few users have problems. I search the error." Anyone know if its safe to mine there? They have most of the net hash.

Right, I just realised that I misread the dates of the block dump I posted - so those blocks were downloaded before I updated the client.

At this point in time anyone past block 17520 on the "old" chain like myself is going to reject any blocks found by new clients, even though we're both running the same new version. This is similar to what happened with Krugercoin: everyone forked to their own private chains when they upgraded, so the clients ended up rejecting blocks and banning each other.

It's important to check that coin-base.info upgraded prior to the fork - if they did not, they will have extended the chain past block 17520 using the old difficulty retarget algorithm, which new clients will reject, because they're expecting KGW at that point. This means that anyone with a block count below 17520 will never be able to sync past it, even if they delete the blockchain and restart.

All old nodes are either no longer online or not on the new wallet which is why your wallet doesn't update past 17533.  I sent an email to coin-base.info asking if they would be kind enough to set up a public node to connect to since they seem to be the only pool mining on the correct blockchain right now.

Same here => 17533
Deleted everything but the wallet and syncing again from the beginning, also tried with -rescan and still waiting on 17533

Wallet sync problem. Stuck @ block 17533.

my conf:

listen=1
daemon=1
server=1
rpcuser=username
rpcpassword=password
rpcport=15332
port=14333
rpcconnect=127.0.0.1
addnode=astrocoin.no-ip.biz
addnode=blockxplorer.com
addnode=107.22.238.207
addnode=24.184.100.134
addnode=198.245.54.21
addnode=213.127.238.164

Should KGW change the difficulty at the fork point immediately or can it take several blocks before it starts the per-block adjustments? Went past the fork point about 10 hours ago, but difficulty hasn't changed...

15-Mar-2014 07:33:17 height: 17517  difficulty: 11.44455344  tx: 2
15-Mar-2014 20:36:48 height: 17518  difficulty: 11.44455344  tx: 3
16-Mar-2014 09:06:40 height: 17519  difficulty: 11.44455344  tx: 2
16-Mar-2014 16:27:27 height: 17520  difficulty: 11.44455344  tx: 10  <-- fork point
17-Mar-2014 00:26:08 height: 17521  difficulty: 11.44455344  tx: 2  <-- first use of KGW?
17-Mar-2014 00:51:50 height: 17522  difficulty: 11.44455344  tx: 1
18-Mar-2014 16:52:33 height: 17523  difficulty: 11.44455344  tx: 5
18-Mar-2014 18:05:05 height: 17524  difficulty: 11.44455344  tx: 1
18-Mar-2014 19:08:55 height: 17525  difficulty: 11.44455344  tx: 1
18-Mar-2014 21:33:20 height: 17526  difficulty: 11.44455344  tx: 2
18-Mar-2014 21:34:57 height: 17527  difficulty: 11.44455344  tx: 1
18-Mar-2014 22:14:02 height: 17528  difficulty: 11.44455344  tx: 1
18-Mar-2014 22:49:12 height: 17529  difficulty: 11.44455344  tx: 1