e6ug
|
|
May 01, 2018, 06:07:32 PM |
|
I have been with intense for quite sometime now. Followed every move they make and development they are going. Intense is not a scam coin. Project is very solid and roadmap is feasible. I tell you that before this 2nd quarter ends. You'll see big updates from the devs.
It maybe so. But what I see - everything that is connected with pallas has some problems. His XCN was hacked with 260 millions of coins, no normal exchange - only chineese/thai shady ones and no willingness to get to normal exchange or at least that stocks one. And this is after 4 years of "development"? Here with Intense also "hackers hackers" everywhere. Pallas the legendary member with perfect trust? You need to gtfo with your silly accusations! Pallas has done nothing but good for the crypto community, what have you done?
|
|
|
|
MrMoloch
Newbie
Offline
Activity: 7
Merit: 0
|
|
May 01, 2018, 06:08:58 PM |
|
Hi! Why do I sometimes have full synchronization, then 174372 -> 179096
|
|
|
|
wtfpdf
Newbie
Offline
Activity: 48
Merit: 0
|
|
May 01, 2018, 06:24:03 PM |
|
Hi! Why do I sometimes have full synchronization, then 174372 -> 179096 you have to avoid your daemon communicate with v3 of nodes. use dedicated v4 nodes like this: intensecoind --add-exclusive-node 140.82.9.90:48772 --add-exclusive-node 62.48.164.60:48772 --add-exclusive-node 69.162.83.202:48772 --add-exclusive-node 5.249.27.162:48772 --add-exclusive-node 54.37.87.203:48772 and if possible, use the most recent version of daemon, i had a strange blockchain overload errors until I compiled a newest one from git repository a hour ago
|
|
|
|
MrMoloch
Newbie
Offline
Activity: 7
Merit: 0
|
|
May 01, 2018, 06:54:40 PM |
|
Hi! Why do I sometimes have full synchronization, then 174372 -> 179096 you have to avoid your daemon communicate with v3 of nodes. use dedicated v4 nodes like this: intensecoind --add-exclusive-node 140.82.9.90:48772 --add-exclusive-node 62.48.164.60:48772 --add-exclusive-node 69.162.83.202:48772 --add-exclusive-node 5.249.27.162:48772 --add-exclusive-node 54.37.87.203:48772 and if possible, use the most recent version of daemon, i had a strange blockchain overload errors until I compiled a newest one from git repository a hour ago thank you
|
|
|
|
dragonmike
|
|
May 01, 2018, 08:01:48 PM |
|
The daemon seems to sync 100 blocks every time you start it and then stop. At this rate I'm going to close and reopen it 500 times until I finally get the damn thing synced...
|
|
|
|
SlowGrowth
|
|
May 01, 2018, 08:16:09 PM |
|
The daemon seems to sync 100 blocks every time you start it and then stop. At this rate I'm going to close and reopen it 500 times until I finally get the damn thing synced... I apologize for all the issues users are facing with sync, we will release a new version 2.0.2 in the next few days to solve these issues. Thank you for your patience and support
|
|
|
|
mroctopus
Newbie
Offline
Activity: 174
Merit: 0
|
|
May 01, 2018, 08:48:35 PM |
|
The daemon seems to sync 100 blocks every time you start it and then stop. At this rate I'm going to close and reopen it 500 times until I finally get the damn thing synced... I apologize for all the issues users are facing with sync, we will release a new version 2.0.2 in the next few days to solve these issues. Thank you for your patience and support thumb up
|
|
|
|
lncm
Member
Offline
Activity: 388
Merit: 13
|
|
May 01, 2018, 09:11:42 PM |
|
My wallet is syncing fine.
I know it's monero devs fault, but GUI looks awful in HiDPI displays.
Previous wallet was much better.
|
|
|
|
Edwinc08
Newbie
Offline
Activity: 63
Merit: 0
|
|
May 01, 2018, 10:13:10 PM |
|
can anyone tell me where I can find the intense daemon in windows 10? I want to delete it and download it again. Thanks
|
|
|
|
ThePigwee
Member
Offline
Activity: 181
Merit: 46
Lethean COO
|
|
May 02, 2018, 01:42:26 AM |
|
can anyone tell me where I can find the intense daemon in windows 10? I want to delete it and download it again. Thanks The data is located ind C:\ProgramData\Intensecoin The folder should be called Imdb. If you delete that, it will delete the blockchain data.
|
|
|
|
|
xiaopihai
Member
Offline
Activity: 173
Merit: 13
|
|
May 02, 2018, 02:23:06 AM |
|
global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [62.48.164.60:48772 OUT] Sync data returned a new top block candidate: 172897 -> 174625 [Your node is 1728 blocks (2 days) behind]
|
|
|
|
qq34711
Newbie
Offline
Activity: 5
Merit: 0
|
|
May 02, 2018, 03:45:47 AM |
|
200+ ITNS of mine in the OFFICAL POOL had mysteriously disappeared ...
|
|
|
|
mroctopus
Newbie
Offline
Activity: 174
Merit: 0
|
|
May 02, 2018, 03:56:23 AM |
|
thumb up
|
|
|
|
hustmobile
Newbie
Offline
Activity: 7
Merit: 0
|
|
May 02, 2018, 04:02:31 AM |
|
thumb up thumb up +1
|
|
|
|
Alu_voin
Newbie
Offline
Activity: 38
Merit: 0
|
|
May 02, 2018, 05:56:09 AM |
|
Hello everybody! Today the synchronization of the wallet (GUI 2.0.1) has finally ended, but there is nothing to rejoice! On an old wallet (GUI 1.4.1) I have a balance: 45775.00, and in a new wallet (GUI 2.0.1): 58.00. What happened to my other coins (45517.00)? I lost my coins? How to solve the problem, the developers, please help. I thank everyone for their help! Below there is a link where I made a screenshot of the wallets. https://drive.google.com/open?id=1_oJ7MMv8y4Ag6bemJXzVrK0RbskpfMoG
|
|
|
|
readonly
Jr. Member
Offline
Activity: 238
Merit: 6
|
|
May 02, 2018, 06:19:59 AM |
|
thumb up thumb up +1 thumb up +1
|
LETHEAN (https://lethean.io/) ★ BLOCKCHAIN BACKED P2P VPN ★ VPN Whitepaper (https://lethean.io/vpn-whitepaper/)
|
|
|
|
jardine
|
|
May 02, 2018, 08:24:37 AM |
|
What about a mac-version of wallet 2.0.1? When it s planned to release?
|
|
|
|
dragonmike
|
|
May 02, 2018, 08:49:59 AM Last edit: May 02, 2018, 09:36:00 AM by dragonmike |
|
Using the parameters suggested on the intensecoin page above does revive the syncing somehow but the daemon stops after a few minutes so it still needs re-starting regularly. Hope the next version will be more stable!
EDIT: actually it stops loading blocks after 90 seconds. Only a restart will get it to sync again.
EDIT2: here's an extract of the daemon with set_log 1:
2018-05-02 09:34:08.174 [P2P3] WARN net.p2p src/p2p/net_node.inl:848 [54.37.87.203:48772 OUT] COMMAND_TIMED_SYNC Failed 2018-05-02 09:34:12.230 [P2P7] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [112.94.4.145:59291 INC] Sync data returned a new top block candidate: 171869 -> 179096 [Your node is 7227 blocks (10 days) behind] SYNCHRONIZATION started 2018-05-02 09:34:13.185 [P2P3] WARN net contrib/epee/include/net/levin_protocol_handler_async.h:475 [121.32.247.45:17116 INC] Signature mismatch, connection will be closed 2018-05-02 09:34:14.231 [P2P7] WARN net.p2p src/p2p/net_node.inl:1564 [0.0.0.0:0 OUT] back ping connect failed to 112.94.4.145:48772 2018-05-02 09:34:15.658 [P2P3] ERROR net.cn src/cryptonote_protocol/cryptonote_protocol_handler.inl:1063 [54.37.87.203:48772 OUT] transaction verification failed on NOTIFY_RESPONSE_GET_OBJECTS, tx_id = 7befd8327288da882e197fc9acaffa240ab744c5137050f5fa6036a874ef7c23, dropping connection 2018-05-02 09:34:15.757 [P2P0] ERROR net.cn src/cryptonote_protocol/cryptonote_protocol_handler.inl:1025 [159.89.249.113:48772 OUT] Got block with unknown parent which was not requested - querying block hashes 2018-05-02 09:34:17.021 [P2P0] ERROR net.cn src/cryptonote_protocol/cryptonote_protocol_handler.inl:1063 [159.89.249.113:48772 OUT] transaction verification failed on NOTIFY_RESPONSE_GET_OBJECTS, tx_id = 7befd8327288da882e197fc9acaffa240ab744c5137050f5fa6036a874ef7c23, dropping connection 2018-05-02 09:34:26.229 [P2P3] WARN net.p2p src/p2p/net_node.inl:1564 [0.0.0.0:0 OUT] back ping connect failed to 5.80.151.52:48772 2018-05-02 09:34:26.282 [P2P3] WARN net.p2p src/p2p/net_node.inl:1564 [0.0.0.0:0 OUT] back ping connect failed to 178.95.180.150:48772 2018-05-02 09:34:27.265 [P2P7] ERROR net.cn src/cryptonote_protocol/cryptonote_protocol_handler.inl:1063 [178.95.180.150:49240 INC] transaction verification failed on NOTIFY_RESPONSE_GET_OBJECTS, tx_id = 7befd8327288da882e197fc9acaffa240ab744c5137050f5fa6036a874ef7c23, dropping connection 2018-05-02 09:34:35.947 [P2P4] ERROR net.cn src/cryptonote_protocol/cryptonote_protocol_handler.inl:933 returned not all requested objects (context.m_requested_objects.size()=20), dropping connection 2018-05-02 09:34:36.003 [P2P3] ERROR net.cn src/cryptonote_protocol/cryptonote_protocol_handler.inl:1063 [140.82.9.90:48772 OUT] transaction verification failed on NOTIFY_RESPONSE_GET_OBJECTS, tx_id = 7befd8327288da882e197fc9acaffa240ab744c5137050f5fa6036a874ef7c23, dropping connection 2018-05-02 09:34:39.015 [P2P7] WARN net.p2p src/p2p/net_node.inl:1564 [0.0.0.0:0 OUT] back ping connect failed to 216.56.240.80:48772 2018-05-02 09:34:39.323 [P2P3] WARN net.p2p src/p2p/net_node.inl:1564 [0.0.0.0:0 OUT] back ping connect failed to 36.79.28.18:48772 2018-05-02 09:34:39.700 [P2P3] ERROR net.cn src/cryptonote_protocol/cryptonote_protocol_handler.inl:1025 [86.122.3.67:63732 INC] Got block with unknown parent which was not requested - querying block hashes 2018-05-02 09:34:44.196 [P2P9] ERROR net.cn src/cryptonote_protocol/cryptonote_protocol_handler.inl:1063 [140.82.9.90:48772 OUT] transaction verification failed on NOTIFY_RESPONSE_GET_OBJECTS, tx_id = 7befd8327288da882e197fc9acaffa240ab744c5137050f5fa6036a874ef7c23, dropping connection 2018-05-02 09:34:50.440 [P2P7] WARN net.p2p src/p2p/net_node.inl:1564 [0.0.0.0:0 OUT] back ping connect failed to 117.102.89.98:48772 2018-05-02 09:34:50.891 [P2P7] ERROR net.cn src/cryptonote_protocol/cryptonote_protocol_handler.inl:933 returned not all requested objects (context.m_requested_objects.size()=20), dropping connection 2018-05-02 09:34:51.040 [P2P4] ERROR net.cn src/cryptonote_protocol/cryptonote_protocol_handler.inl:933 returned not all requested objects (context.m_requested_objects.size()=20), dropping connection 2018-05-02 09:34:59.913 [P2P3] ERROR net.cn src/cryptonote_protocol/cryptonote_protocol_handler.inl:933 returned not all requested objects (context.m_requested_objects.size()=20), dropping connection 2018-05-02 09:35:03.841 [P2P9] ERROR net.cn src/cryptonote_protocol/cryptonote_protocol_handler.inl:1025 [86.122.3.67:63732 INC] Got block with unknown parent which was not requested - querying block hashes 2018-05-02 09:35:09.585 [P2P3] ERROR net contrib/epee/include/net/levin_protocol_handler_async.h:289 [54.37.87.203:48772 OUT] [levin_protocol] -->> start_outer_call failed 2018-05-02 09:35:09.586 [P2P3] WARN net.p2p src/p2p/net_node.inl:848 [54.37.87.203:48772 OUT] COMMAND_TIMED_SYNC Failed 2018-05-02 09:35:09.586 [P2P3] ERROR net contrib/epee/include/net/levin_protocol_handler_async.h:289 [62.48.164.60:48772 OUT] [levin_protocol] -->> start_outer_call failed 2018-05-02 09:35:09.587 [P2P3] WARN net.p2p src/p2p/net_node.inl:848 [62.48.164.60:48772 OUT] COMMAND_TIMED_SYNC Failed 2018-05-02 09:35:09.588 [P2P3] ERROR net contrib/epee/include/net/levin_protocol_handler_async.h:289 [140.82.9.90:48772 OUT] [levin_protocol] -->> start_outer_call failed 2018-05-02 09:35:09.588 [P2P3] WARN net.p2p src/p2p/net_node.inl:848 [140.82.9.90:48772 OUT] COMMAND_TIMED_SYNC Failed 2018-05-02 09:35:09.590 [P2P3] ERROR net contrib/epee/include/net/levin_protocol_handler_async.h:289 [159.89.249.113:48772 OUT] [levin_protocol] -->> start_outer_call failed 2018-05-02 09:35:09.591 [P2P3] WARN net.p2p src/p2p/net_node.inl:848 [159.89.249.113:48772 OUT] COMMAND_TIMED_SYNC Failed 2018-05-02 09:35:17.118 [P2P4] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:305 [140.82.9.90:48772 OUT] Sync data returned a new top block candidate: 171869 -> 174841 [Your node is 2972 blocks (4 days) behind] SYNCHRONIZATION started 2018-05-02 09:35:17.198 [P2P4] ERROR net.cn src/cryptonote_protocol/cryptonote_protocol_handler.inl:1025 [86.122.3.67:63732 INC] Got block with unknown parent which was not requested - querying block hashes
|
|
|
|
|