block stuck at 166142 #65
Comments
|
If you are running version 2.0 or later of the software, that's good and as intended. The blockchain just forked today. Blocks are coming in very slowly as the pools are getting their code fixed and people are updating their software. At the time of this post current top block is only 166145. |
|
So the network is fully functional right now without the announcement? |
|
Tentatively, we were still experiencing timestamp issues until only a couple hours ago. We finally determined it was an issue in the pool code and not the daemon, but it was unclear initially. We still need to update seed nodes and the block explorer. Today was spent working with pool owners to make sure the network can still make coins. We'll roll things out in full scale tomorrow. |
|
The network now has a limited number of nodes running the V4 hardfork! The final roll-out is not ready yet (block explorer and seed nodes still outstanding), but if you want to start mining now, you can. There are 3 pools currently known to be up to date: the official pool (http://intensecoin.com/pool), Venthos' pool (https://itnspool.net/) or ddvs1' pool (https://intense.west-pool.org/#/dashboard). Your old wallet addresses still work fine for mining. We will release a comprehensive upgrade document for your old wallets, full release binaries (no GUI is posted yet), and update the block explorer/seed nodes tomorrow. The purpose of this message is to give you a status update and allow you to resume mining if you wish. You must use a monerov7/cryptonight-variant-1 compliant miner. NOTE that none of these pools have seen a block mature yet, so payments could be unreliable initially! Release CLI binaries are available for Linux, Mac and Windows As I mentioned seed nodes are not updated yet, you may consider running your local node with |
|
Hello I tried with --add-priority-node pool.intensecoin.com:48772 --add-priority-node 62.48.164.60:48772 --add-priority-node 5.249.27.162:48772 --add-priority-node 140.82.9.90:48772 But it showed this: Blockchain was imported from https://github.com/valiant1x/intensecoin/releases/tag/v1.45-snap |
|
Sorry that's my error, please remove the add priority node line that
includes a domain. Add priority node only accepts IPs. I have edited my
above answer to reflect that but you must have used my response before I
changed it.
…On Thu, Apr 19, 2018 at 1:53 AM KhmerRun ***@***.***> wrote:
Hello I tried with --add-priority-node pool.intensecoin.com:48772
--add-priority-node 62.48.164.60:48772 --add-priority-node
5.249.27.162:48772 --add-priority-node 140.82.9.90:48772
But it showed this:
2018-04-19 05:56:29.435 7fea22aae740 INFO global src/daemon/main.cpp:279
Intense Coin 'Belaya' (v2.0.0.0-release)
2018-04-19 05:56:29.436 7fea22aae740 INFO global src/daemon/protocol.h:55
Initializing cryptonote protocol...
2018-04-19 05:56:29.436 7fea22aae740 INFO global src/daemon/protocol.h:60
Cryptonote protocol initialized OK
2018-04-19 05:56:29.436 7fea22aae740 INFO global src/daemon/p2p.h:63
Initializing p2p server...
2018-04-19 05:56:29.438 7fea22aae740 INFO global src/daemon/core.h:89
Deinitializing core...
2018-04-19 05:56:29.441 7fea22aae740 ERROR daemon src/daemon/core.h:94
Failed to deinitialize core...
2018-04-19 05:56:29.441 7fea22aae740 INFO global src/daemon/protocol.h:77
Stopping cryptonote protocol...
2018-04-19 05:56:29.441 7fea22aae740 INFO global src/daemon/protocol.h:81
Cryptonote protocol stopped successfully
2018-04-19 05:56:29.441 7fea22aae740 ERROR daemon src/daemon/main.cpp:287
Exception in main! Failed to initialize p2p server.
Blockchain was imported from
https://github.com/valiant1x/intensecoin/releases/tag/v1.45-snap
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#65 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AcaMTeYPQi5kakVX4fADyX3PF5XweSLsks5tqCZpgaJpZM4Ta9Sv>
.
|
|
blockchain sync OK now. Thank you. |
|
As I have seen above, the block height shall be 166XXX but from priority node 173402 now: 2018-04-19 06:57:17.321 [P2P6] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [140.82.9.90:48772 OUT] Sync data returned a new top block candidate: 165031 -> 166158 [Your node is 1127 blocks (1 days) behind] |
|
I compiled the latest daemon, deleted local blockchain data so I could start sync from scratch. 2018-04-19 07:52:55.574 7f0cfaa03740 WARN blockchain.db.lmdb src/blockchain_db/lmdb/db_lmdb.cpp:72 Error attempting to retrieve a hard fork version at height 0 from the db: MDB_NOTFOUND: No matching key/data pair found ote_protocol_handler.inl:1154 [24.158.130.107:48772 OUT] Synced 1801/173419 EDIT: Currently at height 151992 on v3 of blockchain. https://itns.pool.gntl.co.uk is heading in right direction. |
|
@KhmerRun your height is not 173402, that is the highest height reported by v3 fork clients. your daemon is not accepting those blocks so don't worry. @BKdilse looks good. When your pool is up and running on V4 please message me on Discord @valiant and let me know so I can update the announcement indicating your pool is compliant. |
|
@valiant1x my daemon appears stuck on height 166266. Any ideas? |
|
@BKdilse when launching the daemon please use --add-exclusive-node instead of --add-priority-node: |
|
@valiant1x That's better, I did try exclusive, but only 1 node. Now it's syncing. I'll ping you on Discord once complete. Thanks |
|
daemon is now working, but my miners are having "low difficulty share" errors |
|
Make sure to use a miner compatible with monerov7 pow algo and that it is indeed using it, and not the former algorithm. |
|
thanks! all working smoothly now |
|
I'm up and running, and have tested with 1 miner |
anyone can help me?
The text was updated successfully, but these errors were encountered: