Hi everyone..anyone having an issues with the latest wallet? Mine hasnt received its last 4 mining payments. It just stopped for no reason about a day ago. Im using the latest gui wallet, but started to download the CLI wallet to see if that would make a difference if i had a local copy of the blockchain.
Everything looks fine for my GUI wallet  Have you checked if your letheand.exe is still in the folder? Not deleted by an antivirus software? I had that in the past and the GUI was not complaining :p Thanks for the response. yeah its there im looking at it now.. i just started it up and its syncing the blockchain UPDATE - for reasons unknown, all payments hit the wallet 1 to 3 days after payment was sent. Very odd.. but it finally came in. Hi, sorry this is our fault! The default remote node that we maintain (sync.lethean.io) was stuck for a bit. I anticipated quick resolution so did not make any announcement - but unfortunately resolution took 24-36 hours. We try to monitor the sync node closely and intervene as soon as we notice any issues, as we understand it is a backbone of most peoples' usage. Thanks for your patience. Also, sorry I am not very active here at all. If you would like to hear more from me, join our Discord  By the way, if you have not seen our new website, check it out. I am so proud of Casey (@Thepigwee) for putting this together! We finally have a modern and usable place to call home!  Thanks for the reply, payments still seem delayed. One went out around 4 hours ago but it hasnt hit the wallet yet. As long as it gets there eventually i dont care as im a long term HOLD. The new website is really nice, looked at it this morning. The only risk i see with Lethean now is competition. Lethean needs to hire someone to really market the VPN and crypto used for the VPN. All you guys need to do is take 1/10th of the worlds VPN usage from other vendors to be a huge success. Ive worked in corporate IT for 20 years, i set up SSL VPNs all the time and am very familiar with the technology. You guys have something great here, but it must be marketed really hard to be a success. That's really odd. I am not aware of any TX or block delays. The mempool is empty according to explorer.lethean.io.. What is the TX ID? Did you check it in the explorer? I completely agree, we need to market strategically and more aggressively. This is one of our primary goals moving forward - increasing use of the software. The website is one small step toward broader goals to improve user experience and increase user engagement. |
|
|
|
Hi everyone..anyone having an issues with the latest wallet? Mine hasnt received its last 4 mining payments. It just stopped for no reason about a day ago. Im using the latest gui wallet, but started to download the CLI wallet to see if that would make a difference if i had a local copy of the blockchain.
Everything looks fine for my GUI wallet Have you checked if your letheand.exe is still in the folder? Not deleted by an antivirus software? I had that in the past and the GUI was not complaining :p Thanks for the response. yeah its there im looking at it now.. i just started it up and its syncing the blockchain UPDATE - for reasons unknown, all payments hit the wallet 1 to 3 days after payment was sent. Very odd.. but it finally came in. Hi, sorry this is our fault! The default remote node that we maintain (sync.lethean.io) was stuck for a bit. I anticipated quick resolution so did not make any announcement - but unfortunately resolution took 24-36 hours. We try to monitor the sync node closely and intervene as soon as we notice any issues, as we understand it is a backbone of most peoples' usage. Thanks for your patience. Also, sorry I am not very active here at all. If you would like to hear more from me, join our Discord By the way, if you have not seen our new website, check it out. I am so proud of Casey (@Thepigwee) for putting this together! We finally have a modern and usable place to call home! |
|
|
|
Did the whole Lethean network just die? My local daemon shows the total network hashrate as 620 H/s. I thought it's a problem on my side, went to check other larger pools and they're all dead - no one seems to be finding any blocks. What's going on? I'm stuck at 296645. The official pool is somewhat close as well. And hashvault.pro is at 298288. Did the chain split? Tonight, over the course of several hundred blocks, it would appear some manipulation occurred to drop difficulty and make a bunch of low difficulty (essentially "free") blocks. We are looking into the issue to determine the exact cause. At this time it is unknown how the exploit occurred. The good news is that daemons are automatically properly re-syncing back to the main chain before any of the block manipulation started (block 296225). However, any daemon mining blocks (eg. pool daemons) will require a restart before they will work correctly. To that end, Venthos and I have restarted our pool daemons and are attempting to get the network moving again. I am off to bed now but will resume analysis of the issue first thing in the morning to figure out what went wrong and ensure the issue does not recur. I will update you as we know more. |
|
|
|
Hey, finally updated the original post! Sorry for the delay, busy coding proxy and VPN I am sure there are some mistakes, so let me know if anything needs to be changed. Updated Lethean sig in case anyone else wants to represent  [center]
[color=#0a1f36]▀[color=#0e2c4b]▀[color=#123960]▀[color=#164576]▀[color=#1a528b]▀[color=#1e5fa0]▀[color=#226bb6]▀[color=#2678cb]▀ [url=https://lethean.io][color=#1e5fa0]★★★[/color][b][color=#1e5fa0] LETHEAN[/b] [color=#1e5fa0] ★★★ [/color] [/url] ▀[/color]▀[/color]▀[/color]▀[/color]▀[/color]▀[/color]▀[/color]▀[/color]
[color=#123861]┊┈ ┊┈ ┊┈ ┊┈ ┊[/color][color=#1e5fa0] [b]THE SAFEST WAY TO BE ONLINE: BLOCKCHAIN VPN[/b][color=#123861]┊┈ ┊┈ ┊┈ ┊┈ ┊
█ █ █ █ █ █ [color=#1798d6][/color] [url=https://medium.com/@letheanVPN][font=Arial][b][color=#122874]Medium[/color][/b][/font][/url] [color=#1798d6]◉[/color] [url=https://twitter.com/letheanVPN][font=Arial][b][color=#122874]Twitter[/color][/b][/font][/url] [color=#1798d6]◉[/color] [url=https://discord.gg/f3XQgA3][font=Arial][b][color=#122874]Discord[/color][/b][/font][/url] [color=#1798d6]◉[/color] [url=https://www.reddit.com/r/Lethean/][font=Arial][b][color=#122874]Reddit[/color][/b][/font][/url] [color=#1798d6]◉[/color] [url=https://t.me/letheanVPN][font=Arial][b][color=#122874]Telegram[/color][/b][/font][/url][color=#1798d6] ◉ [/color][url=https://www.facebook.com/lethean.io/][font=Arial][b][color=#122874]Facebook[/color][/b][/font][/url] [color=#1798d6] ◉ [/color] [url=https://lethean.io/vpn-whitepaper/][font=Arial][b][color=#122874]Whitepaper[/color][/b][/font][/url] █ █ █ █ █ [/center] |
|
|
|
Great news! Any guide on how to transit from ITNS old wallet to new LTHN wallet safely?
If your itns wallet was up to date, you don't need to do anything, just run the LTHN one. I don't trust |automatic| stuff and i cannot find the actual wallet file either. So without backup I prefer having a simple 1-2-3 procedure. The new wallet uses the same data directory as the old one, which is why he said you don't need to do anything. There are no automatic processes occurring yet. We will be transitioning to a Lethean data directory in the near future. For now, nothing has changed. Your wallet is still stored in My Documents > intensecoin > wallets. |
|
|
|
Version 2.0.2 beta release is available for Windows now!
2.0.2 fixes sync issues and adds a new feature to automatically import pre-rebase wallets using intense-wallet-cli. Use the commands --wallet-file <old.wallet> or --upgrade-legacy <old.wallet>
--upgrade-legacy only upgrades the file and exits, while --wallet-file loads the wallet after upgrading.
The new feature and 2.0.2 release will be in open beta for a short while until we bump it to an official release. I expect linux and mac binaries to be available tomorrow. Please DM me on our Discord which is the easiest way to get a hold of me directly, or post on our GitHub issues page with any problems.
|
|
|
|
The daemon exploded when it hit block 167k. The official pool was rolled back 400 blocks and is mining again. I'll try to update our Discord announcement post as other pool owners get their pools updated to fix the broken daemons, but in the meantime, the only pool that you can mine is http://intensecoin.com/pool . For more information, see https://github.com/valiant1x/intensecoin/issues/67#issuecomment-382936780It looks like the network is totally fubar - no block found on the official pool in over an hour and the hashvault pool also reporting effort on the current block exceeding 1300%. Well, we were warned to mine at our own risk...  Also, the instructions I was given earlier to use the --add-priority-node switches to sync the daemon didn't work; I had to use --add-exclusive-node instead, as reported by @YaStaer. Once synced, the balance from my 1.4.2 wallet showed up, but not the most recent mining payments from today. So, my recommendation - worth price paid - is to stop mining until things get well and truly sorted out. Apologies for the headaches, Magic. Thanks for your patience. |
|
|
|
no pool is working properly ... i dont have even pending ballance on any pool ...
Pending balances will lag more right now because all pools are using the full 60 block maturity time since things are still a bit uncertain. That means your pending balance will always be 60 blocks behind (about 2 hours). At least that's how it worked with pre-Snipa22-based pool software, assuming the new pool software works the same. |
|
|
|
RE pools - Payments appear to be working as expected. The reddit guide is still 100% valid The blockchain should automatically reorganize. It will definitely happen when the v4 chain exceeds the v3 chain. If your v3 (pre-fork) chain was synced to be longer than the current v4 chain, and you're having troubles syncing the current v4 chain, use `intense-blockchain-import --pop-blocks 7500` to manually discard 7500 blocks from your chain. |
|
|
|
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: https://github.com/valiant1x/intensecoin/releases/tag/v2.0.0As I mentioned seed nodes are not updated yet, you may consider running your local node with `--add-priority-node 140.82.9.90: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` to make syncing more reliable. |
|
|
|
Don't be such a Negative Nancy. Looking at the current development status, it doesn't look so bleak to me. The devs are open and honest and share their development status, which is a lot more than you can say for lots of other projects. Furthermore, ITNS has a plan and a vision and they're creating something actually new and useful and unique. Yeah, that does take time to do right. The devs are on track according to the timeline of the roadmap.
I'm mining/hodling ITNS since 09/2017. WHY ON EARTH would I (or anyone really) leave just before things finally about to happen? This is beyond me... What I've done personally in the last 2-3 weeks I was buying 4 times the amount I've been originally hodling - under 60 sats. Yes, that investment is at a tiny bit of loss right now, big deal, I didn't get the best price possible, but I didn't want to miss out lol. Do you guys actually read the updates posted on the site? It's not simply a project anymore, they're becoming a legal entity. And like that, an estabilished brand and company. Also VPN is on the way. So I you leave I wish you the best but the jokes on you. Appreciate your votes of support and confidence guys, these are the types of posts that keep us going Excitement in the team is growing as we draw closer to release of our products!! |
|
|
|
As mentioned in the main ITNS ANN thread (looks like SlowGrowth forgot to cross-post here), those that were missed for the fact that Slack display names were not properly read have been re-evaluated. According to our re-evaluation of the 446 people that were excluded from the original airdrop for the reason of not finding their Slack/Discord membership information, 95 of these users were actually qualified to receive payment. Please see the new tab in the airdrop sheet here, labeled Airdrop RECHECK. We are giving the community 48 hours to double-check this to verify that the entries are correct as re-checked. If there is an issue, please DM @SlowGrowth#2620 on Discord. After that process is complete, we will issue the promised 1k ITNS reconciliation payments to those missed originally and qualifying according to this form (see column should_be_paid). Looks okay this time. thanks. Thanks for your patience and understanding everyone. The payments were sent in TXs: 5491faa0499b7c19465a384ec8718b17afa19200c91334fd8e620af2efb29d1f
2a39b519ae42e2e63c2880ad0c2d2bf88cc371e364312c953a092c20d8c24151
c7ed1df1178b4431fd3ecea6aa422dff806813396285f908ff476d4b68aef383
a2f71e1285319026bf041eb186486b8d852b88228acb0c8be3469ba867aec737
|
|
|
|
I think now half of the participants will have FB LIKE NOT VALIDATED  Just as in the original assessment of airdrop participants, we did not exclude users that failed FB like validation since most people did not have proper privacy settings and we did not warn users ahead of time. |
|
|
|
i didnt open my wallet for 2 months and now when i try i put my password i get WAITING FOR PEER CONNECTIONS TO OPEN WALLET . it stay stuck on that !
First download new version of wallet  Is this mandatory? My old version is working fine. Depends on how old his wallet version is! If it's so old that it is hardforked, yes, it will fail to connect. |
|
|
|
Good morning everyone,
I would like to say that after some thought our team decided to giveaway a consolation reward of 1k Intense to all those that missed the airdrop due to slack username issue.
I hope that everyone can accept this as a gesture of goodwill, and also accept my apologies for the issues experienced.
Have a great weekend,
Francisco
Those that were missed for the fact that Slack display names were not properly read have been re-evaluated. According to our re-evaluation of the 446 people that were excluded from the original airdrop for the reason of not finding their Slack/Discord membership information, 95 of these users were actually qualified to receive payment. Please see the new tab in the airdrop sheet here, labeled Airdrop RECHECK. We are giving the community 48 hours to double-check this to verify that the entries are correct as re-checked. If there is an issue, please DM @SlowGrowth#2620 on Discord. After that process is complete, we will issue the promised 1k ITNS reconciliation payments to those missed originally and qualifying according to this form (see column should_be_paid). |
|
|
|
As mentioned in the main ITNS ANN thread (looks like SlowGrowth forgot to cross-post here), those that were missed for the fact that Slack display names were not properly read have been re-evaluated. According to our re-evaluation of the 446 people that were excluded from the original airdrop for the reason of not finding their Slack/Discord membership information, 95 of these users were actually qualified to receive payment. Please see the new tab in the airdrop sheet here, labeled Airdrop RECHECK. We are giving the community 48 hours to double-check this to verify that the entries are correct as re-checked. If there is an issue, please DM @SlowGrowth#2620 on Discord. After that process is complete, we will issue the promised 1k ITNS reconciliation payments to those missed originally and qualifying according to this form (see column should_be_paid). |
|
|
|
Hi everyone, since there has been some doubt expressed about the devs 'dumping' the premine, we devised a mechanism that will allow you to verify our continued ownership and responsible stewardship of the funds. Previously we had some reservations about doing this since screenshots can be easily forged, but an astute user pointed out we could circumvent the untraceability of the protocol by exposing the view keys to a wallet. Of course, these measures are only necessary since CryptoNote based coins do not allow easy traceability of the blockchain as Bitcoin does. To prove these funds are intact and recent, I moved all of the dev funds to an address and am sharing the private view key, which will allow you to view incoming transactions. You can see that nearly 123,000,000 coins arrived to this wallet yesterday, around block 140400. Of course, the amount is less than our originally allocated 150,000,000, because we have paid out various airdrops and core team members since the coin's inception on August 15, 2017. All team members are paid out once per month on a 24 month agreement. You will need to use the rebase/beta wallet ( version 1.44.1 or later). Instructions: 1. Use the intense-wallet-cli to generate a view only wallet: ./intense-wallet-cli --generate-from-view-key devfunds 2. Use the following address and private view key: [wallet iz53uS]: address
iz53uSWTQq7fjGsqSTCSBwcjQjsZh8LeR48iLEzhAwqNFLaAneZsXoGW6uFC9NRKTf8hsQok7DxTD8yNUh36hFZX1X2RJpi3h
[wallet iz53uS]: viewkey
secret: d2148b99e2bcc8cc44cb3b558f52d215294cca849eb2670aae9fab4584002308
When prompted for a height to sync from, enter 140400 or 03/06/2018 to save yourself some time. Entering 0 is not a problem but it will take longer to sync. For the skeptical users, hopefully this helps solidify some trust and faith in our team. We're in this for the long haul. We have never and will never lie to you, and we are very transparent about all of our developments and plans. BTW, regarding airdrop concession payouts, give me a couple days. We are taking it nice and slow to avoid another mistake! Hindsight is 20/20 |
|
|
|
By the way, what you have extracted as my "username" is nowhere in my profile (can not understand where did you find such information!!) and when you search in slack directory with the "username" you have extracted, it finds zero results. However if you search the directory with the display name (the @name I inserted in the airdrop form) which is the proper username in Slack nowadays, it gives the proper results. I can not write it clearer than this, i believe, so am really sorry if you guys cannot understand.
Sounds like a good (and the only fair) solution to me. The IntenseCoin guys needs to re-verify all those that haven't received an airdrop because of a Slack username issue and compare the submitted @username with what's shown in that "Slack Directory". I'm not on Slack, but I guess this is some form of follower list. Finally send out the missing airdrops. I checked the airdrop form. It asked for your slack username. It specifically said username. Screenshot below. 565 people were paid and used the proper information requested by the form. To those that incorrectly filled out the form, I'm sorry, that stinks, but the payments were already made. 2.5million ITNS was allocated to this airdrop and was distributed among the properly validated submissions.  |
|
|
|
|
Show Posts
