Topic: [ANN] INTENSE COIN - Blockchain backed decentralized VPN - Hybrid PoW - page 22. (Read 235824 times)

Have we any economy plan for vpn pricing?
So, If we ll have 1000 users of vpn for 2$ mounth - it is 2000$ only.
It will not realy affects on itns price.
Am I wrong? Have you some calc of future price?

maybe not fully sync. there are bugs. please wait for GUI 2.0.2.

Check our 1st of May post in our website.

All speaking about coins and wallet synchronisation. But what with the core project? Does decentralized VPN available already? Could you share your experience how it works?

Dear Intense Family,

I know everyone is having some issues with sync, we are working on a new release to solve these and it will be pushed in the next days.

Meanwhile i am running this 15,000 ITNS giveaway on twitter, if anyone would like to enter just RT the following link:

https://twitter.com/c1sc0r1b31r0/status/991730714986074112

The winner will be selected random by the 20th of May at 9pm UTC.

Good luck and thank you for all the support

Hello, thank you for confirming, I tried number of ways, even the blog post way you mentioned:

2018-05-02 16:39:23.685 [P2P7]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:305     [140.82.9.90:48772 OUT] Sync data returned a new top block candidate: 173376 -> 175052 [Your node is 1676 blocks (2 days) behind]
SYNCHRONIZATION started
2018-05-02 16:40:05.661 [P2P9]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:305     [62.48.164.60:48772 OUT] Sync data returned a new top block candidate: 173376 -> 175053 [Your node is 1677 blocks (2 days) behind]
SYNCHRONIZATION started


It does not seem to work for myself as each time the amount of blogs behind increases, its suppose to decrease?

Sorry to hear that you are having an issue. I would recommend rescanning your balance in the new wallet. It can be found in “settings”. If this does not work, make sure that you have imported the correct wallet. If you are in need of some extensive troubleshooting, please reach out to us on Discord or Telegram.

To those having issues with syncing, it is a known issue that we are facing. Some nodes still running V3 are causing the daemon to not sync properly. Make sure you have the exclusive nodes in our update when opening your wallet. We are working on a new wallet that has these properties already integrated.

Also... my wallet showed my balance (up to the date it was able to synch) for a while but when I re-started it... it no longer does.

I tried this... so far it doesn't seem to be working... but I will let it run for a while and check back in.

Well. So far having issues synching. It goes for a while, stops... then I closed wallet & daemon and synch has started all over from scratch.

https://github.com/valiant1x/intensecoinwallet/releases/

Looks like 2.0.1 GUI is available now -- great =)

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

What about a mac-version of wallet 2.0.1? When it s planned to release?

THE NEW ITNS FEATURE LOOKS AWESOME    


;

thumb up +1 

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

thumb up +1

thumb up